unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: don't require path hints for *shell*
Date: Thu, 28 Feb 2008 16:41:36 -0500	[thread overview]
Message-ID: <87hcfsvjvz.fsf@stupidchicken.com> (raw)
In-Reply-To: 87tzlq7d1c.fsf@jidanni.org

jidanni@jidanni.org writes:

> Why do we have to give *shell* a hint (./) to get it to expand paths?
> $ emacs -Q -f shell
> c d SPC <tab> <tab> <tab> <tab> . / <tab>
> Bash needs no hint. Act like bash as the default, please.
> emacs-version "22.1.1"

The following patch implements this behavior.  If no one objects, I'll
check it into the trunk shortly.

*** emacs/lisp/shell.el.~1.149.2.4.~	2008-01-10 10:25:37.000000000 -0500
--- emacs/lisp/shell.el	2008-02-28 16:34:30.000000000 -0500
***************
*** 191,197 ****
      shell-dynamic-complete-environment-variable
      shell-dynamic-complete-command
      shell-replace-by-expanded-directory
!     comint-dynamic-complete-filename)
    "List of functions called to perform completion.
  This variable is used to initialize `comint-dynamic-complete-functions' in the
  shell buffer.
--- 191,197 ----
      shell-dynamic-complete-environment-variable
      shell-dynamic-complete-command
      shell-replace-by-expanded-directory
!     comint-dynamic-complete-as-filename)
    "List of functions called to perform completion.
  This variable is used to initialize `comint-dynamic-complete-functions' in the
  shell buffer.





  reply	other threads:[~2008-02-28 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 17:11 don't require path hints for *shell* jidanni
2008-02-28 21:41 ` Chong Yidong [this message]
2008-04-03  5:15 ` Chong Yidong
2008-06-04 15:16   ` bug#361: " Stephen Berman
2008-07-23 17:35     ` bug#361: marked as done (don't require path hints for *shell*) 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

  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=87hcfsvjvz.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=bug-gnu-emacs@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).