From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15461@debbugs.gnu.org, Jarek Czekalski <jarekczek@poczta.onet.pl>
Subject: bug#15461: why do I need it
Date: Thu, 26 Sep 2013 16:39:07 -0400 [thread overview]
Message-ID: <jwvvc1nxqsw.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83pprvfoqh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Sep 2013 20:59:34 +0300")
> If the only use case where you need this is completion of executables,
> an alternative solution could be to teach such completion to look in
> the current buffer's default directory, on systems where that is
> implicit. This could be an easier solution than futzing with the
> environment.
Completion should mirror the behavior of the code that spawns the
process, so if the process name can be relative to default-directory,
completion should also accept file names in default-directory.
Stefan
next prev parent reply other threads:[~2013-09-26 20:39 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvvc1nxqsw.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=15461@debbugs.gnu.org \
--cc=eliz@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 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.