[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RP] [PATCH 3/6] Disable sfdump if there is no xrandr support.
|
From: |
Mathieu OTHACEHE |
|
Subject: |
Re: [RP] [PATCH 3/6] Disable sfdump if there is no xrandr support. |
|
Date: |
Sun, 27 Nov 2016 11:31:27 +0100 |
|
User-agent: |
mu4e 0.9.17; emacs 25.1.1 |
Hi,
> I think this is headed in the wrong direction. There is no reason to
> disable this command when we can easily deal with the single available
> screen.
Yes I agree, it is not a very good idea after all.
Maybe we could copy the old behaviour by mapping the Xrandr identifier
to an integer going from 0 to screen count.
For example,
Xrandr id -> Ratpoison id
0x47 0
0x48 1
0x49 2
Then we would use this ratpoison id to identify screens in sdump,
sselect and sfrestore commands.
Mathieu
[RP] [PATCH 2/6] Use xrandr output identifiers in sselect., Mathieu OTHACEHE, 2016/11/25
[RP] [PATCH 5/6] Kill gcc uninitialized warning, Mathieu OTHACEHE, 2016/11/25
[RP] [PATCH 4/6] Use xrandr output identifiers in srestore., Mathieu OTHACEHE, 2016/11/25
[RP] [PATCH 6/6] Update XRandr related documentation and man., Mathieu OTHACEHE, 2016/11/25