[ Adding fvwm@fvwm.org back -- please don't go culling the Cc list! ] 2009/8/2 Charlie <aries...@clearmail.com.au>: > I attempted to run FvwmConsole through my ~/.xsession but that didn't > work either. Maybe my syntax was wrong.
No, that won't work because FvwmConsole is a FVWM module -- FVWM has to spawn it so it can create a pair of pipes to communicate with the module, broadcast messages to it, etc. > Oh yes, I tried to run it the first few times by clicking on the module > in fvwmModules, and I also have a fvwmConsole socket in my ~/.fvwm/ > directory, but still couldn't get it to work. Some other module like > fvwmDesker work fine. Will try out what you have posted above as soon as Then it won't have been anything to do with "ModulePath" which is good. I don't understand though why you can have the socket kicking around though. That gets removed when FvwmConsole does (i.e., the module dies.) Are you saying it's *always* present -- even before starting FvwmConsole? That being the case, remove that socket first. FvwmConsole will try and use xterm by default to provide a console for you. You *do* have xterm installed, right? If not see the "-terminal" option to FvwmConsole to perhaps try some other terminal emulator. Until I get some concrete feedback, I'm done clutching at straws for now. :) -- Thomas Adam
