[ Adding this back to fvwm@ where your original reply should have gone. ] 2009/11/21 Leo Simon <[email protected]>: > I'm calling fvwm from startx, which calls .xinit, which calls fvwm without > arguments. My fvwm configuration is in the directory ~simon/.fvwm, which is > attached as a zip file.
Well, other than that missing ~/.fvwm2rc or ~/.fvwm/config or ~/.fvwm/fvwm2rc or the actual file which *calls* the files you posted, here's what's happening, and why. I can't tell from looking at these files in which order they're read in, but it doesn't take a genius to work out that if the "startup" file read first (which I assume it is), and you have this in it: DestroyModuleConfig FvwmTaskBar: * *FvwmTaskBar: Geometry +0+0 *FvwmTaskBar: Rows 1 ... which is correct. "+0+0" is the top-left of the screen. However, later on in the "modules" file, we also see this: *FvwmTaskBar: Geometry +0-0 *FvwmTaskBar: Fore Black *FvwmTaskBar: Back #c0c0c0 ... fail. "+0-0" is the *bottom left* of the screen --- and hence I suspect that the definition in "modules" for your FvwmTaskBar config is read *AFTER* the one in the "startup" file, clobbering the settings you wanted. So, the solution is simple. Tidy your config up, it's a mess. -- Thomas Adam
