This may just be an issue with the Terminal program in OS X, but I'm
having some problems with the ACS characters in the threading (I'm not
setting $ascii_chars) having breaks between them.
The behavior can be seen here:
http://soulrebels.com/mutt_threads.png
Normally (sorry Thomas), I just use x
On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
> This may just be an issue with the Terminal program in OS X, but I'm
> having some problems with the ACS characters in the threading (I'm not
> setting $ascii_chars) having breaks between them.
>
> The behavior can be seen here:
> htt
Hi,
I have mail in mutt with the an encoded Subject: line which seems to decode
wrong (the German Umlaut ü is not shown); how could I decode the line
Subject:
=?UTF-8?B?Uu+/vWNrc2VuZHVuZyAoTnIuIEUtQS0yMTcyKSBhYmdlc2NobG9zc2Vu?=
to UTF-8 chars to check what is wrong? Thanks
matthia
On Sun, Oct 28, 2012 at 02:53:30PM -0500, David Champion wrote:
> * On 28 Oct 2012, Remco Rijnders wrote:
> > >others, it was working fine). I was just monkeying around with my GPG
> > >options, and I wonder if that's still happening. I think I may have
> > >figured it out, but I'd love some con
On Tue, Oct 30, 2012 at 05:08:55PM -0500, Derek Martin wrote:
> Bizzare. The only factor which is obvious to me as a possible
> differentiating factor is that the first is quoted printable, and the
> second is plain text. I'm assuming that the first was QP because
> there was a line that started
On Tue, Oct 30, 2012 at 02:15:45PM +0100, Dennis Preiser wrote:
> On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
> > This may just be an issue with the Terminal program in OS X, but I'm
> > having some problems with the ACS characters in the threading (I'm not
> > setting $ascii_char
Derek Martin wrote:
> Bizzare. The only factor which is obvious to me as a possible
> differentiating factor is that the first is quoted printable, and the
> second is plain text. I'm assuming that the first was QP because
> there was a line that started with "from", whereas the second had
> none
Kevin J. McCarthy wrote:
> Now, I'm not sure *why* mutt would be doing this. Perhaps someone more
> knowledgeable will have suggestions. Do you have any strange hooks or
> non-default gpg settings in your muttrc that would turn off QP?
Sorry to reply to myself. Looking at the mutt source, the
p
On Tue, Oct 30, 2012 at 07:45:27PM -0700, Kevin J. McCarthy wrote:
> Interestingly if I manually strip the whitespace and canonicalize line
> endings, the signature passes. So somehow you are correctly generating
> the signature (with trailing whitespace removed), but are sending the
> email out w
