all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jarek Czekalski <jarekczek@poczta.onet.pl>
Cc: 15461@debbugs.gnu.org
Subject: bug#15461: why do I need it
Date: Thu, 26 Sep 2013 20:59:34 +0300	[thread overview]
Message-ID: <83pprvfoqh.fsf@gnu.org> (raw)
In-Reply-To: <52446D87.9070501@poczta.onet.pl>

> Date: Thu, 26 Sep 2013 19:23:19 +0200
> From: Jarek Czekalski <jarekczek@poczta.onet.pl>
> 
> > So I wonder what are the real-life use cases that motivated you to ask
> > for this change.  Is that only completion?
> 
> I like to have my environment comfortable. I often work with batch 
> files, sometimes they have long names. Whether I am in native windows 
> shell (cmd.exe) or in my previous editor (jedit) I am used to get the 
> batch file name completed after pressing tab. A requirement of typing 
> always the full name of a batch file is awkward.
> 
> You ask such a question that I am not sure what answer you expect.

I expected nothing more than the answer to the question.  Apologies if
the question was not clear enough.

Let me try to elaborate.

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.

The disadvantage of adding something to the environment is that it
affects more than just your use case, and it also affects every
sub-process Emacs will run.  The broader the effect, the higher the
risk of unintended consequences (a.k.a. "bugs that we will introduce
while fixing this one").

It sounds like your problem is indeed limited to completion of
executable file names, which seems to suggest that a narrower, more
specific solution is possible.





  reply	other threads:[~2013-09-26 17:59 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 [this message]
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
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=83pprvfoqh.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 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.