The show command outputs all messages in the threads that match the
search-terms. This patch introduces a 'match:[01]' entry to the 'message{'
line output by the show command. Value of 1 indicates that the message is
matching the search expression.
Signed-off-by: Bart Trojanowski
---
notmuch-s
When _notmuch_thread_create() is given a query string, it can return more
messages than just those matching the query. To distinguish those that
matched the query expression, the MATCHING_SEARCH flag is set
appropriately.
Signed-off-by: Bart Trojanowski
---
lib/notmuch.h |1 +
lib/thread.cc
This patch allows for different flags, internal to notmuch, to be set on a
message object. The patch does not define any such flags, just the
facilities to manage these flags.
Signed-off-by: Bart Trojanowski
---
lib/message.cc | 19 +++
lib/notmuch.h | 14 ++
2
The following 3 patches implement this feature.
Internally the message object learns about flags. Only a single flag is
defined to denote that a message matched the search expression.
That flag is then rendered on the "message{" line in the output of
notmuch show like this:
message{ id:... dept
The list of tags to be applied by 'notmuch new' can be configured in
the configuration file. This command line option can be used to
override the list of tags from the coonfiguration file on the command
line. You may repeat the option several times if you want to apply
more than one tag:
notmuch
If the user runs 'notmuch setup' and there is no configuration file yet
then we also add the new section [new] to the configuration file and
set the tags option as:
tags=inbox;unread
This will be picked up by 'notmuch new' and all new mail added to the
database will be tagged with the two tags
Add support for section [new] in the configuration file. This section
is supposed to contain options for 'notmuch new'. Currently there is
only one option called tags.
The tags option can be used to configure a set of tags to be applied
by 'notmuch new'. Individual tags are separated by semicolon.
Instead of adding 'inbox' and 'unread' tags directly in the code of
'notmuch-new', we can specify a list of tags to be added to newly
created messages with a configuration file option or a command line
option. That's more flexible, it allows the user to select which tags
should be added.
Signed-of
I would like to propose that we make the list of tags applied by 'notmuch new'
configurable. Right now notmuch applies two tags to all new messages added to
the database, 'inbox' and 'unread'. The two tags are added by the C code in
notmuch-new.c and they cannot be changed without editing the sourc
* Jan Janak [091124 17:11]:
> I would like to propose that we make the list of tags applied by 'notmuch new'
> configurable. Right now notmuch applies two tags to all new messages added to
> the database, 'inbox' and 'unread'. The two tags are added by the C code in
> notmuch-new.c and they cannot
It turns out that this ID has id: prefixed (which I thought was fine
because I'm frequently doing another query with it). But git send-email
doesn't strip that, so this was not threaded correctly. Would this be
better with the id: prefix stripped?
Jed
On Wed, 25 Nov 2009 10:28:00 +0530, "Aneesh Kumar K.V" wrote:
> This add two faces, notmuch-show-subject-face and
> notmuch-tag-face. The first face is used to show the subject
> line in the notmuch-show-mode and the second one to show tags
> in the notmuch-search-mode.
>
First, I definetly think
Puts current message ID in the kill ring. This is useful any time you
want to explicitly refer to the message, such as in the body of another
message, through git format-patch, or on IRC.
It is bound to "C-c i".
Corrected spelling of function name in commit message, and updated to
apply against
This patch adds support for notmuch show --only-matching-messages
which limits the output to only the top level messages matching
the search terms provides.
Example:
$ notmuch search subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b
thread:23d99d0f364f93e90e15df8b42eddb5b July 31 [4/12
Hi,
I find this patch useful for searching my mail. I realize that the
option is horrendously long, and I would take any suggestions to shorten
it or to use a short op, like -m.
-Bart
On Tue, 2009-11-24 at 23:10 +0100, Jan Janak wrote:
> Instead of 'inbox' and 'unread', I configure
> 'notmuch new' to add a new tag called 'new' (and only that one). This tag
> marks newly added messages that haven't been properly tagged yet by my
> auto-tagging scripts.
Oh, brilliant! I like i
As I see this every time I poll for new mail, the joke becomes very old
very quickly. The other instances of "not much" are shown much less
often and have a much more natural style, this one however feels forced,
impairing the humorous effect.
Signed-off-by: Chris "the critic" Wilson
---
notmuc
This is useful any time you want to explicitly refer to the message,
such as in the body of another message, through git format-patch, or on
IRC.
It is bound to "C-c i".
Signed-off-by: Jed Brown
---
notmuch.el | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/
On 24-11 08:38, Keith Packard wrote:
> On Tue, 24 Nov 2009 13:14:07 +0100, Jan Janak wrote:
>
> > I like this. I think this is much cleaner than the "virtual tag"
> > approach.
>
> A disadvantage I see is that you would not see this 'virtual tags' in
> the list of tags on each message.
Maybe I
* Keith Packard [091124 11:38]:
> A disadvantage I see is that you would not see this 'virtual tags' in
> the list of tags on each message. And, we'd have to put the virtual tags
> in the .config file or the command line would become a lot less
> useful. Speaking of which, we should put the folder
On Tue, 24 Nov 2009 08:38:20 -0800, Keith Packard wrote:
> A disadvantage I see is that you would not see this 'virtual tags' in
> the list of tags on each message.
Is it not cheap to check the current search results against the vtags
(named searches) that you have defined. Then you can show the
On Tue, Nov 24, 2009 at 5:10 PM, Jan Janak wrote:
> I would like to propose that we make the list of tags applied by 'notmuch new'
> configurable. Right now notmuch applies two tags to all new messages added to
> the database, 'inbox' and 'unread'. The two tags are added by the C code in
> notmuch
Another minor patch, fixing a couple of resource leaks in error paths.
---
notmuch-count.c | 52
1 files changed, 36 insertions(+), 16 deletions(-)
diff --git a/notmuch-count.c b/notmuch-count.c
index 77aa433..b5808f5 100644
--- a/notmuch-c
Hi Carl,
> "Carl" == Carl Worth writes:
Carl> I agree that trying to support OOM doesn't make sense without
Carl> testing. But that's why I want to test notmuch with memory-fault
Carl> injection. We've been doing this with the cairo library with good
Carl> success for a while
On Tue, Nov 24, 2009 at 4:16 AM, Carl Worth wrote:
> And notice, I don't think we'll need to do the "virtual tag" thing of
> associating a tag name with a search and doing the work of making
> notmuch maintain the consistency of that tag and search string. It will
> be much more clean (and shouldn
On Mon, Nov 23, 2009 at 5:55 AM, Carl Worth wrote:
> On Sun, 22 Nov 2009 18:14:20 -0500, Jameson Graef Rollins finestructure.net> wrote:
>> I think Carl said he wanted to keep the ability to specify exactly
>> where the database is stored, so if we could move away from something
>> that makes any
On Tue, 24 Nov 2009 11:40:24 -0800, Carl Worth wrote:
[snip]
> Anyway, this is really great stuff, Alexander. Thanks for coding it up!
>
Awesome thanks. Makes things much more useable anyway. :)
> I've pushed it out now, (with a little bit more in the way of commit
> messages---thanks for humo
On Mon, 23 Nov 2009 23:45:03 -0800, Alexander Botero-Lowry wrote:
> ---
> notmuch.el | 18 +++---
> 1 files changed, 15 insertions(+), 3 deletions(-)
Hmm... no real content for me to reply to here... :-)
Anyway, this is really great stuff, Alexander. Thanks for coding it up!
I've
On Mon, 23 Nov 2009 19:43:26 -0800, Keith Packard wrote:
> On Mon, 23 Nov 2009 19:16:54 -0800, Carl Worth wrote:
> > Then tags become something that are just for manual manipulation. What
> > do you think?
I really think this is the way to go.
> And disadvantages as searching might actually be
Hi all,
I'm a Gnus user and use notmuch mostly for searching. When I want to
reply to a message, I need to get back to Gnus, so that my Gnus posting
styles (gcc into that group, right email address, correct signature,...)
are applied.
Therefore, I created this small snippet. Now C-c C-c inside
hment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20091124/223cea1c/attachment.pgp>
31 matches
Mail list logo
