unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 24471@debbugs.gnu.org
Subject: bug#24471: 25.1.50; Error on empty PATH component
Date: Mon, 19 Sep 2016 22:14:32 +0300	[thread overview]
Message-ID: <83intrhfc7.fsf@gnu.org> (raw)
In-Reply-To: <87ponzlnep.fsf@Rainer.invalid> (message from Achim Gratz on Mon,  19 Sep 2016 21:06:38 +0200)

> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Mon, 19 Sep 2016 21:06:38 +0200
> 
> I've updated from Emacs 24.5 to Emacs 25.1 this morning at work.
> Starting the new Emacs produced an error during initialization trying to
> process (directory-file-name nil).  The reason it turned out was that
> our IT department in their infinite wisdom had ended the system PATH
> with a ';'.  Emacs extended that path with ';/usr/bin/' (or something
> like that, I'm making this report from home), this created an empty path
> element that ended up at directory-file-name.  Emacs should sanitize the
> PATH if it can't process nil in downstream functions.

Please show the Lisp backtrace from the error, so that the path from
PATH to directory-file-name could be seen.

Thanks.





  reply	other threads:[~2016-09-19 19:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 19:06 bug#24471: 25.1.50; Error on empty PATH component Achim Gratz
2016-09-19 19:14 ` Eli Zaretskii [this message]
2016-09-19 21:41   ` Achim Gratz
2016-09-19 21:59     ` Noam Postavsky
2016-09-22 18:44       ` Achim Gratz
2016-09-22 19:30         ` Eli Zaretskii
2016-09-22 20:10           ` Achim Gratz
2016-09-23  6:59             ` Eli Zaretskii
2016-09-23 15:54               ` Glenn Morris
2016-10-17  1:56                 ` Glenn Morris
2016-10-17 16:21                 ` Achim Gratz
2016-09-22 22:28           ` Noam Postavsky
2016-09-23  7:14             ` Eli Zaretskii
2016-10-17 16:25           ` Achim Gratz
2016-10-17 17:36             ` Eli Zaretskii
2016-10-17 18:16               ` Achim Gratz
2016-10-17 18:53                 ` Eli Zaretskii

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83intrhfc7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24471@debbugs.gnu.org \
    --cc=Stromeko@nexgo.de \
    /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/emacs.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).