[notmuch] Emacs: Problem viewing a thread after reading it once interface

* Carl Worth [091204 13:55]: > So maybe we need "notmuch show" to accept a second query string > to do something like: > > notmuch show tag:foo --matching tag:inbox > > which will display all threads with messages matching "tag:foo" but then > mark only the messages matching "tag:inbox"

[notmuch] [PATCH] vim: preserve the 'show everything' flag when finding next/prev buffer

* Carl Worth [091203 16:31]: > Sorry I missed this with your earlier, related changes. But I've pushed > this now. Thanks. -Bart -- WebSig: http://www.jukie.net/~bart/sig/

[notmuch] semi-usable notmuch-gtk client

* Baruch Even [091127 12:58]: > I added a quick hack to show a message thread in notmuch-gtk and this > makes it semi-usable. I don't actually parse the reply of notmuch-show > but it's already passably usable to read mail. got screenshots? Cheers, -Bart --

[notmuch] [PATCH RFC] debugger: detect presence of ptrace type debuggers

According to the internet [1], this is a more reliable way of detecting if one is under the spell of a debugger. Should work for ptrace, strace, gdb, etc. Basically anything that uses the ptrace() syscall. [1] http://vx.netlux.org/lib/vsc04.html --- debugger.c |5 + 1 files changed, 5

[notmuch] [PATCH 2/2] vim: use notmuch show --entire-thread

--- vim/plugin/notmuch.vim |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim index 34d70d9..a226f20 100644 --- a/vim/plugin/notmuch.vim +++ b/vim/plugin/notmuch.vim @@ -409,7 +409,7 @@ endfunction function!

[notmuch] [PATCH 1/2] notmuch-show: limit display to only matching messages

With the --only-matching-messages option the output will contain all dozen messages: $ notmuch show --entire-thread subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 12 Signed-off-by: Bart Trojanowski --- notmuch-show.c | 48

[notmuch] [PATCH] vim: preserve the 'show everything' flag when finding next/prev buffer

-by: Bart Trojanowski --- vim/plugin/notmuch.vim |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim index b415f50..34d70d9 100644 --- a/vim/plugin/notmuch.vim +++ b/vim/plugin/notmuch.vim @@ -275,6 +275,7 @@ function

[notmuch] [PATCH 2/3] have _notmuch_thread_create mark which messages matched the query

On Fri, 27 Nov 2009 17:15:35 -0800, Carl Worth wrote: > This is a very useful feature, Bart. Thanks for coding it up. And it's a > nicely-implemented patch series as well. Thanks. I've found it very handy. > By the way, do you think that this support obviates the > --only-matching-messages

[notmuch] [PATCH] correct message flag enum value so that it matches the type

As per Carl's request, this patch corrects the only value defined under the notmuch_message_flag_t enum typedef to match the name of the type. Signed-off-by: Bart Trojanowski --- lib/notmuch.h |2 +- lib/thread.cc |2 +- notmuch-show.c |2 +- 3 files changed, 3 insertions(+), 3

[notmuch] [PATCH] Return unpropertized strings for filename and message-id

* Bart Trojanowski [091127 18:32]: > You can actually put arbitrary text between the diffstat output and the first > diff --git line. For example: Oops, and that's exactly what you said... > > So to satisfy "git am", introductory and explanatory portions of &g

[notmuch] [PATCH] Return unpropertized strings for filename and message-id

> Alternately, one can put introductory text in one message, and the > dry commit-only stuff as a reply. You can actually put arbitrary text between the diffstat output and the first diff --git line. For example: --- 8< --- >From e6628e78d9ce3f9383a4699df9063a648617b428 Mo

[notmuch] [PATCH 2/2] vim: use notmuch show --entire-thread

--- vim/plugin/notmuch.vim |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim index 34d70d9..a226f20 100644 --- a/vim/plugin/notmuch.vim +++ b/vim/plugin/notmuch.vim @@ -409,7 +409,7 @@ endfunction function!

[notmuch] [PATCH 2/4] notmuch: Config option to specify tags to be applied by 'notmuch new'.

Jan, I really want this feature to get in, so I am going to do my best to review your code :) Here are some more sticking points... > +char ** > +notmuch_config_get_new_tags (notmuch_config_t *config, size_t *length); If you are not giving over control of the pointer to the caller please

[notmuch] [PATCH] notmuch-new: Option to disable tags from the configuration file.

Jan, I think your use of STRNCMP_LITERAL here is wrong... > + } else if (STRNCMP_LITERAL (argv[i], "--no-config-tags") == 0) { > + add_config_tags = 0; it will happily match "--no-config-tags-xxx". Can I also suggest including --no-config-tags in the 'notmuch help'

[notmuch] [PATCH -v4] notmuch.el: Add face support to search and show mode

* Jeffrey Ollie [091125 09:33]: > On Tue, Nov 24, 2009 at 11:24 PM, Alexander Botero-Lowry > wrote: > > > > This way of detecting the tags seems ok, but I think it would be nicer > > if it could be done even more deterministically. :) One idea that be > > neat is to have a --format=sexp for

[notmuch] vim interface pull request

