> > You can work around this by putting MUTTDIR in your shell environment > > before running mutt. > > Hmm, how do you read my mind? :)
:) Well, I actually do this for a few variables -- predating the $my_xyz feature. I should switch where I can though, so I can drop the setenv patch. (Lets me stuff things into the environment from inside mutt.) > A more elegant solution could be a config var $configdir or $scriptdir for > people who > > - have more then one script laying around in ~/.mutt (or wherever) > - don't want to put Mutt-specific scripts in a location on $PATH You also can do this in ~/.muttrc: source "~/.mutt/muttrc.py|" and generate your "real" muttrc programmatically: another way to do things like macros/variables and search paths, and you also get to automatically define hooks, lists, etc. based on the contents of your filesystem. But once again this only executes at startup -- it doesn't update itself continuously. If you're ambitious enough you could set mutt up to reload much of its configuration every time you change folders, or something. But I'm not sure how useful this really is for most people. :) -- -D. [EMAIL PROTECTED] NSIT University of Chicago
