> Quoth David Bremner on Jul 13 at 11:20 am:
>> Austin Clements writes:
>>
>> > The right answer might be something between notmuch-go and dme's
>> > patch. Currently notmuch-go uses a hard-coded set of searches, while
>> > dme's patch derives them from the saved searches.
>>
>> I'm not really
> Quoth David Bremner on Jul 13 at 11:20 am:
>> Austin Clements writes:
>>
>> > The right answer might be something between notmuch-go and dme's
>> > patch. Currently notmuch-go uses a hard-coded set of searches, while
>> > dme's patch derives them from the saved searches.
>>
>> I'm not really
On Thu, 26 Jun 2014, admin at softded.net wrote:
> Hello,
>
> Xapian have remote database mode:
> http://xapian.org/docs/remote.html
>
> Do you plan use it in future? I have more then 8 million letters and my
> xapian db use 50 gb store :)
I don't think we have any plans to do that. However, assu
On Thu, 26 Jun 2014, ad...@softded.net wrote:
> Hello,
>
> Xapian have remote database mode:
> http://xapian.org/docs/remote.html
>
> Do you plan use it in future? I have more then 8 million letters and my
> xapian db use 50 gb store :)
I don't think we have any plans to do that. However, assumin
This adds the current query as a "default value" to
notmuch-read-qeury. The default value is available via a down-arrow as
opposed to history which is available from the up arrow.
Note if a user presses return in the minibuffer this value is not
returned.
The implementation is simple but notmuch-
Dump currently only takes the read lock. Xapian can cope with some
changes while maintaining a read snapshot but with more changes it
fails. Currently notmuch just gives a xapian error.
To avoid this we take the write lock when dumping. This prevents other
notmuch processes from modifying the xapi
This adds the current query as a "default value" to
notmuch-read-qeury. The default value is available via a down-arrow as
opposed to history which is available from the up arrow.
Note if a user presses return in the minibuffer this value is not
returned.
The implementation is simple but notmuch-
Dump currently only takes the read lock. Xapian can cope with some
changes while maintaining a read snapshot but with more changes it
fails. Currently notmuch just gives a xapian error.
To avoid this we take the write lock when dumping. This prevents other
notmuch processes from modifying the xapi
Hi
On Thu, 12 Jun 2014, David Bremner wrote:
> Mark Walters writes:
>
>
>>> mjw1009 suggested to change NOTMUCH_DATABASE_MODE_READ_ONLY on line
>>> 215 of notmuch-dump.c to NOTMUCH_DATABASE_MODE_READ_WRITE
>>>
>>> I'm wondering if thi
Hi
On Thu, 12 Jun 2014, David Bremner wrote:
> Mark Walters writes:
>
>
>>> mjw1009 suggested to change NOTMUCH_DATABASE_MODE_READ_ONLY on line
>>> 215 of notmuch-dump.c to NOTMUCH_DATABASE_MODE_READ_WRITE
>>>
>>> I'm wondering if thi
Hello
On Tue, 10 Jun 2014, Eric Gillespie wrote:
> I'm a long-time nmh user, and I heard notmuch was supposed to
> handle mh folders, so I gave it a shot.
>
> It's crazy slow. The first 'notmuch new' took 4 hours, but maybe
> that's expected. However, every 'notmuch new' takes 4 - 10
> hours.
Hello
On Tue, 10 Jun 2014, Eric Gillespie wrote:
> I'm a long-time nmh user, and I heard notmuch was supposed to
> handle mh folders, so I gave it a shot.
>
> It's crazy slow. The first 'notmuch new' took 4 hours, but maybe
> that's expected. However, every 'notmuch new' takes 4 - 10
> hours.
tree overrides notmuch-show-get-prop so that it can use many of the
utility function directly. Now that tree is in mainline the version
from tree can be moved to show and the original overridden show
version dropped.
---
I should have done this ages ago but forgot about it.
Best wishes
Mark
em
tree overrides notmuch-show-get-prop so that it can use many of the
utility function directly. Now that tree is in mainline the version
from tree can be moved to show and the original overridden show
version dropped.
---
I should have done this ages ago but forgot about it.
Best wishes
Mark
em
On Mon, 12 May 2014, David Edmondson wrote:
> On Sat, May 10 2014, Aaron Ecay wrote:
>> 2014ko maiatzak 8an, Mark Walters-ek idatzi zuen:
>>>
>>> Hi
>>>
>>> This version looks good to me.
>>>
>>> The only slight query I have is wh
notmuch-search-archive-thread moves to the next line after tagging. In
the normal case this makes sense, but if the region is active, it tags
the whole region and then it doesn't really. Thus only move to the
next line if region is not active.
---
In response to the request in the parent message.
On Thu, 05 Jun 2014, Jani Nikula wrote:
> This is effectively a revert of
>
> commit 6812136bf576d894591606d9e10096719054d1f9
> Author: Jani Nikula
> Date: Mon Mar 31 00:21:48 2014 +0300
>
> lib: drop support for single-message mbox files
>
> The intention was to drop support for indexing
On Thu, 05 Jun 2014, Tom Hirschowitz wrote:
> Hi all,
>
> I'm trying to define a macro for notmuch/emacs which in show-mode would
>
> - prompt the user for tags (possibly starting with "+"),
>
> - tag the shown message with these tags plus an additional fixed tag,
>say "+local".
>
> I know
On Fri, 06 Jun 2014, Maarten Aertsen wrote:
> Hi everyone,
>
> (summary of IRC-conversation just now)
> I did:
> - run notmuch new (and afew -t) in cron, every two minutes
> - run notmuch dump in cron, every 12 hours
>
> I expected:
> - notmuch dump to complete, possibly causing notmuch new
On Mon, 12 May 2014, David Edmondson wrote:
> On Sat, May 10 2014, Aaron Ecay wrote:
>> 2014ko maiatzak 8an, Mark Walters-ek idatzi zuen:
>>>
>>> Hi
>>>
>>> This version looks good to me.
>>>
>>> The only slight query I have is wh
notmuch-search-archive-thread moves to the next line after tagging. In
the normal case this makes sense, but if the region is active, it tags
the whole region and then it doesn't really. Thus only move to the
next line if region is not active.
---
In response to the request in the parent message.
On Thu, 05 Jun 2014, Jani Nikula wrote:
> This is effectively a revert of
>
> commit 6812136bf576d894591606d9e10096719054d1f9
> Author: Jani Nikula
> Date: Mon Mar 31 00:21:48 2014 +0300
>
> lib: drop support for single-message mbox files
>
> The intention was to drop support for indexing
On Thu, 05 Jun 2014, Tom Hirschowitz wrote:
> Hi all,
>
> I'm trying to define a macro for notmuch/emacs which in show-mode would
>
> - prompt the user for tags (possibly starting with "+"),
>
> - tag the shown message with these tags plus an additional fixed tag,
>say "+local".
>
> I know
On Fri, 06 Jun 2014, Maarten Aertsen wrote:
> Hi everyone,
>
> (summary of IRC-conversation just now)
> I did:
> - run notmuch new (and afew -t) in cron, every two minutes
> - run notmuch dump in cron, every 12 hours
>
> I expected:
> - notmuch dump to complete, possibly causing notmuch new
Tomi Ollila writes:
> On Mon, Jun 02 2014, Mark Walters wrote:
>
>> Vladimir Marek writes:
>>
>>> Hi,
>>>
>>> I want to import bigger chunk of archived messages into my notmuch
>>> database. It's about 100k messages. The problem is,
Mark Walters writes:
> Vladimir Marek writes:
>
>>> > I want to import bigger chunk of archived messages into my notmuch
>>> > database. It's about 100k messages. The problem is, that I most probably
>>> > have quite a lot of those messages in t
Vladimir Marek writes:
>> > I want to import bigger chunk of archived messages into my notmuch
>> > database. It's about 100k messages. The problem is, that I most probably
>> > have quite a lot of those messages in the DB. Basically I would like to
>> > add only those I don't have already.
>> >
Vladimir Marek writes:
> Hi,
>
> I want to import bigger chunk of archived messages into my notmuch
> database. It's about 100k messages. The problem is, that I most probably
> have quite a lot of those messages in the DB. Basically I would like to
> add only those I don't have already.
>
> Ther
Tomi Ollila writes:
> On Mon, Jun 02 2014, David Edmondson wrote:
>
>> When the user begins forwarding a message, the resulting composition
>> buffer should not be marked as modified, in order that it can
>> immediately be killed without prompting.
>> ---
>
> LGTM.
>
> Tomi
and me. +1
Mark
>
Tomi Ollila writes:
> On Mon, Jun 02 2014, Mark Walters wrote:
>
>> Vladimir Marek writes:
>>
>>> Hi,
>>>
>>> I want to import bigger chunk of archived messages into my notmuch
>>> database. It's about 100k messages. The problem is,
Mark Walters writes:
> Vladimir Marek writes:
>
>>> > I want to import bigger chunk of archived messages into my notmuch
>>> > database. It's about 100k messages. The problem is, that I most probably
>>> > have quite a lot of those messages in t
Vladimir Marek writes:
>> > I want to import bigger chunk of archived messages into my notmuch
>> > database. It's about 100k messages. The problem is, that I most probably
>> > have quite a lot of those messages in the DB. Basically I would like to
>> > add only those I don't have already.
>> >
Vladimir Marek writes:
> Hi,
>
> I want to import bigger chunk of archived messages into my notmuch
> database. It's about 100k messages. The problem is, that I most probably
> have quite a lot of those messages in the DB. Basically I would like to
> add only those I don't have already.
>
> Ther
Tomi Ollila writes:
> On Mon, Jun 02 2014, David Edmondson wrote:
>
>> When the user begins forwarding a message, the resulting composition
>> buffer should not be marked as modified, in order that it can
>> immediately be killed without prompting.
>> ---
>
> LGTM.
>
> Tomi
and me. +1
Mark
>
Hi
I think notmuch-search-tag (and other tagging functions) were cleaned up
for 0.17: in particular their interactive behaviour
changed. notmuch-search-tag now only looks at the region if called
interactively. I think the following would do what you want
(define-key notmuch-search-mode-map "d"
Hi
I think notmuch-search-tag (and other tagging functions) were cleaned up
for 0.17: in particular their interactive behaviour
changed. notmuch-search-tag now only looks at the region if called
interactively. I think the following would do what you want
(define-key notmuch-search-mode-map "d"
On Wed, 07 May 2014, Olivier Berger
wrote:
> Hi.
>
> Mark Walters writes:
>
>> Hello
>>
>> As this section was rather outdated I have updated to modern notmuch. (In
>> fact the lisp snippets should work back to at least 0.13)
>>
>> On Tue
On Tue, 20 May 2014, David Edmondson wrote:
> Add a function and key-binding to toggle the collapsing of citations
> within the current message.
Hi
I like the idea. It seems a little odd to want to toggle the citations
closing some and opening others. I wonder whether the following action
would
On Wed, 07 May 2014, Olivier Berger wrote:
> Hi.
>
> Mark Walters writes:
>
>> Hello
>>
>> As this section was rather outdated I have updated to modern notmuch. (In
>> fact the lisp snippets should work back to at least 0.13)
>>
>> On Tue
On Tue, 20 May 2014, David Edmondson wrote:
> Add a function and key-binding to toggle the collapsing of citations
> within the current message.
Hi
I like the idea. It seems a little odd to want to toggle the citations
closing some and opening others. I wonder whether the following action
would
Currently notmuch-tag throws a "wrong-type-argument stringp nil" if
passed a nil query-string. Catch this and provide a more useful error
message. This fixes a case in notmuch-tree (if you try to tag when at
the end of the buffer).
Secondly, as pointed out by David (dme)
`notmuch-search-find-stabl
Currently notmuch-tag throws a "wrong-type-argument stringp nil" if
passed a nil query-string. Catch this and provide a more useful error
message. This fixes a case in notmuch-tree (if you try to tag when at
the end of the buffer).
Secondly, as pointed out by David (dme)
`notmuch-search-find-stabl
On Tue, 20 May 2014, David Edmondson wrote:
> On Mon, May 19 2014, Mark Walters wrote:
>> On Mon, 19 May 2014, David Edmondson wrote:
>>> `notmuch-search-find-stable-query-region' is expected to examine the
>>> region between `beg' and `end' to genera
On Tue, 20 May 2014, David Edmondson wrote:
> On Mon, May 19 2014, Mark Walters wrote:
>> On Mon, 19 May 2014, David Edmondson wrote:
>>> `notmuch-search-find-stable-query-region' is expected to examine the
>>> region between `beg' and `end' to genera
On Mon, 19 May 2014, David Edmondson wrote:
> `notmuch-search-find-stable-query-region' is expected to examine the
> region between `beg' and `end' to generate a query that can be used to
> include all threads in that region. If the region contains no threads,
> it should throw an error rather th
On Mon, 19 May 2014, David Edmondson wrote:
> `notmuch-search-find-stable-query-region' is expected to examine the
> region between `beg' and `end' to generate a query that can be used to
> include all threads in that region. If the region contains no threads,
> it should throw an error rather th
On Mon, 12 May 2014, David Edmondson wrote:
> Replying to a message with multiple parts will now typically include
> content from several parts (whereas previously only the first part was
> used). Update the expected output from the emacs reply tests
> accordingly.
I will reply here rather than t
On Tue, 13 May 2014, David Edmondson wrote:
> Firstly, I don't think that the code resulting from this patch series is
> beyond improvement - the intention was really only that it be better
> than the current implementation.
>
> On Mon, May 12 2014, Mark Walters wrote:
&g
On Mon, 12 May 2014, David Edmondson wrote:
> Replying to a message with multiple parts will now typically include
> content from several parts (whereas previously only the first part was
> used). Update the expected output from the emacs reply tests
> accordingly.
I will reply here rather than t
On Tue, 13 May 2014, David Edmondson wrote:
> Firstly, I don't think that the code resulting from this patch series is
> beyond improvement - the intention was really only that it be better
> than the current implementation.
>
> On Mon, May 12 2014, Mark Walters wrote:
&g
On Mon, 12 May 2014, David Edmondson wrote:
> Use the message display code to generate message text to cite in
> replies.
So this is the key change. I am trying to work out what the actual
changes are here: in your commit message for the test update 7/9 you say
that the old code only output the
On Mon, 12 May 2014, David Edmondson wrote:
> No code uses the 'no-buttons argument to
> `notmuch-show-insert-bodypart', so remove it.
> ---
> emacs/notmuch-show.el | 9 +++--
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
> in
On Mon, 12 May 2014, David Edmondson wrote:
> Various pieces of code assumed (reasonably) that part header buttons
> are present. Modify them to avoid problems if no part headers were
> inserted.
Despite your reservations on irc this looks fine to me.
MW
> ---
> emacs/notmuch-show.el | 88
>
On Mon, 12 May 2014, David Edmondson wrote:
> Make the function that determines whether a part header should be
> inserted a user controlled, with some example functions.
> ---
> emacs/notmuch-show.el | 21 +++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/
On Mon, 12 May 2014, David Edmondson wrote:
> Move the determination of whether a part header is required to a
> distinct function.
> ---
> emacs/notmuch-show.el | 25 ++---
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/emacs/notmuch-show.el b/emacs/notm
On Mon, 12 May 2014, David Edmondson wrote:
> emacs: Improve the cited message included in replies
>
> I tried to do things in small increments to make it easier to review.
>
> v2:
> - Don't run the text/plain hooks when generating the message to quote.
>
> v3:
> - Remove the 'no-button code, as
On Mon, 12 May 2014, David Edmondson wrote:
> On Sun, May 11 2014, Mark Walters wrote:
>> This adds a function that highlights searches which have newly arrived
>> messages (ones which arrived since the previous refresh of
>> notmuch-hello). It does that by getting a
On Mon, 12 May 2014, David Edmondson wrote:
> On Sun, May 11 2014, Mark Walters wrote:
>> Extend the saved search plist to include a :display-function property
>> that can customise the display of the saved search. It can change the
>> count string displayed and the name stri
On Mon, 12 May 2014, David Edmondson wrote:
> Use the message display code to generate message text to cite in
> replies.
So this is the key change. I am trying to work out what the actual
changes are here: in your commit message for the test update 7/9 you say
that the old code only output the
On Mon, 12 May 2014, David Edmondson wrote:
> No code uses the 'no-buttons argument to
> `notmuch-show-insert-bodypart', so remove it.
> ---
> emacs/notmuch-show.el | 9 +++--
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
> in
On Mon, 12 May 2014, David Edmondson wrote:
> Various pieces of code assumed (reasonably) that part header buttons
> are present. Modify them to avoid problems if no part headers were
> inserted.
Despite your reservations on irc this looks fine to me.
MW
> ---
> emacs/notmuch-show.el | 88
>
On Mon, 12 May 2014, David Edmondson wrote:
> Make the function that determines whether a part header should be
> inserted a user controlled, with some example functions.
> ---
> emacs/notmuch-show.el | 21 +++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/
On Mon, 12 May 2014, David Edmondson wrote:
> Move the determination of whether a part header is required to a
> distinct function.
> ---
> emacs/notmuch-show.el | 25 ++---
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/emacs/notmuch-show.el b/emacs/notm
On Mon, 12 May 2014, David Edmondson wrote:
> emacs: Improve the cited message included in replies
>
> I tried to do things in small increments to make it easier to review.
>
> v2:
> - Don't run the text/plain hooks when generating the message to quote.
>
> v3:
> - Remove the 'no-button code, as
On Mon, 12 May 2014, David Edmondson wrote:
> On Sat, May 10 2014, Mark Walters wrote:
>> On Thu, 08 May 2014, David Edmondson wrote:
>>> emacs: Improve the cited message included in replies
>>>
>>> v2:
>>> - Don't run the text/plain hooks
On Mon, 12 May 2014, David Edmondson wrote:
> On Sun, May 11 2014, Mark Walters wrote:
>> This adds a function that highlights searches which have newly arrived
>> messages (ones which arrived since the previous refresh of
>> notmuch-hello). It does that by getting a
On Mon, 12 May 2014, David Edmondson wrote:
> On Sun, May 11 2014, Mark Walters wrote:
>> Extend the saved search plist to include a :display-function property
>> that can customise the display of the saved search. It can change the
>> count string displayed and the name stri
On Mon, 12 May 2014, David Edmondson wrote:
> On Sat, May 10 2014, Mark Walters wrote:
>> On Thu, 08 May 2014, David Edmondson wrote:
>>> emacs: Improve the cited message included in replies
>>>
>>> v2:
>>> - Don't run the text/plain hooks
This omits the count for the specific search. This makes notmuch-hello
faster, particularly for large complex saved searches.
---
emacs/notmuch-hello.el |7 +++
1 file changed, 7 insertions(+)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index 265b879..b3b539d 100644
--- a
This adds a function that highlights searches which have newly arrived
messages (ones which arrived since the previous refresh of
notmuch-hello). It does that by getting a full list of matching
message ids and checking whether any new messages have appeared. Thus
it will be slow on large saved sear
We will use cl at runtime in the next patch so require cl (rather than
just having it eval-when-compile). We require it in notmuch-lib anyway
so this is no loss in requiring it here too.
---
emacs/notmuch-hello.el |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/emacs/no
This is an example of a possible display function. It displays the
count for a search as messages/threads. This will be slow on a large
search but could be useful for a small search.
It also extends and renames the existing (unused)
notmuch-saved-search-count function to count threads if wanted. T
This adds a variable which keeps track of the previous saved search
results. It is stored as a plist with keys being the saved
searches. The result the saved search display function gave last time
is passed to the display-function as the the keyword :old argument.
This is useful for display functi
Extend the saved search plist to include a :display-function property
that can customise the display of the saved search. It can change the
count string displayed and the name string. Thus the user can
customise so that a particular search:
does not show a count (and is thus hello is faster), show
Separate the code that prints a saved-search and count into its own
function.
---
emacs/notmuch-hello.el | 30 +++---
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index 3de5238..0a7004c 100644
--- a/emacs/
ed by the saved searches themselves. I think this is OK (because
plist uses eq not equal) but would like a confirmation.
Finally, some of this infrastructure could be used to do async counts
at a later stage. I have some preliminary patches, but that is all
rather more fragile.
Best wishes
Mark
Mar
This adds a function that highlights searches which have newly arrived
messages (ones which arrived since the previous refresh of
notmuch-hello). It does that by getting a full list of matching
message ids and checking whether any new messages have appeared. Thus
it will be slow on large saved sear
This omits the count for the specific search. This makes notmuch-hello
faster, particularly for large complex saved searches.
---
emacs/notmuch-hello.el |7 +++
1 file changed, 7 insertions(+)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index 265b879..b3b539d 100644
--- a
We will use cl at runtime in the next patch so require cl (rather than
just having it eval-when-compile). We require it in notmuch-lib anyway
so this is no loss in requiring it here too.
---
emacs/notmuch-hello.el |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/emacs/no
This is an example of a possible display function. It displays the
count for a search as messages/threads. This will be slow on a large
search but could be useful for a small search.
It also extends and renames the existing (unused)
notmuch-saved-search-count function to count threads if wanted. T
This adds a variable which keeps track of the previous saved search
results. It is stored as a plist with keys being the saved
searches. The result the saved search display function gave last time
is passed to the display-function as the the keyword :old argument.
This is useful for display functi
ed by the saved searches themselves. I think this is OK (because
plist uses eq not equal) but would like a confirmation.
Finally, some of this infrastructure could be used to do async counts
at a later stage. I have some preliminary patches, but that is all
rather more fragile.
Best wishes
Mark
Mar
Extend the saved search plist to include a :display-function property
that can customise the display of the saved search. It can change the
count string displayed and the name string. Thus the user can
customise so that a particular search:
does not show a count (and is thus hello is faster), show
Separate the code that prints a saved-search and count into its own
function.
---
emacs/notmuch-hello.el | 30 +++---
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index 3de5238..0a7004c 100644
--- a/emacs/
On Thu, 08 May 2014, David Edmondson wrote:
> emacs: Improve the cited message included in replies
>
> v2:
> - Don't run the text/plain hooks when generating the message to quote.
>
In principle I like this approach: keeping show and reply closely linked
seems good.
At the moment, as you say, th
On Thu, 08 May 2014, David Edmondson wrote:
> emacs: Improve the cited message included in replies
>
> v2:
> - Don't run the text/plain hooks when generating the message to quote.
>
In principle I like this approach: keeping show and reply closely linked
seems good.
At the moment, as you say, th
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.
To use set notmuch-show-mark-read-function to #'notmuch-show-do-seen
---
This adds the functionality to do my previous mark unread logic (see
id:139593
Hi
I think the functionality is well worth having ("|" cat - > a-file is
ugly!). However, I am not sure about this approach.
The first two patches are fine, although I think I like constructing a
query then quoting rather than quoting bits of a query and bolting them
together (even the both work
On Fri, 09 May 2014, David Edmondson wrote:
> On Fri, May 09 2014, Mark Walters wrote:
>> This is v4 of this set. v3 is at
>> id:139593-13297-1-git-send-email-markwalters1009 at gmail.com
>>
>> David (dme) was not keen on the logic in the previous patch so I have
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.
To use set notmuch-show-mark-read-function to #'notmuch-show-do-seen
---
This adds the functionality to do my previous mark unread logic (see
id:139593
Hi
I think the functionality is well worth having ("|" cat - > a-file is
ugly!). However, I am not sure about this approach.
The first two patches are fine, although I think I like constructing a
query then quoting rather than quoting bits of a query and bolting them
together (even the both work
On Fri, 09 May 2014, David Edmondson wrote:
> On Fri, May 09 2014, Mark Walters wrote:
>> This is v4 of this set. v3 is at
>> id:139593-13297-1-git-send-email-markwalters1...@gmail.com
>>
>> David (dme) was not keen on the logic in the previous patch so I have
>
Add a function for updating seen messages to the
post-command-hook. This function calls a customizable (by eg
defcustom) function with parameters the start and end of the current
window and that function can decide what to mark read based on that
and the current point.
Since this is in the post-co
From: David Bremner
The unread/read changes will use the post-command-hook. test_emacs
does not call the post-command-hook. This adds a notmuch-test-progn
which takes a list of commands as argument and executes them in turn
but runs the post-command-hook after each one.
The caller can batch oper
read/unread logic mentioned in
id:87a9atmpkf.fsf at qmul.ac.uk are fixed.
The first patch is unchanged. Since the new mark-read function is
small it folded neatly into the patch removing the old unread logic.
Finally, as with previous versions, all tests pass.
Best wishes
Mark
Mark Walte
Add a function for updating seen messages to the
post-command-hook. This function calls a customizable (by eg
defcustom) function with parameters the start and end of the current
window and that function can decide what to mark read based on that
and the current point.
Since this is in the post-co
From: David Bremner
The unread/read changes will use the post-command-hook. test_emacs
does not call the post-command-hook. This adds a notmuch-test-progn
which takes a list of commands as argument and executes them in turn
but runs the post-command-hook after each one.
The caller can batch oper
nread logic mentioned in
id:87a9atmpkf@qmul.ac.uk are fixed.
The first patch is unchanged. Since the new mark-read function is
small it folded neatly into the patch removing the old unread logic.
Finally, as with previous versions, all tests pass.
Best wishes
Mark
Mark Walters (2):
Hi
This version looks good to me.
The only slight query I have is which key to bind it to: Austin used g
in notmuch-go and this uses j. Austin said on irc that he chose g
because it wasn't bound and matched gmail's shortcut.
Personally I like j (as it starts fewer words than g) and given that w
On Thu, 08 May 2014, David Edmondson wrote:
> On Wed, May 07 2014, Mark Walters wrote:
>> A message is marked read if:
>>
>> 1) if you navigate to a message using n/p (next/prev open message)
>>
>> 2) if you navigate to it using N/P (next/prev message) regard
501 - 600 of 3168 matches
Mail list logo
