From: Chong Yidong <cyd@stupidchicken.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [david.hansen@gmx.net: Re: comint's directory tracking doesn't understand \( or \)]
Date: Sun, 04 Mar 2007 14:26:30 -0500 [thread overview]
Message-ID: <87irdgkdy1.fsf@stupidchicken.com> (raw)
In-Reply-To: <85ejo5j9bj.fsf@lola.goethe.zz> (David Kastrup's message of "Sun\, 04 Mar 2007 16\:51\:44 +0100")
David Kastrup <dak@gnu.org> writes:
>> BTW, I can't seem to reproduce the problem referenced in the original
>> bug report.
>>
>> M-x shell RET
>> ~ $ cd /tmp/
>> /tmp $ mkdir /tmp/'(2007)'
>> /tmp $ cd \(2007\)
>> /tmp/(2007) $ pwd
>>
>> => /tmp/(2007)
>
> Uh, I guess you should not use
> pwd RET
> but rather
> M-x pwd RET
>
> for checking the problem.
I understand the problem now (the original recipe wasn't clear).
I don't think we should make the proposed change to comint.el. AFAIK,
the detailed rules for how backslash escape works is, in principle,
different from shell to shell, and even if we choose to obey (e.g.)
bash semantics for backslash escapes, we might still be incompatible
with other shells. This might also introduce subtle bugs into
non-shell uses of comint mode.
It seems there will always be *some* way of confusing the directory
tracker: that's what `M-x dirs' is for.
next prev parent reply other threads:[~2007-03-04 19:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 17:44 [david.hansen@gmx.net: Re: comint's directory tracking doesn't understand \( or \)] Richard Stallman
2007-03-04 13:13 ` David Hansen
2007-03-04 15:45 ` Chong Yidong
2007-03-04 15:51 ` David Kastrup
2007-03-04 19:26 ` Chong Yidong [this message]
2007-03-04 19:32 ` David Kastrup
2007-03-04 19:39 ` Lennart Borgman (gmail)
2007-03-04 20:16 ` David Kastrup
2007-03-04 20:25 ` Lennart Borgman (gmail)
2007-03-04 19:47 ` Miles Bader
2007-03-04 21:45 ` Stefan Monnier
2007-03-04 22:06 ` Andreas Seltenreich
2007-03-04 23:42 ` Stefan Monnier
2007-03-04 23:13 ` David Hansen
2007-03-04 23:30 ` David Kastrup
2007-03-05 2:09 ` David Hansen
2007-03-04 19:40 ` Robert J. Chassell
2007-03-04 20:17 ` David Kastrup
2007-03-04 23:22 ` Chris Moore
2007-03-04 23:23 ` Tom Tromey
2007-03-05 2:55 ` Richard Stallman
2007-03-05 6:23 ` David Hansen
2007-03-05 21:50 ` Richard Stallman
2007-03-06 2:23 ` Stefan Monnier
2007-03-06 3:10 ` David Hansen
2007-03-06 22:36 ` Richard Stallman
2007-03-07 0:48 ` Miles Bader
2007-03-07 14:49 ` David Hansen
2007-03-08 3:16 ` Richard Stallman
2007-03-09 19:55 ` Chong Yidong
2007-03-09 20:28 ` Glenn Morris
2007-03-09 20:45 ` David Hansen
2007-03-09 21:08 ` David Kastrup
2007-03-10 0:04 ` Chong Yidong
2007-03-10 8:06 ` David Hansen
2007-03-10 20:18 ` Chong Yidong
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=87irdgkdy1.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=dak@gnu.org \
--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).