Hi, * William Yardley [06-05-26 10:37:01 -0700] wrote:
On Fri, May 26, 2006 at 05:32:24PM +0000, Rocco Rutte wrote:* William Yardley [06-05-26 10:27:16 -0700] wrote:
> Anyway, other programs seem to manage to do it successfully...
...and most of these (and all I've seen) have mechanisms for changing the config from the application and thus they have to. This is not true for mutt (except shell escape :).
Correct. But we were discussing having a menu interface to the mutt config (or at least that's what I was talking about).
Okay, I didn't follow the discussion close enough.As long as mutt has support for the 'source' command and hooks, everything except a read-only view of the current settings doesn't make much sense.
Support for writing such files would require tons of extra information to be kept in memory and something like a stack or states plus many unanswered questions (like: the user has ~/.muttrc and sources ~/mutt/configfile and sets option $bar in both to different values, then he changes $bar in a config menu, where should the change be written to?)
IMHO mutt's config mechanism is just too powerful to support a builtin config menu to be implemented in a sane fashion.
bye, Rocco -- :wq!