Subject: bug#24471: 25.1.50; Error on empty PATH component

From: Noam Postavsky <[email-masked]>
Date: Thu, 22 Sep 2016 18:28:46 -0400

found 24471 25.1
tag 24471 = patch
quit

On Thu, Sep 22, 2016 at 3:30 PM, Eli Zaretskii <[email-masked]> wrote:
>> From: Achim Gratz <[email-masked]>
>> 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.