From: Richard Stallman <rms@gnu.org>
Subject: [Peter_Dyballa@Web.DE: popd in tcsh fails]
Date: Mon, 22 Aug 2005 21:28:53 -0400 [thread overview]
Message-ID: <E1E7Nav-00058y-Ry@fencepost.gnu.org> (raw)
[I sent this message twice before but did not get a response.]
Can someone please look at this, then ack to me?
------- Start of forwarded message -------
To: emacs-pretest-bug@gnu.org
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Date: Wed, 20 Jul 2005 15:36:11 +0200
X-Sender: Peter_Dyballa@web.de
Subject: popd in tcsh fails
Sender: emacs-pretest-bug-bounces+rms=gnu.org@gnu.org
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python
X-Spam-Level:
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
Hello!
I am using tcsh 6.12.00 in *shell* mode and GNU Emacs does not seem to
understand popd, i.e. after a popd in *shell* file name completion or
dired start with the directory that was before my working directory.
These variables are customized:
'(comint-completion-recexact t)
'(comint-input-ignoredups t)
'(comint-input-ring-file-name ".emacs.d/history")
'(comint-prompt-regexp "^[a-z]+ [0-9]+ /\\\\ " t)
'(comint-use-prompt-regexp nil)
'(shell-cd-regexp "[cp]d")
'(shell-dirtrack-verbose nil)
'(shell-pushd-regexp "p(ush|)d")
Important settings:
value of $LC_ALL: de_DE.UTF-8
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: de_DE.UTF-8
locale-coding-system: utf-8
default-enable-multibyte-characters: t
Major mode: Shell
Minor modes in effect:
display-time-mode: t
mouse-sel-mode: t
show-paren-mode: t
desktop-save-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
tooltip-mode: t
auto-compression-mode: t
menu-bar-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
next-error-follow-minor-mode: Fol
- --
Greetings
Pete
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is winning."
-- Rich Cook
_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------
next reply other threads:[~2005-08-23 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 1:28 Richard Stallman [this message]
2005-08-23 18:02 ` [Peter_Dyballa@Web.DE: popd in tcsh fails] Emilio Lopes
2005-08-23 18:41 ` Emilio Lopes
2005-08-24 10:32 ` Richard M. Stallman
2005-08-23 18:48 ` Fwd: popd in tcsh fails Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 13:22 [Peter_Dyballa@Web.DE: popd in tcsh fails] Dhruva Krishnamurthy (RBIN/EDI3) *
2005-08-08 13:50 ` David Kastrup
2005-08-08 13:57 ` Peter Dyballa
2005-08-08 12:09 Richard Stallman
2005-07-24 21:14 Richard M. Stallman
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=E1E7Nav-00058y-Ry@fencepost.gnu.org \
--to=rms@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).