From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>, 2062@emacsbugs.donarmstrong.com
Cc: Emacs Bug Tracker <submit@emacsbugs.donarmstrong.com>
Subject: bug#2062: PATH can contain non-expanded variables
Date: Mon, 26 Jan 2009 23:01:05 +0100 [thread overview]
Message-ID: <e01d8a50901261401l2077a7bdm65e605712b5a8f75@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0901260500h18a7ac63uf5c88cbb515ddeb0@mail.gmail.com>
On Mon, Jan 26, 2009 at 2:00 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> Package: emacs,w32
> Version: 23.0.60
>
> It is possible for PATH (or other path-like variables, like EMACSPATH
> and EMACSLOADPATH) to contain unexpanded variables:
>
> ELISP> exec-path
> ("c:/emacs/bin" "%MYTEST%" "C:/WINDOWS/system32" "C:/WINDOWS"
> "C:/WINDOWS/system32/Wbem" "c:/emacs/trunk/bin")
>
> for example, if the user has set
> "HKLM\Microsoft\Windows\CurrentVersion\App Paths\emacs.exe\Path" as a
> REG_EXPAND_SZ.
>
> These variables should be expanded, but currently
> emacs.c:decode_env_path does not. The following patch fixes it.
>
> Comments?
Nice. Thanks.
next prev parent reply other threads:[~2009-01-26 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7ccd24b0901280707u39a4364bk76339f2e5956fa5@mail.gmail.com>
2009-01-26 13:00 ` bug#2062: PATH can contain non-expanded variables Juanma Barranquero
2009-01-26 22:01 ` Lennart Borgman [this message]
2009-01-27 1:56 ` Jason Rumney
2009-01-27 8:34 ` Juanma Barranquero
2009-01-27 9:24 ` Jason Rumney
2009-01-27 10:25 ` Juanma Barranquero
2009-01-27 13:29 ` Jason Rumney
2009-01-27 14:42 ` Juanma Barranquero
2009-01-27 19:02 ` Stefan Monnier
2009-01-27 20:00 ` Juanma Barranquero
2009-01-28 8:39 ` Jason Rumney
2009-01-28 8:45 ` Juanma Barranquero
2009-01-27 19:30 ` Eli Zaretskii
2009-01-27 19:55 ` Juanma Barranquero
2009-01-28 4:12 ` Eli Zaretskii
2009-01-28 8:36 ` Juanma Barranquero
2009-01-28 14:24 ` Stefan Monnier
2009-01-28 15:15 ` bug#2062: marked as done (PATH can contain non-expanded variables) Emacs bug Tracking System
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=e01d8a50901261401l2077a7bdm65e605712b5a8f75@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=2062@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
--cc=submit@emacsbugs.donarmstrong.com \
/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).