On Fri, 26 May 2017 14:34:30 +0200 Alexander Feldman <a...@llama.gs> wrote:
> I want to try working on support for HiDPI devices. Can you help a bit > with telling me about your development loop? I am an Emacs developer, > and I have the habit of: > > 1. edit sources > 2. compile > 3. run a binary to see my changes > > My question is how do you run "nested" wmaker, for example in a window, > so I don't have to restart the window manager every time. I usually run separate display. One way was already covered by Doug - by using Xephyr you can benefit on nested X sessions, but sometimes it is not enough. I was bumped on such situation during development of multi-screen features. Xephyr (AFAIK) doesn't support randr extensions and couple of virtual screens at the same time[1], so real X session to the rescue :) My simple workflow was as follows: 1. Prepare simple ~/.xinitrc only with one line: terminal emulator of choice 2. start new x session using startx command (i.e "startx -- :1") 3. Back to display :0 4. Do some hacking on the code, compile 5. go to the second display (ctrl+alt+f8 in my case) 7. execute binary in terminal, check how it works 8. exit (or simply ctrl-c on terminal) window manager, and back to first display 9. repeat steps 4-8 until result is satisfying :) HTH :) [1] https://superuser.com/questions/1179552 -- -^- _ something is grinding the emptiness: _ /O)_\// Meshuggah - New Millennium Cyanide Christ (_(|__(_(_) grf. Ophidian Trek -- -^- _ something is grinding the emptiness: _ /O)_\// Meshuggah - Dancers To A Discordant System (_(|__(_(_) grf. Ophidian Trek -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
