Defer notmuch.el setup

Defer notmuch.el setup

[artur.brzozowski]

[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]

Hi.

I am trying out notmuch and notmuch.el as an Emacs user. When adding some
funcitonality to Emacs, I usually wrap its setup inside a (with-eval-after-load)
block to defer it for when it is needed. I noticed that in case of notmuch.el,
some settings are not properly set if included in in the macro - here I mean a
quite important option 'notmuch-search-oldest-first' which I set to nil. When
included inside the (with-eval-after-load) body it remains unchanged. Of course
italso makes me wonder if any other variable acts in this way and needs to be
set at Emacs runtime.

Is that a bug?

~Artur

[-- Attachment #1.2: Type: text/html, Size: 1128 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: Defer notmuch.el setup

[David Bremner]

"artur.brzozowski" <artur.brzozowski@protonmail.com> writes:

> I am trying out notmuch and notmuch.el as an Emacs user. When adding some
> funcitonality to Emacs, I usually wrap its setup inside a (with-eval-after-load)
> block to defer it for when it is needed. I noticed that in case of notmuch.el,
> some settings are not properly set if included in in the macro - here I mean a
> quite important option 'notmuch-search-oldest-first' which I set to nil. When
> included inside the (with-eval-after-load) body it remains unchanged. Of course
> italso makes me wonder if any other variable acts in this way and needs to be
> set at Emacs runtime.

I'm not sure about with-eval-after-load, but

1) you need to use setq-default for this variable (or use customize),
   because it is buffer-local.

2) You can achieve the same deferral of settings by adding your settings
   to ~/.emacs.d/notmuch-config.el

Re: Defer notmuch.el setup

[Dan Čermák]

Hi David,

David Bremner <david@tethera.net> writes:

> 2) You can achieve the same deferral of settings by adding your settings
>    to ~/.emacs.d/notmuch-config.el

Does notmuch automatically load that file upon launching?


Thanks,

Dan

Re: Defer notmuch.el setup

[David Bremner]

Dan Čermák <dan.cermak@posteo.net> writes:

> Hi David,
>
> David Bremner <david@tethera.net> writes:
>
>> 2) You can achieve the same deferral of settings by adding your settings
>>    to ~/.emacs.d/notmuch-config.el
>
> Does notmuch automatically load that file upon launching?

Yep, see [1] for the details.

[1]: https://notmuchmail.org/doc/latest/notmuch-emacs.html#init-file\r

Re: Defer notmuch.el setup

[David Bremner]

David Bremner <david@tethera.net> writes:

> "artur.brzozowski" <artur.brzozowski@protonmail.com> writes:
>
>> I am trying out notmuch and notmuch.el as an Emacs user. When adding some
>> funcitonality to Emacs, I usually wrap its setup inside a (with-eval-after-load)
>> block to defer it for when it is needed. I noticed that in case of notmuch.el,
>> some settings are not properly set if included in in the macro - here I mean a
>> quite important option 'notmuch-search-oldest-first' which I set to nil. When
>> included inside the (with-eval-after-load) body it remains unchanged. Of course
>> italso makes me wonder if any other variable acts in this way and needs to be
>> set at Emacs runtime.
>
> I'm not sure about with-eval-after-load, but
>
> 1) you need to use setq-default for this variable (or use customize),
>    because it is buffer-local.

Artur reported off list that using setq-default was the fix.