RFC 2047 encoder botched?

When replying to the attached message, the subject header gets botched, and one of the RFC 2047 encoded-words torn apart. I haven't time right now to track that down to a specific version. Relevant parameters: send_charset="us-ascii:iso-8859-1:iso-8859-15:iso-8859-2:utf-8" Cheers, -- Thomas Ro

Re: [PATCH, RFC] mouse tracking support

On 2007-05-31 06:39:45 -0600, Kyle Wheeler wrote: >> | $ printf "\033[?9h"# turn X10 mouse reporting on >> | $ printf "\033[?1000h" # turn mouse reporting on >> | $ printf "\033[?1000l" # turn mouse reporting off > > ... should I try the first two before starting mutt? No,

Re: [PATCH, RFC] mouse tracking support

Hi Alain, On Wednesday, May 30 at 11:14 AM, quoth Alain Bench: The terminal has to report mouse events to applications. Terminal.app doesn't appear to be doing mouse reporting at all. Well, I figured Terminal.app wouldn't (or at it would be a bear to do, at least), but I don't use Terminal

[Mutt] #2901: wrong parameter micalg with mutt 1.5.15 and gpgme

#2901: wrong parameter micalg with mutt 1.5.15 and gpgme I compiled a clean mutt 1.5.15 with gcc 3.4.5 as follows: {{{ ./configure --prefix=/usr \ --build=i386-pc-linux-gnu \ --sysconfdir=/etc \ --localstatedir=/var/lib \

Re: [Mutt] #2901: wrong parameter micalg with mutt 1.5.15 and gpgme

#2901: wrong parameter micalg with mutt 1.5.15 and gpgme Changes (by lespocky): * keywords: => gpgme micalg -- Ticket URL:

Re: [PATCH, RFC] mouse tracking support

Hi Kyle, On Wednesday, May 23, 2007 at 19:23:04 -0600, Kyle Wheeler wrote: > trouble getting [mouse tracking] to work on MacOS X. The terminal has to report mouse events to applications. Terminal.app doesn't appear to be doing mouse reporting at all. | $ printf "\033[?9h" # turn