Currently we support both string and list forms of tag-changes for
historical reasons. This is about to change, so fix pick's tests that
use the legacy string form of tag-changes.
---
contrib/notmuch-pick/test/emacs-pick | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
This is similar to the previous commit, but applies to search.
Search is somewhat more complicated because its tagging operations can
also apply to a region. Hence, this lifts interactive prompting into
a helper function. This also takes advantage of the new ability to
provide a prompt to
This modifies all tagging operations in show to call
`notmuch-read-tag-changes' in their interactive specification to input
tag changes, rather than depending on lower-level functions to prompt
for tag changes regardless of their calling context.
Besides being more Elispy and providing a more
This modifies the interface of `notmuch-read-tag-changes' to take an
optional prompt string as well as a list of existing tags instead of a
query. This list of tags is used to populate the tag removal
completions and lets the caller compute these in a more
efficient/consistent manner than
The calling convention for `notmuch-tag' changed in commit 97aa3c06 to
take a list of tag changes instead of a argument, but the call
from `notmuch-search-tag-all' still passed a argument. This
happened to work for interactive calls because tag-changes would be
nil, so the `apply' call would
This is v2 of id:1382471457-26056-1-git-send-email-amdragon at mit.edu.
It improves some documentation strings, fixes one bug, and elimintes
some redundant code. The diff from v1 is below.
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index ef77839..f66d669 100644
---
uch-read-tag-changes'. Since it's redundant, I've removed it.
> But that was all I found. All tests pass and everything I try behaves
> exactly as expected.
>
> Best wishes
>
> Mark
>
>
> On Tue, 22 Oct 2013, Austin Clements wrote:
> > This series improves tag change co
We no longer use this, since we've lifted all interactive behavior to
the appropriate interactive entry points. Because of this,
`notmuch-tag' also no longer needs to return the tag changes list,
since the caller always passes it in.
---
emacs/notmuch-tag.el | 19 ---
1 file
---
contrib/notmuch-pick/notmuch-pick.el | 36 +---
1 file changed, 21 insertions(+), 15 deletions(-)
diff --git a/contrib/notmuch-pick/notmuch-pick.el
b/contrib/notmuch-pick/notmuch-pick.el
index 8f504ed..13682ea 100644
--- a/contrib/notmuch-pick/notmuch-pick.el
Currently we support both string and list forms of tag-changes for
historical reasons. This is about to change, so fix pick's tests that
use the legacy string form of tag-changes.
---
contrib/notmuch-pick/test/emacs-pick | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
`notmuch-pick-tag' takes a list of tag changes, but
`notmuch-pick-archive-message' passes it a argument. This
happens to work if `notmuch-archive-tags' contains a single tag (which
it usually does), but will break if it does not.
---
contrib/notmuch-pick/notmuch-pick.el | 3 +--
1 file changed,
This is similar to the previous commit, but applies to search.
Search is somewhat more complicated because its tagging operations can
also apply to a region. Hence, this lifts interactive prompting into
a helper function. This also takes advantage of the new ability to
provide a prompt to
This modifies all tagging operations in show to call
`notmuch-read-tag-changes' in their interactive specification to input
tag changes, rather than depending on lower-level functions to prompt
for tag changes regardless of their calling context.
Besides being more Elispy and providing a more
This modifies the interface of `notmuch-read-tag-changes' to take an
optional prompt string as well as a list of existing tags instead of a
query. This list of tags is used to populate the tag removal
completions and lets the caller compute these in a more
efficient/consistent manner than
The calling convention for `notmuch-tag' changed in commit 97aa3c06 to
take a list of tag changes instead of a argument, but the call
from `notmuch-search-tag-all' still passed a argument. This
happened to work for interactive calls because tag-changes would be
nil, so the `apply' call would
This series improves tag change completion in various ways for
commands like +, -, and *.
>From a user perspective, this provides command-specific prompts like
"Tag message" and "Tag all" instead of the generic "Tag" prompt, and
bases tag removal completions on the tags that are in the buffer,
This modifies the interface of `notmuch-read-tag-changes' to take an
optional prompt string as well as a list of existing tags instead of a
query. This list of tags is used to populate the tag removal
completions and lets the caller compute these in a more
efficient/consistent manner than
Currently we support both string and list forms of tag-changes for
historical reasons. This is about to change, so fix pick's tests that
use the legacy string form of tag-changes.
---
contrib/notmuch-pick/test/emacs-pick | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
This modifies all tagging operations in show to call
`notmuch-read-tag-changes' in their interactive specification to input
tag changes, rather than depending on lower-level functions to prompt
for tag changes regardless of their calling context.
Besides being more Elispy and providing a more
The calling convention for `notmuch-tag' changed in commit 97aa3c06 to
take a list of tag changes instead of a rest argument, but the call
from `notmuch-search-tag-all' still passed a rest argument. This
happened to work for interactive calls because tag-changes would be
nil, so the `apply' call
This series improves tag change completion in various ways for
commands like +, -, and *.
From a user perspective, this provides command-specific prompts like
Tag message and Tag all instead of the generic Tag prompt, and
bases tag removal completions on the tags that are in the buffer,
rather
`notmuch-pick-tag' takes a list of tag changes, but
`notmuch-pick-archive-message' passes it a rest argument. This
happens to work if `notmuch-archive-tags' contains a single tag (which
it usually does), but will break if it does not.
---
contrib/notmuch-pick/notmuch-pick.el | 3 +--
1 file
This is similar to the previous commit, but applies to search.
Search is somewhat more complicated because its tagging operations can
also apply to a region. Hence, this lifts interactive prompting into
a helper function. This also takes advantage of the new ability to
provide a prompt to
We no longer use this, since we've lifted all interactive behavior to
the appropriate interactive entry points. Because of this,
`notmuch-tag' also no longer needs to return the tag changes list,
since the caller always passes it in.
---
emacs/notmuch-tag.el | 19 ---
1 file
tests pass and everything I try behaves
exactly as expected.
Best wishes
Mark
On Tue, 22 Oct 2013, Austin Clements amdra...@mit.edu wrote:
This series improves tag change completion in various ways for
commands like +, -, and *.
From a user perspective, this provides command
We no longer use this, since we've lifted all interactive behavior to
the appropriate interactive entry points. Because of this,
`notmuch-tag' also no longer needs to return the tag changes list,
since the caller always passes it in.
---
emacs/notmuch-tag.el | 19 ---
1 file
Currently we support both string and list forms of tag-changes for
historical reasons. This is about to change, so fix pick's tests that
use the legacy string form of tag-changes.
---
contrib/notmuch-pick/test/emacs-pick | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
This is v2 of id:1382471457-26056-1-git-send-email-amdra...@mit.edu.
It improves some documentation strings, fixes one bug, and elimintes
some redundant code. The diff from v1 is below.
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index ef77839..f66d669 100644
---
This is similar to the previous commit, but applies to search.
Search is somewhat more complicated because its tagging operations can
also apply to a region. Hence, this lifts interactive prompting into
a helper function. This also takes advantage of the new ability to
provide a prompt to
`notmuch-pick-tag' takes a list of tag changes, but
`notmuch-pick-archive-message' passes it a rest argument. This
happens to work if `notmuch-archive-tags' contains a single tag (which
it usually does), but will break if it does not.
---
contrib/notmuch-pick/notmuch-pick.el | 3 +--
1 file
---
contrib/notmuch-pick/notmuch-pick.el | 36 +---
1 file changed, 21 insertions(+), 15 deletions(-)
diff --git a/contrib/notmuch-pick/notmuch-pick.el
b/contrib/notmuch-pick/notmuch-pick.el
index 8f504ed..13682ea 100644
--- a/contrib/notmuch-pick/notmuch-pick.el
This modifies all tagging operations in show to call
`notmuch-read-tag-changes' in their interactive specification to input
tag changes, rather than depending on lower-level functions to prompt
for tag changes regardless of their calling context.
Besides being more Elispy and providing a more
The calling convention for `notmuch-tag' changed in commit 97aa3c06 to
take a list of tag changes instead of a rest argument, but the call
from `notmuch-search-tag-all' still passed a rest argument. This
happened to work for interactive calls because tag-changes would be
nil, so the `apply' call
This modifies the interface of `notmuch-read-tag-changes' to take an
optional prompt string as well as a list of existing tags instead of a
query. This list of tags is used to populate the tag removal
completions and lets the caller compute these in a more
efficient/consistent manner than
Previously, we cleaned the downloaded performance corpus and the
cached indexes on 'make clean'. This seems heavy-handed, since these
take a long time to download, unpack, and index. They also aren't
make targets to begin with. Move cleaning these to 'make distclean'.
This isn't exactly the
Previously, we cleaned the downloaded performance corpus and the
cached indexes on 'make clean'. This seems heavy-handed, since these
take a long time to download, unpack, and index. They also aren't
make targets to begin with. Move cleaning these to 'make distclean'.
This isn't exactly the
LGTM.
Quoth Mark Walters on Oct 13 at 8:39 am:
> Currently notmuch-show looks at the prefix-arg directly via
> current-prefix-arg. This changes it to use the interactive
> specification.
>
> One test (for elide-toggle functionality) set the prefix arg
> directly. Update this test to set the new
Code looks good. Two minor comments below.
Quoth Mark Walters on Oct 09 at 9:01 pm:
> Currently notmuch-show looks at the prefix-arg directly via
> current-prefix-arg. This changes it to use the interactive
> specification.
> ---
> emacs/notmuch-show.el | 12 +++-
> emacs/notmuch.el
LGTM.
Quoth Mark Walters on Oct 13 at 8:39 am:
Currently notmuch-show looks at the prefix-arg directly via
current-prefix-arg. This changes it to use the interactive
specification.
One test (for elide-toggle functionality) set the prefix arg
directly. Update this test to set the new
Code looks good. Two minor comments below.
Quoth Mark Walters on Oct 09 at 9:01 pm:
Currently notmuch-show looks at the prefix-arg directly via
current-prefix-arg. This changes it to use the interactive
specification.
---
emacs/notmuch-show.el | 12 +++-
emacs/notmuch.el |
Authors and subjects can contain embedded, encoded control characters
like "\n" and "\t" that mess up display. Transform control characters
into spaces everywhere we display them in search and show.
---
This could obviously use some tests, but I thought I'd get it out
there to see what people
Authors and subjects can contain embedded, encoded control characters
like \n and \t that mess up display. Transform control characters
into spaces everywhere we display them in search and show.
---
This could obviously use some tests, but I thought I'd get it out
there to see what people
ttle discussion of this in my earlier attempt at
> fixing this: eg id:87mwy4smad.fsf at qmul.ac.uk
>
> Best wishes
>
> Mark
>
> On Mon, 07 Oct 2013, Austin Clements wrote:
> > I was hacking on undo support for notmuch-emacs and sort of
> > accidentally wrote this instead.
Quoth Mark Walters on Oct 09 at 8:43 am:
>
> On Mon, 07 Oct 2013, Austin Clements wrote:
> > I was hacking on undo support for notmuch-emacs and sort of
> > accidentally wrote this instead. This series fixes a set of
> > well-known races where tagging from search-m
Quoth Jani Nikula on Oct 09 at 9:41 am:
> On Tue, 08 Oct 2013, Austin Clements wrote:
> > These queries will match exactly the set of messages currently in the
> > thread, even if more messages later arrive. Two queries are provided:
> > one for matched messages and one f
Quoth Mark Walters on Oct 09 at 8:38 am:
>
> On Wed, 09 Oct 2013, Jani Nikula wrote:
> > On Tue, 08 Oct 2013, Austin Clements wrote:
> >> (Unfortunately, it's difficult to first demonstrate this problem with
> >> a known-broken test because modern Linux kernels ha
Quoth Mark Walters on Oct 08 at 8:27 am:
> On Mon, 07 Oct 2013, Austin Clements wrote:
> > (Unfortunately, it's difficult to first demonstrate this problem with
> > a known-broken test because modern Linux kernels have argument length
> > limits in the megabytes, which ma
Quoth Mark Walters on Oct 08 at 7:48 am:
> On Mon, 07 Oct 2013, Austin Clements wrote:
> > Previously, the CLI would print a deprecation warning if a client
> > requested any format version other than the current one. However, if
> > we add fields that are backwards-compati
Quoth Mark Walters on Oct 08 at 7:48 am:
On Mon, 07 Oct 2013, Austin Clements amdra...@mit.edu wrote:
Previously, the CLI would print a deprecation warning if a client
requested any format version other than the current one. However, if
we add fields that are backwards-compatible
Quoth Mark Walters on Oct 08 at 8:27 am:
On Mon, 07 Oct 2013, Austin Clements amdra...@mit.edu wrote:
(Unfortunately, it's difficult to first demonstrate this problem with
a known-broken test because modern Linux kernels have argument length
limits in the megabytes, which makes Emacs
Quoth Mark Walters on Oct 09 at 8:38 am:
On Wed, 09 Oct 2013, Jani Nikula j...@nikula.org wrote:
On Tue, 08 Oct 2013, Austin Clements amdra...@mit.edu wrote:
(Unfortunately, it's difficult to first demonstrate this problem with
a known-broken test because modern Linux kernels have
Quoth Jani Nikula on Oct 09 at 9:41 am:
On Tue, 08 Oct 2013, Austin Clements amdra...@mit.edu wrote:
These queries will match exactly the set of messages currently in the
thread, even if more messages later arrive. Two queries are provided:
one for matched messages and one for unmatched
Quoth Mark Walters on Oct 09 at 8:43 am:
On Mon, 07 Oct 2013, Austin Clements amdra...@mit.edu wrote:
I was hacking on undo support for notmuch-emacs and sort of
accidentally wrote this instead. This series fixes a set of
well-known races where tagging from search-mode unexpectedly
id:87mwy4smad@qmul.ac.uk
Best wishes
Mark
On Mon, 07 Oct 2013, Austin Clements amdra...@mit.edu wrote:
I was hacking on undo support for notmuch-emacs and sort of
accidentally wrote this instead. This series fixes a set of
well-known races where tagging from search-mode
Quoth Mark Walters on Oct 06 at 9:14 pm:
>
> This whole series looks good to me. If you are rolling another version
> for any reason I have one trivial comment
>
> On Sun, 06 Oct 2013, Austin Clements wrote:
> > Traditionally, function documentation strings a
---
emacs/notmuch.el | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index e559472..c47c6b5 100644
--- a/emacs/notmuch.el
+++ b/emacs/notmuch.el
@@ -141,10 +141,15 @@ This is basically just `format-kbd-macro' but we also
convert
This fixes races in thread-local and global tagging in notmuch-search
(e.g., "+", "-", "a", "*", etc.). Previously, these would modify tags
of new messages that arrived after the search. Now they only operate
on the messages that were in the threads when the search was
performed. This prevents
These tests check that both thread-local and global search tagging
operations are race-free. They are currently known-broken because
they aren't race-free.
---
test/emacs | 26 ++
1 file changed, 26 insertions(+)
diff --git a/test/emacs b/test/emacs
index
---
devel/TODO | 6 ++
1 file changed, 6 insertions(+)
diff --git a/devel/TODO b/devel/TODO
index 844555e..f212483 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -114,6 +114,12 @@ are multiple ideas that might make sense. Some consensus
needs to be
reached on this issue, and then both reply
These queries will match exactly the set of messages currently in the
thread, even if more messages later arrive. Two queries are provided:
one for matched messages and one for unmatched messages.
This can be used to fix race conditions with tagging threads from
search results. While tagging
(Unfortunately, it's difficult to first demonstrate this problem with
a known-broken test because modern Linux kernels have argument length
limits in the megabytes, which makes Emacs really slow!)
---
emacs/notmuch-lib.el | 8
emacs/notmuch-tag.el | 12 ++--
test/emacs
This adds support for passing a string to write to notmuch's stdin to
`notmuch-call-notmuch-process' and `notmuch-call-notmuch-sexp'. Since
this makes both interfaces a little more complicated, it also unifies
their documentation better.
---
emacs/notmuch-lib.el | 39
Previously, this was in notmuch.el, but all of the other notmuch call
wrappers were in notmuch-lib.el. Move `notmuch-call-notmuch-process'
to live with its friends. This happens to fix a missing dependency
from notmuch-tag.el, which required notmuch-lib, but not notmuch.
---
The first subprocess error exit code test assumed the *Notmuch errors*
buffer would be empty. Rather than assuming, make it so.
---
test/emacs | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/test/emacs b/test/emacs
index 5bc3efc..05295af 100755
--- a/test/emacs
+++
This documents the extent of the notmuch_messages_t* pointers returned
by notmuch_thread_get_toplevel_messages and
notmuch_thread_get_messages.
---
lib/notmuch.h | 4
1 file changed, 4 insertions(+)
diff --git a/lib/notmuch.h b/lib/notmuch.h
index 998a4ae..217bf46 100644
--- a/lib/notmuch.h
Previously, the CLI would print a deprecation warning if a client
requested any format version other than the current one. However, if
we add fields that are backwards-compatible, but want clients to be
able to depend on, we need to bump the version, but that doesn't make
the older version
Previously, the show schema and the search schema used different
"thread" non-terminals. While these schemata don't interact, this is
still confusing, so rename search's "thread" to "thread_summary". To
further limit confusion, prefix all top-level search non-terminals now
begin with "search_".
I was hacking on undo support for notmuch-emacs and sort of
accidentally wrote this instead. This series fixes a set of
well-known races where tagging from search-mode unexpectedly affects
messages that arrived after the search was performed (and hence the
user doesn't know they're tagging them).
I was hacking on undo support for notmuch-emacs and sort of
accidentally wrote this instead. This series fixes a set of
well-known races where tagging from search-mode unexpectedly affects
messages that arrived after the search was performed (and hence the
user doesn't know they're tagging them).
Previously, this was in notmuch.el, but all of the other notmuch call
wrappers were in notmuch-lib.el. Move `notmuch-call-notmuch-process'
to live with its friends. This happens to fix a missing dependency
from notmuch-tag.el, which required notmuch-lib, but not notmuch.
---
(Unfortunately, it's difficult to first demonstrate this problem with
a known-broken test because modern Linux kernels have argument length
limits in the megabytes, which makes Emacs really slow!)
---
emacs/notmuch-lib.el | 8
emacs/notmuch-tag.el | 12 ++--
test/emacs
---
devel/TODO | 6 ++
1 file changed, 6 insertions(+)
diff --git a/devel/TODO b/devel/TODO
index 844555e..f212483 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -114,6 +114,12 @@ are multiple ideas that might make sense. Some consensus
needs to be
reached on this issue, and then both reply
This adds support for passing a string to write to notmuch's stdin to
`notmuch-call-notmuch-process' and `notmuch-call-notmuch-sexp'. Since
this makes both interfaces a little more complicated, it also unifies
their documentation better.
---
emacs/notmuch-lib.el | 39
Previously, the show schema and the search schema used different
thread non-terminals. While these schemata don't interact, this is
still confusing, so rename search's thread to thread_summary. To
further limit confusion, prefix all top-level search non-terminals now
begin with search_.
---
The first subprocess error exit code test assumed the *Notmuch errors*
buffer would be empty. Rather than assuming, make it so.
---
test/emacs | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/test/emacs b/test/emacs
index 5bc3efc..05295af 100755
--- a/test/emacs
+++
These queries will match exactly the set of messages currently in the
thread, even if more messages later arrive. Two queries are provided:
one for matched messages and one for unmatched messages.
This can be used to fix race conditions with tagging threads from
search results. While tagging
Previously, the CLI would print a deprecation warning if a client
requested any format version other than the current one. However, if
we add fields that are backwards-compatible, but want clients to be
able to depend on, we need to bump the version, but that doesn't make
the older version
This documents the extent of the notmuch_messages_t* pointers returned
by notmuch_thread_get_toplevel_messages and
notmuch_thread_get_messages.
---
lib/notmuch.h | 4
1 file changed, 4 insertions(+)
diff --git a/lib/notmuch.h b/lib/notmuch.h
index 998a4ae..217bf46 100644
--- a/lib/notmuch.h
These tests check that both thread-local and global search tagging
operations are race-free. They are currently known-broken because
they aren't race-free.
---
test/emacs | 26 ++
1 file changed, 26 insertions(+)
diff --git a/test/emacs b/test/emacs
index
This fixes races in thread-local and global tagging in notmuch-search
(e.g., +, -, a, *, etc.). Previously, these would modify tags
of new messages that arrived after the search. Now they only operate
on the messages that were in the threads when the search was
performed. This prevents
Quoth Mark Walters on Oct 06 at 9:14 pm:
This whole series looks good to me. If you are rolling another version
for any reason I have one trivial comment
On Sun, 06 Oct 2013, Austin Clements amdra...@mit.edu wrote:
Traditionally, function documentation strings are intended primarily
---
NEWS | 8
1 file changed, 8 insertions(+)
diff --git a/NEWS b/NEWS
index 2e845f4..4f3b98a 100644
--- a/NEWS
+++ b/NEWS
@@ -17,6 +17,14 @@ New options to better support handling duplicate messages
bigger than the number of matching messages due to duplicates
(i.e. multiple
This improves the function documentation for many interactive
commands, either by improving their documentation string where the
improvement also makes sense for programmatic use or by adding a
'notmuch-doc property where it doesn't.
For nearly all commands that support a prefix argument, this
Traditionally, function documentation strings are intended primarily
for programmers, rather than users. They're written from the
perspective of calling the function, not interactively invoking it.
They're only ever displayed along with the function prototype (and
often refer to argument names).
Correct some grammatical errors, fix some violations of standard
documentation string formatting conventions, and be more precise.
---
emacs/notmuch-show.el | 18 ++
emacs/notmuch.el | 10 +-
2 files changed, 15 insertions(+), 13 deletions(-)
diff --git
Like `notmuch-mua-new-forward-message', this is meant to be invoked
programmatically by something that can provide a reasonable query
string.
In fact, `notmuch-mua-new-reply's interactive specification didn't
match its arguments, so it wouldn't have worked interactively.
---
emacs/notmuch-mua.el
`notmuch-mua-new-forward-message' must be called from a buffer
containing a raw RFC2822-formatted message to forward. Hence, it's
intended to be invoked programmatically through something else that
sets up this buffer (like `notmuch-show-forward-message'), not
interactively.
Remove its
The first three patches in this series simply fix some function
documentation string problems I found while making the other patches.
I'm marking them trivial because they don't affect any code.
The rest of this series improves a bunch of the built-in Emacs help,
accessed through `notmuch-help'
Great list.
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not. I'd
like a solution that either naturally doesn't have this problem, that
Great list.
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not. I'd
like a solution that either naturally doesn't have this problem, that
The first three patches in this series simply fix some function
documentation string problems I found while making the other patches.
I'm marking them trivial because they don't affect any code.
The rest of this series improves a bunch of the built-in Emacs help,
accessed through `notmuch-help'
Like `notmuch-mua-new-forward-message', this is meant to be invoked
programmatically by something that can provide a reasonable query
string.
In fact, `notmuch-mua-new-reply's interactive specification didn't
match its arguments, so it wouldn't have worked interactively.
---
emacs/notmuch-mua.el
---
NEWS | 8
1 file changed, 8 insertions(+)
diff --git a/NEWS b/NEWS
index 2e845f4..4f3b98a 100644
--- a/NEWS
+++ b/NEWS
@@ -17,6 +17,14 @@ New options to better support handling duplicate messages
bigger than the number of matching messages due to duplicates
(i.e. multiple
Correct some grammatical errors, fix some violations of standard
documentation string formatting conventions, and be more precise.
---
emacs/notmuch-show.el | 18 ++
emacs/notmuch.el | 10 +-
2 files changed, 15 insertions(+), 13 deletions(-)
diff --git
`notmuch-mua-new-forward-message' must be called from a buffer
containing a raw RFC2822-formatted message to forward. Hence, it's
intended to be invoked programmatically through something else that
sets up this buffer (like `notmuch-show-forward-message'), not
interactively.
Remove its
Quoth Mark Walters on Sep 15 at 9:17 am:
> Austin recently introduced a new global keymap. This makes pick use
> this global map.
>
> In most cases pick needs to override this global map because
> it wants to close the message pane before doing the action. However,
> this documents the
Quoth Mark Walters on Sep 15 at 9:17 am:
Austin recently introduced a new global keymap. This makes pick use
this global map.
In most cases pick needs to override this global map because
it wants to close the message pane before doing the action. However,
this documents the over-rides and
Definitely LGTM.
Quoth Mark Walters on Sep 14 at 9:17 pm:
> In the recent changes for search order handling the default-value of
> notmuch-search-oldest-first was used. However, default-value needs a
> symbol so the symbol-name needs to be quoted.
>
> This missing quote was causing strange
Definitely LGTM.
Quoth Mark Walters on Sep 14 at 9:17 pm:
In the recent changes for search order handling the default-value of
notmuch-search-oldest-first was used. However, default-value needs a
symbol so the symbol-name needs to be quoted.
This missing quote was causing strange
Quoth Mark Walters on Sep 12 at 10:33 am:
>
> Hi
>
> On Tue, 10 Sep 2013, David Bremner wrote:
> >> Ideally, we would put this output in the notmuch errors buffer but the
> >> handler is called asynchronously so we don't know when the output will
> >> appear. Thus if we put it straight into the
701 - 800 of 3445 matches
Mail list logo
