From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Stromeko@nexgo.de, 24471@debbugs.gnu.org
Subject: bug#24471: 25.1.50; Error on empty PATH component
Date: Fri, 23 Sep 2016 10:14:35 +0300 [thread overview]
Message-ID: <837fa3dr50.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-_m0=Qt875aiu=v=NmYYh_1gp+V2etiBZZ92LL6oJRq1Q@mail.gmail.com> (message from Noam Postavsky on Thu, 22 Sep 2016 18:28:46 -0400)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Thu, 22 Sep 2016 18:28:46 -0400
> Cc: Achim Gratz <Stromeko@nexgo.de>, 24471@debbugs.gnu.org
>
> 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.
File name encoding should not be the problem, because the Lisp getenv
takes care of that already (see make_string). As for file-name
handlers, do we expect PATH to include such file names?
(decode_env_path is more general, and used not just for PATH.)
next prev parent reply other threads:[~2016-09-23 7: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fa3dr50.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24471@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.