* David Thorburn-Gundlach <[EMAIL PROTECTED]> [2002-06-02]: > % 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 > 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?
he's probably looking for auto_edit.. > % and feels like looking at the /etc/Muttrc, I > % can send it. This brings up the real question > % to solve my problem - is there any way to make > % mutt ignore the /etc/Muttrc completely ? > mutt -h | grep -i muttrc > -F <file> specify an alternate muttrc file > -n causes Mutt not to read the system Muttrc --> mutt -n -F /dev/null we should tell users to start mutt like this when they *really* want to make sure to check mutt's *default* behaviour. > You mentioned your non-standard config; > where did you get your mutt itself? he probably got mutt from some linux distribution which mucks around with the setup files. *hrmpf* > P.S. I really wish you would quit with the top-posting and > non-trimming. Sven, do you have a .sig for this? ;-) you mean, "TOFU" (text oben, full-quote unten)? well, i sure do now... Sven -- TOFU lusers on mutt-users: Kyle Knack <[EMAIL PROTECTED]>
