FVWM colorsets not working
I recently installed Slackware with fvwm2, and I can't seem to be able to set the color of the window titles and borders. They are just light gray whether focused or not. If I comment out the Style "*" lines, is is dark gray when unfocused.
I also wonder if it is possible to have the window focus when clicked, but not rise above other windows unless clicked on the title? Here is my .fvwm2rc file: Code:
DesktopSize 1x1 |
Quote:
Quote:
The default policy anyway already does what you want, if I remember correctly. When you don't have a config file, if you click an application you give it the focus, but only clicking on the title bar will raise it. Quote:
|
Quote:
Quote:
Quote:
|
Quote:
In fact, if my memory serves correctly, the colorset handling is *completely* different, look at the FvwmThemes module which is the way to handle colorsets in 2.4 I think. That syntax you are using is for 2.5. Most of the tutorials and stuff you find on the net will only work for 2.5 as well. So you might really consider upgrading. Quote:
The config on your home should always prevail over any other configuration file. The order of precedence is detailed in the man page though, in case you want to make sure. I don't have 2.4.x installed. So, do you want SloppyFocus or ClickToFocus? Quote:
|
Well, i'm just using what came with Slackware64 13.0.
I will see if I can get a newer version. |
On the fvwm.org website, it says that 2.4.20 is the newest stable release.
Should I just get the new unstable one? |
Regardless of the classification, 2.5 is just as stable (well, I can't say I've tested every feature, I don't think anyone has). My guess is that they haven't pushed to 2.6 yet just because there are goals that have not yet been achieved, but otherwise I haven't suffered any stability problem so far.
|
I ran this:
Code:
removepkg fvwm Code:
./configure I tried manually as root deleting all the files and folders with "fvwm" in the name, and then running make install. still nothing. startx would only work as root. So I am writing this message in the links command-line browser, because startx did not work as a regular user. I hope someone helps fast! P.S. I am very, very glad that Slackware does not have a graphical login screen, this way I can use the command line when my GUI is completely screwed up. |
Quote:
Quote:
In any case, try to run Code:
which fvwm |
whereis fvwm does return a path, I don't remember it.
I searched for xinitrc, there were a few files in a directory that I also forgot (it was /etc/X11/<something...>), and there were a few xinitrc.<windowmanager> files, but not for FVWM. There was some xinitrc file hilighted red with an @ symbol on the end, I am not sure what's the deal with that. I also think that I forgot the dot in the beginning, I will check again. I hardly remember what I did because it is so difficult and frustrating to get links to log into LQ. I just logged into Ctrl-Alt-F2 and checked again, and there is no .xinitrc file in /etc/X11/xinit. ls says there is a xinitrc file (no dot), but cat and vim say it is not there. |
Quote:
In the past, fvwm 2.x was called "fvwm2", but that binary was renamed to simply "fvwm", without the "2". So, if you $HOME/.xinitrc file contains "fvwm2" if needs to be changed to "fvwm", otherwise you are pointing to a non-existing binary. |
I don't have such a file in my home directory.
|
I see that that xinitrc file that I have in /etc/X11/xinit is actually a link to a file xinitrc.fvwm2 in the same directory, that does not exist.
|
Than I have no idea how are you starting fvwm at all.
The startx script usually has something similar to this on it: Code:
userclientrc=$HOME/.xinitrc Alternatively, just create your $HOME/.xinitrc, and launch fvwm from there, simply this will work: Code:
fvwm > ${HOME}/fvwm.log 2>&1 |
Quote:
|
All times are GMT -5. The time now is 08:51 AM. |