Re: fvwm95 after hamm upgrade
Doug Thistlethwaite <doug.t@deltanet.com> writes:
> Hello,
>
> I upgraded my bo system to hamm last night. Everything went pretty
> well, though I did have the run the "install" portion of dselect
> several times for it to get through without errors...
Well, I'm impressed - I made a slight error in packaging up fvwm95 for
hamm, such that bo upgrades aren't as smooth as they could be - oops.
> Anyhow - Everything seems to have installed fine. But I have now
> noticed that my windows manager fvwm95 does not seem to read my
> prior config file in my home directory
>
> The config info was in /home/doug/.fvwm2rc95 on my bo system and
> everything seemed to work fine.
>
> The first lines of my window-managers
>
> /usr/X11R6/bin/fvwm95
> /usr/X11R6/bin/fvwm2
> ...
>
> What do I need to do so my windows manager will read my ini file?
The name of the ini file changed between the bo and hamm versions - if
you had a customized system-wide initialization file, you got a little
message about it. Personal initialization files are harder to check
for.
Anyway:
1) The name of the new initialization file is .fvwm95rc - you can
rename your .fvwm2rc95 to .fvwm95rc and it'll work, BUT
2) fvwm95 now has an improved configuration, much like the
configuration scheme of fvwm2 - if you use this new scheme then
whenever you install new packages, they'll appear in your fvwm95 menu
the next time you restart fvwm95. For more information on this new
scheme, refer to /usr/doc/fvwm95/README.sysrc.gz. The basic gist is
to create a subdirectory called .fvwm95 and then place in it a file
called post.hook containing your own customizations. There are also
some examples of things you can do with the system configuration files
in the system config. files themselves (they're all commented out;
uncomment what you want).
Note that if you do have a ~/.fvwm95rc file, the new configuration
scheme won't get touched, and your menu won't get updated to show the
list of currently installed packages.
Some people who are used to the one long monolithic configuration file
find the new config. scheme a bit confusing - but it's not, really.
I'd be glad to help you with it.
Reply to: