unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, 24471@debbugs.gnu.org
Subject: bug#24471: 25.1.50; Error on empty PATH component
Date: Thu, 22 Sep 2016 18:28:46 -0400	[thread overview]
Message-ID: <CAM-tV-_m0=Qt875aiu=v=NmYYh_1gp+V2etiBZZ92LL6oJRq1Q@mail.gmail.com> (raw)
In-Reply-To: <83eg4benr2.fsf@gnu.org>

found 24471 25.1
tag 24471 = patch
quit

On Thu, Sep 22, 2016 at 3:30 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Achim Gratz <Stromeko@nexgo.de>
>> Date: Thu, 22 Sep 2016 20:44:00 +0200
>>
>> Here's the (redacted) backtrace leading to the error I encountered.
>>
>> --8<---------------cut here---------------start------------->8---
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>   directory-file-name(nil)
>>   mapcar(directory-file-name ("c:/WINDOWS/SYSTEM32/" "c:/WINDOWS/" "c:/WINDOWS/SYSTEM32/WBEM/" nil "c:/Local_Install/share/emacs-25.1/libexec/emacs/25.1/x86_64-w64-mingw32/"))
>>   eval((mapcar (quote directory-file-name) (append (parse-colon-path (getenv "PATH")) (list exec-directory))))
>>   custom-push-theme(theme-value exec-path user set (quote ("/usr/bin")))
>>   custom-theme-set-variables(user ((exec-path (quote ("/usr/bin")))))
>>   apply(custom-theme-set-variables user ((exec-path (quote ("/usr/bin")))))
>>   custom-set-variables((exec-path (quote ("/usr/bin"))))
>>   eval-buffer(#<buffer  *load*> nil "//server/Gratz/GNU/.emacs" nil t)  ; Reading at buffer position 3839
>
> Thanks.  Does the patch below fix the problem?

Ah, the custom :standard value is different from the initial value,
which uses decode_env_path. Is it possible to use the same code for
both? It seems that decode_env_path handles some extra things: file
name encoding, checking for file name handlers.





  parent reply	other threads:[~2016-09-22 22:28 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
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 [this message]
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='CAM-tV-_m0=Qt875aiu=v=NmYYh_1gp+V2etiBZZ92LL6oJRq1Q@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=24471@debbugs.gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=eliz@gnu.org \
    /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).