>>>>> "Dominik" == Dominik Vogt <fvwm-workers@fvwm.org> writes:
Dominik> On Fri, Jun 29, 2001 at 08:32:06AM -0400, Dan Espen wrote: ... >> I've only got one computer at home, this is difficult to debug without >> 2 machines. Dominik> You can either start a second X server and fvwm in an XNest Dominik> window: Dominik> $ exec Xnest -full -sync -name "Xnest :3" :3 Dominik> $ fvwm2 -d :3 -cmd "FvwmCpp $HOME/.fvwm/.fvwm2rc" Dominik> Or start a second X server: Dominik> $ exec xinit /bin/sleep 100000 -- :1 Dominik> $ fvwm2 -d :1 -cmd "FvwmCpp $HOME/.fvwm/.fvwm2rc" Dominik> Running fvwm in xnest is often easier to debug since you don't Dominik> need to switch screens, but moving the pointer out of the window Dominik> may generate unwanted events. VNC is another good choice. It's what I used to use occasionally for debugging fvwm, along with XMX (which also worked fairly well although sometimes that had bugs of it's own which interfered) and Xnest (and occasionally in conjunction with xmon/xscope, of course). It shouldn't have any problems with the pointer leaving the window since the vncviewer window is totally separate from the actual Xvnc X11 session. I felt that using the virtual terminals (under Linux or AIX 3.x) for debugging fvwm was rather difficult... Chuck -- Charles K. Hines <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Principal Scientist at ReQuest Technologies Inc (http://www.ReQuestTech.com/) Martial Arts Instructor [Modern Arnis and Balintawak Escrima] "Go back to sleep, Chuck. You're just havin' a nightmare -- of course, we ARE still in Hell." (Gary Larson) -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
