From: David Bremner <david@tethera.net>
To: "Charles-André Roy" <caroy47@videotron.ca>, notmuch@notmuchmail.org
Subject: Re: Cannot Start Notmuch (invalid-read-syntax "#")
Date: Mon, 13 Sep 2021 08:51:04 -0300 [thread overview]
Message-ID: <87wnnk3d93.fsf@tethera.net> (raw)
In-Reply-To: <87zgsg3dhx.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
>> Debugger entered--Lisp error: (invalid-read-syntax "#")
>> read(#<buffer *load*>)
>> eval-buffer(#<buffer *load*> nil "/home/charles/.notmuch-config" nil t) ; Reading at buffer position 2
>> load-with-code-conversion("/home/charles/.notmuch-config" "/home/charles/.notmuch-config" t t)
>> load("~/.notmuch-config" t t nil t)
>
> The emacs function load is for lisp files. $HOME/.notmuch-config is an
> INI style config file, which does indeed have many '#' in it by
> default. Why emacs is trying to run .notmuch-config as lisp is currently
> a mystery to me.
Oh, I might know what is happening. notmuch-emacs is trying to load
.notmuch-config.el, and you (maybe?) have $HOME in your emacs load-path.
I guess I would pretty strongly recommmend not having $HOME in your
emacs load-path (at least I just end up with random files in my $HOME).
If it's important to you to have $HOME in your load-path, you can use
the XDG location for your config file: put it in
$HOME/.config/notmuch/default/config.
d
next prev parent reply other threads:[~2021-09-13 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 1:37 Cannot Start Notmuch (invalid-read-syntax "#") Charles-André Roy
2021-09-13 11:45 ` David Bremner
2021-09-13 11:51 ` David Bremner [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-13 15:43 Charles-André Roy
2021-09-13 16:50 ` David Bremner
2021-09-13 19:43 Charles-André Roy
2021-09-13 21:32 ` Tomi Ollila
2021-09-14 12:16 ` David Bremner
2021-09-14 14:47 ` Charles-André Roy
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=87wnnk3d93.fsf@tethera.net \
--to=david@tethera.net \
--cc=caroy47@videotron.ca \
--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).