From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Wrong PATH in MSYS2/MINGW64 builds?
Date: Fri, 29 May 2015 08:05:46 +0600 [thread overview]
Message-ID: <CAP_d_8UFe1nuBPB4=j-tD1g_CHu+EhxW0TMrN_Sg+_txcdQ5hg@mail.gmail.com> (raw)
In-Reply-To: <83r3q0wrvw.fsf@gnu.org>
On Thu, May 28, 2015 at 11:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> From: Óscar Fuentes <ofv@wanadoo.es>
>> >>
>> >> I would expect from Emacs to be able to execute the applications that
>> >> reside on the same directory as emacs.exe.
>> >
>> > Why would you expect that?
>>
>> Because it's the default native behavior on Windows?
>>
> Why would you think Emacs should invoke CreateProcess with just
> "bzip2" as the program name?
I'm not thinking what Emacs "should" or "should not". I'm just
pointing out that being able to run programs that reside in the same
directory as the calling process' executable (as well as several other
directories not necessarily listed on $PATH) is a reasonable
expectation for a Windows user.
next prev parent reply other threads:[~2015-05-29 2:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 13:56 Wrong PATH in MSYS2/MINGW64 builds? Angelo Graziosi
2015-05-28 14:11 ` Óscar Fuentes
2015-05-28 15:09 ` Eli Zaretskii
2015-05-28 15:36 ` Óscar Fuentes
2015-05-28 16:37 ` Eli Zaretskii
2015-05-28 16:52 ` Yuri Khan
2015-05-28 17:09 ` Eli Zaretskii
2015-05-29 2:05 ` Yuri Khan [this message]
2015-05-29 6:05 ` Eli Zaretskii
2015-05-28 15:41 ` Angelo Graziosi
2015-05-28 16:49 ` Eli Zaretskii
2015-05-28 21:51 ` Angelo Graziosi
2015-05-29 5:55 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2015-05-28 15:06 Angelo Graziosi
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='CAP_d_8UFe1nuBPB4=j-tD1g_CHu+EhxW0TMrN_Sg+_txcdQ5hg@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.