unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 38273@debbugs.gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>
Subject: bug#38273: emacs doesn't open files
Date: Wed, 20 Nov 2019 18:19:51 +0100	[thread overview]
Message-ID: <CAJ3okZ3q5rT0bn54ddh9KjXwrsuvgLZ1KDanapYXQ6XdxuhLzg@mail.gmail.com> (raw)
In-Reply-To: <87zhgrv8kh.fsf@gmail.com>

Hi Maxim,

Thank you to looking.

On Tue, 19 Nov 2019 at 22:51, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> Did you sort out your issue?  Perhaps logging out then back in could
> define the missing EMACSLOADPATH environment variable? Or manually
> sourcing your current profile's etc/profile and starting Emacs from that
> shell?

Yes, sourcing the current etc/profile fixes the issue.

Therefore, EMACSLOADPATH should be the culprit and I had done a
mistake, not enough investigating before reporting. My bad! Sorry!


> I'll try to isolate how to reproduce the problem; if you have a way to
> reproduce it I'm interested!

I think it comes from the new EMACSLOADPATH variable. The new Emacs
binary is looking at it so if the etc/profile is not yet sourced then
troubles arises.
That's why it does not happen with "-Q" because no-site-file and
no-site-lisp, i.e., EMACSLOADPATH is not "required".
However, "-q" just turns off the ~/.emacs and needs EMACSLOADPATH.

So I think to reproduce: install an old Emacs, upgrade, do not source
again the current profile, launch Emacs from this profile.

Well, it is not an issue but a bad practise. :-)
Sorry.


All the best,
simon

  parent reply	other threads:[~2019-11-20 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 15:35 bug#38273: emacs doesn't open files Jesse Gibbons
2019-11-19 16:16 ` zimoun
2019-11-19 21:51   ` Maxim Cournoyer
2019-11-20  4:08     ` Jesse Gibbons
2019-11-20 17:20       ` zimoun
2019-11-20 17:19     ` zimoun [this message]
2019-11-22  3:46       ` Maxim Cournoyer
2019-11-22 13:42         ` zimoun
2019-11-19 17:07 ` bug#38274: " Jesse Gibbons
2019-11-19 21:20   ` bug#38273: " Maxim Cournoyer
2019-11-20  4:13     ` Jesse Gibbons

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=CAJ3okZ3q5rT0bn54ddh9KjXwrsuvgLZ1KDanapYXQ6XdxuhLzg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=38273@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    --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).