From: Miles Bader <miles@gnu.org>
Subject: Re: *shell* TAB *Completions* fooled by $PWD/
Date: 18 Jul 2002 03:26:28 +0900 [thread overview]
Message-ID: <87wuru2otn.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: vafu1mywauc.fsf@lucy.cs.uni-dortmund.de
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > This is a hard problem to solve,
>
> Isn't it enough to just send the current contents of the line,
> followed by TAB, to the shell and to parse the output?
There are many annoying little wrinkles involved in doing this
correctly, so that it's definitely not a `just' thing.
Annoying little wrinkle (1): you don't actually know who's listening
when you send input to the subprocess -- it may be the shell you
started, it may be some process running under the shell...
[The recent conversation about python-mode is a somewhat different case,
because there you can make more assumptions about what the subprocess is
doing.]
-Miles
--
Saa, shall we dance? (from a dance-class advertisement)
next prev parent reply other threads:[~2002-07-17 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 21:13 *shell* TAB *Completions* fooled by $PWD/ Dan Jacobson
[not found] ` <200207081820.g68IKeP12935@aztec.santafe.edu>
2002-07-09 0:24 ` Dan Jacobson
2002-07-09 7:54 ` Miles Bader
2002-07-10 6:03 ` Dan Jacobson
2002-07-10 17:31 ` Miles Bader
2002-07-10 16:48 ` Kevin Rodgers
2002-07-10 17:45 ` Dan Jacobson
2002-07-10 18:21 ` Kevin Rodgers
2002-07-10 18:30 ` David Kastrup
2002-07-11 12:01 ` Richard Stallman
2002-07-11 13:26 ` Miles Bader
2002-07-11 13:30 ` David Kastrup
2002-07-11 13:55 ` Miles Bader
2002-07-11 14:31 ` David Kastrup
2002-07-11 17:06 ` Kevin Rodgers
2002-07-11 23:05 ` David Kastrup
2002-07-12 8:09 ` Andreas Schwab
2002-07-17 16:58 ` Kai Großjohann
2002-07-17 18:26 ` Miles Bader [this message]
2002-07-18 12:01 ` Kai Großjohann
2002-07-18 12:18 ` Andreas Schwab
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=87wuru2otn.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@gnu.org \
/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).