On 2012-08-30, Jaimos Skriletz wrote: >> which in some way say that it is not possible. >> > > Correct it is not possible to dump the whole running config. I would suggest > you find the config file on the machine if you want the whole config. > OK
>> I want to find what action take in effect when double clicking on window >> border. For application, like "gmrun" (which have no titles) double clicking >> hide that window in background and raise another window to foreground (sorry >> if I describe in non-technical terms). >> > > There is a method to get some info about the current running config. Though > the PrintInfo command (see the man page for more details) you can print all > the keybindings. > > PrintInfo Bindings > > Will print all of the keybindings to stderr (this is $HOME/.xsession-errors > in many cases). > Using PrintInfo I reach my goal (from FvwmConsole). Info about ~/.xsession-errors is valuable. It is out of scope of Fvwm guides (only in http://www.fvwm.org/documentation/faq/#toc_5.8 "5.8 How do I capture the output (e.g. errors) of fvwm?"). I use nodm display manager to auto-login (without password prompt) and automatically launch my ~/.xinitrc. In my case errors come to ~/.xsession-errors. It is convenient open this file in Emacs with auto-revert-tail-mode. FAQ say about possibility to get errors in FvwmConsole but I don't get errors here. In any case I don't need this. Thanks for all who answer to me (also in private). -- Best regards!
