From: Kevin Rodgers <kevinr@ihs.com>
Subject: Re: *shell* TAB *Completions* fooled by $PWD/
Date: Wed, 10 Jul 2002 10:48:57 -0600 [thread overview]
Message-ID: <3D2C6579.3020005@ihs.com> (raw)
In-Reply-To: buowus58hgc.fsf@mcspd15.ucom.lsi.nec.co.jp
Miles Bader wrote:
> In general, you can't rely on completion in shell-mode to know about the
> exact internal state of the shell process, since there's no way for
> emacs to figure that out (it tries to track the current directory, since
> that's very important, but even that can sometimes get messed up). The
> value of the PWD environment variable in emacs is just whatever value it
> got at startup.
The shell.el directory tracking mechanism could be modified to update
the PWD environment variable as well as its internal variables. But
unlike its internal variables, which can be local to the *shell* buffer,
the environment variable's value is shared via the global
process-environment Emacs variable. (And we have to consider the case
when there's more than one *shell* buffer.) But perhaps Shell mode could
make process-environment local to the *shell* buffer, so it would be free
to update PWD.
--
Kevin Rodgers <kevinr@ihs.com>
next prev parent reply other threads:[~2002-07-10 16:48 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 [this message]
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
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=3D2C6579.3020005@ihs.com \
--to=kevinr@ihs.com \
/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).