emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24471: closed (25.1.50; Error on empty PATH compon


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24471: closed (25.1.50; Error on empty PATH component)
Date: Mon, 17 Oct 2016 01:57:01 +0000

Your message dated Sun, 16 Oct 2016 21:56:49 -0400
with message-id <address@hidden>
and subject line Re: bug#24471: 25.1.50; Error on empty PATH component
has caused the debbugs.gnu.org bug report #24471,
regarding 25.1.50; Error on empty PATH component
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24471: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24471
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.1.50; Error on empty PATH component Date: Mon, 19 Sep 2016 21:06:38 +0200
In GNU Emacs 25.1 (x86_64 for Windows)

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.



Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs



--- End Message ---
--- Begin Message --- Subject: Re: bug#24471: 25.1.50; Error on empty PATH component Date: Sun, 16 Oct 2016 21:56:49 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Version: 25.2

Glenn Morris wrote:

> Please just replace nil elements with ".".
>
> The point of that code in cus-start is so that exec-path does not show
> up in customize-rogue output under normal circumstances. A test case is
>
> PATH=:$PATH emacs -Q -f customize-rogue

Done.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]