unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: 'Emacs Developers' <emacs-devel@gnu.org>
Subject: RE: FW: shell: cd after &
Date: Wed, 11 Jun 2003 17:42:29 +0100	[thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC10755405@eagle.midas-kapiti.com> (raw)

You can always do M-x dirs RET to resync emacs' idea of the directory
stack.  

It might be useful to add a selectable feature whereby emacs does a
(dirs) after each (comint-send-input).  You'd want to turn it off if you
did ftp or something from the *shell*.  I remember implementing
something like that many years ago, but decided it would be too annoying
to put in shell.el.  Nothing is going to be infallible.

As the shell.el comment says, "The solution is to relax, not stress out
about it, and settle for a hack that works pretty well in typical
circumstances."

-----Original Message-----
From: Rajesh Vaidheeswarran [mailto:rv@gnu.org]
Sent: 11 June 2003 16:52
To: Stephen J. Turnbull
Cc: Marshall, Simon; 'Emacs Developers'; Norbert Koch
Subject: Re: FW: shell: cd after &


One of the issues that I have always found to be clunky with the
existing
cwd tracking in shell is its inability to track the pwd after every
command,
not just explicit directory commands.

For instance, I use a program called `workon' extensively to work with
different cvs modules. The program sets the pertinent environment
variables
and exec a shell and puts the user in the root of the cvs module.

When I use this within emacs, I typically do something like

% workon emacs
% cd `pwd`

for emacs to understand the current directory.

Of course, I don't have any suggestions on how this can be solved.
Anyway, I guess the current change in question is a step in the right
direction. 

In a previous message, "Stephen J. Turnbull" writes:

> >>>>> "Simon" == Simon Marshall <Marshall> writes:
> 
>     Simon> I don't know if anyone cares enough about this.  It's so
>     Simon> long since I maintained shell.el I don't know if it's worth
>     Simon> it.
> 
> FWIW Norbert Koch <viteno@xemacs.org> approved it for XEmacs.  So, if
> you want rationale, you could ask him.

             reply	other threads:[~2003-06-11 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 16:42 Marshall, Simon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 15:03 FW: shell: cd after & Marshall, Simon
2003-06-11 13:24 ` Stephen J. Turnbull
2003-06-11 15:52   ` Rajesh Vaidheeswarran
2003-06-11 16:04     ` Rajesh Vaidheeswarran

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=FC3DA3DC8D4AD311AB910020352A8FDC10755405@eagle.midas-kapiti.com \
    --to=simon.marshall@misys.com \
    --cc=emacs-devel@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).