On Thu, Dec 13, 2001 at 11:17:04PM -0800, Tenebrae wrote:
> Holy !_at_#$, there were a lot of changes! Where have I been? Sitting under
> a RedHat 6.2 / RPM rock, apparently...
> I've just spent the last week reinstalling and setting up my system with a
> new hard drive and noticed a couple errors in my .fvwm2rc so I thought I'd
> search through my FVWM mailing list archives and see if I could find them.
> "All fixed in the new version," they said. The errors, for the curious,
> included a "*FvwmTaskBar: cannot open console" for no reason I could
> immediately find, and a failure of my cute little Start button to raise
> back up after being clicked.
> Well, the upgrade fixed those...
> ...and launched a whole new set of errors with my dot file. Sheesh.
> Turns out there are all kinds of new functions and features that made my
> poor little dot file which was migrated from FVWM 2.2.4-4 from 2.0.46
> and before that, fvwm95. Or something like that.
> In other words, there was a ton of obsolete junk in it, and the upgrade
> broke my lovely desktop in all kinds of interesting ways. I just had a
> fun night looking at all kinds of man pages, web sites, and other peoples'
> dot files from the same version (in particular, thank you Glen Lee Edwards
> for posting yours - it was the 8th match in a Yahoo search for .fvwm2rc
> and 2.4.3). The end result is still far from where I want it to be.
That's why we wrote a script that converts 2.2.x configs into
2.4.x configs:
utils/fvwm24_convert
In the source distribution.
> If you can offer suggestions on the following points, please do:
> 1) FvwmButtons doesn't want to stay put like the FvwmTaskbar does. I
> coulda sworn both used to...
What does it do instead? And what are the responsible lines of
your config file?
> 2) I get an error message when I start fvwm2. It says,
> "[FVWM][ParseBinding]: <<ERROR>> No such key: Help"
> I echo its sentiment. Help? Must be some old junk somewhere in my dot
> file, but I am having no luck finding it.
Just ignore that message.
> 4) I have to type in ctrl-alt-F1 to view error messages like that and
> ctrl-alt-F7 to get back to X. Is there a way I can have it spit stuff
> like that out to a nice little term on my desktop instead? I hate it when
> stuff goes on behind my back and I don't notice those nasty little errors
> piling up back there until it's too late...
Well, starting a console should be part of your config file. I
myself start X with
$ startx 2>&1 | tee $HOME/.X.err
And then run an xterm with
Exec xterm -T XMessages -e tail -f $HOME/.X.err
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: d.vogt_at_lifebits.de
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Dec 14 2001 - 05:07:16 GMT