Re: query-feature (was Re: Problem composing mail since switching to SuSE)
Rocco, et al -- ...and then Rocco Rutte said... % % Hi, Hello! % % * David T-G [2002-06-02 04:40:58 CEST] wrote: ... % % 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). Ah! Since it's been around forever, you must mean something other than :set ?feature to show how feature is set... Does this basically spit out a whole muttrc of settings or some such? % % Cheers, Rocco TIA HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28513/pgp0.pgp Description: PGP signature
Re: Problem composing mail since switching to SuSE
* Kyle Knack [EMAIL PROTECTED] [2002-05-31 23:48:21 -0400]: I recently switched my workstation from RedHat 7.1 to SuSE 7.3, and now I'm having a funny problem when I compose mail. Mutt is no longer asking me for a recipient or CC address when I hit 'm' to compose mail (ask for CC is explicitly turned on in my config). My configuration is fairly non-stock, but I can't seem to find any option related to this. If anyone knows off the top of their head what might be causing it, please let me know. If necessary, I can post all or some of my config (fairly long). Thanks! 6.3.10 askbcc Type: boolean Default: no If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before editing an outgoing message. 6.3.11 askcc Type: boolean Default: no If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. Nicolas
Re: Problem composing mail since switching to SuSE
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])
Re: Problem composing mail since switching to SuSE
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])
Re: Problem composing mail since switching to SuSE
Kyle -- ...and then Kyle Knack said... % % And, as it always turns out, as soon as I sent that, I figured it out. Sort of, I think. % 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? % 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 Of course: [zero] [9:37pm] ~ mutt -h | grep -i muttrc -F file specify an alternate muttrc file -ncauses Mutt not to read the system Muttrc % should be the default behavior with no options, but I get the same % results. Thanks! 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. You mentioned your non-standard config; where did you get your mutt itself? % % Kyle % % % * Kyle Knack [EMAIL PROTECTED] [020601 22:29]: P.S. -- I really wish you would quit with the top-posting and non-trimming. Sven, do you have a .sig for this? ;-) HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28481/pgp0.pgp Description: PGP signature
Re: Problem composing mail since switching to SuSE
* David T-G [EMAIL PROTECTED] [020601 22:44]: 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. You mentioned your non-standard config; where did you get your mutt itself? It turned out to be 'set autoedit' in the Muttrc. I unset it now in mine and all is well. Thanks for the help. Kyle -- Kyle Knack ([EMAIL PROTECTED]) msg28485/pgp0.pgp Description: PGP signature
Re: Problem composing mail since switching to SuSE
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
Re: Problem composing mail since switching to SuSE
* 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 -ncauses 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]
Re: Problem composing mail since switching to SuSE
* Rocco Rutte [EMAIL PROTECTED] [2002-06-02 03:14]: I've heard lots of things about heavily patched SuSe kernels (... and people suggesting not to use them) and SuSe at all. oh, SuSE... right. 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. SuSE - the Linux Windows from Nuremberg ;-) Sven [what would be a good signature now? ah - got it!] -- Sven Guckes [EMAIL PROTECTED] [Linux Distributions, 2000-07-28] LINUX? Which one? BestLinux, BlueCat Linux, Caldera OpenLinux, Conectiva Linux, Corel Linux, Debian GNU/Linux, DragonLinux, easyLinux, Elfstone Linux, Gentus Linux, Jurix Linux, L13Plus, Linux Antarctica, Linux by LibraNet, Linux Mandrake, LinuxOne, LinuxPPC, Linux Pro, LinuxWare, LuteLinux, MaxOS(TM), MkLinux, Platinum Linux, RedHat Linux, Redmond Linux, Rock Linux, RT-Linux, Slackware Linux, Stampede Linux, Storm Linux 2000, S.u.S.E. Linux, TurboLinux, Yellow Dog Linux, Yggdrasil Linux; SMALL Linux Distributions: Armed Linux, Coyote Linux, ChainSaw Linux, DLX Linux, DOS Linux, File, Print CD Server, hal91 Floppy Linux, Linux Embedded, Monkey Linux, muLinux, Peanut Linux, Phat Linux, ThinLinux, TINY Linux, tomsrtbt, Trustix Secure Linux, White Dwarf Linux, WinLinux 2000, WholeLinux, ZipHam.
Re: Problem composing mail since switching to SuSE
* Sven Guckes [EMAIL PROTECTED] [020601 23:22]: he probably got mutt from some linux distribution which mucks around with the setup files. *hrmpf* Actually, it's based off of Chris Gushue's .muttrc, with a fair amount of changes of my own. you mean, TOFU (text oben, full-quote unten)? well, i sure do now... Sven -- TOFU lusers on mutt-users: Kyle Knack [EMAIL PROTECTED] Point taken. -- Kyle Knack ([EMAIL PROTECTED])
