headers
Matthew Sachs | 1 Jul 2003 02:51
Favicon
Gravatar

Bug #1556

Has anyone looked at bug #1556?  I submitted it a couple of months 
ago, and haven't heard anything.  The file which the patch I submitted 
along with my bug report touches hasn't been updated since November 
2002, according to CVS.  This bug is blocking mutt adoption at our
site.

If there's anything else I can do to help get this issue resolved, I'm 
still willing to work on this bug.

Thanks.

--

-- 
Matthew Sachs   <matthewg <at> zevils.com>
http://www.zevils.com/ * GPG key: 0x600A0342 * PGP key: 0x93EA1151
Permalink | Reply | 0 comments |
headers
Aaron Schrab | 1 Jul 2003 02:31

Re: bug#1538: mutt-1.5.4i: forward-message from the attachment menu -> segmentation fault

At 22:06 -0500 14 Apr 2003, I wrote:
> This is likely related to:
> 
> > patch-1.3.24.ats.parent_match.1
> 
> I received a similar problem report quite some time ago.  Replying to a
> message from the attachment menu would cause mutt to crash if that patch
> was applied, but work fine without the patch.  Although in that case it
> this apparently only happened with some messages.
> 
> Unfortunately I haven't yet had time to really look into it.  Hopefully
> I'll be able to do so soon.

I finally found time to fix this, a fixed version of the patch is now up
at:

  http://www.schrab.com/aaron/mutt/patch-1.5.4.ats.parent_match.1

--

-- 
Aaron Schrab     aaron <at> schrab.com      http://www.schrab.com/aaron/
 To err is human -- to blame it on a computer is even more so.
Permalink | Reply | 1 comment |
headers
Thomas Roessler | 1 Jul 2003 05:00

[2003-07-01] CVS repository changes

This message was generated and sent automatically.  It contains a
summary of the CVS commits over the last 48 hours.  These changes
should be propagated to the public repository within at most a day
or two.  Most probably, they have already been propagated.
Permalink | Reply | 0 comments |
headers
gray | 1 Jul 2003 06:34

bug#1583: mutt-1.4.1i: mutt swallows leading 't' in subject of reply to reply

Package: mutt
Version: 1.4.1i
Severity: normal

-- Please type your report below this line

When replying to a reply, mutt will swallow the leading 't' after the
're:' part of the subject.  For instance, if I reply to a message with
the subject "re: test", mutt will prompt the subject as "re: est".  I
can reproduce this error by sending myself a message with the subject
"re: test" and then replying to that message.  My guess is there is a
missing backslash in subject parsing code that looks for tabs, but I'm
too lazy to follow the breadcrumbs.  

-- Build environment information

(Note: This is the build environment installed on the system
muttbug is run on.  Information may or may not match the environment
used to build mutt.)

- gcc version information
gcc
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/specs
Configured with: ../gcc-3.2.2/configure --prefix=/usr --enable-shared --enable-threads=posix
--enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose
--target=i386-slackware-linux --host=i386-slackware-linux
Thread model: posix
gcc version 3.2.2

- CFLAGS
(Continue reading)

Permalink | Reply | 1 comment |
headers
Noel Flicken | 1 Jul 2003 13:52
Favicon

bug#1583: mutt-1.4.1i: mutt swallows leading 't' in subject of reply to reply

* gray <at> euthanasia.ath.cx <gray <at> euthanasia.ath.cx> skribis 2003-07-01 03:57:
> When replying to a reply, mutt will swallow the leading 't' after the
> 're:' part of the subject.  For instance, if I reply to a message with
> the subject "re: test", mutt will prompt the subject as "re: est".  I
> can reproduce this error by sending myself a message with the subject
> "re: test" and then replying to that message.  My guess is there is a
> missing backslash in subject parsing code that looks for tabs, but I'm
> too lazy to follow the breadcrumbs.  

I had the same problem, and your message inspired me to track down the
cause.  In my case, it was related to the reply_regexp variable.
Here was my original setting (notice single quotes):

set reply_regexp='^(re:[ \t])?(\[[[:digit:][:alpha:]_-]\])?(re([\[0-9\]+])*):[ \t]*'

Changing the single quotes (') to double quotes (") fixed the problem:

set reply_regexp="^(re:[ \t])?(\[[[:digit:][:alpha:]_-]\])?(re([\[0-9\]+])*):[ \t]*"

Test this out: reply to a message with the subject "Re:  test" (note
2 spaces before first 't').  The reply will now have the subject of
"Re: est" (note that first space and 't' were removed).

HTH,

  Noel
--

-- 
(*_    the drunken penguin says:
//\      "Oni metis makulon en mian kalkulon."
V_/_
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marco d'Itri | 1 Jul 2003 18:02
Picon
Favicon
Gravatar

bug#1584: mutt: Allow fcc-hook to work with postponed messages

Package: mutt
Version: 1.5.4-1
Severity: normal

[NOTE: this bug report has been submitted to the debian BTS as Bug#199529.
Please Cc all your replies to 199529 <at> bugs.debian.org .]

From: change <at> nas.com
Subject: mutt: Allow fcc-hook to work with postponed messages
Date: Tue, 1 Jul 2003 08:20:34 -0700 (PDT)

I noticed that mutt's "fcc-hook" command doesn't seem to 
work with postponed messages, only when new ones are 
created.

You can duplicate this problem by doing:

1.) Postpone a test email to muttbugtest <at> aol.com

2.) Exit mutt.

