saving message/rfc822 attachments to a folder

2000-11-28 Thread Andrew Pimlott
I'm using mutt 1.2.5i from Debian 2.2. It seems that, if I have a message with message/rfc822 attachments (eg, some mailing list digests), I can do some but not all of the operations on the attachment that I could do on a normal message. In particular, I want to save an attachment as a separate

Re: saving message/rfc822 attachments to a folder

2000-11-29 Thread Andrew Pimlott
On Wed, Nov 29, 2000 at 02:12:19AM +0100, Daniel González Gasull wrote: > When reading the message, go to the attach menu, > then you can save individual attachments. If the > attachment is message/rfc822, you can save it in a > mail folder. Try it. I do it usually. Ok, I'm stupid. I was misl

postponed message lost

2001-04-11 Thread Andrew Pimlott
There may be a bug in mutt 1.2.5 that causes postponed messages to be lost. I just postponed a message in the usual way (quit from editor to the message view, press 'q' to quit, press 'y' to postpone). About 30 seconds later, I attempted to resume the message. I pressed 'm' to mail, pressed 'y'

Re: postponed message lost

2001-04-11 Thread Andrew Pimlott
On Wed, Apr 11, 2001 at 08:58:57PM +0200, Rado S. wrote: > On Tue 10.Apr'01 at 19:51:54 -0400 wrote > Andrew Pimlott <[EMAIL PROTECTED]>: > > / There may be a bug in mutt 1.2.5 that causes postponed messages to > / be lost. > > When you edit a message but don

Re: postponed message lost

2001-04-12 Thread Andrew Pimlott
On Wed, Apr 11, 2001 at 06:07:19PM -0400, William Park wrote: > I'm running 1.2i, and don't have problem with postponed messages. Can > you duplicate the problem consistently? No (and sorry for not saying this). I was not able to reproduce it, and since nobody else seems ever to have observed i

long line handling

2001-08-08 Thread Andrew Pimlott
When the "markers" and "smart_wrap" options are both off, it would be nice if mutt would print long lines to the screen without a newline. This way, if I copy the line in an xterm, the whole line goes into the cut buffer unbroken. As it is, I get unwanted newlines in the cut buffer. I tool a lo

Re: long line handling

2001-08-08 Thread Andrew Pimlott
On Wed, Aug 08, 2001 at 02:25:01PM -0400, Thomas E. Dickey wrote: > On Wed, 8 Aug 2001, Andrew Pimlott wrote: > > > When the "markers" and "smart_wrap" options are both off, it would > > be nice if mutt would print long lines to the screen without a > &g

Re: long line handling

2001-08-08 Thread Andrew Pimlott
On Wed, Aug 08, 2001 at 03:45:12PM -0400, Thomas Dickey wrote: > > > still won't work (xterm won't retain it as a single line if it wasn't > > > written as a single line, and you can't count on any screen optimization > > > library to do this). > > > > I thought that if mutt had written it as a s

~f patterns in score commands

1999-09-28 Thread Andrew Pimlott
When I construct a score pattern using ~f, it appears to behave differently from in other contexts. Specifically, the expression seems to be matched only against the email address, not the name. Eg, if this message is From: Andrew Pimlott <[EMAIL PROTECTED]>, an ordinary search for eith

quote_regexp occasionally ignored

2002-03-01 Thread Andrew Pimlott
I'm using mutt 1.3.27i from Debian "testing". I've noticed that occasionally, quoted text isn't highlighted in the pager. I have quote_regexp set in my .muttrc: set quote_regexp="^[[:blank:]]*([[:alnum:]]{0,10}>|[]|:}#);+]|-> )" This should match (among other things) any line with a leadin

Re: quote_regexp occasionally ignored

2002-03-02 Thread Andrew Pimlott
On Fri, Mar 01, 2002 at 01:03:59PM -0600, Aaron Schrab wrote: > quote_regexp is ignored for format=flowed messages since RFC 2646, which > describes that format, mandates that only ">" characters at the very > beginning of a line are to be considered quote characters. In the > message you attache