On Sat, 07 May 2011 11:14:08 +0200, Pieter Praet wrote:
> On Fri, 06 May 2011 18:06:47 -0700, Jameson Graef Rollins finestructure.net> wrote:
> > On Fri, 6 May 2011 19:55:26 -0400, Austin Clements
> > wrote:
> > > Perhaps text summary output should *always* do this. The text summary
> > > form
On Fri, 06 May 2011 18:06:47 -0700, Jameson Graef Rollins wrote:
> On Fri, 6 May 2011 19:55:26 -0400, Austin Clements
> wrote:
> > Perhaps text summary output should *always* do this. The text summary
> > format is meant half for user consumption and half for emacs
> > consumption and allowing
On Sat, 07 May 2011 11:14:08 +0200, Pieter Praet wrote:
> On Fri, 06 May 2011 18:06:47 -0700, Jameson Graef Rollins
> wrote:
> > On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> > > Perhaps text summary output should *always* do this. The text summary
> > > format is meant half for
On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> Perhaps text summary output should *always* do this. The text summary
> format is meant half for user consumption and half for emacs
> consumption and allowing newlines that don't indicate the end of a
> summary line seems bad for *both*
On Fri, 06 May 2011 18:06:47 -0700, Jameson Graef Rollins
wrote:
> On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> > Perhaps text summary output should *always* do this. The text summary
> > format is meant half for user consumption and half for emacs
> > consumption and allowing ne
Sanitize "Subject:" and "Author:" fields to not contain control
characters for sanitized_text format.
When a Subject field contains encoded CRLF sequences, these sequences
would appear unfiltered in the output of notmuch search. This confused
the notmuch emacs interface leading to "Unexpected Outp
Perhaps text summary output should *always* do this. The text summary
format is meant half for user consumption and half for emacs
consumption and allowing newlines that don't indicate the end of a
summary line seems bad for *both* use cases.
On Fri, May 6, 2011 at 7:17 PM, Florian Friesdorf wro
On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> Perhaps text summary output should *always* do this. The text summary
> format is meant half for user consumption and half for emacs
> consumption and allowing newlines that don't indicate the end of a
> summary line seems bad for *both*
On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> Perhaps text summary output should *always* do this. The text summary
> format is meant half for user consumption and half for emacs
> consumption and allowing newlines that don't indicate the end of a
> summary line seems bad for *both*
On Fri, 6 May 2011 19:55:26 -0400, Austin Clements wrote:
> Perhaps text summary output should *always* do this. The text summary
> format is meant half for user consumption and half for emacs
> consumption and allowing newlines that don't indicate the end of a
> summary line seems bad for *both*
Perhaps text summary output should *always* do this. The text summary
format is meant half for user consumption and half for emacs
consumption and allowing newlines that don't indicate the end of a
summary line seems bad for *both* use cases.
On Fri, May 6, 2011 at 7:17 PM, Florian Friesdorf wro
Sanitize "Subject:" and "Author:" fields to not contain control
characters for sanitized_text format.
When a Subject field contains encoded CRLF sequences, these sequences
would appear unfiltered in the output of notmuch search. This confused
the notmuch emacs interface leading to "Unexpected Outp
12 matches
Mail list logo
