On Tue, Feb 27, 2018 at 12:50:03PM +0200, Michelle Konzack wrote: > I have checked since several years where this error is coming from, but > failed, becasue I have no MULTIPLE CONDITIONS > > [fvwm][CreateConditionMask]: <<DEPRECATED>> Use comma instead of > whitespace to separate conditions > > This errors appear, if I move with the mouse from one window to another > without clicking on it. > > I was thinking, this can be only in the styles like >...
Nothing of that has any conditions. It must be somewhere else. > I had my own RootMenu which was not more working and now it show all the > time "Builtin Menu" which I do not want. > > So, if fvwm loads stuff trom elsewhere, than I am right, that my config > has no errors, because the errors are also there, if I have no styles > and whatelese configured... > > How it is possibel, to DISABLE the WHOLE default stuff? Fvwm has a very small builtin configuraion that includes the builtin menu and some very basic bindings and styles. The last command of the default configuration reads the file ConfigFvwmDefaults that is installed along with the binaries. After that, it tries to find the user configuration file, picking the first one in this list: <config file/command from the command line> ~/.fvwm/config /usr/local/share/fvwm/config (depending on the configure prefix) ~/.fvwm/.fvwm2rc ~/.fvwm2rc /usr/local/share/fvwm/.fvwm2rc ... (some more obscure file locations) If it still uses the builtin menu, then either your config file does no do what you think it does. Are there any error messages during startup about missing or inaccessible files; have any files been moved or renamed? Or it uses a different file than it should. Check the above list carefully. Hm, if someone really installed a system wide /usr/local/share/fvwm/config, that would *always* be read instead of the user's ~/.fvwm/.fvwm2rc. > There are several things which I have never configured and can not get > rid of it, because I do not know, where it come from and what it is... Well, since you seem to have quite a few unexpected problems at the moment, there is probably a problem with which configuration files are used. Try to figure out which ones are executed and which ones are not. You can temporarily put an echo command at the top and bottom of all the files: echo !!!!!!!! BEGIN <filename> !!!!!!!! ... echo !!!!!!!! END <filename> !!!!!!!! Also, make sure that all "read" commands actually find the filed they are supposed to read. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
