From: Eli Zaretskii <eliz@gnu.org>
To: Jarek Czekalski <jarekczek@poczta.onet.pl>
Cc: 15461@debbugs.gnu.org
Subject: bug#15461: 24.3; exec-path on ms windows should contain current directory
Date: Mon, 16 Dec 2013 18:45:02 +0200 [thread overview]
Message-ID: <83eh5ceodt.fsf@gnu.org> (raw)
In-Reply-To: <52AEB473.6030508@poczta.onet.pl>
> Date: Mon, 16 Dec 2013 09:06:11 +0100
> From: Jarek Czekalski <jarekczek@poczta.onet.pl>
>
> > If we extend the issue to how executables are found
> > by call-process, cmdproxy, shell-command, etc., we will just add
> > unneeded complexity.
>
> This remark is unnecessary. You already said that "call-process" on
> Windows should not find the executables in the current buffer's
> directory. That's the argument and that's enough. Saying about "unneeded
> complexity" only makes me think that you want to close the bug as
> quickly as possible, without much thinking.
Sorry, that was never the intent. I apologize for whatever of my
wording that led you to this conclusion.
> > Again, let's stay focused on completion.
>
> Agreed. I will provide a completion-only patch.
Thank you.
Btw, if the patch is going to be substantial, you may wish to start
your paperwork with FSF soon, as I don't see your name on file with
the FSF copyright assignment records.
next prev parent reply other threads:[~2013-12-16 16:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 13:24 bug#15461: 24.3; exec-path on ms windows should contain current directory Jarek Czekalski
2013-09-25 15:48 ` Eli Zaretskii
2013-09-26 17:23 ` bug#15461: why do I need it Jarek Czekalski
2013-09-26 17:59 ` Eli Zaretskii
2013-09-26 20:39 ` Stefan Monnier
2013-09-26 20:40 ` bug#15461: answer Jarek Czekalski
2013-12-15 20:32 ` bug#15461: 24.3; exec-path on ms windows should contain current directory Jarek Czekalski
2013-12-15 21:16 ` Eli Zaretskii
2013-12-16 8:06 ` Jarek Czekalski
2013-12-16 16:45 ` Eli Zaretskii [this message]
2013-12-18 8:15 ` Jarek Czekalski
2013-12-25 23:14 ` bug#15461: 24.3; [PATCH] " Jarek Czekalski
2013-12-26 16:23 ` Eli Zaretskii
2013-12-26 22:27 ` Jarek Czekalski
2013-12-26 23:22 ` Juanma Barranquero
2013-12-27 8:19 ` Eli Zaretskii
2013-12-27 21:02 ` Jarek Czekalski
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=83eh5ceodt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15461@debbugs.gnu.org \
--cc=jarekczek@poczta.onet.pl \
/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).