Mutt hanging on new message.
So, a couple days ago, best I can figure, after a reboot, mutt now can't open temp files, or at least that's what I'm guessing, because it hangs after entering subject and hitting enter. GDB is saying it's on an open() call. It hangs indefinitely. This reboot didn't change much, I did it because apache-ssl wasn't working after a Debian upgrade, and I just upgraded again and rebooted. No kernel change, nothing weird installing. /tmp has permissions drwxrwxrwt, changing tmpdir to $HOME doesn't help, subdirectories of it don't help, nothing.. I didn't change any rc files. mutt's version is 1.4.0-2, and like I say, nothing weird changed. All the rc files hadn't changed for about 4 days before it got weird. And even that was just an unmy_hdr. I'm completely stumped, and sending this through /usr/bin/mail.
Re: Mutt hanging on new message.
Ryan -- ...and then Ryan Sorensen said... % % So, a couple days ago, best I can figure, after a reboot, mutt now can't open % temp files, or at least that's what I'm guessing, because it hangs after % entering subject and hitting enter. Have you checked your disk space? It's happenned to the best of us :-) 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! msg30318/pgp0.pgp Description: PGP signature
Problem with folder-hook
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi fellow mutters, I am having a problem getting a folder-hook working properly. I have the following folder-hook in my muttrc file: folder-hook =INBOX 'push T~r1m\n\;s=archive/INBOX\n' I want mutt to automatically move mail older than 1 month from my Maildir-format INBOX into an archive mbox-format INBOX. This folder hook seems to be working nicely except that mutt always moves the last message in my INBOX into the archive INBOX, even though the message should not match ~r1m. Every time I start up mutt, the folder-hook always moves the last message over to the archive box. Any ideas why this is happening? Should I send a flea? Regards, Eric - -- Put your trust in those who are worthy. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9XmjXIUsePhKa5WkRAoysAKCrYYwbWKorkLyfU+NfNbbTPYMOfgCgh/YG HBIsc0fM1WSpl5Gwmocs99I= =YpxE -END PGP SIGNATURE-
Re: Problem with folder-hook
* Eric Blau [EMAIL PROTECTED] [2002-08-17 11:16 -0400]: I am having a problem getting a folder-hook working properly. I have the following folder-hook in my muttrc file: folder-hook =INBOX 'push T~r1m\n\;s=archive/INBOX\n' I want mutt to automatically move mail older than 1 month from my Maildir-format INBOX into an archive mbox-format INBOX. This folder hook seems to be working nicely except that mutt always moves the last message in my INBOX into the archive INBOX, even though the message should not match ~r1m. Every time I start up mutt, the folder-hook always moves the last message over to the archive box. Any ideas why this is happening? Should I send a flea? That's the way tag-prefix works. If there are no tagged messages, it fails, and the rest of your macro continues. You can find one possible solution on my homepage. Nicolas
Re: Problem with folder-hook - ~r vs ~d
* Eric Blau [EMAIL PROTECTED] [2002-08-17 15:17]: I am having a problem getting a folder-hook working properly. I want mutt to automatically move mail older than 1 month from my Maildir-format INBOX into an archive mbox-format INBOX. please put the description of the goal *first* - thankyou. I have the following folder-hook in my muttrc file: folder-hook =INBOX 'push T~r1m\n\;s=archive/INBOX\n' this macro was easier to read if you made it a macro and used the command *names*. This folder hook seems to be working nicely except that mutt always moves the last message in my INBOX into the archive INBOX, even though the message should not match ~r1m. Every time I start up mutt, the folder-hook always moves the last message over to the archive box. Any ideas why this is happening? ~r takes *no* argument and is for *all* read messages. i think you want to use ~d which takes a date range as an argument. here's the macro way: folder-hook =INBOX 'macro index ,, \ tag-pattern~d1m\ntag-prefixsave-message=archive/INBOX\n' advantage: you issue the command, so you know what and when it's happening. apply when necessary. you can leave out the last \n so you can still back out with CTRL-G if you issued the command accidentally. Should I send a flea? no! scratch yourself on the head instead. ;-) Sven [damn - there goes another smiley from my supply]
Re: save-hook-list
* Gregor Zattler [EMAIL PROTECTED] [2002-08-16 17:42]: i would be perfectly satisfied if i could see a dump of hooks, so i can debug my configuration. That's all. I don't even think such a menu would be very useful: Hooks are for automated mail handling, so there is not much sense in setting, moving, editing them... except if you could save the hook-lists and load them on startup. so all it takes is a dump of the current list to a file. then you can look at it and rearrange it with your editor :unhook * and :source file from within. sounds fine. so, developers, how about a save-hook-list command? Sven
Re: CC: folder-hook with same From:
Michael wrote, Saku Ytti ([EMAIL PROTECTED]) muttered: Problem is, mutt doesn't allow writing Cc to same address as From, maybe a sanity check, I don't know. Hm, I can't reproduce that here. Mutt 1.4i This is what I'm looking for: folder-hook list 'my_hdr From: My Name list@address folder-hook list 'my_hdr Cc: List list@address This works here, too. Sure you don't have send-hooks which set From: in any way? Nope, no send-hooks. If I write new mail via 'm' I get the From and Cc formatted as expected by configartion above but if I reply via 'r' the Cc doesn't appear unless I change it to something different than From. ps. sorry about missing in-reply-to/reference headers. :( -- ++ytti
Re: auto_view with mutt in Cygwin?
On 08-16 02:55, Sven Guckes wrote: * Sean LeBlanc [EMAIL PROTECTED] [2002-08-15 20:18]: I can't seem to figure out how to get mutt to dump html to lynx (or links) in Cygwin. I have the same setting I have on my FreeBSD box, but Mutt says: mailcap entry for type text/html not found for any html mail I get? ...and yet I have a text/html entry in my ~/.mailcap file. Anyone using mutt under Cygwin that has figured this out? did you check the files in $mailcap_path, too? smacks forehead It turns out I left off the copiousoutput bit...thinking that was something links needed, and since I was using lynx, not links, on my Cygwin setup, I foolishly left that out of my .mailcap text/html entry. It wasn't until I was reading some man page(forget which it was now) that I realized I *needed* that to be on there. :) -- Sean LeBlanc:[EMAIL PROTECTED] Anti-trust laws should be approached with exactly that attitude.
Re: Cygwin + mailcap - copiousoutput required!
* Sean LeBlanc [EMAIL PROTECTED] [2002-08-17 20:20]: It turns out I left off the copiousoutput bit. thinking that was something links needed, and since I was using lynx, not links, on my Cygwin setup, I foolishly left that out of my .mailcap text/html entry. It wasn't until I was reading some man page(forget which it was now) that I realized I *needed* that to be on there. :) could have been the manual to muttrc (see below). it says this field is optional. go figure. but mind you it also says this: Without this flag, Mutt assumes that the command is interactive. and we don't want interaction here, now, do we? ;-) Sven === man muttrc 5.3.3. Advanced mailcap Usage 5.3.3.1. Optional Fields In addition to the required content-type and view command fields, you can add semi-colon ';' separated fields to set flags and other options. Mutt recognizes the following optional fields: copiousoutput This flag tells Mutt that the command passes possibly large amounts of text on stdout. This causes Mutt to invoke a pager (either the internal pager or the external pager defined by the pager variable) on the output of the view command. Without this flag, Mutt assumes that the command is interactive. One could use this to replace the pipe to more in the lynx -dump example in the Basic section: text/html; lynx -dump %s ; copiousoutput This will cause lynx to format the text/html output as text/plain and Mutt will use your standard pager to display the results.
