will help much here
> because much of your time is probably spent waiting for I/O).
I don't think I understand what you mean by dummy info in a thread
object.
> I don't think there would be any downside to doing this for eager
> consumers like the CLI.
one should think so, yes.
/p
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/8bb52855/attachment.pgp>
vailable
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/23ad4e6a/attachment.pgp>
arl
--
carl.d.worth at intel.com
-- 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/20110527/d94d24fd/attachment.pgp>
On Fri, May 27, 2011 at 2:04 PM, Patrick Totzke
wrote:
> Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011:
>> >> > > Have you tried simply calling list() on your thread
>> >> > > iterator to see how expensive it is? ?My bet is that it's quite cheap,
>> >> > > both
lable
Type: application/pgp-signature
Size: 965 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/d45b6e14/attachment.pgp>
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/f9cf0cd3/attachment.pgp>
This is the best way to make the displayed output for
decrypted/verified messages clearer. The special sigstatus and
encstatus buttons are now displayed under the part header button. The
part header button is also tweaked to provide information to user
about how to proces crypto.
---
This patch
Most of the time, every entry in the list of identities has the same user name
part. It can then be filled in automatically, and the user can only be prompted
for the email address, which makes the interface much cleaner.
---
Hi Jameson,
Once again, a very good suggestion. I had doubts at first
When replying, the From: address is already filled in by notmuch reply, so most
of the time there is no need to prompt the user for it.
---
Hi Jameson,
You're right, this is mostly annoying when replying to messages. Here's a fix.
Regards,
Thomas
emacs/notmuch-mua.el |7 +--
1 files
On Thu, 26 May 2011 10:20:21 -0700, Carl Worth wrote:
> On Thu, 26 May 2011 09:31:19 +0100, Patrick Totzke googlemail.com> wrote:
> > Wow. This reads really complicated. All I want to say is:
> > if I change tags in my search-results view, I get Xapian errors :)
>
> Yes, that's frustrating. I
notmuchmail.org/pipermail/notmuch/attachments/20110527/7eea47d9/attachment.pgp>
ble
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/31cfbfc8/attachment-0001.pgp>
This is the best way to make the displayed output for
decrypted/verified messages clearer. The special sigstatus and
encstatus buttons are now displayed under the part header button. The
part header button is also tweaked to provide information to user
about how to proces crypto.
---
We probably shouldn't have been doing this anyway, but we do it here
specifically because we don't want the content of the
application/pgp-encrypted parts to be displayed and cluttering the
message show.
---
emacs/notmuch-show.el |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
The primary goal here is to keep the decrypted output as similarly
structured as undecrypted output as possible. Now, when decrypting
parts, only the original encrypted part is replaced by the it's
decrypted content. If this part isn't itself a multipart, then all
part numbering should remain
Some folks have complained about the part renumbering that occurs when
the entire multipart/signed part is replaced with the part contents
after verification. This is primarily because it incurs an additional
computational cost to retrieve individual parts, since verification
has to be performed
Ok. So I very much hope this patch series satisfies those who were
bothered by the part renumbering that was happening when PGP/MIME
parts were processed. For signed messages we no longer modify the
parts at all, so numbering always remains constant, and for encrypted
messages the numbering will
7 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110527/595cc12b/attachment.patch>
On Thu, 26 May 2011 14:31:30 -0700, Carl Worth wrote:
> On Thu, 26 May 2011 14:26:34 +0400, Dmitry Kurochkin gmail.com> wrote:
> > It is called indirectly. What is the best way to fix it? I imagine
> > that we can replace `isearch-range-invisible' function with another one,
> > which would
The patch adds `notmuch-isearch-range-invisible' function which
is the same as `isearch-range-invisible' but with fixed Emacs bug
`notmuch-isearch-range-invisible' instead of the original
`isearch-range-invisible' when in `notmuch-show-mode'.
---
emacs/notmuch-wash.el | 67
Reply to sender is currently bound to R
---
emacs/notmuch-mua.el | 10 ++
emacs/notmuch-show.el |8 +++-
emacs/notmuch.el |2 +-
3 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/emacs/notmuch-mua.el b/emacs/notmuch-mua.el
index 61a723b..c9c5854 100644
---
notmuch.1 | 13 +
notmuch.c | 10 ++
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/notmuch.1 b/notmuch.1
index a1c7fa8..c434e77 100644
--- a/notmuch.1
+++ b/notmuch.1
@@ -388,6 +388,19 @@ Includes subject and quoted message body.
.BR headers\-only
Possible values are "sender" which replies just to sender and
"all" (the default).
More precisely reply to sender follows these rules:
reply only to sender unless it was the user
reply only to all people on the to line unless they were all the user
reply to all people on the cc line
Many thanks for the rapid response: I have modified the
patches as suggested and this version includes the
necessary documentation changes. I have also modified the
emacs portion to apply to current master.
Best wishes
Mark
These patches implement a reply to sender function.
On the command
On 05/26/2011 06:04 PM, Carl Worth wrote:
> 2. The hello screen is now lying a bit by saying "all tags".
>
>Perhaps if the user has the notmuch-hello-hide-tags variable set to
>non-nil the text might change somewhat? I'm not sure to what exactly.
maybe "all non-hidden tags" ?
Excerpts from Austin Clements's message of Thu May 26 22:43:02 +0100 2011:
> http://notmuch.198994.n3.nabble.com/notmuch-s-idea-of-concurrency-failing-an-invocation-tp2373468p2565731.html
ah, good old peterson :P thanks.
> > > Though, Patrick, that solution doesn't address your problem.? On the
>
When replying, the From: address is already filled in by notmuch reply, so most
of the time there is no need to prompt the user for it.
---
Hi Jameson,
You're right, this is mostly annoying when replying to messages. Here's a fix.
Regards,
Thomas
emacs/notmuch-mua.el |7 +--
1 files
Most of the time, every entry in the list of identities has the same user name
part. It can then be filled in automatically, and the user can only be prompted
for the email address, which makes the interface much cleaner.
---
Hi Jameson,
Once again, a very good suggestion. I had doubts at first
Ok. So I very much hope this patch series satisfies those who were
bothered by the part renumbering that was happening when PGP/MIME
parts were processed. For signed messages we no longer modify the
parts at all, so numbering always remains constant, and for encrypted
messages the numbering will
We probably shouldn't have been doing this anyway, but we do it here
specifically because we don't want the content of the
application/pgp-encrypted parts to be displayed and cluttering the
message show.
---
emacs/notmuch-show.el |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
The primary goal here is to keep the decrypted output as similarly
structured as undecrypted output as possible. Now, when decrypting
parts, only the original encrypted part is replaced by the it's
decrypted content. If this part isn't itself a multipart, then all
part numbering should remain
Some folks have complained about the part renumbering that occurs when
the entire multipart/signed part is replaced with the part contents
after verification. This is primarily because it incurs an additional
computational cost to retrieve individual parts, since verification
has to be performed
On Fri, 27 May 2011 11:14:59 +0200, Thomas Jost schno...@schnouki.net wrote:
You're right, this is mostly annoying when replying to messages. Here's a fix.
Awesome. Thanks, Thomas. Tested and works great.
jamie.
pgpQ1DnF9hcWt.pgp
Description: PGP signature
Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011:
Have you tried simply calling list() on your thread
iterator to see how expensive it is? My bet is that it's quite cheap,
both memory-wise and CPU-wise.
Funny thing:
q=Database().create_query('*')
On Fri, 27 May 2011 03:27:35 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Ok. So I very much hope this patch series satisfies those who were
bothered by the part renumbering that was happening when PGP/MIME
parts were processed. For signed messages we no longer modify the
From the commit message:
This patch allows the user to define various sections that will
be displayed in notmuch-hello. I tried to keep the section
description flexible, so it allows different queries for the
tag buttons and the counts next to them, as well as hiding items
with zero results.
This is the best way to make the displayed output for
decrypted/verified messages clearer. The special sigstatus and
encstatus buttons are now displayed under the part header button. The
part header button is also tweaked to provide information to user
about how to proces crypto.
---
This patch
On Fri, May 27, 2011 at 2:04 PM, Patrick Totzke
patricktot...@googlemail.com wrote:
Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011:
Have you tried simply calling list() on your thread
iterator to see how expensive it is? My bet is that it's quite cheap,
On Wed, 1 Dec 2010 21:27:52 +0100, Joel Borggrén-Franck
joel.borggren.fra...@gmail.com wrote:
From: Joel Borggrén-Franck j...@codehouse.se
Change #!/bin/bash at start of tests to #!/usr/bin/env bash. That way
systems running on bash 4 can prepend bash = 4 to path before
running the tests.
I forgot to run the test suite with the previous patch, which
revealed some minor formatting problems, updated patch in the
attachment.
From bca5a58d7910b6d46a782db787dfe07e2fcf21e1 Mon Sep 17 00:00:00 2001
From: Daniel Schoepe daniel.scho...@googlemail.com
Date: Thu, 26 May 2011 23:03:22 +0200
Accidentally attached the old file again, sorry for the noise.
From cafc93e3364955cab70885fec740fee87bc3248e Mon Sep 17 00:00:00 2001
From: Daniel Schoepe daniel.scho...@googlemail.com
Date: Thu, 26 May 2011 23:03:22 +0200
Subject: [PATCH] emacs: User-defined sections in notmuch-hello
This patch
On Tue, 10 May 2011 10:25:08 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
The patch replaces all (message (buffer-string)) calls in emacs
tests with (princ (buffer-string)). This avoids accidentally
interpreting '%' as format specifiers and makes code simpler
because we do not
This is an amended patch which uses `isearch-range-invisible' from Emacs
trunk r104393 (includes the second patch from #8721).
Regards,
Dmitry
From d56f2c308c995639aad04f0e5388b52912e603b0 Mon Sep 17 00:00:00 2001
From: Dmitry Kurochkin dmitry.kuroch...@gmail.com
Date: Fri, 27 May 2011 01:35:09
On Fri, 27 May 2011 03:27:35 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Ok. So I very much hope this patch series satisfies those who were
bothered by the part renumbering that was happening when PGP/MIME
parts were processed. For signed messages we no longer modify the
45 matches
Mail list logo
