emacs complains about encoding?

On Wed, May 23, 2012 at 4:15 AM, Michal Sojka wrote: >> I think the current plan is to use the same decoding lookup table that >> notmuch-show is using in reply too. > > Which table do you refer to? notmuch-show-handlers-for? Yep, that looks like the right thing. I've been particularly busy

Re: emacs complains about encoding?

On Wed, May 23, 2012 at 4:15 AM, Michal Sojka sojk...@fel.cvut.cz wrote: I think the current plan is to use the same decoding lookup table that notmuch-show is using in reply too. Which table do you refer to? notmuch-show-handlers-for? Yep, that looks like the right thing. I've been

emacs complains about encoding?

Tomi Ollila writes: > Michal Sojka writes: > >> Hello Adam, >> >> Adam Wolfe Gordon writes: >>> It turns out it's actually not the emacs side, but an interaction >>> between our JSON reply format and emacs. >>> >>> The JSON reply (and show) code includes part content for

Re: emacs complains about encoding?

Tomi Ollila tomi.oll...@iki.fi writes: Michal Sojka sojk...@fel.cvut.cz writes: Hello Adam, Adam Wolfe Gordon awg+notm...@xvx.ca writes: It turns out it's actually not the emacs side, but an interaction between our JSON reply format and emacs. The JSON reply (and show) code includes part

emacs complains about encoding?

Michal Sojka writes: > Hello Adam, > > Adam Wolfe Gordon writes: >> It turns out it's actually not the emacs side, but an interaction >> between our JSON reply format and emacs. >> >> The JSON reply (and show) code includes part content for all text/* >> parts except

emacs complains about encoding?

Hello Adam, Adam Wolfe Gordon writes: > It turns out it's actually not the emacs side, but an interaction > between our JSON reply format and emacs. > > The JSON reply (and show) code includes part content for all text/* > parts except text/html. Because all JSON is

Re: emacs complains about encoding?

Hello Adam, Adam Wolfe Gordon awg+notm...@xvx.ca writes: It turns out it's actually not the emacs side, but an interaction between our JSON reply format and emacs. The JSON reply (and show) code includes part content for all text/* parts except text/html. Because all JSON is required to be

Re: emacs complains about encoding?

Michal Sojka sojk...@fel.cvut.cz writes: Hello Adam, Adam Wolfe Gordon awg+notm...@xvx.ca writes: It turns out it's actually not the emacs side, but an interaction between our JSON reply format and emacs. The JSON reply (and show) code includes part content for all text/* parts except

emacs complains about encoding?

On Wed, May 16, 2012 at 3:24 AM, Tomi Ollila wrote: > Haa, It doesn't matter which is the original encoding of the message; > > notmuch reply id:20120515194455.B7AD5100646 at guru.guru-group.fi > > where ?notmuch show --format=raw ^^^ ?outputs (among other lines): > > ?Content-Type: text/plain;

Re: emacs complains about encoding?

On Wed, May 16, 2012 at 3:24 AM, Tomi Ollila tomi.oll...@iki.fi wrote: Haa, It doesn't matter which is the original encoding of the message; notmuch reply id:20120515194455.b7ad5100...@guru.guru-group.fi where  notmuch show --format=raw ^^^  outputs (among other lines):  Content-Type:

emacs complains about encoding?

On Wed, May 16 2012, Jani Nikula wrote: > Tomi Ollila writes: >> IT h\344ppens. >> >> Attempting to reply to this email should expose the problem. >> >> \304\344li\366 \344l\344 ly\366, \366\366li\344 l\344ikkyy. (\nnn text above hand-(query)-replaced) > > The problem bisected to

emacs complains about encoding?

Tomi Ollila writes: > IT h?ppens. > > Attempting to reply to this email should expose the problem. > > ??li? ?l? ly?, ??li? l?ikkyy. The problem bisected to f6c170fabca8f39e74705e3813504137811bf162 ("emacs: Correctly quote non-text/plain parts in reply"). The commit reverts cleanly, replying

emacs complains about encoding?

On Tue, May 15 2012, Tomi Ollila wrote: > IT h?ppens. > > Attempting to reply to this email should expose the problem. > > ??li? ?l? ly?, ??li? l?ikkyy. This email: id:"20120515194455.B7AD5100646 at guru.guru-group.fi" was supposed to be reply to email id:"878vgzrvik.fsf at beesknees.cern.ch"

Re: emacs complains about encoding?

Tomi Ollila tomi.oll...@iki.fi writes: IT häppens. Attempting to reply to this email should expose the problem. Ääliö älä lyö, ööliä läikkyy. The problem bisected to f6c170fabca8f39e74705e3813504137811bf162 (emacs: Correctly quote non-text/plain parts in reply). The commit reverts cleanly,

Re: emacs complains about encoding?

On Wed, May 16 2012, Jani Nikula wrote: Tomi Ollila tomi.oll...@iki.fi writes: IT h\344ppens. Attempting to reply to this email should expose the problem. \304\344li\366 \344l\344 ly\366, \366\366li\344 l\344ikkyy. (\nnn text above hand-(query)-replaced) The problem bisected to

emacs complains about encoding?

IT h?ppens. Attempting to reply to this email should expose the problem. ??li? ?l? ly?, ??li? l?ikkyy. -- Tomi

Re: emacs complains about encoding?

IT häppens. Attempting to reply to this email should expose the problem. Ääliö älä lyö, ööliä läikkyy. -- Tomi ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch

Re: emacs complains about encoding?

On Tue, May 15 2012, Tomi Ollila tomi.oll...@iki.fi wrote: IT häppens. Attempting to reply to this email should expose the problem. Ääliö älä lyö, ööliä läikkyy. This email: id:20120515194455.b7ad5100...@guru.guru-group.fi was supposed to be reply to email

emacs complains about encoding?

Dear all, i've just yesterday pulled from git recent version of notmuch and started to use it. With respect to previous version (~2months old?) I have now problem, that when I receive from somebody an email using 'whatever' (understood uknown) encoding, the email is in emacs displayed correctly.

emacs complains about encoding?

Dear all, i've just yesterday pulled from git recent version of notmuch and started to use it. With respect to previous version (~2months old?) I have now problem, that when I receive from somebody an email using 'whatever' (understood uknown) encoding, the email is in emacs displayed correctly.