all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; command paths are not expanded in *shell* buffer
Date: Sun, 18 May 2008 23:50:31 +0200	[thread overview]
Message-ID: <87mymn9t94.fsf@escher.local.home> (raw)
In-Reply-To: 61D1EAB9-5B39-4E41-B22D-B34B51E4CE30@Freenet.DE

On Sun, 18 May 2008 19:56:05 +0200 Peter Dyballa <Peter_Dyballa@Freenet.DE> wrote:

> After launching GNU Emacs with -Q and creating a *shell* buffer (with
> tcsh 6.12.00 (Astron) 2002-07-23 (powerpc-apple-darwin) options
> 8b,nls,dl,al,kan,sm,rh,color,dspm,filec) I can't expand the absolute
> path of GNU Emacs. It does not work when I start typing /us<TAB> nor
> does it work when I insert a <SPC> before the /us start of the path
> name. (When I type <RET> to get rid of everything typed tcsh asks me
> whether /usr is OK, autocorrect and 'correct = all' are set). It also
> fails with relative paths.
>
> It works (with absolute and relative paths) when I start the command
> with another word (some command or alias).
[...]
> This behaviour started weeks, or months, ago. I then thought it was
> due to adding 'correct = all', but *shell* in GNU Emacs 22.2 does not
> show the same ... and the tcsh setting plays no role!

I see the same behavior in GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+
Version 2.12.0) of 2008-05-15 with bash.  It works fine in GNU Emacs
23.0.60.7 (i686-pc-linux-gnu, GTK+ Version 2.12.0) of 2008-02-21.

Steve Berman





  reply	other threads:[~2008-05-18 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87d4kviavz.fsf@stupidchicken.com>
2008-05-18 17:56 ` 23.0.60; command paths are not expanded in *shell* buffer Peter Dyballa
2008-05-18 21:50   ` Stephen Berman [this message]
2008-07-30 16:45   ` bug#274: marked as done (23.0.60; command paths are not expanded in *shell* buffer) Emacs bug Tracking System

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mymn9t94.fsf@escher.local.home \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.