Hi James,
On Fri, 19 Aug 2011, James Vasile wrote:
Display a maximum of 150 results when searching for messages. This
prevents client lag when searches return thousands of results you'll
never look at
I would not like this feature. If I search for something I really want
to see everything.
On Fri, 19 Aug 2011, James Vasile wrote:
On Fri, 19 Aug 2011 17:00:23 +0200, Michal Sojka sojk...@fel.cvut.cz wrote:
Hi James,
On Fri, 19 Aug 2011, James Vasile wrote:
Display a maximum of 150 results when searching for messages. This
prevents client lag when searches return
Emacs 23.2 queries by default about killing existing processes. This
is annoying when one wants to interrupt long search with 'q' key.
Disable this behavior for notmuch.
--
I'm resending this again as jrollins requested in
id:871uwhz228@servo.factory.finestructure.net. Can anyone check
On Mon, 22 Aug 2011, Tomi Ollila wrote:
On Mon 22 Aug 2011 17:28, Tomi Ollila tomi.oll...@nixu.com writes:
On Mon 22 Aug 2011 16:49, Michal Sojka sojk...@fel.cvut.cz writes:
id:871uwhz228@servo.factory.finestructure.net. Can anyone check
whether this works with emacs earlier than 23.2
Emacs 23.2 queries by default about killing existing processes. This
is annoying when one wants to interrupt long search with 'q' key.
Disable this behavior for notmuch.
---
emacs/notmuch.el |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/emacs/notmuch.el
interconnected.
Is there something I can do to help with the review?
I think there's also one performance improvement written by Michal
Sojka, that isn't included in this version yet,
Yes, that's true. I'm aware of one bug in this improvement. I usually
start notmuch by
emacsclient -c
On Mon, 28 Nov 2011, Dmitry Kurochkin wrote:
Hi Daniel.
On Thu, 24 Nov 2011 15:01:01 +0100, Daniel Schoepe dan...@schoepe.org wrote:
On Thu, 24 Nov 2011 09:54:50 -0400, David Bremner da...@tethera.net wrote:
On Mon, 10 Oct 2011 15:39:41 +0200, Daniel Schoepe dan...@schoepe.org
wrote:
When notmuch-search-line-faces is used to set background color in search
results, the highlight of the current line is not always displayed
correctly. This patch fixes that by increasing the priority property of
the highlight overlay.
---
emacs/notmuch.el | 15 +++
1 files changed,
When notmuch-search-line-faces is used to set background color in search
results, the highlight of the current line is not always displayed
correctly. This patch fixes that by increasing the priority property of
the highlight overlay.
---
emacs/notmuch.el | 15 +++
1 files changed,
On Fri, 17 Feb 2012, Dmitry Kurochkin wrote:
Found a small bug...
Changes:
v10:
* explicitly return nil from `notmuch-hello-insert-recent-searches',
otherwise `indent-rigidly' returns a marker pointing to non-existing
buffer and breaks final-target-pos handling in `notmuch-hello'
The result is that hello screen shows much faster when some sections are
hidden.
---
emacs/notmuch-hello.el | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index aad373d..e9caade 100644
---
After recent rework of a/A/x/X key bindings, the important paragraph in
documentation of `notmuch-show-archive-thread' stayed hidden from users,
because no key is bound to this function.
This patch copies the important paragraph to the documentation of
functions currently bound to keys.
---
On Sun, 19 Feb 2012, Jani Nikula wrote:
On Feb 19, 2012 12:44 AM, Michal Sojka sojk...@fel.cvut.cz wrote:
After recent rework of a/A/x/X key bindings, the important paragraph in
documentation of `notmuch-show-archive-thread' stayed hidden from users,
because no key is bound
On Tue, 21 Feb 2012, Mark Walters wrote:
On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka sojk...@fel.cvut.cz wrote:
On Sun, 19 Feb 2012, Jani Nikula wrote:
On Feb 19, 2012 12:44 AM, Michal Sojka sojk...@fel.cvut.cz wrote:
After recent rework of a/A/x/X key bindings, the important
On Wed, 22 Feb 2012, Serge Z wrote:
Hello!
I've got the following problem: fetched emails can be in different encodings.
And searching a term typed in one encoding (system default) does not match the
same term in another encoding.
The solution, as I see, can be in preprocessing each
Emails that are encoded differently than as ASCII or UTF-8 are not
indexed properly by notmuch. It is not possible to search for non-ASCII
words within those messages.
---
test/encoding|9 +
test/test-lib.sh |5 +
2 files changed, 14 insertions(+), 0 deletions(-)
diff
On Fri, 24 Feb 2012, Serge Z wrote:
Quoting Michal Sojka (2012-02-24 04:33:15)
Emails that are encoded differently than as ASCII or UTF-8 are not
indexed properly by notmuch. It is not possible to search for non-ASCII
words within those messages.
Ok. But we can preprocess each incoming
---
test/encoding |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/test/encoding b/test/encoding
index 3992b5c..f0d073c 100755
--- a/test/encoding
+++ b/test/encoding
@@ -22,7 +22,6 @@ irrelevant
message}
test_begin_subtest Search for ISO-8859-2 encoded message
This fixes a bug that didn't allow to search for non-ASCII words such
parts. The code here was copied from show_text_part_content(), because
the show command already does the needed conversion when showing the
message.
---
lib/index.cc | 15 +++
1 files changed, 15 insertions(+), 0
On Fri, 24 Feb 2012, Serge Z wrote:
Quoting Michal Sojka (2012-02-24 11:00:02)
I'm not big fan of adding preprocessor. First, I thing that both
reasons you mention are actually bugs and it would be better to fix them
for everybody than requiring each user to configure some preprocessor
On Sat, 25 Feb 2012, Serge Z wrote:
Hi!
I've struck another problem:
I've got an html/text email with body encoded with cp1251.
Its encoding is mentioned in both Content-type: email header and html meta
tag. So when the client tries to display it with external html2text converter,
The
On Thu, 01 Mar 2012, David Bremner wrote:
Pushed, finally. Thanks for both of your hard work on this.
Hi,
is anybody willing to review
id:1329603149-6047-1-git-send-email-sojk...@fel.cvut.cz? I'd like to
see it merged togetger with these patches as it makes my work with
notmuch-hello much
Hi list,
when I try to reply within emacs to a particular message, I get JSON
readtable error. This happens with with the current git master as well
as with a version from about a month ago. Is this a known problem or
shall I dig into it and find what wrong?
Thanks,
-Michal
Hi Adam,
Adam Wolfe Gordon awg+notm...@xvx.ca writes:
On Mon, Apr 30, 2012 at 09:00, Michal Sojka sojk...@fel.cvut.cz wrote:
when I try to reply within emacs to a particular message, I get JSON
readtable error. This happens with with the current git master as well
as with a version from about
Sometimes, notmuch reply outputs something to stderr, for example:
Failed to verify signed part: Cannot verify multipart/signed part:
unsupported signature protocol. When this happens, replying in emacs
fails, because emacs cannot parse the error message as JSON.
This patch causes emacs to ignore
David Belohrad da...@belohrad.ch writes:
Dear All,
i experience very weird problem: have samsung galaxy tab 10.1 without
any firmware tweaks. now, when I take a picture in the tablet and send
it via email to me, then I open this email in emacs, the picture is not
there. Only text part of
Hello Adam,
Adam Wolfe Gordon awg+notm...@xvx.ca writes:
It turns out it's actually not the emacs side, but an interaction
between our JSON reply format and emacs.
The JSON reply (and show) code includes part content for all text/*
parts except text/html. Because all JSON is required to be
Tomi Ollila tomi.oll...@iki.fi writes:
Michal Sojka sojk...@fel.cvut.cz writes:
Hello Adam,
Adam Wolfe Gordon awg+notm...@xvx.ca writes:
It turns out it's actually not the emacs side, but an interaction
between our JSON reply format and emacs.
The JSON reply (and show) code includes part
Tomi Ollila tomi.oll...@iki.fi writes:
When mail message is read from emacs, the message structure
obtained may contain parts which have content included
(`text/plain` for example) and other parts where content is not
included (`text/html` for example).
In case content is included, the
Hi Doug,
Doug Penner darwinsurvi...@gmail.com writes:
I am in the process of trying to migrate from alpine (which handles
separate accounts *very* distinctly) to notmuch (which combines them). I
have no problem with incoming e-mails being combined (actually looking
forward to it) but am
When one wants to customize the format of reply message, there nothing
to tell the user how to do it. Without knowing that construction of
reply buffer is actually implemented in the message package, it seems
that replying cannot be customized.
Because I was getting annoyed by the empty line the
Hi Jameson,
some comments below.
On Mon, Aug 20 2012, Jameson Graef Rollins wrote:
This new structure holds addresses associated with a thread, both
matched and unmatched. Initially this will be used to replace the
existing infrastructure for storing the addresses of thread authors.
Further
On Thu, Jul 26 2012, Michal Sojka wrote:
When one wants to customize the format of reply message, there nothing
to tell the user how to do it. Without knowing that construction of
reply buffer is actually implemented in the message package, it seems
that replying cannot be customized
On Tue, Sep 04 2012, Michal Nazarewicz wrote:
On Thu, Jul 26 2012, Michal Sojka wrote:
Because I was getting annoyed by the empty line the between citation
line and the quoted message, I figured out that changing this is fairly
easy when one knows what to customize.
On semi-related note
On Tue, Sep 04 2012, Jani Nikula wrote:
On Tue, 04 Sep 2012, Michal Sojka sojk...@fel.cvut.cz wrote:
On Sun, Sep 02 2012, Jani Nikula wrote:
Hi all, v2 of [1] addressing review comments: added NEWS, improved
documentation, made the query customizable.
[1]
id
On Thu, Sep 06 2012, Tomi Ollila wrote:
On Thu, Sep 06 2012, Michal Sojka sojk...@fel.cvut.cz wrote:
When one wants to customize the format of reply message, there is nothing
to tell the user how to do it. Without knowing that construction of
reply buffer is actually implemented
On Thu, Sep 06 2012, Tomi Ollila wrote:
On Thu, Sep 06 2012, Michal Sojka sojk...@fel.cvut.cz wrote:
So far good, but...
You forgot to handle the current group setting for
notmuch-message-replied-tags -- currently notmuch-message.el has this:
(defcustom notmuch-message-replied-tags
On Wed, Sep 05 2012, Michal Nazarewicz wrote:
From: Michal Nazarewicz min...@mina86.com
---
notmuch-show.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
Actually, I don't understand why json does not include all the
headers...
Hi,
I tested this and haven't found any
On Thu, Sep 06 2012, Michal Nazarewicz wrote:
From: Michal Nazarewicz min...@mina86.com
---
notmuch-show.c |7 +++
test/json|8
test/test-lib.sh |5 +
3 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
Hello,
in emacs, I have a problem displaying an email that contain the
following part (--format=json):
{
content-type : image/svg+xml,
filename : _logo.svg,
id : 4
}
I see this message mm-image-fit-p: Invalid image specification and no
other emails after this
This patch reworks date/time parser library test program to make it
easier to to write the actual tests. It also modifies the notmuch test
script and adds several new tests to it.
The INPUT file for the test contains both the dates to be parsed as well
as the expected results. The test program
On Thu, Sep 13 2012, Michal Nazarewicz wrote:
On Wed, Sep 12 2012, Jani Nikula wrote:
Add a custom value range processor to enable date and time searches of
the form date:since..until, where since and until are expressions
understood by the previously added date/time parser, to restrict the
On Wed, Oct 03 2012, Jani Nikula wrote:
On Tue, 25 Sep 2012, Michal Sojka sojk...@fel.cvut.cz wrote:
Hello Jani,
On Wed, Sep 12 2012, Jani Nikula wrote:
Add a date/time parser to notmuch, to be used for adding date range
query support for notmuch lib later on. Add the parser to a directory
On Wed, Oct 03 2012, Jani Nikula wrote:
On Tue, 25 Sep 2012, Michal Sojka sojk...@fel.cvut.cz wrote:
This patch reworks date/time parser library test program to make it
easier to to write the actual tests. It also modifies the notmuch test
script and adds several new tests
2012-02-25 [1/8] Jani Nikula| Tomi Ollila, Mark
Walters; [RFC PATCH 0/2] natural language date range search (inbox list notmuch
notmuch::patch notmuch::wip unread watch)
thread:5191 2011-08-15 [2/8] Jani Nikula, Michal Sojka| Jason
Woofenden, Tomi Ollila; [RFC PATCH 3/3] lib: add
As mentioned by Jani Nikula in id:87vcccp4y3@nikula.org, some cases
of maildir synchronization are not covered by our tests. Let's add the
missing tests.
---
test/maildir-sync | 12
1 file changed, 12 insertions(+)
diff --git a/test/maildir-sync b/test/maildir-sync
index
From: Michal Sojka so...@os.inf.tu-dresden.de
Some MUA's like mutt show the difference between new emails living in maildir
directory new/, and old emails living in maildir directory cur/. However
notmuch tag unconditionally moves selected messages from new/ to cur/, even if
no maildir
hopefully enough to satisfy
mutt (and maybe other MUAs showing the new status) users checking the new
status.
Changelog:
* v2: Fix bool type as well as NULL returned despite having no errors (Austin
Clements)
* v4: Tag the related test (contributed by Michal Sojka) as working
Signed-off
):
tags_to_maildir_flags: Don't rename if no flags change
Michal Sojka (2):
test: Adding non-maildir tags does not move message from new to cur
test: Add some missing maildir synchronization tests
lib/message.cc| 13 -
test/maildir-sync | 20
2 files changed, 32
Hello Jani,
On Sat, Dec 08 2012, Jani Nikula wrote:
On Sat, 08 Dec 2012, da...@tethera.net wrote:
From: Michal Sojka so...@os.inf.tu-dresden.de
Some MUA's like mutt show the difference between new emails living in
maildir
directory new/, and old emails living in maildir directory cur
On Sat, Jan 25 2014, David Bremner wrote:
Michal Sojka sojk...@fel.cvut.cz writes:
Hello,
in emacs, I have a problem displaying an email that contain the
following part (--format=json):
{
content-type : image/svg+xml,
filename : _logo.svg,
id : 4
}
I
This happens when there is some garbage after the last Message-ID in
the References header. See for example
https://lkml.org/lkml/headers/2014/5/19/864.
---
test/T510-thread-replies.sh | 28
1 file changed, 28 insertions(+)
diff --git a/test/T510-thread-replies.sh
. I think that my problem is orthogonal to what was
discussed there.
The patch does not break any existing text (except two in
T460-emacs-tree.sh, which fail even with 0.18 on my system).
Cheers,
-Michal
Michal Sojka (2):
Add test for incorrect threading of messages
Make parsing of References
Hi all!
On Wed, Jul 16 2014, Trevor Jim wrote:
If you would like to incorporate things into the main branch, that
would be great. Here's what I think the status is:
The asynchronous mail address harvesting works pretty well. Much
better than having to install python etc. It would be better
Notmuch currently has an address completion mechanism that requires
external script to provide completion candidates. This patch adds a
completion mechanism found in https://github.com/tjim/nevermore, which
is implemented in elisp only.
notmuch-lib.el is extended with function
On Wed, Jul 30 2014, David Bremner wrote:
Michal Sojka sojk...@fel.cvut.cz writes:
Notmuch currently has an address completion mechanism that requires
external script to provide completion candidates. This patch adds a
completion mechanism found in https://github.com/tjim/nevermore, which
On Thu, Jul 31 2014, Trevor Jim wrote:
BTW I have been refactoring my async process code. You might consider
it for your patch.
I'll look at that. I figured out that I might also reuse
notmuch-parser.el. I'll post here my findings later.
-Michal
___
Hi David,
On Fri, Aug 01 2014, David Bremner wrote:
Michal Sojka sojk...@fel.cvut.cz writes:
notmuch-company.el hooks itself into message-mode and uses
company-mode to offer the completion to the user. The file is put into
the contrib directory which means that the use has to install
Currently, notmuch has an address completion mechanism that requires
external command to provide completion candidates. This patch adds a
completion mechanism inspired by https://github.com/tjim/nevermore,
which is implemented in Emacs lisp only.
The core of the new mechanism is the function
On 11.8.2014 17:31, Michal Sojka wrote:
Currently, notmuch has an address completion mechanism that requires
external command to provide completion candidates. This patch adds a
completion mechanism inspired by https://github.com/tjim/nevermore,
which is implemented in Emacs lisp only.
The core
out by others.
This is not (yet) based on Jani's patch for printing the addresses by
notmuch search (id:1410021689-15901-1-git-send-email-j...@nikula.org).
I'll at this as a next step as it will simplify the elisp code and
make the address completion faster.
Michal Sojka (3):
Emacs: Display
The TAB-initiated address completion generates completion candidates
synchronously, blocking the UI. Since this can take long time, it is
better to let the use know what's happening.
---
emacs/notmuch-address.el | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
+1,81 @@
+;; notmuch-company.el --- Mail address completion for notmuch via company-mode
-*- no-byte-compile: t; lexical-binding: t -*-
+
+
+;; Authors: Trevor Jim t...@mac.com
+;; Michal Sojka sojk...@fel.cvut.cz
+;;
+;; Keywords: mail, completion
+
+;; This program is free software; you
Currently, notmuch has an address completion mechanism that requires
external command to provide completion candidates. This patch adds a
completion mechanism inspired by https://github.com/tjim/nevermore,
which is implemented in Emacs lisp only.
The preexisting address completion mechanism,
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only this structure.
This will become handy in the following patches.
---
notmuch-search.c | 122
---
test/T090-search-output.sh | 59 +++
test/T095-search-unique.sh | 63 ++
2 files changed, 122 insertions(+)
create mode 100755 test/T095-search-unique.sh
diff --git a/test/T090-search-output.sh
The new outputs allow printing senders, recipients or both of matching
messages.
This code based on a patch from Jani Nikula.
---
completion/notmuch-completion.bash | 2 +-
completion/notmuch-completion.zsh | 3 +-
doc/man1/notmuch-search.rst| 22 +++-
notmuch-search.c
).
Another nice use case is sending patched with git:
git send-email --cc-cmd='nmsenders id:' ...
where nmsenders script contains:
notmuch search --output=sender $(notmuch search --output=threads $1)
Michal Sojka (5):
cli: Refactor option passing in the search command
cli: Extend
On Thu, Sep 25 2014, Tomi Ollila wrote:
On Mon, Sep 22 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only
Hi Olivier,
On Wed, Sep 24 2014, Olivier Berger wrote:
Hi.
Maybe this is obvious, but I can't figure out how to change the sort
order from inside a threaded view when reviewing discussions in a
thread, in Emacs.
Using removes thread indentation, but then I'm not sure what the sort
order
Hi David,
On Sat, Sep 27 2014, David Bremner wrote:
A future modification of notmuch_message_tags_to_maildir_flags and
notmuch_message_maildir_flags_to_tags could allow 26 more tags to be
synced via maildir.
---
I'm not sure if this is worth pursuing or not, but I thought I'd toss
it out
On Wed, Oct 01 2014, Sergei Shilovsky wrote:
---
doc/man1/notmuch-config.rst | 18 ++
1 file changed, 18 insertions(+)
diff --git a/doc/man1/notmuch-config.rst b/doc/man1/notmuch-config.rst
index 3c9a568..9de5534 100644
--- a/doc/man1/notmuch-config.rst
+++
):
cli: Add support for parsing multiple keyword arguments
Michal Sojka (3):
cli: Refactor option passing in the search command
cli: Extend the search command for --output=addresses and similar
cli: Add configurable address deduplication for --output=addresses
command-line-arguments.c
The code here is an extended version of a patch from Jani Nikula.
---
completion/notmuch-completion.bash | 6 ++-
completion/notmuch-completion.zsh | 3 +-
doc/man1/notmuch-search.rst| 32
notmuch-search.c | 101 ++---
From: Jani Nikula j...@nikula.org
This allows having multiple --foo=bar --foo=baz options on the command
line, with the corresponding values OR'd together.
[Test added by Michal Sojka]
---
command-line-arguments.c | 6 +-
command-line-arguments.h | 1 +
test/T410-argument
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only this structure.
This will become handy in the following patches.
---
notmuch-search.c | 122
The new outputs allow printing senders, recipients or both of matching
messages.
This code based on a patch from Jani Nikula.
---
completion/notmuch-completion.bash | 2 +-
completion/notmuch-completion.zsh | 3 +-
doc/man1/notmuch-search.rst| 22 +++-
notmuch-search.c
On Mon, Oct 06 2014, Tomi Ollila wrote:
On Sun, Oct 05 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
The new outputs allow printing senders, recipients or both of matching
messages.
This code based on a patch from Jani Nikula.
OK, IMO...
1/4 OK
Before 2/4 add support for 'flag
multiple keyword arguments
Michal Sojka (3):
cli: Refactor option passing in the search command
cli: Extend the search command for --output={sender,recipients}
cli: Add an option to filter our duplicate addresses
command-line-arguments.c | 6 +-
command-line-arguments.h
From: Jani Nikula j...@nikula.org
This allows having multiple --foo=bar --foo=baz options on the command
line, with the corresponding values OR'd together.
[Test added by Michal Sojka]
---
command-line-arguments.c | 6 +-
command-line-arguments.h | 1 +
test/T410-argument
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only this structure.
This will become handy in the following patches.
---
notmuch-search.c | 122
This adds a --filter-by option to notmuch search. It can be used to
filter out duplicate addresses in --output=sender/receivers.
The code here is an extended version of a patch from Jani Nikula.
---
completion/notmuch-completion.bash | 6 ++-
completion/notmuch-completion.zsh | 3 +-
The new outputs allow printing senders, recipients or both of matching
messages. The --output option is converted from keyword argument to
flags argument, which means that the user can use --output=sender and
--output=recipients simultaneously, to print both. Other combinations
produce an error.
Hi Mark,
I mostly agree with your points mentioned in this and other your emails.
I'll prepare v4 based on that.
On Wed, Oct 22 2014, Mark Walters wrote:
On Sun, 12 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
The new outputs allow printing senders, recipients or both of matching
This output can be used with --output=recipients or --output=sender and
in addition to the mailboxes, it prints how many times was each mailbox
encountered during search.
---
completion/notmuch-completion.bash | 2 +-
completion/notmuch-completion.zsh | 2 +-
doc/man1/notmuch-search.rst
- There is no way to output unfiltered (duplicite) addresses.
Hopefully, the introduction of --output=count is sufficient
replacement for this feature.
Cheers,
-Michal
Jani Nikula (1):
cli: Add support for parsing keyword-flag arguments
Michal Sojka (5):
cli: search: Refactor passing of command line
The new outputs allow printing senders, recipients or both of matching
messages. To print both, the user can use --output=sender and
--output=recipients simultaneously.
Currently, the same address can appear multiple times in the output. The
next patch will change this. For this reason, the test
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only this structure.
This will become handy in the following patches.
---
notmuch-search.c | 125
This converts notmuch search to use the recently introduced
keyword-flag argument parser. At this point, it only makes the code
slightly less readable but following patches that add new --output
keywords will profit from this.
---
notmuch-search.c | 35 ++-
1 file
From: Jani Nikula j...@nikula.org
This allows having multiple --foo=bar --foo=baz options on the command
line, with the corresponding values OR'd together.
[Test added by Michal Sojka]
---
command-line-arguments.c | 6 +-
command-line-arguments.h | 1 +
test/T410-argument
Hi Mark,
On Thu, Oct 30 2014, Mark Walters wrote:
Hi
On Mon, 27 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass
On Thu, Oct 30 2014, Mark Walters wrote:
On Mon, 27 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
This adds an algorithm to filter out duplicate addresses from address
outputs (sender, receivers). The algorithm can be configured with
--filter-by command line option.
The code here
On Thu, Oct 30 2014, Tomi Ollila wrote:
On Thu, Oct 30 2014, Mark Walters markwalters1...@gmail.com wrote:
On Mon, 27 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
This adds an algorithm to filter out duplicate addresses from address
outputs (sender, receivers). The algorithm can
: Add support for parsing keyword-flag arguments
Michal Sojka (6):
cli: search: Refactor passing of command line options
cli: search: Convert --output to keyword-flag argument
cli: search: Add --output={sender,recipients}
cli: search: Do not output duplicate addresses
cli: search: Add
Many functions that implement the search command need to access command
line options. Instead of passing each option in a separate variable, put
them in a structure and pass only this structure.
This will become handy in the following commits.
---
notmuch-search.c | 125
From: Jani Nikula j...@nikula.org
This allows having multiple --foo=bar --foo=baz options on the command
line, with the corresponding values OR'd together.
[Test added by Michal Sojka]
---
command-line-arguments.c | 6 +-
command-line-arguments.h | 1 +
test/T410-argument
This converts notmuch search to use the recently introduced
keyword-flag argument parser. At this point, it only makes the code
slightly less readable but following commits that add new --output
keywords will profit from this.
---
notmuch-search.c | 35 ++-
1 file
The new outputs allow printing senders, recipients or both of matching
messages. To print both, the user can use --output=sender and
--output=recipients simultaneously.
Currently, the same address can appear multiple times in the output.
The next commit will change this. For this reason, tests
This output can be used with --output=recipients or --output=sender
and in addition to the addresses, it prints how many times was each
address encountered during search.
---
completion/notmuch-completion.bash | 2 +-
completion/notmuch-completion.zsh | 2 +-
doc/man1/notmuch-search.rst
This option allows to configure the criterion for duplicate address
filtering. Without this option, all unique combinations of name and
address parts are printed. This option allows to filter the output
more, for example to only contain unique address parts.
---
completion/notmuch-completion.bash
201 - 300 of 883 matches
Mail list logo
