I think it should be possible to use a configuration file, however
it should still be possible to override anything in there with a
command line option.
Sure, and that is quite simple, --eval="(set! foo-option bar)".
> In short, the console-client should be changed to use Guile
Personally, I very much dislike config files to be scripts. It's
best if they are just a list of key-value pairs, one per line,
separated by tab or =. Some config files are not suitable for such
a simple format, but I think this one is.
How would you reconfigure keybindings? Add hooks that are run on some
kind of event? Maybe include a specific file depending on the phases
of the moon? What about changing values in a running console-client
without having to restart it (changing the timeout for when the
screensaver starts comes to mind)? What if I want to run
"start-browser" when I click on a url with my mouse in the console?
I think that those who have objected to the use of Guile just don't
see the posibilities that it would allow the user to do. I atleast
would love to see the console-client be morphed into some kind of
version of Emacs where you can have multiple windows, frames, etc.
Running scheme code here and there, extending things as you go on.
Note that nobody is forcing you to use the "scripting" facilities in
Guile, your configuration file can be a simple file that just has a
bunch of set!'s. But you shouldn't force me to this little box where
I can't do crazy things. The Hurd is after all about allowing users
to do what they want without screwing up for other users.
Cheers.
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
