Hi Jamie,
any chance of getting this patch into 0.6?
It would enable me to run the tests for the nixos package without
patching.
You could pull it from:
git://github.com/chaoflow/notmuch.git
branch: for-review/test-fixes
commit: d8842075b1ff6f008e60aced5f4e0b4d7ac79515
regards
On Mon, 18 Apr
On Fri, 06 May 2011 11:09:19 +0200, Florian Friesdorf wrote:
> any chance of getting this patch into 0.6?
Hi, Florian. Yes, I have included this patch in the
release-candidate/0.6 branch.
jamie.
pgpkckcJzTQkq.pgp
Description: PGP signature
___
notmu
Hi, folks. As some of you already know, I am trying to put together a
release candidate for a 0.6 release that we can present to cworth for
approval. This branch can be found in my public notmuch repository in
the "release-candidate/0.6" branch:
git remote add jrollins git://finestructure.net/no
Hi, Filipe. I notice that you have been submitting a lot of patches for
vim support. As you may have seen, I'm trying to put together a release
candidate for notmuch 0.6. Since I know nothing about vim, would you be
willing to prepare a patch set that includes all of the patches to vim
support t
On Fri, 06 May 2011 12:47:35 -0700, Jameson Graef Rollins
wrote:
> On Fri, 06 May 2011 11:09:19 +0200, Florian Friesdorf
> wrote:
> > any chance of getting this patch into 0.6?
>
> Hi, Florian. Yes, I have included this patch in the
> release-candidate/0.6 branch.
great! all tests pass now o
On Fri, 06 May 2011 12:46:34 -0700, Jameson Graef Rollins
wrote:
> I might try to add a couple of more things before declaring the
> candidate release-ready, but this is more-or-less it. Please start
> using this branch "in production" as much as possible, so that we can
> build up a chorus of s
On Mon, 18 Apr 2011 19:41:39 +0200, Florian Friesdorf wrote:
> My first patch send to the list, not sure whether done properly.
Just fine, Florian. Thanks for the contribution!
One small thing you might do differently in the future is to tweak the
email message to read exactly like a commit mess
On Fri, 06 May 2011 14:06:22 -0700, Carl Worth wrote:
(..)
thx for all the suggestions - mail marked and will reread before the
next patch.
--
Florian Friesdorf
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: f...@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafase
In the release-candidate/0.6, the emacs UI is still not able to handle
messages where control characters are contained in the Subject: or
Author: fields.
As suggested by Pieter Prat, I turned Andreas Amann's patch into a
separate format.
The patch works and is very useful for me.
Is the general
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
Hi Carl,
On Fri, 06 May 2011 14:06:22 -0700, Carl Worth wrote:
> On Mon, 18 Apr 2011 19:41:39 +0200, Florian Friesdorf
> wrote:
> > My first patch send to the list, not sure whether done properly.
>
> Just fine, Florian. Thanks for the contribution!
>
> One small thing you might do different
On Fri, 06 May 2011 12:46:34 -0700, Jameson Graef Rollins
wrote:
> Hi, folks. As some of you already know, I am trying to put together a
> release candidate for a 0.6 release that we can present to cworth for
> approval. This branch can be found in my public notmuch repository in
> the "release
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
Thanks for pulling this together.
I sent two patches to the list on March 16. They were a bug fix to
allow notmuch to correctly handle some poorly formatted email. Nobody
ever replied, but I'd like to see the bug fixed nonetheless, as it
results in unreadable mail. Since I've actually seen such
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 19:56:30 -0400, James Vasile
wrote:
> Thanks for pulling this together.
>
> I sent two patches to the list on March 16. They were a bug fix to
> allow notmuch to correctly handle some poorly formatted email. Nobody
> ever replied, but I'd like to see the bug fixed nonethele
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 May 06, 2011 at 07:56 PM -0400, James Vasile wrote:
Thanks for pulling this together.
I sent two patches to the list on March 16. They were a bug fix to
allow notmuch to correctly handle some poorly formatted email. Nobody
ever replied, but I'd like to see the bug fixed nonetheless, as it
-
Florian Friesdorf
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: flo at chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/5117fc95/attachment.pgp>
ble
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/0e983010/attachment.pgp>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/2f846e24/attachment.pgp>
mail.org/pipermail/notmuch/attachments/20110506/0f516cc3/attachment.pgp>
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/3529d596/attachment.pgp>
Spaeth
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/9d463279/attachment.pgp>
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/ca25f918/attachment.pgp>
,blafasel,OFTC
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/dcc012e0/attachment-0001.pgp>
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
Thanks for pulling this together.
I sent two patches to the list on March 16. They were a bug fix to
allow notmuch to correctly handle some poorly formatted email. Nobody
ever replied, but I'd like to see the bug fixed nonetheless, as it
results in unreadable mail. Since I've actually seen such
---
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110506/c644e96d/attachment.pgp>
On May 06, 2011 at 07:56 PM -0400, James Vasile wrote:
>Thanks for pulling this together.
>
>I sent two patches to the list on March 16. They were a bug fix to
>
>allow notmuch to correctly handle some poorly formatted email. Nobody
>ever replied, but I'd like to see the bug fixed nonetheless, a
30 matches
Mail list logo
