On Tue, 04 Nov 2014, Michal Sojka wrote:
> On Tue, Nov 04 2014, Mark Walters wrote:
>> On Mon, 03 Nov 2014, Michal Sojka wrote:
>>> This moves address-related functionality from search command to the
>>> new address command. The implementation shares almost all cod
On Mon, 03 Nov 2014, Michal Sojka wrote:
> Hi all,
>
> this is v2 of "notmuch address" patchset. It obsoletes [1].
>
> Don't be scared by the number of patches. Most of them are trivial
> refactoring. Patches 1-4 refactor the code so that "notmuch search"
> command is easier to split. Patch 5 is
On Sat, 01 Nov 2014, Jani Nikula wrote:
> On Sat, 01 Nov 2014, Michal Sojka wrote:
>> On Sat, Nov 01 2014, Jani Nikula wrote:
>>> On Fri, 31 Oct 2014, Michal Sojka wrote:
This option allows to configure the criterion for duplicate address
filtering. Without this option, all unique com
On Mon, 03 Nov 2014, Michal Sojka wrote:
> This output prints how many times was each address encountered during
> search.
> ---
> completion/notmuch-completion.bash | 2 +-
> completion/notmuch-completion.zsh | 2 +-
> doc/man1/notmuch-address.rst | 7 ++
> notmuch-search.c
> Hi
>
> On Mon, 03 Nov 2014, Michal Sojka wrote:
>> Now, when address related outputs are in a separate command, it makes
>> no sense to combine multiple --output options in search command line.
>> Using switch statement to handle different outputs is more readable
>> than a series of if stateme
On Mon, 03 Nov 2014, Michal Sojka wrote:
> This moves address-related functionality from search command to the
> new address command. The implementation shares almost all code and
> some command line options.
>
> Options --offset and --limit were intentionally not included in the
> address command
Hi
On Mon, 03 Nov 2014, Michal Sojka wrote:
> Now, when address related outputs are in a separate command, it makes
> no sense to combine multiple --output options in search command line.
> Using switch statement to handle different outputs is more readable
> than a series of if statements.
I a
On Mon, 03 Nov 2014, Michal Sojka wrote:
> Hi all,
>
> this is v2 of "notmuch address" patchset. It obsoletes [1].
>
> Don't be scared by the number of patches. Most of them are trivial
> refactoring. Patches 1-4 refactor the code so that "notmuch search"
> command is easier to split. Patch 5 is
On Sat, 01 Nov 2014, Jani Nikula wrote:
> On Sat, 01 Nov 2014, Michal Sojka wrote:
>> On Sat, Nov 01 2014, Jani Nikula wrote:
>>> On Fri, 31 Oct 2014, Michal Sojka wrote:
This option allows to configure the criterion for duplicate address
filtering. Without this option, all unique com
On Mon, 03 Nov 2014, Michal Sojka wrote:
> This output prints how many times was each address encountered during
> search.
> ---
> completion/notmuch-completion.bash | 2 +-
> completion/notmuch-completion.zsh | 2 +-
> doc/man1/notmuch-address.rst | 7 ++
> notmuch-search.c
> Hi
>
> On Mon, 03 Nov 2014, Michal Sojka wrote:
>> Now, when address related outputs are in a separate command, it makes
>> no sense to combine multiple --output options in search command line.
>> Using switch statement to handle different outputs is more readable
>> than a series of if stateme
On Mon, 03 Nov 2014, Michal Sojka wrote:
> This moves address-related functionality from search command to the
> new address command. The implementation shares almost all code and
> some command line options.
>
> Options --offset and --limit were intentionally not included in the
> address command
Hi
On Mon, 03 Nov 2014, Michal Sojka wrote:
> Now, when address related outputs are in a separate command, it makes
> no sense to combine multiple --output options in search command line.
> Using switch statement to handle different outputs is more readable
> than a series of if statements.
I a
Hi
On Sun, 02 Nov 2014, Michal Sojka wrote:
> On Sat, Nov 01 2014, Mark Walters wrote:
>> On Fri, 31 Oct 2014, Michal Sojka wrote:
>>> This output can be used with --output=recipients or --output=sender
>>> and in addition to the addresses, it prints how many
Hi
On Sun, 02 Nov 2014, Michal Sojka wrote:
> On Sat, Nov 01 2014, Mark Walters wrote:
>> On Fri, 31 Oct 2014, Michal Sojka wrote:
>>> This output can be used with --output=recipients or --output=sender
>>> and in addition to the addresses, it prints how many
On Fri, 31 Oct 2014, Michal Sojka wrote:
> 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.
Hi
I have a couple comments on this patch.
> ---
> completion/notmuch-compl
full diff below):
>
> - Added quoting of name parts if that is necessary (pointed out by
> Mark Walters). Structured formats contain both full address
> (possibly with quoted name) and unquoted individual fields.
> - Fixed bug in --output=count --filter-by=*fold (reported by Jess
On Fri, 31 Oct 2014, Michal Sojka wrote:
> 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.
Hi
I have a couple comments on this patch.
> ---
> completion/notmuch-compl
On Fri, 31 Oct 2014, Tomi Ollila wrote:
> On Fri, Oct 31 2014, Michal Sojka wrote:
>
>> On Fri, Oct 31 2014, Mark Walters wrote:
>>> My only query is in the text output: should the name part be printed as
>>> a quoted string. For example currently I get a line of
Hi
On Fri, 31 Oct 2014, Michal Sojka wrote:
> On Fri, Oct 31 2014, Mark Walters wrote:
>> My only query is in the text output: should the name part be printed as
>> a quoted string. For example currently I get a line of the form
>>
>> Bloggs, Fred
>
> Good poi
Hi
I attach a patch which does the quoting for real names but I don't know
if we want it: it changes (example taken from the test suite)
Fran?ois Boulogne to
=?iso-8859-1?q?Fran=E7ois?= Boulogne
(which is what was in the original email)
Plausibly the best thing is just to leave the series as
On Fri, 31 Oct 2014, Tomi Ollila wrote:
> On Fri, Oct 31 2014, Michal Sojka wrote:
>
>> On Fri, Oct 31 2014, Mark Walters wrote:
>>> My only query is in the text output: should the name part be printed as
>>> a quoted string. For example currently I get a line of
Hi
On Fri, 31 Oct 2014, Michal Sojka wrote:
> On Fri, Oct 31 2014, Mark Walters wrote:
>> My only query is in the text output: should the name part be printed as
>> a quoted string. For example currently I get a line of the form
>>
>> Bloggs, Fred
>
> Good poi
On Thu, 30 Oct 2014, Michal Sojka wrote:
> Hi all,
>
> this is v5 of the search --output=address series. It obsoletes v4
> (id:1414421455-3037-1-git-send-email-sojkam1 at fel.cvut.cz).
>
> I addresses comments from Mark and Tomi. Based on the comments to v4
> and earlier versions, patches 1-4 shou
es as is, so the
text output is readable and parseable in the common cases.
Anyway the patch is attached if anyone wants to experiment.
Best wishes
Mark
>From 53b1ced2d6a9fbbba93448325f795e6b99faa240 Mon Sep 17 00:00:00 2001
From: Mark Walters
Date: Fri, 31 Oct 2014 10:11:40 +
Subject
On Thu, 30 Oct 2014, Michal Sojka wrote:
> Hi all,
>
> this is v5 of the search --output=address series. It obsoletes v4
> (id:1414421455-3037-1-git-send-email-sojk...@fel.cvut.cz).
>
> I addresses comments from Mark and Tomi. Based on the comments to v4
> and earlier versions, patches 1-4 should
On Thu, 30 Oct 2014, Tomi Ollila wrote:
> On Thu, Oct 30 2014, Mark Walters wrote:
>
>> On Mon, 27 Oct 2014, Michal Sojka wrote:
>>> This adds an algorithm to filter out duplicate addresses from address
>>> outputs (sender, receivers). The algorithm can be c
On Mon, 27 Oct 2014, Michal Sojka 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 is an extended version of a patch from Jani Nikula.
Hi
As thi
On Mon, 27 Oct 2014, Michal Sojka wrote:
> 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
> nex
Hi
On Mon, 27 Oct 2014, Michal Sojka 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 this structure.
>
> This will become handy in the following patches
On Thu, 30 Oct 2014, Tomi Ollila wrote:
> On Thu, Oct 30 2014, Mark Walters wrote:
>
>> On Mon, 27 Oct 2014, Michal Sojka wrote:
>>> This adds an algorithm to filter out duplicate addresses from address
>>> outputs (sender, receivers). The algorithm can be c
On Mon, 27 Oct 2014, Michal Sojka 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 is an extended version of a patch from Jani Nikula.
Hi
As thi
On Mon, 27 Oct 2014, Michal Sojka wrote:
> 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
> nex
Hi
On Mon, 27 Oct 2014, Michal Sojka 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 this structure.
>
> This will become handy in the following patches
Hi
On Wed, 29 Oct 2014, Jesse Rosenthal wrote:
> [I'm not sure why the below reply did not go to the list. Later replies
> did, so I assume there must have been so problem in the sending. Mark,
> apologies if you get this twice.]
>
> Hi,
>
> Thanks for taking a look
Hi
On Tue, 07 Oct 2014, Jesse Rosenthal wrote:
> Currently the thread is named based on either the oldest or newest
> matching message (depending on the search order). If this message has
> an empty subject, though, the thread will show up with an empty
> subject in the search results. (See the
Hi
On Wed, 29 Oct 2014, Jesse Rosenthal wrote:
> [I'm not sure why the below reply did not go to the list. Later replies
> did, so I assume there must have been so problem in the sending. Mark,
> apologies if you get this twice.]
>
> Hi,
>
> Thanks for taking a look
Hi
On Tue, 07 Oct 2014, Jesse Rosenthal wrote:
> Currently the thread is named based on either the oldest or newest
> matching message (depending on the search order). If this message has
> an empty subject, though, the thread will show up with an empty
> subject in the search results. (See the
Hi
I definitely like the idea: some comments below.
On Fri, 24 Oct 2014, David Edmondson wrote:
> In addition to the :authors attribute of each search result, include
> :authors_matched and :authors_non_matched attributes. Both attributes
> are always included. If there are no non-matching auth
Hi
I definitely like the idea: some comments below.
On Fri, 24 Oct 2014, David Edmondson wrote:
> In addition to the :authors attribute of each search result, include
> :authors_matched and :authors_non_matched attributes. Both attributes
> are always included. If there are no non-matching auth
On Sun, 12 Oct 2014, Michal Sojka wrote:
> 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,
On Sun, 12 Oct 2014, Michal Sojka wrote:
> 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,
On Sun, 12 Oct 2014, Michal Sojka wrote:
> 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,
On Sun, 12 Oct 2014, Michal Sojka 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 this structure.
>
> This will become handy in the following patches.
Hi
On Sun, 12 Oct 2014, Michal Sojka wrote:
> 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,
On Sun, 12 Oct 2014, Michal Sojka 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 this structure.
>
> This will become handy in the following patches.
Hi
On Tue, 07 Oct 2014, Austin Clements wrote:
> This is v2 of the
> id:1412345958-8278-1-git-send-email-aclements at csail.mit.edu. This
> adds some comments and clarifies some code as suggested by David.
> Patch 6 is new in v2 and adds some bit-twiddling macros for clarity
> and robustness in lat
On Tue, 07 Oct 2014, Austin Clements wrote:
> From: Austin Clements
>
> Previously, it was necessary to link new messages to children to work
> around some (though not all) problems with the old metadata-based
> approach to stored thread IDs. With ghost messages, this is no longer
> necessary, s
merging updated only the thread IDs of message
> documents, not thread IDs stored in user metadata. As originally
> diagnosed by Mark Walters [1] and as demonstrated by the broken
> T260-thread-order test, this can cause notmuch to fail to link
> messages even though they're in
Hi
I am slowly working my way through this series: only two trivial queries
so far.
On Tue, 07 Oct 2014, Austin Clements wrote:
> From: Austin Clements
>
> This updates the message abstraction to support ghost messages: it
> adds a message flag that distinguishes regular messages from ghost
>
On Tue, 07 Oct 2014, Austin Clements wrote:
> This is v2 of the
> id:1412345958-8278-1-git-send-email-acleme...@csail.mit.edu. This
> adds some comments and clarifies some code as suggested by David.
> Patch 6 is new in v2 and adds some bit-twiddling macros for clarity
> and robustness in later
On Tue, 07 Oct 2014, Austin Clements wrote:
> From: Austin Clements
>
> Previously, it was necessary to link new messages to children to work
> around some (though not all) problems with the old metadata-based
> approach to stored thread IDs. With ghost messages, this is no longer
> necessary, s
merging updated only the thread IDs of message
> documents, not thread IDs stored in user metadata. As originally
> diagnosed by Mark Walters [1] and as demonstrated by the broken
> T260-thread-order test, this can cause notmuch to fail to link
> messages even though they're in
Hi
I am slowly working my way through this series: only two trivial queries
so far.
On Tue, 07 Oct 2014, Austin Clements wrote:
> From: Austin Clements
>
> This updates the message abstraction to support ghost messages: it
> adds a message flag that distinguishes regular messages from ghost
>
On Mon, 08 Sep 2014, David Edmondson wrote:
> On Mon, Aug 11 2014, 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/nevermo
On Mon, 08 Sep 2014, David Edmondson wrote:
> On Mon, Aug 11 2014, 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/nevermo
On Sat, 06 Sep 2014, Jani Nikula wrote:
> address-from prints reply-to or from, address-to prints to, cc, and
> bcc, and address-all prints all of them.
This looks good to me. Obviously needs the new commit
message.
I think we should think about the deduplication possibilities but that
can be
This adds a function that marks messages unread if they are "seen"
that is a user configurable amount of them has been visible in the
buffer.
---
emacs/notmuch-show.el | 74 -
1 file changed, 73 insertions(+), 1 deletion(-)
diff --git a/emacs/notm
---
emacs/notmuch-show.el |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 7549fbb..5695d95 100644
--- a/emacs/notmuch-show.el
+++ b/emacs/notmuch-show.el
@@ -224,7 +224,13 @@ For example, if you wanted to remove an \
user selects this option so it is low
risk). If people would prefer not to include it then I can just post
the relevant code to the wiki and people can add it to their .emacs
file if they want this function.
Best wishes
Mark
Mark Walters (2):
emacs: show: document the mark unread defcustom fun
On Sat, 06 Sep 2014, Jani Nikula wrote:
> address-from prints reply-to or from, address-to prints to, cc, and
> bcc, and address-all prints all of them.
Hi
I like these: thanks a lot for doing this.
Just one quick comment before I do an actual review:
> ---
> notmuch-search.c | 113
> ++
On Sat, 06 Sep 2014, Jani Nikula wrote:
> address-from prints reply-to or from, address-to prints to, cc, and
> bcc, and address-all prints all of them.
This looks good to me. Obviously needs the new commit
message.
I think we should think about the deduplication possibilities but that
can be
This adds a function that marks messages unread if they are "seen"
that is a user configurable amount of them has been visible in the
buffer.
---
emacs/notmuch-show.el | 74 -
1 file changed, 73 insertions(+), 1 deletion(-)
diff --git a/emacs/notm
---
emacs/notmuch-show.el |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 7549fbb..5695d95 100644
--- a/emacs/notmuch-show.el
+++ b/emacs/notmuch-show.el
@@ -224,7 +224,13 @@ For example, if you wanted to remove an \
user selects this option so it is low
risk). If people would prefer not to include it then I can just post
the relevant code to the wiki and people can add it to their .emacs
file if they want this function.
Best wishes
Mark
Mark Walters (2):
emacs: show: document the mark unread defcustom fun
On Sat, 06 Sep 2014, Jani Nikula wrote:
> address-from prints reply-to or from, address-to prints to, cc, and
> bcc, and address-all prints all of them.
Hi
I like these: thanks a lot for doing this.
Just one quick comment before I do an actual review:
> ---
> notmuch-search.c | 113
> ++
Hi
On Fri, 05 Sep 2014, David Edmondson wrote:
> Address completion entirely in elisp.
>
> I grew frustrated with having to use an external command to provide
> address completion, as they all had annoyances (up front scanning,
> requiring python bindings, etc.). This is an attempt to provide
>
Hi
On Fri, 05 Sep 2014, David Edmondson wrote:
> Address completion entirely in elisp.
>
> I grew frustrated with having to use an external command to provide
> address completion, as they all had annoyances (up front scanning,
> requiring python bindings, etc.). This is an attempt to provide
>
notmuch-jump uses window-body-width which is not defined in emacs
23. To get around this it does
(unless (fboundp 'window-body-width)
;; Compatibility for Emacs pre-24
(defalias 'window-body-width 'window-width))
This makes sure window-body-width is defined and all should be
well. But it seem
notmuch-jump uses window-body-width which is not defined in emacs
23. To get around this it does
(unless (fboundp 'window-body-width)
;; Compatibility for Emacs pre-24
(defalias 'window-body-width 'window-width))
This makes sure window-body-width is defined and all should be
well. But it seem
Hi
On Wed, 03 Sep 2014, David Belohrad wrote:
> oukej. this seems to be exactly what I'm looking for. Is there a way how
> to 'cycle' in notmuch different From: fields? I'd need to setup like 3
> addresses, each of them with different signatures and be able to easily
> switch between them
Y
Hi
On Wed, 03 Sep 2014, David Belohrad wrote:
> oukej. this seems to be exactly what I'm looking for. Is there a way how
> to 'cycle' in notmuch different From: fields? I'd need to setup like 3
> addresses, each of them with different signatures and be able to easily
> switch between them
Y
default-value needs its argument to be quoted.
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code
(default-value notmuch-search-oldest-first)
just gives the current value of notmuch-search-oldest-first rather
than intended default-value of this variable.
The sym
default-value needs its argument to be quoted.
---
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code didn't give an error but just did the wrong
thing.
Thanks to Jani for finding the bug.
Best wishes
Mark
emacs/notmuch-jump.el |2 +-
1 file changed, 1 ins
default-value needs its argument to be quoted.
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code
(default-value notmuch-search-oldest-first)
just gives the current value of notmuch-search-oldest-first rather
than intended default-value of this variable.
The sym
On Tue, 02 Sep 2014, Tomi Ollila wrote:
> On Tue, Sep 02 2014, Austin Clements wrote:
>
>> 48db8c8 introduced a disagreement between when
>> notmuch_database_needs_upgrade returned TRUE and when
>> notmuch_database_upgrade actually performed an upgrade. As a result,
>> if a database had a versi
default-value needs its argument to be quoted.
---
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code didn't give an error but just did the wrong
thing.
Thanks to Jani for finding the bug.
Best wishes
Mark
emacs/notmuch-jump.el |2 +-
1 file changed, 1 ins
On Tue, 02 Sep 2014, Tomi Ollila wrote:
> On Tue, Sep 02 2014, Austin Clements wrote:
>
>> 48db8c8 introduced a disagreement between when
>> notmuch_database_needs_upgrade returned TRUE and when
>> notmuch_database_upgrade actually performed an upgrade. As a result,
>> if a database had a versi
On Sun, 27 Jul 2014, Austin Clements wrote:
> Previously, our database schema was versioned by a single number.
> Each database schema change had to occur "atomically" in Notmuch's
> development history: before some commit, Notmuch used version N, after
> that commit, it used version N+1. Hence,
Hi
On Sun, 27 Jul 2014, Austin Clements wrote:
> Previously, the upgrade was organized as two passes -- an upgrade
> pass, and a separate cleanup pass -- so the database was always in a
> valid state. This change substantially simplifies this code by
> performing the upgrade in a transaction an
On Sun, 27 Jul 2014, Austin Clements wrote:
> The version number has always been pretty meaningless to the user and
> it's about to become even more meaningless with the introduction of
> "features". Hopefully, the database will remain on version 3 for some
> time to come; however, the introducti
On Sun, 27 Jul 2014, Austin Clements wrote:
> ---
> test/T530-upgrade.sh | 46 ++
> 1 file changed, 46 insertions(+)
Hi
Just a quick comment on this patch so far. After this patch I got lots
of test failures in the second (old) part of T530-upgrade b
On Sun, 27 Jul 2014, Austin Clements wrote:
> Previously, our database schema was versioned by a single number.
> Each database schema change had to occur "atomically" in Notmuch's
> development history: before some commit, Notmuch used version N, after
> that commit, it used version N+1. Hence,
Hi
On Sun, 27 Jul 2014, Austin Clements wrote:
> Previously, the upgrade was organized as two passes -- an upgrade
> pass, and a separate cleanup pass -- so the database was always in a
> valid state. This change substantially simplifies this code by
> performing the upgrade in a transaction an
On Sun, 27 Jul 2014, Austin Clements wrote:
> The version number has always been pretty meaningless to the user and
> it's about to become even more meaningless with the introduction of
> "features". Hopefully, the database will remain on version 3 for some
> time to come; however, the introducti
On Sun, 27 Jul 2014, Austin Clements wrote:
> ---
> test/T530-upgrade.sh | 46 ++
> 1 file changed, 46 insertions(+)
Hi
Just a quick comment on this patch so far. After this patch I got lots
of test failures in the second (old) part of T530-upgrade b
This makes the fact the notmuch-show-get-prop returns nil if the major
mode is neither show not tree explicit.
---
This is a followup to the patch and review comment at
id:874myhabi0.fsf at maritornes.cs.unb.ca
Best wishes
Mark
emacs/notmuch-show.el |3 ++-
1 file changed, 2 insertions(+),
This adds a function that marks messages unread if they are "seen"
that is a user configurable amount of them has been visible in the
buffer.
---
This adds my preferred mark unread function as an option: see
id:1399650320-1382-1-git-send-email-markwalters1009 at gmail.com for a
previous version. T
This makes the fact the notmuch-show-get-prop returns nil if the major
mode is neither show not tree explicit.
---
This is a followup to the patch and review comment at
id:874myhabi0@maritornes.cs.unb.ca
Best wishes
Mark
emacs/notmuch-show.el |3 ++-
1 file changed, 2 insertions(+), 1
This adds a function that marks messages unread if they are "seen"
that is a user configurable amount of them has been visible in the
buffer.
---
This adds my preferred mark unread function as an option: see
id:1399650320-1382-1-git-send-email-markwalters1...@gmail.com for a
previous version. This
On Tue, 15 Jul 2014, David Bremner wrote:
> Mark Walters writes:
>
>>
>> Discussion with Olly on irc indicates that this is currently the best
>> solution: in xapian trunk there may be better possibilities using
>> snapshots but they need to make it to a release
On Tue, 15 Jul 2014, David Bremner wrote:
> Mark Walters writes:
>
>>
>> Discussion with Olly on irc indicates that this is currently the best
>> solution: in xapian trunk there may be better possibilities using
>> snapshots but they need to make it to a release
On Tue, 15 Jul 2014, Austin Clements wrote:
> This is version 2 of
> id:1405353735-26244-1-git-send-email-amdragon at mit.edu and addresses
> Mark's comments in id:87egxnd4aq.fsf at qmul.ac.uk.
>
> The diff from v1 is below.
This version gets a +1 from me. I would have a slight preference for
ma
On Tue, 15 Jul 2014, Austin Clements wrote:
> This is version 2 of
> id:1405353735-26244-1-git-send-email-amdra...@mit.edu and addresses
> Mark's comments in id:87egxnd4aq@qmul.ac.uk.
>
> The diff from v1 is below.
This version gets a +1 from me. I would have a slight preference for
making t
On Tue, 15 Jul 2014, David Bremner wrote:
> Mark Walters writes:
>> + (cond ((eq major-mode 'notmuch-show-mode)
>> + (notmuch-show-get-message-properties))
>> + ((eq major-mode 'notmuch-tree-mode)
>> +
On Tue, 15 Jul 2014, Austin Clements wrote:
> Quoth Mark Walters on Jul 14 at 10:22 pm:
>>
>> On Mon, 14 Jul 2014, Austin Clements wrote:
>> > This introduces notmuch-jump, which is like a user-friendly,
>> > user-configurable global prefix map for saved se
On Tue, 15 Jul 2014, David Bremner wrote:
> Mark Walters writes:
>> + (cond ((eq major-mode 'notmuch-show-mode)
>> + (notmuch-show-get-message-properties))
>> + ((eq major-mode 'notmuch-tree-mode)
>> +
On Tue, 15 Jul 2014, Austin Clements wrote:
> Quoth Mark Walters on Jul 14 at 10:22 pm:
>>
>> On Mon, 14 Jul 2014, Austin Clements wrote:
>> > This introduces notmuch-jump, which is like a user-friendly,
>> > user-configurable global prefix map for saved se
nk it's better than my suggestion.
> This code is a combination of work from myself (originally,
> "notmuch-go"), David Edmondson, and modifications from Mark Walters.
> ---
> emacs/Makefile.local | 3 +-
> emacs/notmuch-hello.el | 2 +
> emacs/notmuch-jump.e
nk it's better than my suggestion.
> This code is a combination of work from myself (originally,
> "notmuch-go"), David Edmondson, and modifications from Mark Walters.
> ---
> emacs/Makefile.local | 3 +-
> emacs/notmuch-hello.el | 2 +
> emacs/notmuch-jump.e
401 - 500 of 3168 matches
Mail list logo
