From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Fabio Natali <me@fabionatali.com>
Cc: help-guix@gnu.org
Subject: Re: Emacs EXWM requires restart after a Guix Home reconfigure
Date: Mon, 17 Apr 2023 14:08:11 -0400 [thread overview]
Message-ID: <87pm824c1g.fsf@gmail.com> (raw)
In-Reply-To: <87a5z8qbl0.fsf@reckondigital.com> (Fabio Natali's message of "Sun, 16 Apr 2023 13:02:35 +0100")
Hi Fabio,
Fabio Natali <me@fabionatali.com> writes:
> Dear All,
>
> I seem to be having a problem with my current Guix Home + Emacs + EXWM
> setup.
>
> Every time a new package is installed via a Guix Home reconfigure, EXWM
> requires a restart for the new package to become available, i.e. visible
> to Emacs. More details follow.
>
> Setup:
>
> - Guix Home to manage my user's environment
> - Emacs EXWM as a window manager
> - A single Emacs daemon + multiple emacsclient instances
>
> Steps to reproduce the problem:
>
> - Add a new Emacs package to a Guix Home declaration =config.scm=
> - Run =guix home reconfigure config.scm=
> - The new package is not available and can't be loaded in Emacs
> - Run =M-x guix-emacs-autoload-packages=
> - The new package is still not available
I think there's nothing special about 'guix home' or ExWM here; it
happens with any Emacs package installation; Emacs must be restarted
completely (M-x guix-emacs-autoload-packages doesn't suffice). It's a
regression that was introduced with the move to use
subdirectories/subdirs files for the Emacs package installation layout,
in 79cfe30f3eb10bd3dbf7aa0f6e873c945d7d0ea5 ("build-system: emacs: Use
subdirectories again."), if memory serves.
We should open a bug about that and see if we can come up with a fix!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-04-17 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 12:02 Emacs EXWM requires restart after a Guix Home reconfigure Fabio Natali
2023-04-17 18:08 ` Maxim Cournoyer [this message]
2023-04-19 9:32 ` Fabio Natali
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm824c1g.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@fabionatali.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.