unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	38309@debbugs.gnu.org, a@ajgrf.com
Subject: bug#38309: Recent $EMACSLOADPATH changes crash gnome-session
Date: Tue, 26 Nov 2019 10:30:11 +0100	[thread overview]
Message-ID: <87eexvc7do.fsf@gnu.org> (raw)
In-Reply-To: <87k17n0z9t.fsf@lassieur.org> ("Clément Lassieur"'s message of "Tue, 26 Nov 2019 10:20:46 +0100")

Hello,

clement@lassieur.org (Clément Lassieur) skribis:

> Before the patches, restarting Emacs was enough to have new packages
> installed.  Now I have to reboot my computer every time I 'guix package
> -i emacs-something'.  Emacs is central to my workflow and I often change
> things around (as do a lot of Guix users).  It is inconvenient, really.

I wasn’t aware of that, it sounds like a drawback.  I wonder if
Emacs-Guix knows how to deal with that (until now it was able to
directly load Emacs packages you’d install with itself).

I think I would lean towards a revert (that is, a single commit
reverting the 3 (?) patches that implement this new approach).

Then we can discuss the change with less pressure and make sure
stakeholders weigh in (they could have done that before but apparently
many, myself included, missed that opportunity :-)).

Thoughts?

Thanks,
Ludo’.

  reply	other threads:[~2019-11-26  9:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  2:25 bug#38309: Recent $EMACSLOADPATH changes crash gnome-session Alex Griffin
2019-11-22 13:00 ` Clément Lassieur
2019-11-22 13:15   ` Mathieu Othacehe
2019-11-22 17:40     ` Maxim Cournoyer
2019-11-23 18:05       ` Ludovic Courtès
2019-11-24  3:45         ` Maxim Cournoyer
2019-11-24 17:56           ` Ludovic Courtès
2019-11-25 17:23             ` Maxim Cournoyer
2019-11-26  9:20               ` Clément Lassieur
2019-11-26  9:30                 ` Ludovic Courtès [this message]
2019-11-27 14:10                 ` Maxim Cournoyer
2019-11-27 14:15                   ` Clément Lassieur
2019-11-27 17:30                   ` Clément Lassieur
2019-11-26  9:43               ` Clément Lassieur
2019-11-26  4:04             ` Maxim Cournoyer
2019-11-26  8:56               ` Ludovic Courtès
2019-11-27  3:12                 ` Maxim Cournoyer
2019-11-27  9:04                   ` Clément Lassieur
2019-11-27  0:01 ` Leo Prikler
2019-11-27 13:58   ` Maxim Cournoyer
2019-11-27 14:21     ` Jelle Licht
2019-11-28  5:28       ` Maxim Cournoyer
2019-12-02 10:36     ` Clément Lassieur
2019-12-03  9:38       ` Arne Babenhauserheide
2019-12-04  9:14       ` Ludovic Courtès
2019-12-04 10:14         ` Clément Lassieur
2019-12-04 12:31           ` Arne Babenhauserheide
2019-12-04 11:11         ` Arne Babenhauserheide
2019-12-06 17:02           ` Maxim Cournoyer
2019-12-07 16:18             ` Arne Babenhauserheide

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eexvc7do.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38309@debbugs.gnu.org \
    --cc=a@ajgrf.com \
    --cc=clement@lassieur.org \
    --cc=maxim.cournoyer@gmail.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).