Hello,
when I run
notmuch --config=$HOME/.notmuch-config-work new
NOTMUCH_CONFIG isn't set when the hooks are running. This would however
be quite useful such that e.g. afew uses the right database. Of course I
could do
NOTMUCH_CONFIG=$HOME/.notmuch-config-work notmuch new
inst
Hello David,
On Tue 02 Jun 2020 at 12:41PM +01, David Edmondson wrote:
> I'd hoped that:
>
> (require 'notmuch-mua)
> (setq mail-user-agent 'notmuch-user-agent)
>
> would be sufficient to get things wired up, but it doesn't seem to be.
>
> If we fix that, would it seem more appropriate? If we get
post-push comments =D
On Mon, Jun 01 2020, Daniel Kahn Gillmor wrote:
> Signed-off-by: Daniel Kahn Gillmor
> ---
> NEWS | 35 +++
> 1 file changed, 35 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index 14db7f6f..1921127f 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -1
Hello,
(already reported in #notmuch, bremner asked to forward to this list)
Using bash (Debian, 5.0-4) and notmuch (also Debian, 0.29.3-1+b2) I
noticed a breakage in notmuch's bash completion:
$ notmuch --config=/hobash: [: too many arguments
bash: declare: cannot use `-f' to ma
The features that require field processor support, are now just
documented w/o mentioning **Xapian Field Processors**' is needed
for those.
Replaced "compact" and "field_processor" with "retry_lock" in
build_with config option, as it is currently the only one that
is optionally excluded. The forme
Hi Anton,
Great that you're looking at this API! My apologies for the late
response, this slipped by me probably as I was bulk marking things as
read when I came back from a few weeks away.
On Thu 07 May 2020 at 15:57 +0200, Anton Khirnov wrote:
> 1) What is the logic behind choosing whether som
On Monday, 2020-06-01 at 10:36:16 -07, Sean Whitton wrote:
> Hello,
>
> I don't want to put (require 'notmuch) into my Emacs init because that
> will slow down initial Emacs startup a fair bit, especially since my
> (file which is equivalent to) notmuch-config.el does quite a bit of
> processing t
