On Jul 25 11:46, David Champion wrote: > > 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. :)
Wow, one could write a research paper on Mutt configuration :) The number of my scripts and vars is greater than one but so far still manageable by hand and some backtick-magic here and there. Thanks! steve