On Mon, 16 May 2011 13:59:51 -0700, Carl Worth wrote:
> So what I'd love to see from here is a commit with a description like
> the above, and then a test case looking like your example.
>
> From there, I'd next like a new version of the commit that gets the
> intended behavior with less code
e: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110517/cad2c922/attachment.pgp>
We're not properly concatenating the Received headers if we parse them
while requesting a header that isn't Received.
this fixes notmuch-reply address detection in a bunch of situations.
diff --git a/lib/message-file.c b/lib/message-file.c
index 7722832..dd0f698 100644
--- a/lib/message-file.c
Hi,
On Mon, 16 May 2011 09:29:19 -0700, Jameson Graef Rollins wrote:
> On Mon, 16 May 2011 11:27:52 -0400, Jesse Rosenthal
> wrote:
> > The decision, if I remember correctly, was that regions are so intuitive
> > for emacs users, and many people reported trying to tag by region
> > without
On Mon, 16 May 2011 11:52:43 +0200, Thomas Jost
wrote:
> On Mon, 16 May 2011 19:29:07 +1000, Stewart Smith flamingspork.com> wrote:
> (people who don't use or like ido may want to replace
> ido-completing-read with completing-read)
I couldn't get ido to work at all (Ubuntu Natty). It would
lol, made my day!
Simon
On 05/16/2011 11:05 PM, Daniel Kahn Gillmor wrote:
> On 05/16/2011 04:50 PM, Daniel Kahn Gillmor wrote:
>> So a message like this:
>>
>> A???multipart/signed 355339 bytes
>> B ???multipart/mixed 353462 bytes
>> C ???text/plain 235 bytes
>> D ???image/jpeg attachment
On Mon, 16 May 2011 09:29:19 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
On Mon, 16 May 2011 11:27:52 -0400, Jesse Rosenthal jrosent...@jhu.edu
wrote:
The decision, if I remember correctly, was that regions are so intuitive
for emacs users, and many people reported
On Mon, 16 May 2011 13:59:51 -0700, Carl Worth cwo...@cworth.org wrote:
So what I'd love to see from here is a commit with a description like
the above, and then a test case looking like your example.
From there, I'd next like a new version of the commit that gets the
intended behavior with