On Thu, 15 Apr 2010, Carl Worth wrote:
> On Tue, 13 Apr 2010 18:37:57 +0200, Gregor Hoffleit
> wrote:
> > The test suite doesn't yet cover --format=json output nor UTF-8 in
> > subject or body.
> >
> > This patch starts with test cases for 'search --format=json' and
> > 'show --format=json'.
>
Before and after the assignment operator, no spaces are allowed.
I don't know if there are any /bin/sh which allow spaces, but at least
in bash, csh and zsh, the former code was no valid assigment.
---
configure |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure
---
emacs/notmuch.el | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index be09f42..17e0e86 100644
--- a/emacs/notmuch.el
+++ b/emacs/notmuch.el
@@ -696,6 +696,15 @@ characters as well as `_.+-'.
(apply 'notmuch-call-notm
Sebastian Spaeth writes:
> On 2010-04-14, Jason White wrote:
> > > Also add a --sort=unsorted command line option to notmuch search to test
> > > this.
> >
> > Does this provide relevance-ranked search results? I think relevance ranking
> > is the Xapian default if a sort order isn't specified.
>
On Thu, 15 Apr 2010 08:16:09 -0400, Servilio Afre Puentes
wrote:
> ---
> emacs/notmuch.el | 11 ++-
> 1 files changed, 10 insertions(+), 1 deletions(-)
>
Thanks very much for the contribution. It would be nice (and Carl will
almost certainly ask for this) to have a meaningful commit
Define a new `mail-user-agent' (`notmuch-user-agent') and use it by
default. Re-arrange various routines that send mail to use this
(compose, reply, forward). Insert a `User-Agent:' header by default.
---
emacs/notmuch-hello.el |2 +
emacs/notmuch-mua.el | 94 ++
On Thu, 15 Apr 2010 16:50:27 +0100, David Edmondson wrote:
> Define a new `mail-user-agent' (`notmuch-user-agent') and use it by
> default. Re-arrange various routines that send mail to use this
> (compose, reply, forward). Insert a `User-Agent:' header by default.
I meant to add that this was a
On Tue, 06 Apr 2010 19:01:07 +0200, Michal Sojka wrote:
> here is my report of git's test-lib relicensing. The following is the
> last list sent to me by Junio. I guess you have this information
> somewhere in your mailbox as well.
Hi Michal,
Thanks for following up with this.
> There are three
On Wed, 14 Apr 2010 09:44:16 +0200, "Sebastian Spaeth"
wrote:
> On 2010-04-13, Carl Worth wrote:
> > No, wait! I want more from you. :-)
>
> Sigh, they always want more :-)
Sorry about that. :-)
> See the "sister mail" to this thread, in which I simply added the whole
> shebang to notmuch.el (
On Thu, 15 Apr 2010 10:33:46 +0200, Michal Sojka wrote:
> are you still interrested in modular test suite from git? If so, could
> you please look at id:87mxxg7bxo@steelpick.2x.cz and tell me your
> opinion. I'm still updating the modularized tests to match the state in
> master but every chan
On Wed, 14 Apr 2010 17:59:01 -0700, Carl Worth wrote:
> We could fix all[*] the bugs of "*" by changing it to simply call the
> new region-based tagging function. The only concern I have with that is
> that it might be significantly slower, (it will execute N "notmuch tag"
> commands to tag the N
On Thu, 15 Apr 2010 16:04:38 -0400, Jesse Rosenthal wrote:
> Not quite true: the region command only executes one "notmuch tag"
> command over "id:X or id:Y or id:Z or ...".
Sorry -- I meant, of course: over "thread:X or thread:Y or thread:Z or ..."
__
One of the searches that I use most frequently, (for mail that I want to
respond to on a fairly timely basis), is
tag:inbox and tag:to-me [*]
Sometimes, this search will show a large mailing-list thread with only a
few messages open. Perhaps part-way through the thread, someone st
On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth wrote:
> Some people will claim (and I've even agreed) that the space bar is too
> magic. But this bug also happens with an explicit command to archive the
> current thread (such as hitting 'a').
>
> I think the fix is to change these commands to only
On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth wrote:
> One of the searches that I use most frequently, (for mail that I want to
> respond to on a fairly timely basis), is
>
> tag:inbox and tag:to-me [*]
>
> Sometimes, this search will show a large mailing-list thread with only a
>
On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth wrote:
> A bad bug occurs when paging through the thread with the space
> bar. After showing me these few messages, it will then proceed to
> archive *all* the messages in the thread (not only those it showed
> me). And I'm likely to be unaware of thi
Does anyone know how to "bounce" a message, in the mutt sense of the
term where the message is send unaltered to a new recipient, in
notmuch/emacs? I can't find any way to do it with message-mode. I
think this was very useful feature in mutt, and it would be great if we
could add a command to not
I figured we should have a central place to collect feature ideas -
finding them in the mail archives (and IRC logs) is getting old...
So I started a feature idea / request page on the wiki - please comment
and add your own requests.
http://notmuchmail.org/feature-requests/
/D
--
Dirk Hohndel
Notmuch compiles just fine with GMime 2.6, so accept it in the configure
script.
---
configure |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index eebe075..d4d462f 100755
--- a/configure
+++ b/configure
@@ -188,6 +188,11 @@ if pkg-config --modve
On Thu, 15 Apr 2010 16:04:38 -0400, Jesse Rosenthal wrote:
> On Wed, 14 Apr 2010 17:59:01 -0700, Carl Worth wrote:
> > We could fix all[*] the bugs of "*" by changing it to simply call the
> > new region-based tagging function. The only concern I have with that is
> > that it might be significant
On Thu, 15 Apr 2010 14:07:37 -0700, Dirk Hohndel wrote:
> I am always confused about the behavior of 'a' - does it archive the
> current message? Or the current thread? Or the current thread down to
> where I am? Or (as you propose) just the open messages?
>
> I think we really need to spend some
On Thu, 15 Apr 2010 11:51:47 +0200, Gregor Hoffleit wrote:
> Before and after the assignment operator, no spaces are allowed.
> I don't know if there are any /bin/sh which allow spaces, but at least
> in bash, csh and zsh, the former code was no valid assigment.
Thanks, Gregor.
I went through al
Signed-off-by: Dirk Hohndel
---
TODO | 45 +
1 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO
index 14c5fd0..226f243 100644
--- a/TODO
+++ b/TODO
@@ -56,6 +56,24 @@ Change 'a' command in thread-view mode to only archive o
On 2010-04-15, Olly Betts wrote:
> > I would be happy to have it called --sort=relevance too, the unsorted
> > points out potential performance improvements a bit better, IMHO
> > (although they seem to be really small with a warm cache).
>
> When using the results of a search to add/remove tags
Previously, we always sorted the returned results by some string value,
(newest-to-oldest by default), however in some cases (as when applying
tags to a search result) we are not interested in any special order.
This introduces a NOTMUCH_SORT_UNSORTED value that does just that. It is
not used at t
In some cases, we might not be interested in any special sort order, so
this introduces a --sort=unsorted command line option together with its
documentation.
Signed-off-by: Sebastian Spaeth
---
notmuch-search.c |2 ++
notmuch.1| 10 ++
notmuch.c|7 ---
3 fi
It's not neccessary to sort the results before we apply tags. Xapian
contributor Olly Betts says that savings might be bigger with a cold
file cache and (as unsorted implies really sorted by document id) a better
cache locality when applying tags to messages.
Signed-off-by: Sebastian Spaeth
---
On Fri, Apr 16, 2010 at 08:37:04AM +0200, Sebastian Spaeth wrote:
> On 2010-04-15, Olly Betts wrote:
> > Also, sorting by relevance requires more calculations and may require
> > fetching additional data (document length for example).
> >
> > So I think it would make sense for --sort=relevance and
On Thu, 15 Apr 2010, Carl Worth wrote:
> On Tue, 13 Apr 2010 18:37:57 +0200, Gregor Hoffleit
> wrote:
> > The test suite doesn't yet cover --format=json output nor UTF-8 in
> > subject or body.
> >
> > This patch starts with test cases for 'search --format=json' and
> > 'show --format=json'.
>
Before and after the assignment operator, no spaces are allowed.
I don't know if there are any /bin/sh which allow spaces, but at least
in bash, csh and zsh, the former code was no valid assigment.
---
configure |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure
---
emacs/notmuch.el | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index be09f42..17e0e86 100644
--- a/emacs/notmuch.el
+++ b/emacs/notmuch.el
@@ -696,6 +696,15 @@ characters as well as `_.+-'.
(apply 'notmuch-call-notm
Sebastian Spaeth writes:
> On 2010-04-14, Jason White wrote:
> > > Also add a --sort=unsorted command line option to notmuch search to test
> > > this.
> >
> > Does this provide relevance-ranked search results? I think relevance ranking
> > is the Xapian default if a sort order isn't specified.
>
On Thu, 15 Apr 2010 08:16:09 -0400, Servilio Afre Puentes wrote:
> ---
> emacs/notmuch.el | 11 ++-
> 1 files changed, 10 insertions(+), 1 deletions(-)
>
Thanks very much for the contribution. It would be nice (and Carl will
almost certainly ask for this) to have a meaningful commit m
Define a new `mail-user-agent' (`notmuch-user-agent') and use it by
default. Re-arrange various routines that send mail to use this
(compose, reply, forward). Insert a `User-Agent:' header by default.
---
emacs/notmuch-hello.el |2 +
emacs/notmuch-mua.el | 94 ++
On Thu, 15 Apr 2010 16:50:27 +0100, David Edmondson wrote:
> Define a new `mail-user-agent' (`notmuch-user-agent') and use it by
> default. Re-arrange various routines that send mail to use this
> (compose, reply, forward). Insert a `User-Agent:' header by default.
I meant to add that this was a
application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/6439b50d/attachment.pgp>
t --version" output or
something. I can't give any reason for this though. I'll fix this.
-Carl
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/3eacf251/attachment.pgp>
pplication/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/75ca4410/attachment.pgp>
On Wed, 14 Apr 2010 17:59:01 -0700, Carl Worth wrote:
> We could fix all[*] the bugs of "*" by changing it to simply call the
> new region-based tagging function. The only concern I have with that is
> that it might be significantly slower, (it will execute N "notmuch tag"
> commands to tag the N
On Thu, 15 Apr 2010 16:04:38 -0400, Jesse Rosenthal
wrote:
> Not quite true: the region command only executes one "notmuch tag"
> command over "id:X or id:Y or id:Z or ...".
Sorry -- I meant, of course: over "thread:X or thread:Y or thread:Z or ..."
- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/ce17d605/attachment.pgp>
er?
jamie.
-- 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/20100415/2a44b143/attachment.pgp>
On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth wrote:
> One of the searches that I use most frequently, (for mail that I want to
> respond to on a fairly timely basis), is
>
> tag:inbox and tag:to-me [*]
>
> Sometimes, this search will show a large mailing-list thread with only a
>
On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth wrote:
> A bad bug occurs when paging through the thread with the space
> bar. After showing me these few messages, it will then proceed to
> archive *all* the messages in the thread (not only those it showed
> me). And I'm likely to be unaware of thi
dd a command to notmuch-show to do the same thing. Any
suggestions?
jamie.
-- 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/at
I figured we should have a central place to collect feature ideas -
finding them in the mail archives (and IRC logs) is getting old...
So I started a feature idea / request page on the wiki - please comment
and add your own requests.
http://notmuchmail.org/feature-requests/
/D
--
Dirk Hohndel
Notmuch compiles just fine with GMime 2.6, so accept it in the configure
script.
---
configure |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index eebe075..d4d462f 100755
--- a/configure
+++ b/configure
@@ -188,6 +188,11 @@ if pkg-config --modve
ably need to arrange for notmuch to accept search
specifications on stdin or so.
-Carl
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/726d72f7/attachment.pgp>
at we have anything close to that in
the current implementation.
So that's why we're here talking I think. :-)
-Carl
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100415/5d0e75f5/attachment.pgp>
Signed-off-by: Dirk Hohndel
---
TODO | 45 +
1 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO
index 14c5fd0..226f243 100644
--- a/TODO
+++ b/TODO
@@ -56,6 +56,24 @@ Change 'a' command in thread-view mode to only archive o
51 matches
Mail list logo