Carl, as you already know, I've spent some time working on a vim-based interface to notmuch. I currently only depend on the 'march:[01]' patches that we talked about briefly on irc. Everything else is isolated to the 'vim' directory and should not effect anyone else. My efforts are cataloged

[notmuch] [PATCH 3/3] notmuch-show: identify which messages printed matched the query string

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

[notmuch] [PATCH 2/3] have _notmuch_thread_create mark which messages matched the query

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

[notmuch] [PATCH 1/3] message: add flags to notmuch_message_t

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

[notmuch] notmuch show should tell us what messages matched the search expression

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:...

[notmuch] [PATCH 0/4] Make tags applied by 'notmuch new' configurable.

* 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

[notmuch] [PATCH] notmuch-show: add option to limit display to only matching messages

'message{' | wc -l 12 With the --only-matching-messages option the output is limited to the matching messages only: $ notmuch show --only-matching-messages subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 4 Signed-off-by: Bart Trojanowski --- notmuch-show.c

[notmuch] (no subject)

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

[notmuch] notmuch 'index' mode.

* 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

[notmuch] [PATCH 3/3] change config file location to be ~/.notmuch/config

I totally agree with Jamie about the config rename. I don't know if I agree with the database location change... but I might just need some convincing. Would it be enough to just read .notmuch/config and fall back to .notmuch-config otherwise? -Bart * Jameson Graef Rollins [091122 17:15]: >

[notmuch] Catching up unread messages

* Tassilo Horn [091122 16:49]: > Ok, so new the question: I indexed all my 63.000 mails, and because it > was a first-time indexing, all my mail now has the tags inbox and > unread. Of course, I don't want to SPC through all threads (using the > great emacs interface) to remove the unread

[notmuch] [RFC] Precedence of OR and AND

* Jed Brown [091122 16:43]: > Absolutely, and I have this applied locally to notmuch.el, but I didn't > fix notmuch-search-filter-by-tag because that would really need to parse > the expression. I'm just asking if anyone else thinks binding OR > tighter than AND would be desirable. Maybe some

[notmuch] [RFC] Precedence of OR and AND

Wouldn't this problem be solved by each filter appending a bracketed version of your filter? You start with tag:inbox and you filter on "term1 or term2" you'd get: tag:inbox and (term1 or term2) Doing it again would result in... tag:inbox and (term1 or term2) and (term3 or

[notmuch] [PATCH] Add SCons build files.

gt; on a wider variety of systems some sort of configuration system will > become necessary. If I can prevent another project from going down > the autoconf/automake path I'll be happy. I started creating CMake > build files but I don't know CMake well enough to come up with a > work

[notmuch] [PATCH] fix notmuch-new bug when database path ends with a trailing /

in the database. The database.path was removed from the full filename, but if the database.path from the config file contained a trailing /, the relative file name would retain an extra leading /... which made it look like an absolute path after it was read out from the DB. Signed-off-by: Bart Trojanowski

[notmuch] [PATCH] Add SCons build files.

* Jeffrey C. Ollie [091122 08:47]: > The SCons build files included here *should* do everything that the > current Makefiles do, plus a little bit of configuration checking. To > build/install: Wouldn't that have the unfortunate side effect of making notmuch unusable w/o emacs and scons

[notmuch] notmuch vim support

* Carl Worth [091121 15:20]: > On Sat, 21 Nov 2009 14:14:02 -0500, Bart Trojanowski > wrote: > > Perfect. How would you like to proceed with the initial integration? > > Pulling my tree, or me squashing all the changes into a single patch? > > Also, are you OK with

[notmuch] notmuch vim support

* Carl Worth [091121 15:14]: > So, well done! Thank you. > I think the only thing we noticed is that "filter" doesn't add the "and" > between the old and new search terms. But Chris may have more to comment > soon. I think I fixed that along the way. I'll verify. > I don't know how realistic

[notmuch] [PATCH 2/2] notmuch list: A new command to produce various lists.

* Carl Worth [091121 18:08]: > Another option would be to just call this "notmuch search" and have an > option to control what is output: > >notmuch search # for threads, as currently >notmuch search --output=tags >notmuch search --output=messages > > Actually, I kind of

[notmuch] hijacked threads can be confusing in notmuch

I'd like to see how other people feel about a problem I just ran into. I wanted to look at the 'notmuch count' patch that Keith Packard posted a couple of days ago (as I am porting his folder mode to notmuch.vim). I was unable to find it using notmuch because he happened to post 3 patches in one

[notmuch] [PATCH] notmuch: Add Maildir directory name as tag name for messages

* Carl Worth [091121 15:28]: > And sadly, I just pulled it out again. > > I realized that I actually don't want my mail tagged based on the > maildir directories I'm using, (they are arbitrarily-named directories > used only to keep the per-directory number of files below about 10 > thousand). >

[notmuch] notmuch vim support

* Stefan Schmidt [091121 14:06]: > IMHO it would be best to do the development inside the main tree. You could > use > branches there too and it would be easier to find and test. And as notmuch is > still under heavy development its not a problem that the vim interface is as > well. Perfect.

[notmuch] notmuch vim support

Hi list, I've spent a few days on porting notmuch.el to vim. It's not as feature rich as notmuch.el yet, but it's coming along nicely. The results of my work are here: git://git.jukie.net/notmuch.git (on the vim branch)