From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: David Bremner <david@tethera.net>
Cc: Boruch Baum <boruch_baum@gmx.com>, notmuch@notmuchmail.org
Subject: Re: bugreport: notmuch-hello (debian package elpa-notmuch 0.37-1)
Date: Thu, 29 Dec 2022 14:38:43 +0100 [thread overview]
Message-ID: <DA0DE3ED-2D94-4E32-8FDA-73A8C69807B5@condition-alpha.com> (raw)
In-Reply-To: <87o7rm73e8.fsf@tethera.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 2450 bytes --]
Perhaps a case for exec-path-from-shell [1]?
[1] https://github.com/purcell/exec-path-from-shell
--alex
--
www.condition-alpha.com / @c_alpha
Sent from my iPhone; apologies for brevity and autocorrect weirdness.
> On 29. Dec 2022, at 14:20, David Bremner <david@tethera.net> wrote:
>
> Boruch Baum <boruch_baum@gmx.com> writes:
>
>> I wasn't sure the best way to report a bug against it, so I hope by
>> sending it to thislist it will find its proper home.
>
> Sure that's fine. Or report a debian bug using reportbug, which saves
> you copying down the relevant versions. In particular it's possibly
> relevant what version of emacs you are using.
>>
>> export NOTMUCH_CONFIG=$HOME/.config/notmuch/notmuch.conf
>>
>> With this setting, I successfully set-up notmuch, created a database,
>> and searched it from the command-line. However, from within emacs, M-x
>> notmuch-hello failed when it would internally send shell command:
>>
>> notmuch count --exclude=false
>>
>> The emacs shell-command error buffer would report "Error: cannot load
>> config file". From outside emacs, that shell command *would* succeed.
>
> I wasn't able to duplicate this (I'm running the debian packages and
> emacs 28).
>
> 1) As a first step, try M-x getenv NOTMUCH_CONFIG
> 2) Just to confirm, you're not doing anything fancy with shell wrappers for
> either emacs or notmuch, are you?
>>
>> What did work for me was to create a default profile folder and move
>> the config file there.
>>
>> export NOTMUCH_CONFIG=""
>
> Being set to the empty string is not the same as being unset from
> notmuch's point of view. So maybe try unset instead. Empty string means
> no config file is searched for or loaded.
>
>> mkdir ~/.config/notmuch/default
>> mv ~/.config/notmuch/{notmuch.conf,default/config}
>>
>> But then, in order to be able to continue to use notmuch from the
>> command-line I needed to perform
>>
>> export NOTMUCH_CONFIG=$HOME/.config/notmuch/default/config
>>
>> So it looks like the elisp package isn't checking the file location
>> precedence mentioned in the man pages.
>
> That definitely should not be the case, but may be potentially related
> to having NOTMUCH_CONFIG="".
>
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
[-- Attachment #1.1.2: Type: text/html, Size: 4983 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1944 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2022-12-29 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 12:23 bugreport: notmuch-hello (debian package elpa-notmuch 0.37-1) Boruch Baum
2022-12-29 13:20 ` David Bremner
2022-12-29 13:38 ` Alexander Adolf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DA0DE3ED-2D94-4E32-8FDA-73A8C69807B5@condition-alpha.com \
--to=alexander.adolf@condition-alpha.com \
--cc=boruch_baum@gmx.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).