On Thu, Sep 26, 2002 at 10:28:56AM -0400, PeterKorman wrote: > On Wed, Sep 25, 2002 at 03:01:06PM -0700, Burton Samograd wrote: > > On Wed, Sep 25, 2002 at 11:36:38PM +0200, Hans Ginzel wrote: > > > > > > Something like: > > > :function reread_cfg_files > > > : reset all options to compile time > > > : source startup files as by usual start > > > :endfunction > > > -- > > > > At the top of your .muttrc > > > > unset * > > unhook * > > > > should do the trick. > > > > burton > > unset * causes > > Error in /home/pkorman/.muttrc, line 1: *: unknown variable > source: errors in /home/pkorman/.muttrc > Press any key to continue... > > > Mutt manual section 3.23 > > The reset command resets all given variables to the compile time > defaults (hopefully mentioned in this manual). If you use the command > set and prefix the variable with ``&'' this has the same behavior as > the reset command. > > With the reset command there exists the special variable ``all'', > which allows you to reset all variables to their system defaults. > > > > reset all > unhook * > > will work. I dont know if it clears folder hooks though. > furthermore, if you rely on settings in /usr/local/etc/Muttrc > you better move everything into your local setting file.
I'm pretty sure it clears folder hooks. if your first lines of .muttrc are: reset all unhook * source /usr/local/etc/Muttrc Your probably in good shape as long as your Muttrc is on this path. JPK -- []+ Wisdom is vindicated by all her children. +[] [] [] []+ GnuPG <ECBA EA08 C3C1 251E 5FB5 D196 F8C8 F8B7 AB60 234D> +[]
