Tabulation in multiline headers
> Hi, Sergei. I'm not clear on where exactly you are seeing a problem > with this tab in the subject line. Is it showing up somewhere you think > it shouldn't? It is shown in e.g. `notmuch show` as well as 'notmuch_message_get_header(m, "subject")` > I'm not sure libnotmuch should be doing any scrubbing of the message > contents. The emacs UI does seem to replace the tab with a space, > though. Maybe other MUAs should be doing the same? My point is that this tabulation character does not relate to the contents of the header (this might be arguable though) and libnotmuch should return the contents, not its representation on file system. -- ? ?, ?? ? Sergei Shilovsky
Tabulation in multiline headers
Lets consider this message: id:87r5aucoeg.fsf at servo.finestructure.net Its subject spreads over 2 lines and the 2nd line is indented with in the file: Subject: running the crypto branch [was: Re: Hiding HTML mime-parts and/or scrubbing (gmail's) HTML-based citation] The issue is that notmuch_message_get_header() returns this whole line with the Tab character (though I guess it should not): running the crypto branch [was: Re: Hiding HTML mime-parts and/orscrubbing (gmail's) HTML-based citation] This file could be imported from gmane though with mb2md. My test long subject message (sent via gmail) didn't got any tabulation. No idea where this tabulation could came from, but would that be correct to replace with space in libnotmuch itself? -- ? ?, ?? ????? Sergei Shilovsky
Re: Tabulation in multiline headers
> Hi, Sergei. I'm not clear on where exactly you are seeing a problem > with this tab in the subject line. Is it showing up somewhere you think > it shouldn't? It is shown in e.g. `notmuch show` as well as 'notmuch_message_get_header(m, "subject")` > I'm not sure libnotmuch should be doing any scrubbing of the message > contents. The emacs UI does seem to replace the tab with a space, > though. Maybe other MUAs should be doing the same? My point is that this tabulation character does not relate to the contents of the header (this might be arguable though) and libnotmuch should return the contents, not its representation on file system. -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Tabulation in multiline headers
Lets consider this message: id:87r5aucoeg@servo.finestructure.net Its subject spreads over 2 lines and the 2nd line is indented with in the file: Subject: running the crypto branch [was: Re: Hiding HTML mime-parts and/or scrubbing (gmail's) HTML-based citation] The issue is that notmuch_message_get_header() returns this whole line with the Tab character (though I guess it should not): running the crypto branch [was: Re: Hiding HTML mime-parts and/orscrubbing (gmail's) HTML-based citation] This file could be imported from gmane though with mb2md. My test long subject message (sent via gmail) didn't got any tabulation. No idea where this tabulation could came from, but would that be correct to replace with space in libnotmuch itself? -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] man: add notes about issues with notmuch-count
1. notmuch count --output=messages outputs estimated number 2. notmuch count --output=(files|threads) can be slow --- doc/man1/notmuch-count.rst | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/man1/notmuch-count.rst b/doc/man1/notmuch-count.rst index ca78c18..3bb6981 100644 --- a/doc/man1/notmuch-count.rst +++ b/doc/man1/notmuch-count.rst @@ -10,7 +10,7 @@ SYNOPSIS DESCRIPTION === -Count messages matching the search terms. +Count (an estimate of) the number of messages matching the search terms. The number of matching messages (or threads) is output to stdout. @@ -25,16 +25,20 @@ Supported options for **count** include ``--output=(messages|threads|files)`` **messages** -Output the number of matching messages. This is the default. +Output an estimate of the number of matching messages. This is the +default. **threads** -Output the number of matching threads. +Output the exact number of matching threads. The search is +performed, so this is a significantly heavier operation than +``--output=messages``. **files** -Output the number of files associated with matching +Output the exact number of files associated with matching messages. This may be bigger than the number of matching messages due to duplicates (i.e. multiple files having the -same message-id). +same message-id). The search is performed, so this is a +significantly heavier operation than ``--output=messages``. ``--exclude=(true|false)`` Specify whether to omit messages matching search.tag\_exclude -- 2.1.0
[PATCH] man: add notes about issues with notmuch-count
Here are some notes to 'notmuch-count' man page and a couple of related suggestions/questions for possible discussion: 1. `notmuch count --output=(messages-exact|messages-estimate)`. Maybe with notmuch_query_count_messages_exact function 2. extract `notmuch count --output=files` to notmuch_query_count_filenames library function Sergei Shilovsky (1): man: add notes about issues with notmuch-count doc/man1/notmuch-count.rst | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) -- 2.1.0
[PATCH v2] Add default configuration values to the man page
--- doc/man1/notmuch-config.rst | 21 + 1 file changed, 21 insertions(+) diff --git a/doc/man1/notmuch-config.rst b/doc/man1/notmuch-config.rst index 3c9a568..2676a86 100644 --- a/doc/man1/notmuch-config.rst +++ b/doc/man1/notmuch-config.rst @@ -49,19 +49,31 @@ The available configuration items are described below. within a sub-directory of the path configured here named ``.notmuch``. +Default: ``$MAILDIR`` variable if set, otherwise ``$HOME/mail``. + **user.name** Your full name. +Default: ``$NAME`` variable if set, otherwise read from +``/etc/passwd``. + **user.primary\_email** Your primary email address. +Default: ``$EMAIL`` variable if set, otherwise constructed from the +username and hostname of the current machine. + **user.other\_email** A list of other email addresses at which you receive email. +Default: not set. + **new.tags** A list of tags that will be added to all messages incorporated by **notmuch new**. +Default: ``unread;inbox``. + **new.ignore** A list of file and directory names, without path, that will not be searched for messages by **notmuch new**. All the files and @@ -69,11 +81,18 @@ The available configuration items are described below. ignored, regardless of the location in the mail store directory hierarchy. +Default: empty list. + **search.exclude\_tags** A list of tags that will be excluded from search results by default. Using an excluded tag in a query will override that exclusion. +Default: empty list. Note that **notmuch-setup(1)** puts +``deleted;spam`` here when creating new configuration file. + + + **maildir.synchronize\_flags** If true, then the following maildir flags (in message filenames) will be synchronized with the corresponding notmuch tags: @@ -104,6 +123,8 @@ The available configuration items are described below. are properly synchronized to the maildir flags, as the commands expect the database and maildir to be in sync. +Default: ``true``. + ENVIRONMENT === -- 2.1.0
[PATCH] man: add notes about issues with notmuch-count
Here are some notes to 'notmuch-count' man page and a couple of related suggestions/questions for possible discussion: 1. `notmuch count --output=(messages-exact|messages-estimate)`. Maybe with notmuch_query_count_messages_exact function 2. extract `notmuch count --output=files` to notmuch_query_count_filenames library function Sergei Shilovsky (1): man: add notes about issues with notmuch-count doc/man1/notmuch-count.rst | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) -- 2.1.0 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] man: add notes about issues with notmuch-count
1. notmuch count --output=messages outputs estimated number 2. notmuch count --output=(files|threads) can be slow --- doc/man1/notmuch-count.rst | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/man1/notmuch-count.rst b/doc/man1/notmuch-count.rst index ca78c18..3bb6981 100644 --- a/doc/man1/notmuch-count.rst +++ b/doc/man1/notmuch-count.rst @@ -10,7 +10,7 @@ SYNOPSIS DESCRIPTION === -Count messages matching the search terms. +Count (an estimate of) the number of messages matching the search terms. The number of matching messages (or threads) is output to stdout. @@ -25,16 +25,20 @@ Supported options for **count** include ``--output=(messages|threads|files)`` **messages** -Output the number of matching messages. This is the default. +Output an estimate of the number of matching messages. This is the +default. **threads** -Output the number of matching threads. +Output the exact number of matching threads. The search is +performed, so this is a significantly heavier operation than +``--output=messages``. **files** -Output the number of files associated with matching +Output the exact number of files associated with matching messages. This may be bigger than the number of matching messages due to duplicates (i.e. multiple files having the -same message-id). +same message-id). The search is performed, so this is a +significantly heavier operation than ``--output=messages``. ``--exclude=(true|false)`` Specify whether to omit messages matching search.tag\_exclude -- 2.1.0 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH v2] Add default configuration values to the man page
--- doc/man1/notmuch-config.rst | 21 + 1 file changed, 21 insertions(+) diff --git a/doc/man1/notmuch-config.rst b/doc/man1/notmuch-config.rst index 3c9a568..2676a86 100644 --- a/doc/man1/notmuch-config.rst +++ b/doc/man1/notmuch-config.rst @@ -49,19 +49,31 @@ The available configuration items are described below. within a sub-directory of the path configured here named ``.notmuch``. +Default: ``$MAILDIR`` variable if set, otherwise ``$HOME/mail``. + **user.name** Your full name. +Default: ``$NAME`` variable if set, otherwise read from +``/etc/passwd``. + **user.primary\_email** Your primary email address. +Default: ``$EMAIL`` variable if set, otherwise constructed from the +username and hostname of the current machine. + **user.other\_email** A list of other email addresses at which you receive email. +Default: not set. + **new.tags** A list of tags that will be added to all messages incorporated by **notmuch new**. +Default: ``unread;inbox``. + **new.ignore** A list of file and directory names, without path, that will not be searched for messages by **notmuch new**. All the files and @@ -69,11 +81,18 @@ The available configuration items are described below. ignored, regardless of the location in the mail store directory hierarchy. +Default: empty list. + **search.exclude\_tags** A list of tags that will be excluded from search results by default. Using an excluded tag in a query will override that exclusion. +Default: empty list. Note that **notmuch-setup(1)** puts +``deleted;spam`` here when creating new configuration file. + + + **maildir.synchronize\_flags** If true, then the following maildir flags (in message filenames) will be synchronized with the corresponding notmuch tags: @@ -104,6 +123,8 @@ The available configuration items are described below. are properly synchronized to the maildir flags, as the commands expect the database and maildir to be in sync. +Default: ``true``. + ENVIRONMENT === -- 2.1.0 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] Avoid empty thread names if possible.
I would also suggest to drop subjects consisting of only "Re:" and "Fwd" sequences
Re: [PATCH] Avoid empty thread names if possible.
I would also suggest to drop subjects consisting of only "Re:" and "Fwd" sequences ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Backward scrolling notmuch_messages_t and notmuch_threads_t
notmuch search --offset` simply skips the number of threads/messages.
This is not so fast if the offset is large.
98 for (i = 0;
99 notmuch_threads_valid (threads) && (limit < 0 || i <
offset + limit);
100 notmuch_threads_move_to_next (threads), i++)
101 {
102 thread = notmuch_threads_get (threads);
103
104 if (i < offset) {
105 notmuch_thread_destroy (thread);
106 continue;
107 }
On Tue, Oct 7, 2014 at 3:16 PM, Jani Nikula wrote:
> On Tue, 07 Oct 2014, Sergei Shilovsky wrote:
>> Lets consider messages first.
>>
>> As far as I get there is no straightforward
>> notmuch_messages_move_to_previous. One can usually implement such
>> behaviour with caching previous messages which is slightly inefficient
>> in memory consumption terms.
>>
>> But we can sort messages either date asc or date desc.
>>
>> Suppose, we're currently at the 1000th message in query "tag:whatever".
>>
>> So if we need to go to the previous message we could do something like
>>
>> notmuch search --sort=oldest-first tag:whatever and \
>> date:..
>>
>> This query's result should start with our 1000th message following its
>> previous message (in terms of the original request). So backward
>> scrolling with no cache looks to be at least possible.
>>
>> Any idea of would that be fine? Is it possible to implement similar
>> thing at low-level?
>
> See notmuch search --offset=N and --limit=N options.
>
> BR,
> Jani.
>
>
>>
>> --
>> ? ?,
>> ?? ?????
>> Sergei Shilovsky
>> ___
>> notmuch mailing list
>> notmuch at notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch
--
? ?,
?? ?
Sergei Shilovsky
Backward scrolling notmuch_messages_t and notmuch_threads_t
Lets consider messages first. As far as I get there is no straightforward notmuch_messages_move_to_previous. One can usually implement such behaviour with caching previous messages which is slightly inefficient in memory consumption terms. But we can sort messages either date asc or date desc. Suppose, we're currently at the 1000th message in query "tag:whatever". So if we need to go to the previous message we could do something like notmuch search --sort=oldest-first tag:whatever and \ date:.. This query's result should start with our 1000th message following its previous message (in terms of the original request). So backward scrolling with no cache looks to be at least possible. Any idea of would that be fine? Is it possible to implement similar thing at low-level? -- ? ?, ?????? ????? Sergei Shilovsky
Re: Backward scrolling notmuch_messages_t and notmuch_threads_t
notmuch search --offset` simply skips the number of threads/messages.
This is not so fast if the offset is large.
98 for (i = 0;
99 notmuch_threads_valid (threads) && (limit < 0 || i <
offset + limit);
100 notmuch_threads_move_to_next (threads), i++)
101 {
102 thread = notmuch_threads_get (threads);
103
104 if (i < offset) {
105 notmuch_thread_destroy (thread);
106 continue;
107 }
On Tue, Oct 7, 2014 at 3:16 PM, Jani Nikula wrote:
> On Tue, 07 Oct 2014, Sergei Shilovsky wrote:
>> Lets consider messages first.
>>
>> As far as I get there is no straightforward
>> notmuch_messages_move_to_previous. One can usually implement such
>> behaviour with caching previous messages which is slightly inefficient
>> in memory consumption terms.
>>
>> But we can sort messages either date asc or date desc.
>>
>> Suppose, we're currently at the 1000th message in query "tag:whatever".
>>
>> So if we need to go to the previous message we could do something like
>>
>> notmuch search --sort=oldest-first tag:whatever and \
>> date:..
>>
>> This query's result should start with our 1000th message following its
>> previous message (in terms of the original request). So backward
>> scrolling with no cache looks to be at least possible.
>>
>> Any idea of would that be fine? Is it possible to implement similar
>> thing at low-level?
>
> See notmuch search --offset=N and --limit=N options.
>
> BR,
> Jani.
>
>
>>
>> --
>> С уважением,
>> Сергей Шиловский
>> Sergei Shilovsky
>> ___
>> notmuch mailing list
>> notmuch@notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch
--
С уважением,
Сергей Шиловский
Sergei Shilovsky
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Backward scrolling notmuch_messages_t and notmuch_threads_t
Lets consider messages first. As far as I get there is no straightforward notmuch_messages_move_to_previous. One can usually implement such behaviour with caching previous messages which is slightly inefficient in memory consumption terms. But we can sort messages either date asc or date desc. Suppose, we're currently at the 1000th message in query "tag:whatever". So if we need to go to the previous message we could do something like notmuch search --sort=oldest-first tag:whatever and \ date:.. This query's result should start with our 1000th message following its previous message (in terms of the original request). So backward scrolling with no cache looks to be at least possible. Any idea of would that be fine? Is it possible to implement similar thing at low-level? -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] debian: append elinks to notmuch-vim dependencies
notmuch-vim uses elinks to convert HTML messages to text.
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 6298deb..146dfea 100644
--- a/debian/control
+++ b/debian/control
@@ -128,7 +128,7 @@ Architecture: all
Section: mail
Breaks: notmuch (<<0.6~254~)
Replaces: notmuch (<<0.6~254~)
-Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, ruby-notmuch
+Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, ruby-notmuch,
elinks
Recommends: ruby-mail
Description: thread-based email index, search and tagging (vim interface)
Notmuch is a system for indexing, searching, reading, and tagging
--
2.1.0
[PATCH v2] VIM: Use notmuch CLI for config
The patch works fine for me. Ian, though I could not test whether result='' matters or not, cause 'notmuch get' looks to always return a string. It also fixes id:CAHc2pO19AZabAiJhdfQR1rL5t0GufLAq5cKb_7w-Z8y+JXT5+g at mail.gmail.com On Fri, Oct 3, 2014 at 10:54 AM, David Bremner wrote: > Ian Main writes: > >> This patch switches from reading .notmuch-config directly to using >> the CLI the same way that emacs does it. It actually uses less code >> and is probably less error prone. >> >> Ian > > The general approach seems sane; it seems quite brittle to read the > config file directly. I notice there is not really any error handling; > OTOH, as far as I can read Ruby, there is not any in the previous > version either. Technically, this does add a dependency of the vim > client on the CLI that did not exist before. Personally I don't find > this onerous (even notmuch-vim users need "notmuch new", except in > rather unusual circumstances.). > > I'd like feedback/testing from actual vim interface users before > merging. > > ___ > notmuch mailing list > notmuch at notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch -- ? ?, ?? ? Sergei Shilovsky
[PATCH] debian: append elinks to notmuch-vim dependencies
notmuch-vim uses elinks to convert HTML messages to text.
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 6298deb..146dfea 100644
--- a/debian/control
+++ b/debian/control
@@ -128,7 +128,7 @@ Architecture: all
Section: mail
Breaks: notmuch (<<0.6~254~)
Replaces: notmuch (<<0.6~254~)
-Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, ruby-notmuch
+Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, ruby-notmuch,
elinks
Recommends: ruby-mail
Description: thread-based email index, search and tagging (vim interface)
Notmuch is a system for indexing, searching, reading, and tagging
--
2.1.0
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v2] VIM: Use notmuch CLI for config
The patch works fine for me. Ian, though I could not test whether result='' matters or not, cause 'notmuch get' looks to always return a string. It also fixes id:cahc2po19azabaijhdfqr1rl5t0guflaq5ckb_7w-z8y+jxt...@mail.gmail.com On Fri, Oct 3, 2014 at 10:54 AM, David Bremner wrote: > Ian Main writes: > >> This patch switches from reading .notmuch-config directly to using >> the CLI the same way that emacs does it. It actually uses less code >> and is probably less error prone. >> >> Ian > > The general approach seems sane; it seems quite brittle to read the > config file directly. I notice there is not really any error handling; > OTOH, as far as I can read Ruby, there is not any in the previous > version either. Technically, this does add a dependency of the vim > client on the CLI that did not exist before. Personally I don't find > this onerous (even notmuch-vim users need "notmuch new", except in > rather unusual circumstances.). > > I'd like feedback/testing from actual vim interface users before > merging. > > ___ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
notmuch-vim doesn't respect notmuch config defaults
I would suggest to use `notmuch config list` to get configuration values in vim if possible Reproduction example follows: /home/sh> cat .notmuch-config [new] tags=new;inbox;unread ignore= [search] exclude_tags=deleted;spam [maildir] synchronize_flags=false /home/sh> notmuch config list new.tags=new;inbox;unread new.ignore= search.exclude_tags=deleted;spam maildir.synchronize_flags=false database.path=/home/sh/mail user.name=Sergei Shilovsky user.primary_email=sshilovsky at gmail.com /home/sh> vim -c :NotMuch Error detected while processing function 13_NotMuch..13_folders.. 13_new_buffer: line6: TypeError: no implicit conversion of nil into String Error detected while processing function 13_NotMuch..13_folders: line2: NoMethodError: undefined method `query' for nil:NilClass Having explicit database.path=/home/sh/mail in the configuration file makes it work -- ? ?, ?????? ????? Sergei Shilovsky
notmuch-vim doesn't respect notmuch config defaults
I would suggest to use `notmuch config list` to get configuration values in vim if possible Reproduction example follows: /home/sh> cat .notmuch-config [new] tags=new;inbox;unread ignore= [search] exclude_tags=deleted;spam [maildir] synchronize_flags=false /home/sh> notmuch config list new.tags=new;inbox;unread new.ignore= search.exclude_tags=deleted;spam maildir.synchronize_flags=false database.path=/home/sh/mail user.name=Sergei Shilovsky user.primary_email=sshilov...@gmail.com /home/sh> vim -c :NotMuch Error detected while processing function 13_NotMuch..13_folders.. 13_new_buffer: line6: TypeError: no implicit conversion of nil into String Error detected while processing function 13_NotMuch..13_folders: line2: NoMethodError: undefined method `query' for nil:NilClass Having explicit database.path=/home/sh/mail in the configuration file makes it work -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] Add default configuration values to the man page
--- 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 +++ b/doc/man1/notmuch-config.rst @@ -49,19 +49,31 @@ The available configuration items are described below. within a sub-directory of the path configured here named ``.notmuch``. +Default: ``$MAILDIR``, otherwise ``$HOME/mail``. + **user.name** Your full name. +Default: ``$NAME`` variable if set, otherwise read from +``/etc/passwd``. + **user.primary\_email** Your primary email address. +Default: ``$EMAIL`` variable if set, otherwise constructed from the +username and hostname of the current machine. + **user.other\_email** A list of other email addresses at which you receive email. +Default: not set. + **new.tags** A list of tags that will be added to all messages incorporated by **notmuch new**. +Default: ``unread;inbox``. + **new.ignore** A list of file and directory names, without path, that will not be searched for messages by **notmuch new**. All the files and @@ -69,11 +81,15 @@ The available configuration items are described below. ignored, regardless of the location in the mail store directory hierarchy. +Default: no tags. + **search.exclude\_tags** A list of tags that will be excluded from search results by default. Using an excluded tag in a query will override that exclusion. +Default: ``deleted;spam``. + **maildir.synchronize\_flags** If true, then the following maildir flags (in message filenames) will be synchronized with the corresponding notmuch tags: @@ -104,6 +120,8 @@ The available configuration items are described below. are properly synchronized to the maildir flags, as the commands expect the database and maildir to be in sync. +Default: ``true``. + ENVIRONMENT === -- 2.1.0
[PATCH] Add default configuration values to the man page
--- 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 +++ b/doc/man1/notmuch-config.rst @@ -49,19 +49,31 @@ The available configuration items are described below. within a sub-directory of the path configured here named ``.notmuch``. +Default: ``$MAILDIR``, otherwise ``$HOME/mail``. + **user.name** Your full name. +Default: ``$NAME`` variable if set, otherwise read from +``/etc/passwd``. + **user.primary\_email** Your primary email address. +Default: ``$EMAIL`` variable if set, otherwise constructed from the +username and hostname of the current machine. + **user.other\_email** A list of other email addresses at which you receive email. +Default: not set. + **new.tags** A list of tags that will be added to all messages incorporated by **notmuch new**. +Default: ``unread;inbox``. + **new.ignore** A list of file and directory names, without path, that will not be searched for messages by **notmuch new**. All the files and @@ -69,11 +81,15 @@ The available configuration items are described below. ignored, regardless of the location in the mail store directory hierarchy. +Default: no tags. + **search.exclude\_tags** A list of tags that will be excluded from search results by default. Using an excluded tag in a query will override that exclusion. +Default: ``deleted;spam``. + **maildir.synchronize\_flags** If true, then the following maildir flags (in message filenames) will be synchronized with the corresponding notmuch tags: @@ -104,6 +120,8 @@ The available configuration items are described below. are properly synchronized to the maildir flags, as the commands expect the database and maildir to be in sync. +Default: ``true``. + ENVIRONMENT === -- 2.1.0 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
gui client
Hi, Is there a GUI notmuch client? Or is somebody working on it? I'm thinking of writing one myself, so I want to know current situation. -- ? ?, ?? ? Sergei Shilovsky
gui client
Hi, Is there a GUI notmuch client? Or is somebody working on it? I'm thinking of writing one myself, so I want to know current situation. -- С уважением, Сергей Шиловский Sergei Shilovsky ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
