On Sun, 16 Aug 2015, David Bremner <da...@tethera.net> wrote:
> From: Jani Nikula <j...@nikula.org>
>
> notmuch-show --verify will now also process S/MIME multiparts if
> encountered. Requires gmime-2.6 and gpgsm.
>
> Based on work by Jameson Graef Rolli
On Fri, 18 Sep 2015, David Bremner wrote:
> Johannes Schauer writes:
>
>> Hi,
>>
>> Quoting David Bremner (2015-09-18 14:03:20)
>>> I'd recommend making your own new test, rather than modifying existing
>>> ones to test multiple things. I'd also recommend
On Sat, 26 Sep 2015, "Wael M. Nasreddine" wrote:
> I have a use case where I'd like to call 'notmuch new'
> programmatically via the bindings (custom Go bindings). Is it at all
> possible to expose notmuch_new_command[0] through lib/notmuch.h? The
> logic of
Per RFC 2183, the values for Content-Disposition values are not
case-sensitive. While at it, use the gmime function for getting at the
disposition string instead of referencing the field directly.
This fixes "attachment" tagging and filename term generation for
attachments while indexing.
---
Complete notmuch address --deduplicate=(no|mailbox|address).
---
completion/notmuch-completion.bash | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/completion/notmuch-completion.bash
b/completion/notmuch-completion.bash
index 960275d1f672..68b069013655 100644
---
On Fri, 24 Apr 2015, Mayeu wrote:
> On Fri, 24 Apr 2015 07:25:28 +0900
> David Bremner wrote:
>> OK. Please try running "notmuch new" (the second time) with --debug.
>
> The output is exactly the same, no other information. I also tried to
> add --verbose
As mentioned in
commit acd66cdec075312944e527febd46382e54d99367
Author: Jani Nikula <j...@nikula.org>
Date: Sat Sep 5 12:35:31 2015 +0300
cli: reset db directory mtime upon directory removal
we don't have an interface to delete directory documents, and they're
left behin
. This series just proves we need to do this.
BR,
Jani.
Jani Nikula (3):
test: flag one more notmuch new test as broken
lib: add interface to delete directory documents
cli: delete directory documents on directory removal
lib/directory.cc | 18 ++
lib/notmuch.h| 7
There was a problem with the directory documents being left behind
when the filesystem directory was removed. This was worked around in
commit acd66cdec075312944e527febd46382e54d99367
Author: Jani Nikula <j...@nikula.org>
Date: Sat Sep 5 12:35:31 2015 +0300
cli: reset db directory
Drop the test update added in
commit e4e04bbc328f990e36b77f508aef904d156029b1
Author: David Bremner
Date: Tue Aug 4 08:48:33 2015 +0200
cli/new: add more debugging output
and mark the test as broken, like the tests flagged as broken in
commit
The side effect is that all of add_files_state will be initialized to
zero, removing any lingering doubt that some of it might not be
initialized. It's not a small struct, and the initialization is
scattered around a bit, so this makes the code more readable.
---
notmuch-new.c | 13 +
Add strcmp_null, a strcmp that handles NULL strings; in strcmp terms a
NULL string is considered to be less than a non-NULL string.
---
util/string-util.c | 13 +
util/string-util.h | 5 +
2 files changed, 18 insertions(+)
diff --git a/util/string-util.c b/util/string-util.c
Currently we key the address hash table with the case sensitive "name
". Switch to case insensitive keying with just address, and
store the case sensitive name and address in linked lists. This will
be helpful in adding support for different deduplication schemes in
the future.
There will be a
First a simple smoke test first, next generate messages with multiple
email address variants and check the behaviour of deduplication
schemes with these.
---
v2: more variation in name parts of email addresses
---
test/T095-address.sh | 74
1
On Thu, 24 Sep 2015, David Bremner <da...@tethera.net> wrote:
> Jani Nikula <j...@nikula.org> writes:
>
>
>> +else
>> +v = !!m1->name - !!m2->name;
>
> Is this really idiomatic? It seems a little difficult to follow to me.
Probably
Check argc mainly to fix unused parameter warning:
test/symbol-test.cc:7:14: warning: unused parameter ‘argc’ [-Wunused-parameter]
int main(int argc, char** argv) {
^
This makes more sense than telling the compiler it's unused on
purpose.
---
test/symbol-test.cc | 3 +++
1 file
On Sun, 20 Sep 2015, David Bremner <da...@tethera.net> wrote:
> Jani Nikula <j...@nikula.org> writes:
>
>> Test not using address deduplication. Incorporate some trivial output
>> sorting tests here, as they seem to lack tests.
>&g
Document the deduplication of results.
---
doc/man1/notmuch-address.rst | 15 +++
1 file changed, 15 insertions(+)
diff --git a/doc/man1/notmuch-address.rst b/doc/man1/notmuch-address.rst
index 9570095b23c8..6003ed29cf32 100644
--- a/doc/man1/notmuch-address.rst
+++
The library does not have a function to remove a directory document
for a path. Usually this doesn't matter except for a slight waste of
space. However, if the same directory gets added to the filesystem
again, the old directory document is found with the old mtime. Reset
the directory mtime on
On Sun, 23 Feb 2014, Mark Walters wrote [1]:
> I was experimenting with letting notmuch new take an argument to tell it
> to scan only a particular directory (and sub-directories) for new
> messages. I came across the following strange behaviour which is also
> present
First a simple smoke test first, next generate messages with multiple
email address variants and check the behaviour of deduplication
schemes with these.
---
test/T095-address.sh | 63
1 file changed, 63 insertions(+)
diff --git
Test not using address deduplication. Incorporate some trivial output
sorting tests here, as they seem to lack tests.
---
test/T095-address.sh | 70
1 file changed, 70 insertions(+)
diff --git a/test/T095-address.sh b/test/T095-address.sh
Not of much consequence, but makes it nicer to do further edits.
---
test/symbol-test.cc | 34 ++
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/test/symbol-test.cc b/test/symbol-test.cc
index fb77b418a1a8..77dbc1af44b2 100644
---
Check argc mainly to fix unused parameter warning:
test/symbol-test.cc:7:14: warning: unused parameter ‘argc’ [-Wunused-parameter]
int main(int argc, char** argv) {
^
This makes more sense than telling the compiler it's unused on
purpose.
---
test/symbol-test.cc | 3 +++
1 file
We'll be needing more mailbox creation soon, so abstract it
away. While at it, check for allocation failures. No other functional
changes.
---
notmuch-search.c | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/notmuch-search.c b/notmuch-search.c
index
Switch to normal glib hash table lookup. The extended version is only
required if the values may contain NULL.
---
notmuch-search.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/notmuch-search.c b/notmuch-search.c
index 3076c3f637b1..7fdc6acaa2fe
For future use in both cli and lib.
---
lib/message-file.c| 21 -
lib/notmuch-private.h | 1 +
util/string-util.c| 21 +
util/string-util.h| 6 ++
4 files changed, 28 insertions(+), 21 deletions(-)
diff --git a/lib/message-file.c
to collect all
results before printing for --deduplicate=address, similar to
--output=count.
BR,
Jani.
Jani Nikula (9):
cli: g_hash_table_lookup_extended is overkill
cli: abstract new mailbox creation
cli: add support for not deduplicating notmuch address results
man: document notmuch
Make it possible to use notmuch address as part of a | sort | uniq -c
pipe instead of forcing --output=count. This is useful for combining
results from multiple notmuch address queries.
---
notmuch-search.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git
Consider all variants of an email address as one, and print the most
common variant.
---
notmuch-search.c | 48 ++--
1 file changed, 42 insertions(+), 6 deletions(-)
diff --git a/notmuch-search.c b/notmuch-search.c
index 7c51d5df6bd4..deb9e58a747c
Document the deduplication of results.
---
doc/man1/notmuch-address.rst | 15 +++
1 file changed, 15 insertions(+)
diff --git a/doc/man1/notmuch-address.rst b/doc/man1/notmuch-address.rst
index 9570095b23c8..4ae7395bce4d 100644
--- a/doc/man1/notmuch-address.rst
+++
Currently we key the address hash table with the case sensitive "name
". Switch to case insensitive keying with just address, and
store the case sensitive name and address in linked lists. This will
be helpful in adding support for different deduplication schemes in
the future.
There will be a
The order of the results with --output=count and --deduplicate=address
are unspecified as they're based on a hash table traversal. This being
the case, optimize the query by explicitly requesting unsorted
results. Clarify the documentation accordingly.
---
doc/man1/notmuch-address.rst | 4 +++-
Document the deduplication based on case insensitive address.
---
doc/man1/notmuch-address.rst | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/doc/man1/notmuch-address.rst b/doc/man1/notmuch-address.rst
index 4ae7395bce4d..b85cc37213e5 100644
---
On Sun, 30 Aug 2015, David Bremner da...@tethera.net wrote:
Jani Nikula j...@nikula.org writes:
+static int
+strcase_equal (const void *a, const void *b)
+{
+return strcasecmp (a, b) == 0;
+}
+
+static unsigned int
+strcase_hash (const void *ptr)
+{
+const char *s = ptr
On Sun, 30 Aug 2015, David Bremner da...@tethera.net wrote:
I guess this doesn't make the error handling worse; both old and new
code silently ignore OOM if I understand correctly.
Oh, and current git will not silently ignore OOM. It will segfault... ;)
BR,
Jani.
On Sun, 30 Aug 2015, David Bremner da...@tethera.net wrote:
Jani Nikula j...@nikula.org writes:
+{ NOTMUCH_OPT_KEYWORD, ctx-dupe, deduplicate, 'x',
probably you want 'D' or 'd' here. Not that it makes a practical
difference at this point.
+ (notmuch_keyword_t []){ { yes, -1
from:amdragon
1544Austin Clements amdra...@mit.edu
63 Austin Clements amdra...@mit.edu
$ notmuch address --output=count from:j...@nikula.org
2344Jani Nikula j...@nikula.org
3 Jani j...@nikula.org
5 j...@nikula.org
6 j...@nikula.org j...@nikula.org
And new deduplication
We'll be needing more mailbox creation soon, so abstract it
away. While at it, check for allocation failures. No other functional
changes.
---
notmuch-search.c | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/notmuch-search.c b/notmuch-search.c
index
Switch to normal glib hash table lookup. The extended version is only
required if the values may contain NULL.
---
notmuch-search.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/notmuch-search.c b/notmuch-search.c
index 3076c3f637b1..7fdc6acaa2fe
Make it possible to use notmuch address as part of a | sort | uniq -c
pipe instead of forcing --output=count. This is useful for combining
results from multiple notmuch address queries.
---
notmuch-search.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/notmuch-search.c
Currently we key the address hash table with the case sensitive name
address. Switch to case insensitive keying with just address, and
store the case sensitive name and address in linked lists. This will
be helpful in adding support different deduplication schemes in the
future. There will be a
On Wed, 26 Aug 2015, Tomi Ollila tomi.oll...@iki.fi wrote:
On Sat, Aug 15 2015, Jani Nikula j...@nikula.org wrote:
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient
On Sun, 23 Aug 2015, David Mazieres dm-list-email-notm...@scs.stanford.edu
wrote:
Sebastian Fischmeister sfisc...@uwaterloo.ca writes:
Hi,
My previous mail editor had a useful feature to resend already sent
emails. It's essentially opening an already sent email and have the
senders,
It doesn't seem likely we can support simple date: expanding to
date:.. any time soon. (This can be done with a future
version of Xapian, or with a custom query query parser.) In the mean
time, provide shorthand date:..! to mean the same. This is
useful, as the expansion takes place before
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
v2: fix killing frame with --create-frame
v3: fix --create-frame w/o --client parameter check
v4:
Automatically starting Emacs in daemon mode if the Emacs server is not
running is a matter of preference better not hard coded in
notmuch-emacs-mua. Add an option to control the behaviour.
---
doc/man1/notmuch-emacs-mua.rst | 9 +++--
notmuch-emacs-mua | 8 ++--
2 files
Move --client handling to a more suitable location. No functional
changes.
---
notmuch-emacs-mua | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/notmuch-emacs-mua b/notmuch-emacs-mua
index e33aa955d6b5..1f088c42feb9 100755
--- a/notmuch-emacs-mua
+++ b/notmuch-emacs-mua
Clearly --no-window-system should be applicable without --client as
well. Prepare for future changes with the naming of the variables.
---
notmuch-emacs-mua | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/notmuch-emacs-mua b/notmuch-emacs-mua
index
Move --client description to a more suitable location, stylistic
changes.
---
doc/man1/notmuch-emacs-mua.rst | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/man1/notmuch-emacs-mua.rst b/doc/man1/notmuch-emacs-mua.rst
index 36b51cdc3b18..7c2f5c24f1c0 100644
---
The main goal is to not force --create-frame on users who dislike
it. Split to some hopefully less controversial prep patches.
BR,
Jani.
Jani Nikula (5):
man: clean up notmuch-emacs-mua man page
notmuch-emacs-mua: support --no-window-system also for non-client
notmuch-emacs-mua: move
Automatically starting Emacs in daemon mode if the Emacs server is not
running is a matter of preference better not hard coded in
notmuch-emacs-mua. Add an option to control the behaviour.
---
doc/man1/notmuch-emacs-mua.rst | 9 +++--
notmuch-emacs-mua | 8 ++--
2 files
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
v2: fix killing frame with --create-frame
v3: fix --create-frame w/o --client parameter check
v4:
Move --client handling to a more suitable location. No functional
changes.
---
notmuch-emacs-mua | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/notmuch-emacs-mua b/notmuch-emacs-mua
index e33aa955d6b5..1f088c42feb9 100755
--- a/notmuch-emacs-mua
+++ b/notmuch-emacs-mua
Move --client description to a more suitable location, stylistic
changes.
---
doc/man1/notmuch-emacs-mua.rst | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/man1/notmuch-emacs-mua.rst b/doc/man1/notmuch-emacs-mua.rst
index 36b51cdc3b18..7c2f5c24f1c0 100644
---
Clearly --no-window-system should be applicable without --client as
well. Prepare for future changes with the naming of the variables.
---
notmuch-emacs-mua | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/notmuch-emacs-mua b/notmuch-emacs-mua
index
The main goal is to not force --create-frame on users who dislike
it. Split to some hopefully less controversial prep patches.
BR,
Jani.
Jani Nikula (5):
man: clean up notmuch-emacs-mua man page
notmuch-emacs-mua: support --no-window-system also for non-client
notmuch-emacs-mua: move
It doesn't seem likely we can support simple date:expr expanding to
date:expr..expr any time soon. (This can be done with a future
version of Xapian, or with a custom query query parser.) In the mean
time, provide shorthand date:expr..! to mean the same. This is
useful, as the expansion takes
From: Jani Nikula <j...@nikula.org>
Clean up punctuation for consistency, and add newline for clean
configure output.
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index d1bcc20eb6c2..d28988036505 100755
--- a/configure
From: Jani Nikula j...@nikula.org
Clean up punctuation for consistency, and add newline for clean
configure output.
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index d1bcc20eb6c2..d28988036505 100755
--- a/configure
+++ b/configure
On Jul 18, 2015 6:32 PM, "Suvayu Ali" wrote:
>
> Hi Xu,
>
> On Sat, Jul 18, 2015 at 10:54:30AM -0400, Xu Wang wrote:
> >
> > First note that I believe notmuch search is case insensitive by
> > default, so your grep should be case insensitive as well.
>
> Good
On Jul 18, 2015 6:32 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
Hi Xu,
On Sat, Jul 18, 2015 at 10:54:30AM -0400, Xu Wang wrote:
First note that I believe notmuch search is case insensitive by
default, so your grep should be case insensitive as well.
Good point, I tried that,
On Thu, 11 Jun 2015, Xu Wang wrote:
> Dear all,
>
> First, I am extremely excited to be a part of this list now. notmuch
> has really helped me. Thank you go all individuals working to improve
> it and to help others to know how to use it.
>
> I would really like to know if a message has been
On Wed, 10 Jun 2015, Robert Künnemann wrote:
> I've been using notmuch for about a year now (using mutt-kz) and I am
> very happy with it. I have, however, a small suggestion about the range
> syntax in search queries. Often, I am looking for emails that have
> occurred, say, in the last week.
On Wed, 10 Jun 2015, Robert Künnemann rob...@kunnemann.de wrote:
I've been using notmuch for about a year now (using mutt-kz) and I am
very happy with it. I have, however, a small suggestion about the range
syntax in search queries. Often, I am looking for emails that have
occurred, say, in
On Thu, 11 Jun 2015, Xu Wang xuwang...@gmail.com wrote:
Dear all,
First, I am extremely excited to be a part of this list now. notmuch
has really helped me. Thank you go all individuals working to improve
it and to help others to know how to use it.
I would really like to know if a message
On Sat, 06 Jun 2015, Johnny Utahh wrote:
> I'm new to Notmuch. Could I get feedback on the following?
>
> https://github.com/johnnyutahh/tag-based-email
> https://github.com/johnnyutahh/tag-based-email#the_main_questions
You're probably better off sending your specific questions to the list,
so
On Sat, 06 Jun 2015, Johnny Utahh notmuchmail@johnnyutahh.com wrote:
I'm new to Notmuch. Could I get feedback on the following?
https://github.com/johnnyutahh/tag-based-email
https://github.com/johnnyutahh/tag-based-email#the_main_questions
You're probably better off sending your specific
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
v2: fix killing frame with --create-frame
v3: fix --create-frame w/o --client parameter check
---
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
v2: fix killing frame with --create-frame
---
doc/man1/notmuch-emacs-mua.rst | 14 +-
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
v2: fix killing frame with --create-frame
---
doc/man1/notmuch-emacs-mua.rst | 14 +-
Let each view have "sort" key with possible values "oldest-first",
"newest-first", and "unsorted", and sort the results
accordingly. Oldest first remains the default.
---
devel/nmbug/nmbug-status | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git
Let each view have sort key with possible values oldest-first,
newest-first, and unsorted, and sort the results
accordingly. Oldest first remains the default.
---
devel/nmbug/nmbug-status | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/devel/nmbug/nmbug-status
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
---
With this, 'notmuch-emacs-mua --client' does what I want, which was
not possible with any combination
Recognize 'notmuch command --help' at the top level as a special case,
and show help for the command. Note that for simplicity, --help is
only recognized as the first option for the subcommand.
---
Creeping featurism or useful? ISTR Mark wanted this.
---
notmuch.c | 4 +++-
1 file changed, 3
If the top level --help is combined with other options, help
fails. For example:
$ notmuch --version --help
Sorry, --help is not a known command. There's not much I can do to help.
Fix this by adjusting argc and argv appropriately. The help command
ignores argv[0] anyway, so we don't
If the top level --help is combined with other options, help
fails. For example:
$ notmuch --version --help
Sorry, --help is not a known command. There's not much I can do to help.
Fix this by adjusting argc and argv appropriately. The help command
ignores argv[0] anyway, so we don't
Recognize 'notmuch command --help' at the top level as a special case,
and show help for the command. Note that for simplicity, --help is
only recognized as the first option for the subcommand.
---
Creeping featurism or useful? ISTR Mark wanted this.
---
notmuch.c | 4 +++-
1 file changed, 3
On Tue, 09 Dec 2014, David Bremner wrote:
> Previously we set up a way for the top level notmuch command to choose
> which gpg binary was invoked by libgmime. In this commit we add the
> (mostly boilplate) code to allow the notmuch-config command to read
> and write this path, and use it in the
On Tue, 09 Dec 2014, David Bremner wrote:
> GMIME takes a path to gpg, but we hardcode that path. In this commit
> we push hardcoding all the way up to the top level of a notmuch
> command, where we can later make it configurable.
Mmmh, to be pedantic, this does not push the hardcoding to the
On Sat, 07 Mar 2015, David Bremner wrote:
> This has been tested with gcc and clang.
> ---
> devel/STYLE | 10 ++
> doc/doxygen.cfg | 2 +-
> lib/notmuch.h | 2 ++
> 3 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/devel/STYLE b/devel/STYLE
> index
On Sat, 07 Mar 2015, David Bremner wrote:
> This should have happened in commit 326e18856, but it didn't.
LGTM.
> ---
> lib/notmuch.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/notmuch.h b/lib/notmuch.h
> index 3e326bf..f0b60b8 100644
> --- a/lib/notmuch.h
>
It's emacsclient command, not comment. Document default values. While
at it, format the environment section similarly to other man pages.
---
doc/man1/notmuch-emacs-mua.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/man1/notmuch-emacs-mua.rst
Notmuch uses long options exclusively all around. The short options in
notmuch-emacs-mua are intentionally just a compatible subset of
mutt(1). Keep it this way, if only to make documenting the fact easy!
The Notmuch style --client long option remains, of course.
---
acs-mua
> @@ -1,4 +1,5 @@
> #!/usr/bin/env bash
> +# -*- mode: shell-script; sh-basic-offset: 4; tab-width: 8 -*-
> #
> # notmuch-emacs-mua - start composing a mail on the command line
> #
> @@ -18,25 +19,47 @@
> # along with this program. If not, see http://www.gnu.o
On Sat, 07 Mar 2015, David Bremner wrote:
> Essentially replace each call to notmuch_count_* with an if block.
LGTM, nitpicks inline.
> ---
> notmuch-count.c | 14 --
> notmuch-reply.c | 8 +++-
> notmuch-search.c | 14 --
> notmuch-show.c | 8 +++-
> 4
On Sat, 07 Mar 2015, David Bremner wrote:
> Although I think it's a pretty bad idea to continue using the old API,
> this allows both a more gentle transition for clients of the library,
> and allows us to break one monolithic change into a series
We should probably bump LIBNOTMUCH_MINOR_VERSION
Up to debate:
1) Is something like this useful at all as an intermediate step before
we can have support for date:? (This can be done with a future
version of Xapian, or with a custom query query parser.)
2) If yes, are there better alternatives to "!" as the end point? (Or
should the special
Use the new notmuch address command to do completion for addresses in
from: and to:. Use --output=sender for both for efficiency, even
though --output=recipients would be more accurate for to: prefix
completion.
---
This is v2 of id:1422388098-16333-5-git-send-email-jani at nikula.org
opting for
On Sat, 07 Mar 2015, David Bremner da...@tethera.net wrote:
Essentially replace each call to notmuch_count_* with an if block.
LGTM, nitpicks inline.
---
notmuch-count.c | 14 --
notmuch-reply.c | 8 +++-
notmuch-search.c | 14 --
notmuch-show.c | 8
On Sat, 07 Mar 2015, David Bremner da...@tethera.net wrote:
This has been tested with gcc and clang.
---
devel/STYLE | 10 ++
doc/doxygen.cfg | 2 +-
lib/notmuch.h | 2 ++
3 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/devel/STYLE b/devel/STYLE
index
On Tue, 09 Dec 2014, David Bremner da...@tethera.net wrote:
Previously we set up a way for the top level notmuch command to choose
which gpg binary was invoked by libgmime. In this commit we add the
(mostly boilplate) code to allow the notmuch-config command to read
and write this path, and
On Sat, 07 Mar 2015, David Bremner da...@tethera.net wrote:
This should have happened in commit 326e18856, but it didn't.
LGTM.
---
lib/notmuch.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/notmuch.h b/lib/notmuch.h
index 3e326bf..f0b60b8 100644
---
On Sat, 07 Mar 2015, David Bremner da...@tethera.net wrote:
Although I think it's a pretty bad idea to continue using the old API,
this allows both a more gentle transition for clients of the library,
and allows us to break one monolithic change into a series
We should probably bump
Up to debate:
1) Is something like this useful at all as an intermediate step before
we can have support for date:query? (This can be done with a future
version of Xapian, or with a custom query query parser.)
2) If yes, are there better alternatives to ! as the end point? (Or
should the special
It's emacsclient command, not comment. Document default values. While
at it, format the environment section similarly to other man pages.
---
doc/man1/notmuch-emacs-mua.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/man1/notmuch-emacs-mua.rst
Notmuch uses long options exclusively all around. The short options in
notmuch-emacs-mua are intentionally just a compatible subset of
mutt(1). Keep it this way, if only to make documenting the fact easy!
The Notmuch style --client long option remains, of course.
---
Use the new notmuch address command to do completion for addresses in
from: and to:. Use --output=sender for both for efficiency, even
though --output=recipients would be more accurate for to: prefix
completion.
---
This is v2 of id:1422388098-16333-5-git-send-email-j...@nikula.org
opting for
If seconds are not specified in the string to be parsed, they're not
set according to the reference time (in the no rounding case) nor
rounded properly (in the rounding up cases). Fix this.
The bug caused searches such as date:10:30..10:30 to match messages
with date exactly 10:30:00 only, and
Extract and add some more tests relating to rounding seconds into a
separate subtest, and flag it as broken. If seconds are not specified,
the time is not set or rounded according to the interface defined in
parse-time-string/parse-time-string.h. Instead, seconds are always set
to 00 in reality,
501 - 600 of 3043 matches
Mail list logo