Re: Output matching line in message body on ~b pattern match

2008-11-13 Thread Ethan Mallove
On Thu, Jul/17/2008 11:09:32PM, Ethan Mallove wrote: > On Wed, Apr/16/2008 12:04:11PM, Ethan Mallove wrote: > > On Tue, Apr/15/2008 11:21:29PM, David Obwaller wrote: > > > On Tue, Apr 15, 2008 at 03:22:26PM -0400, Ethan Mallove wrote: > > > > If this is not possible,

Re: Sort by most recently active thread

2008-08-12 Thread Ethan Mallove
On Mon, Aug/11/2008 10:17:54AM, Kyle Wheeler wrote: > On Monday, August 11 at 11:02 AM, quoth Ethan Mallove: > > My attempts at trying to incorporate this into a macro failed. > > Neither of these do what I want :-\ > > > > macro generic ,ot "Otset > >

Re: Sort by most recently active thread

2008-08-11 Thread Ethan Mallove
On Fri, Aug/08/2008 03:37:18PM, Kyle Wheeler wrote: > On Friday, August 8 at 04:07 PM, quoth Ethan Mallove: > > Is there a way to have mutt sort by most recently active thread? It > > appears that mutt dates an email thread by the timestamp of the > > initiating t

Sort by most recently active thread

2008-08-08 Thread Ethan Mallove
Hello, Is there a way to have mutt sort by most recently active thread? It appears that mutt dates an email thread by the timestamp of the initiating thread email. E.g., instead of this: ... 0 N Thu, Aug/07/2008 08:31:30AM Mutt(5.3K) [Mutt] #3100: forward_attribution missing

Twelve frozen MUTTs in one GNU Screen session

2008-07-21 Thread Ethan Mallove
I have about 12 instances of MUTT (each with a different IMAP folder open) running in a GNU Screen session. They all got stuck suddenly, and I can't figure out why. The "pstack" traces all look similar for each stuck instance of MUTT (see below). $ pstack 31477 31477: mutt -y -e push "=Inbox

Re: Output matching line in message body on ~b pattern match

2008-07-17 Thread Ethan Mallove
On Wed, Apr/16/2008 12:04:11PM, Ethan Mallove wrote: > On Tue, Apr/15/2008 11:21:29PM, David Obwaller wrote: > > On Tue, Apr 15, 2008 at 03:22:26PM -0400, Ethan Mallove wrote: > > > If this is not possible, is there a way to download all the > > > matching messages to

Re: Getting mutt to NOT open default IMAP folder at startup

2008-05-30 Thread Ethan Mallove
On Thu, May/29/2008 02:52:17PM, Kyle Wheeler wrote: > On Thursday, May 29 at 03:06 PM, quoth Ethan Mallove: > > When mutt starts up, it immediately selects my =Inbox. Is there a > > way to turn this behavior off? I ask because I'm launching mutt > > using -e, e.g., &

Getting mutt to NOT open default IMAP folder at startup

2008-05-29 Thread Ethan Mallove
Hello, When mutt starts up, it immediately selects my =Inbox. Is there a way to turn this behavior off? I ask because I'm launching mutt using -e, e.g., $ mutt -e 'push "c=foo\n"' (It may seem odd to not just do "-f =foo". I'm using "push" to get the "foo" folder in my "Open mailbox" history.)

Re: Output matching line in message body on ~b pattern match

2008-04-16 Thread Ethan Mallove
On Tue, Apr/15/2008 11:21:29PM, David Obwaller wrote: > On Tue, Apr 15, 2008 at 03:22:26PM -0400, Ethan Mallove wrote: > > If this is not possible, is there a way to download all the > > matching messages to a local filesystem so I can grep them? > > I don't think it&#

Output matching line in message body on ~b pattern match

2008-04-15 Thread Ethan Mallove
Hello, Is there a way in mutt to "grep" the body of mail messages, and actually see the matching line from the mail message? (Maybe using hooks?) Currently when I filter on the body of messages (using ~b) I get an index listing of all the matching messages, but I need to open each message one by o

Segmentation fault accessing ~/.mutthistory

2007-11-20 Thread Ethan Mallove
Hello, I've attached some truss output for this error and below is a gdb stack trace. I have no references to this mutthistory file in any of my ~/.mutt* files though I made sure the file does exist. My "history" is set to "10" in my muttrc. (gdb) run Starting program: /pkg/mail/bin/mutt wa