On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> So what would be a good format? One possibility would be to
> NULL-delimit the query part; as distasteful as I find that, this part
> of the search output isn't meant for user consumption. Though I fear
> this is endemic to the dual ro
Quoth Sebastian Spaeth on Aug 12 at 10:07 am:
> On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements
> wrote:
> > So what would be a good format? One possibility would be to
> > NULL-delimit the query part; as distasteful as I find that, this part
> > of the search output isn't meant for user con
Quoth Sebastian Spaeth on Aug 12 at 10:07 am:
> On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> > So what would be a good format? One possibility would be to
> > NULL-delimit the query part; as distasteful as I find that, this part
> > of the search output isn't meant for user consum
On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> So what would be a good format? One possibility would be to
> NULL-delimit the query part; as distasteful as I find that, this part
> of the search output isn't meant for user consumption. Though I fear
> this is endemic to the dual ro
Quoth myself on Jul 13 at 2:57 pm:
> Quoth Pieter Praet on Jul 13 at 4:16 pm:
> > Jamie Zawinski once said/wrote [1]:
> > 'Some people, when confronted with a problem, think "I know,
> > I'll use regular expressions." Now they have two problems.'
> >
> > With this in mind, I set out to get r
Quoth myself on Jul 13 at 2:57 pm:
> Quoth Pieter Praet on Jul 13 at 4:16 pm:
> > Jamie Zawinski once said/wrote [1]:
> > 'Some people, when confronted with a problem, think "I know,
> > I'll use regular expressions." Now they have two problems.'
> >
> > With this in mind, I set out to get r
What about encoding in notmuch the elements composing the line, print
the elements with a separator that would be encoded if it appears in
an element, then do the reverse in emacs. One such encoding might be
URL-encoding.
Servilio
What about encoding in notmuch the elements composing the line, print
the elements with a separator that would be encoded if it appears in
an element, then do the reverse in emacs. One such encoding might be
URL-encoding.
Servilio
___
notmuch mailing lis
On Wed, 13 Jul 2011 14:57:21 -0400, Austin Clements wrote:
> Quoth Pieter Praet on Jul 13 at 4:16 pm:
> > On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements
> > wrote:
> > > Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > > > TL;DR: I can haz regex pl0x?
> > >
> > > Oof, what a pain. I'm happy
On Wed, 13 Jul 2011 14:57:21 -0400, Austin Clements wrote:
> Quoth Pieter Praet on Jul 13 at 4:16 pm:
> > On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements
> > wrote:
> > > Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > > > TL;DR: I can haz regex pl0x?
> > >
> > > Oof, what a pain. I'm happy
On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > TL;DR: I can haz regex pl0x?
>
> Oof, what a pain. I'm happy to change the output format of search; I
> hadn't realized how difficult it would be to parse. In fact, I'm not
> sure it's eve
* pieter at praet.org [2011-07-13 Wed 15:16]
> David, would you mind rebasing it?
I'm sorry, I'm not likely to have time to do this.
Quoth Pieter Praet on Jul 13 at 4:16 pm:
> On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements
> wrote:
> > Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > > TL;DR: I can haz regex pl0x?
> >
> > Oof, what a pain. I'm happy to change the output format of search; I
> > hadn't realized how difficul
Quoth Pieter Praet on Jul 13 at 4:16 pm:
> On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> > Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > > TL;DR: I can haz regex pl0x?
> >
> > Oof, what a pain. I'm happy to change the output format of search; I
> > hadn't realized how difficult i
* pie...@praet.org [2011-07-13 Wed 15:16]
> David, would you mind rebasing it?
I'm sorry, I'm not likely to have time to do this.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
On Mon, 11 Jul 2011 17:05:32 -0400, Austin Clements wrote:
> Quoth Pieter Praet on Jul 11 at 10:43 pm:
> > TL;DR: I can haz regex pl0x?
>
> Oof, what a pain. I'm happy to change the output format of search; I
> hadn't realized how difficult it would be to parse. In fact, I'm not
> sure it's eve
TL;DR: I can haz regex pl0x?
I've updated the regex a bit to prevent it from choking on the whole
"parens in subject vs. parens around tags vs. parens around matching
Message-Id's" deal, but it still causes errors in the search buffer due
to the list of Message-Id's being cut off at a seemingly
Quoth Pieter Praet on Jul 11 at 10:43 pm:
> TL;DR: I can haz regex pl0x?
Oof, what a pain. I'm happy to change the output format of search; I
hadn't realized how difficult it would be to parse. In fact, I'm not
sure it's even parsable by regexp, because the message ID's themselves
could contain
Quoth Pieter Praet on Jul 11 at 10:43 pm:
> TL;DR: I can haz regex pl0x?
Oof, what a pain. I'm happy to change the output format of search; I
hadn't realized how difficult it would be to parse. In fact, I'm not
sure it's even parsable by regexp, because the message ID's themselves
could contain
TL;DR: I can haz regex pl0x?
I've updated the regex a bit to prevent it from choking on the whole
"parens in subject vs. parens around tags vs. parens around matching
Message-Id's" deal, but it still causes errors in the search buffer due
to the list of Message-Id's being cut off at a seemingly
20 matches
Mail list logo
