On Mon, Jul 13, 1998 at 09:02:37PM -0400, Tom Malloy wrote:
> I am very upset by these hook things. I do not understand them. They seem
> to be much harder to work with than regular configuration (.*rc) files.
> They seem to require that the user know which hook file to edit. There
> are several,
On Mon, 13 Jul 1998, Tom Malloy wrote:
> editing the existing configuration file. This is practically impossible
> for the novice user.
I wouldn't say I'm a novice but I had much the same problem, I used to
have a great little .fvwmrc file and I wanted to do same thing with my
.fvwm2rc file but
Tom Malloy <[EMAIL PROTECTED]> writes:
| I am very upset by these hook things. I do not understand them. They seem
| to be much harder to work with than regular configuration (.*rc) files.
| They seem to require that the user know which hook file to edit. There
| are several, prethis.hook posttha
Chris wrote:
> Tom Malloy wrote:
>
> But there is just no reason or justification for organizing
> configuration files
> in this confusing and intimidating manner. Applications, and os's, should be
> usable
> and reasonably configurably at every level of userability.
If you feel you have to re
Hi,
If you like programming by example, I can provide you with a
live copy of my fvwm config files (16Kgzipped) which should be a good
start.
http://www.debian.org/%7Esrivasta/fvwmconf.tar.gz> has a
copy. I did not include the custom xpm and gif files that I use,
since it is
Tom Malloy wrote:
But there is just no reason or justification for organizing configuration
files
in this confusing and intimidating manner. Applications, and os's, should be
usable
and reasonably configurably at every level of userability.
Well then, if that's what you want then get KDE or s
6 matches
Mail list logo