3.) Add the following line to your ~/.muttrc

        fcc-hook '~t aol.com' +spammers

4.) Run mutt again

5.) Press "R" to recall the postponed test message.

6.) Behold, the Fcc: field hasn't been updated.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Noel Flicken | 1 Jul 2003 18:17
Favicon

bug#1583: mutt-1.4.1i: mutt swallows leading 't' in subject of reply to reply

* Jeremy A. Gray <gray <at> euthanasia.ath.cx> skribis 2003-07-01 12:00:
> On 01 Jul 2003 Noel Flicken <flicken+mutt-dev <at> WPI.EDU> wrote:
> > set reply_regexp="^(re:[ \t])?(\[[[:digit:][:alpha:]_-]\])?(re([\[0-9\]+])*):[ \t]*"
> 
> This fixed the problem.  My setting was
> 
> set reply_regexp='^([af]w|re)+:[ \t]*'
> 
> and changing from single to double quotes worked for this too.  

Good!  Glad it worked for you.

> > Test this out: reply to a message with the subject "Re:  test" (note
> > 2 spaces before first 't').  The reply will now have the subject of
> > "Re: est" (note that first space and 't' were removed).
> 
> I see this if reply_regexp is enclosed in single quotes, but with double
> quotes get "re: test" (one space).  

Ok.  That should be the expected behavior.  

Maybe there should be a documentation fix to ward off others from
experiencing the same problem?  If not, i'd say this bug can be
closed. 

~Noel
--

-- 
  _o)(o the duelling penguins say:
-./\\//\.-  "La tuta ludo ne valoras kandelon."
 _\_VV_/_
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alain Bench | 1 Jul 2003 14:20
Picon
Favicon

Re: mutt & xterm character injection

Hello Arkadi,

 On Friday, June 27, 2003 at 12:49:30 PM +0300, Arkadi Shishlov wrote:

> Same mailbox opened in linux console shows pseudographic [A0]
> character in Subject.

    The Subject line contains "=?iso-8859-1?Q?=A0?=": That's a
non-breakable space U+00A0 " ".

    If you see a semigraphic char, probably the double horizontal bar
U+2550 "═" (coded A0 in KOI8-R), this only means locale and $charset are
incorrectly set to Latin-1 when your terminal's real charset is KOI8-R.

    On a KOI8-R terminal in a KOI8-R locale and $charset, Mutt will
convert this for display to a non-breakable space coded 9A in KOI8-R.
This is good, Mutt behaves correctly. But your terminal wrongly
interprets the 9A as some SCI control char it is not. The xterm -k8
option should be a solution for you. Or a terminal automatically using
control or printable chars where they are in the used charset.

 On Saturday, June 28, 2003 at 3:00:13 PM +0300, Arkadi Shishlov wrote:

> KOI8 range is 192-255 and 163,179 for CyrillicIO.

    But KOI8-R has printable chars everywhere in the 80-FF range, be it
Cyrillic, semigraphics, or other symbols. Not a single control char
there. I believe that's what Thomas meant.

    And KOI-8 not -R has no Cyrillic IO nor char FF. Also no control
(Continue reading)

Permalink | Reply | 0 comments |
headers
Petr Savicky | 1 Jul 2003 22:58
Picon
Favicon

mutt crashes on certain attachments

I observed a bug in mutt-1.4.1-1, the latest version of mutt in Red Hat 9.

If the list of attachments is required (by pressing "v") in a certain email, mutt
immediately crashes with a Segmentation fault.  The attachments were readable
in mutt-1.2.5.1-1 without problems.

I am sending an example of a mail which demonstrates the bug in an
attached archive.

Best wishes

  Petr Savicky
Attachment (mutterror.tar.gz): application/x-gzip, 2108 bytes
Permalink | Reply | 2 comments |
headers
Nicholas Cole | 2 Jul 2003 01:56
Picon
Favicon

feature request: open multiple folders

I think that mutt would benefit greatly from being
able to display messages from multiple folders at once
(as a single list).  This would make searching for
particular messages much quicker and more flexible.

I don't know enough c to suggest a patch myself, but I
assume that it would be relatively easy to implement;
instead of reading and sorting the mails from one
file, the client would read from several files.

What do others think?  And more importantly, could
someone put together a patch to do it?

Best, N

__________________________________________________
Yahoo! Plus - For a better Internet experience
http://uk.promotions.yahoo.com/yplus/yoffer.html
Permalink | Reply | 8 comments |

Gmane