And, as it always turns out, as soon as I sent that, I figured it out. 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 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 ? I tried 'mutt -F ~/.muttrc', which should be the default behavior with no options, but I get the same results. Thanks!
Kyle * Kyle Knack <[EMAIL PROTECTED]> [020601 22:29]: >I just explicitly unset fast_reply, to no avail. I checked through the >system Muttrc (which I don't even know if it's reading or not since I >have my own .muttrc), and it's not set in there either. As for the >header copying, I'm honestly not sure why I had that on ;) I turned it >off now. > > >Kyle > >P.S. If I sounded a bit harsh in my prior response, I apologize, I did >not intend it in that tone. As I read over it again, it kinda struck me >that way. > >* Rocco Rutte <[EMAIL PROTECTED]> [020601 20:15]: >>Hi, >> >>* Kyle Knack [2002-06-02 01:32:12 CEST] wrote: >>> As I stated, askcc is set to true in my configs, yet it's still not >>> prompting me. It's also not even asking for a subject before spawning >>> vi. >> >>Sounds like $fast_reply is set somewhere. >> >>> * Nicolas Rachinsky <[EMAIL PROTECTED]> [020601 03:38]: >>> >Date: Sat, 1 Jun 2002 09:36:52 +0200 >>> >From: Nicolas Rachinsky <[EMAIL PROTECTED]> >>> >To: [EMAIL PROTECTED] >>> >Cc: Kyle Knack <[EMAIL PROTECTED]> >>> >Subject: Re: Problem composing mail since switching to SuSE >>> >User-Agent: Mutt/1.3.28i >> >>Mind explaining why you quote this? IMHO it's completely >>useless... >> >>Cheers, Rocco >> > >-- >Kyle Knack >([EMAIL PROTECTED]) -- Kyle Knack ([EMAIL PROTECTED])
