Re: [PATCH 3/6] Disable sfdump if there is no xrandr support.
Mathieu OTHACEHE <[email protected]> Sun, 27 Nov 2016 11:31:27 +0100
| Newsgroups | gmane.comp.window-managers.ratpoison.devel |
|---|---|
| Message-ID | <[email protected]> |
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