works both ways.
--
Mike Kelly
-- next part --
A non-text attachment was scrubbed...
Name: 0001-Support-notmuch-count-with-no-args-or.patch
Type: text/x-patch
Size: 772 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100301/b023
On Mon, 01 Mar 2010 13:43:24 -0500, Ben Gamari wrote:
> Excerpts from Michal Sojka's message of Mon Mar 01 12:18:55 -0500 2010:
> > > How do you propose that the backends keep track of what mail has been
> > > indexed?
> >
> > For example by using Xapian metadata:
> > notmuch->xapian_db->set_meta
DraX on IRC asked, so here's a git repository:
git://github.com/dme/noneatall.git
dme.
--
David Edmondson, http://dme.org
On Mon, 01 Mar 2010 14:13:05 +0100
"Sebastian Spaeth" wrote:
> > > to count everything. Anyone have a better option for what the
> > > give-me-everything syntax should be?
> >
> > notmuch count ''
> >
> > The search patterns limit the matched messages/folders. An empty
> > pattern should match
ubt a variety of security holes.
Feel free to use, enhance, etc. It would be good if improvements were
made available to all.
Teaser pictures:
- a list of messages (tag:notmuch in this case):
http://dme.org/notmuch/index-20100301.png
- a displayed forest:
http://dme.org/notmuch/thread-2010030
This is probably a very stupid implementation. I do not know elisp
well, so I appreciate advises on how to avoid code duplication.
Signed-off-by: Michal Sojka
---
notmuch.el | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 6
This adds --sender-only option to reply command, which makes the reply
go only to the original sender.
Signed-off-by: Michal Sojka
---
notmuch-reply.c |9 +++--
notmuch.1 |6 ++
notmuch.c |3 +++
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/notm
On Mon, 01 Mar 2010 11:27:07 -0500, Ben Gamari wrote:
> > 2. get the list of new mails which need to be indexed
> >(current notmuch does recursive file traversal, for git-based store
> >it will be something like system("git diff-tree --name-status ...")
> >
> Is this really necessary? Anot
Signed-off-by: Sebastian Spaeth
---
notmuch-show.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index 0f10797..4c794c4 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@ -310,10 +310,12 @@ format_part_json (GMimeObject *part, int
More json woes... This mail makes json parser commit suicide:
"body": [{"id": 1, "content-type": "text/html"}, {"id": 2,
"content-type": "text/plain", "content": (null)}
and yes, it has empty mime parts.
Sebastian
The previous json patches forgot to add the notmuch tags to the json output.
This is inconsistent to the text output so here they are. We just output a
'tags' field that sends a space delimited list of json-encoded notmuch tags.
Signed-off-by: Sebastian Spaeth
---
notmuch-show.c |5 +++--
I have added a section to http://notmuchmail.org/emacstips/
that tries to describe the common workflow of notmuch.el users. It is
not finished yet, and it might better belong on a page of it's own.
I also recognize that it probably overlaps with James' new page on
initial tagging somewhat, but I w
On Tue, 23 Feb 2010 12:56:15 -0800, Carl Worth wrote:
[JSON patch]
> Anyway, very well done! I've applied this now with one change:
I might be dumb. But does the json output really not provide the notmuch
tags of a message as the text output does, and is that intentional?
I was trying to make no
ail/notmuch/attachments/20100301/059017a1/attachment.mht>
On Fri, 26 Feb 2010 12:08:49 -0800, Carl Worth wrote:
>What's your favorite thing about notmuch?
It is simple and fast. It lets me use emacs as MUA which I tried
before. But I always gave up on GNUS.
>What about notmuch makes it distinctive compared to other email
>programs?
Did I m
When importing a new mail do check for maildir tags and assign corresponding
notmuch tags.
Based on a patch by Michiel Buddingh and
subsequently modified by Tim Stoakes, Stewart Smith, and Sebastian Spaeth (see
mail thread around mail id:20100210031339.GH16686 at mail.rocksoft.com)
Do note th
> > to count everything. Anyone have a better option for what the
> > give-me-everything syntax should be?
>
> notmuch count ''
>
> The search patterns limit the matched messages/folders. An empty pattern
> should match everything.
I agree that '' should work, but then I would expect to have '*'
Excerpts from Michal Sojka's message of Mon Mar 01 12:18:55 -0500 2010:
> > Is this really necessary? Another option (which I believe has been
> > mentioned here in the past) is to simply pass notmuch new a list of
> > message "paths" to add (although I'm not sure if many mail delivery
> > programs
On Mon, 1 Mar 2010 16:39:06 +0100, Sebastian Spaeth
wrote:
> The previous json patches forgot to add the notmuch tags to the json
> output. This is inconsistent to the text output so here they are. We
> just output a 'tags' field that sends a space delimited list of
> json-encoded notmuch tags.
; output field be an array of strings
makes the most sense.
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/20100301/0fd37ca6/attachment.pgp>
On Fri, 26 Feb 2010 12:08:49 -0800, Carl Worth wrote:
>What's your favorite thing about notmuch?
I can process my inbox in a linear fassion (by pressing space). During
that, I'm not distracted by various GUI elements, which remind me how
many other emails I have to read. I can fully concentra
On Mon, 01 Mar 2010 13:43:24 -0500, Ben Gamari wrote:
> Excerpts from Michal Sojka's message of Mon Mar 01 12:18:55 -0500 2010:
> > > How do you propose that the backends keep track of what mail has been
> > > indexed?
> >
> > For example by using Xapian metadata:
> > notmuch->xapian_db->set_meta
On Fri, 26 Feb 2010 12:00:06 -0800, Carl Worth wrote:
> [This mail started as some off-topic rambling in my reply to the
> notmuch-reply script. So that's why it starts on one topic and ends
> somewhere else entirely.]
>
> I'm currently avoiding any locking failures with notmuch commands by
> run
DraX on IRC asked, so here's a git repository:
git://github.com/dme/noneatall.git
dme.
--
David Edmondson, http://dme.org
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Excerpts from Michal Sojka's message of Mon Mar 01 03:57:26 -0500 2010:
> Hi, when you are on this topic, I'll put my two cents in. Currently
> notmuch works only with mail-store comprised of files. People want to
> work with their mails on multiple computers so there are several
> ideas/solutions
On Fri, 26 Feb 2010 14:49:25 -0500, Mike Kelly wrote:
> The following patches attempt to provide a simple, extendable approach
> to handling the 'Seen' maildir flag. To appease (hopefully) everyone, it
> will only do this for new messages. This means that people coming from
> another MUA won't be
ubt a variety of security holes.
Feel free to use, enhance, etc. It would be good if improvements were
made available to all.
Teaser pictures:
- a list of messages (tag:notmuch in this case):
http://dme.org/notmuch/index-20100301.png
- a displayed forest:
http://dme.org/notmuch/thread-2010030
Excerpts from Michal Sojka's message of Mon Mar 01 12:18:55 -0500 2010:
> > Is this really necessary? Another option (which I believe has been
> > mentioned here in the past) is to simply pass notmuch new a list of
> > message "paths" to add (although I'm not sure if many mail delivery
> > programs
On Thu, 25 Feb 2010 01:00:04 +0100 (CET), racin at free.fr wrote:
> Hi Carl,
>
> > Could you also write a commit message describing what the patch does?
> > The easiest way for me to apply that would be if you would create a git
> > commit, then run "git format-patch origin/master" and mail the re
On Wed, 24 Feb 2010 10:19:06 -0800, Carl Worth wrote:
> Elsewhere in the thread Jameson Rollins wrote:
> > I should have mentioned in my previous mail that I think this tool is
> > a great idea, and I plan on using it. I just hope that all of it's
> > functionality will be integrated directly int
On Mon, 01 Mar 2010 13:26:52 -0400, David Bremner wrote:
> On Mon, 1 Mar 2010 16:39:06 +0100, Sebastian Spaeth
> wrote:
> > The previous json patches forgot to add the notmuch tags to the json
> > output. This is inconsistent to the text output so here they are. We
> > just output a 'tags' fiel
This adds --sender-only option to reply command, which makes the reply
go only to the original sender.
Signed-off-by: Michal Sojka
---
notmuch-reply.c |9 +++--
notmuch.1 |6 ++
notmuch.c |3 +++
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/notm
This is probably a very stupid implementation. I do not know elisp
well, so I appreciate advises on how to avoid code duplication.
Signed-off-by: Michal Sojka
---
notmuch.el | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 6
On Mon, 1 Mar 2010 16:39:06 +0100, Sebastian Spaeth
wrote:
> The previous json patches forgot to add the notmuch tags to the json
> output. This is inconsistent to the text output so here they are. We
> just output a 'tags' field that sends a space delimited list of
> json-encoded notmuch tags.
On Mon, 01 Mar 2010 11:27:07 -0500, Ben Gamari wrote:
> > 2. get the list of new mails which need to be indexed
> >(current notmuch does recursive file traversal, for git-based store
> >it will be something like system("git diff-tree --name-status ...")
> >
> Is this really necessary? Anot
Excerpts from Michal Sojka's message of Mon Mar 01 03:57:26 -0500 2010:
> Hi, when you are on this topic, I'll put my two cents in. Currently
> notmuch works only with mail-store comprised of files. People want to
> work with their mails on multiple computers so there are several
> ideas/solutions
Signed-off-by: Sebastian Spaeth
---
notmuch-show.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index 0f10797..4c794c4 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@ -310,10 +310,12 @@ format_part_json (GMimeObject *part, int
More json woes... This mail makes json parser commit suicide:
"body": [{"id": 1, "content-type": "text/html"}, {"id": 2,
"content-type": "text/plain", "content": (null)}
and yes, it has empty mime parts.
Sebastian
___
notmuch mailing list
notmuch@not
The previous json patches forgot to add the notmuch tags to the json output.
This is inconsistent to the text output so here they are. We just output a
'tags' field that sends a space delimited list of json-encoded notmuch tags.
Signed-off-by: Sebastian Spaeth
---
notmuch-show.c |5 +++--
On Fri, 26 Feb 2010 12:08:49 -0800, Carl Worth wrote:
>What's your favorite thing about notmuch?
It is simple and fast. It lets me use emacs as MUA which I tried
before. But I always gave up on GNUS.
>What about notmuch makes it distinctive compared to other email
>programs?
Did I m
> > to count everything. Anyone have a better option for what the
> > give-me-everything syntax should be?
>
> notmuch count ''
>
> The search patterns limit the matched messages/folders. An empty pattern
> should match everything.
I agree that '' should work, but then I would expect to have '*'
I have added a section to http://notmuchmail.org/emacstips/
that tries to describe the common workflow of notmuch.el users. It is
not finished yet, and it might better belong on a page of it's own.
I also recognize that it probably overlaps with James' new page on
initial tagging somewhat, but I w
On Tue, 23 Feb 2010 12:56:15 -0800, Carl Worth wrote:
[JSON patch]
> Anyway, very well done! I've applied this now with one change:
I might be dumb. But does the json output really not provide the notmuch
tags of a message as the text output does, and is that intentional?
I was trying to make no
Resending as this did not get through the list somehow. Sorry, if it
pops up twice now
--- Begin Message ---
>From git repository git://github.com/spaetz/notmuch-all-feature.git I
would like to advocate the following branches for quick pulling. Each
contains 1 or 2 patches. They have all been base
When importing a new mail do check for maildir tags and assign corresponding
notmuch tags.
Based on a patch by Michiel Buddingh and
subsequently modified by Tim Stoakes, Stewart Smith, and Sebastian Spaeth (see
mail thread around mail id:20100210031339.gh16...@mail.rocksoft.com)
Do note that
On Fri, 26 Feb 2010 12:08:49 -0800, Carl Worth wrote:
>What's your favorite thing about notmuch?
I can process my inbox in a linear fassion (by pressing space). During
that, I'm not distracted by various GUI elements, which remind me how
many other emails I have to read. I can fully concentra
On Fri, 26 Feb 2010 12:00:06 -0800, Carl Worth wrote:
> [This mail started as some off-topic rambling in my reply to the
> notmuch-reply script. So that's why it starts on one topic and ends
> somewhere else entirely.]
>
> I'm currently avoiding any locking failures with notmuch commands by
> run
On Thu, 25 Feb 2010 01:00:04 +0100 (CET), ra...@free.fr wrote:
> Hi Carl,
>
> > Could you also write a commit message describing what the patch does?
> > The easiest way for me to apply that would be if you would create a git
> > commit, then run "git format-patch origin/master" and mail the resul
On Wed, 24 Feb 2010 10:19:06 -0800, Carl Worth wrote:
> Elsewhere in the thread Jameson Rollins wrote:
> > I should have mentioned in my previous mail that I think this tool is
> > a great idea, and I plan on using it. I just hope that all of it's
> > functionality will be integrated directly int
49 matches
Mail list logo
