Package: mutt
Version: 1.5.9-2sarge1
Severity: normal

I'm using mutt with courier-imap, here, but I also have seen this
behavior with other IMAP servers (haven't tried it without IMAP).

I have also seen the problem with latest mutt from www.backports.org
(1.5.11+cvs20060403-0bpo1).

To reproduce:

t (to tag a message)
# (on another message to link the two into a thread)
$ (to sync to the server)

Note that after '#', everything looks good, but then it disappears after
'$'.  However, if I exit mutt and then return, everything looks good
again, so I guess it is some kind of display issue?

The following in my ~/.muttrc may be relevant:

set sort=threads
set sort_aux=reverse-last-date
set strict_threads=yes


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mutt depends on:
ii  exim4                 4.50-8sarge2       metapackage to ease exim MTA (v4) 
ii  exim4-daemon-light [m 4.50-8sarge2       lightweight exim MTA (v4) daemon
ii  libc6                 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii  libdb4.3              4.3.27-2           Berkeley v4.3 Database Libraries [
ii  libgnutls11           1.0.16-13.2        GNU TLS library - runtime library
ii  libidn11              0.5.13-1.0         GNU libidn library, implementation
ii  libncursesw5          5.4-4              Shared libraries for terminal hand
ii  libsasl2              2.1.19-1.5sarge1   Authentication abstraction library

-- no debconf information

-- 
Encrypted Mail Preferred:
    Key ID:  8527B9AF
    Key Fingerprint:  E1B6 40B6 B73F 695E 0D3B  644E 6427 DD74 8527 B9AF
    Information:  http://www.gnupg.org/
                                                                                
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to