Cursor should stay on laste selected entry when imap or directory browsing
Hi! Well, in mutt terms both are directory: Browsing local filesystem and imap mailboxes (with c - TAB). When entering the browser the cursor hits the first entry of the list instead of keeping its postition on the last left entry. Is this behaviour able to be configured? I found a ticket regarding this: http://dev.mutt.org/trac/ticket/1268 Is this still active - namely and unhandled issue? I wonder because 4 years before it is considered half intregated... Kind Regards, Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
Re: Cursor should stay on laste selected entry when imap or directory
On Tue, Nov 03, 2009 at 11:18:52AM +0100, Konstantin Kletschke wrote: Well, in mutt terms both are directory: Browsing local filesystem and imap mailboxes (with c - TAB). When entering the browser the cursor hits the first entry of the list instead of keeping its postition on the last left entry. Is this behaviour able to be configured? I'm sure it can be; let me just say that I don't know how. When I used Debian's binary mutt 1.5.18 it behaved as per what you want. When I switched to mutt 1.5.20 (compiled by me) it behaved as per what you have now. I guess this means that the behavior changed from version .18 to version .20, a compile option is missing or a patch is missing. This behavior used to annoy me when I first started using my own mutt 1.5.20 but I don't give it a second thought now as I use the index numbers to navigate. I found a ticket regarding this: http://dev.mutt.org/trac/ticket/1268 Is this still active - namely and unhandled issue? I wonder because 4 years before it is considered half intregated... Kind Regards, Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
Re: mutt removing stuff in brackets from subject
All, Still having this issue. When I reply (or group reply), everything inside of a Fwd: [Blah Blah] results in a Fwd: subject. Any other thoughts on what may be causing this? -j On Sun, Jul 19, 2009 at 8:30 PM, Nicolas Sebrecht nicolas.s-...@laposte.net wrote: On Wed, Jun 17, 2009 at 02:57:45PM +0200, Michael Tatge wrote: * On Wed, Jun 17, 2009 09:47AM +0200 Rejo Zenger (mutt-us...@subs.krikkit.nl) muttered: ++ 16/06/09 19:51 +0200 - Michael Tatge: When I respond to an email that has a subject similar to: [StuffHere] Blah Blah Blah Mutt actually *removes* everything inside of the brackets and the brackets themselves. Any thoughts on why this happens? Works fine here. There is a setting that might be resposible though. Check reply_regexp Correct me if I'm wrong, but I don't think that particular setting would remove a thing form the subject. The manual says: A regular expression used to recognize reply messages when threading and replying. ^ I tend to think it should not be used when threading: replying and threading are two unrelated tasks. What about adding a $thread_regexp? -- Nicolas Sebrecht
HTML mail: Why isn't it displayed?
Hi, I've got an email with these headers: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam_score: 4.4 X-Spam_score_int: 44 X-Spam_bar: !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=de lang=de head Mutt displays the HTML garbage as plain text, unreadable. Now I've no idea if the problem is with mutt, or if the headers or something else are wrong. If the problem is with the email, it would be nice to know which RFCs are to be applied so that I can refer the sender of these mails to them and have them send them correctly encoded.
Re: HTML mail: Why isn't it displayed?
PS: Mutt seems to ignore ~/.mailcap. l...@cat:~/Mail$ mutt -nF /dev/null -Q mailcap_path mailcap_path=~/.mailcap:/usr/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap l...@cat:~/Mail$ So which of the mailcap files mutt finds in the mailcap_path will it use? The manual doesn't say. On Tue, Nov 03, 2009 at 10:58:02PM -0700, lee wrote: Hi, I've got an email with these headers: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam_score: 4.4 X-Spam_score_int: 44 X-Spam_bar: !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=de lang=de head Mutt displays the HTML garbage as plain text, unreadable. Now I've no idea if the problem is with mutt, or if the headers or something else are wrong. If the problem is with the email, it would be nice to know which RFCs are to be applied so that I can refer the sender of these mails to them and have them send them correctly encoded.
