Hi, * David T-G [2002-06-02 04:40:58 CEST] wrote: > ...and then Kyle Knack said...
> % Apparently mutt is still reading in values from /etc/Muttrc, and > % something in there is causing this to happen. The fast_reply option is > % turned off in both my config and the /etc/Muttrc. If anyone is bored Hey, I checked that, in your personal it didn't appear. Mutt also has built-in default values. If an option is not changed anywhere, the built-in default is used. So, in your case, 'turned off' would mean: unset fast_reply ...while it currently is unchanged and not turned off by the config files. > That doesn't make sense; why do you say that mutt is reading from Muttrc > when you then say that fast_reply is turned off in Muttrc? I don't understand it either. > Do you have > #set fast_reply > or > set nofast_reply > in either of your muttrc files? It's unlikely, but perhaps it was > compiled in as "on" by default. I've heard lots of things about heavily patched SuSe kernels (...and people suggesting not to use them) and SuSe at all. Allthough I never used it I would say that SuSe makes lots of changes to sources before they make a package out of it. In less words: It's SuSe and thus maybe not as unlikely as you think. > You mentioned your non-standard config; > where did you get your mutt itself? I think I mentioned it before, but the query-feature from the unstable branch (which didn't seem to make it in 1.4) is extremely usefull in such a case (since it dumps the real value mutt would use, either from init.h, Muttrc or ~/.muttrc). Cheers, Rocco
