unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: shell-mode command completion with slashes
Date: Thu, 30 Oct 2008 21:56:55 -0400	[thread overview]
Message-ID: <barmar-D921C3.21565530102008@mara100-84.onlink.net> (raw)
In-Reply-To: mailman.2518.1225396148.25473.help-gnu-emacs@gnu.org

In article <mailman.2518.1225396148.25473.help-gnu-emacs@gnu.org>,
 Stephen Berman <stephen.berman@gmx.net> wrote:

> On Thu, 30 Oct 2008 12:57:22 -0400 Barry Margolin <barmar@alum.mit.edu> wrote:
> 
> > I'm running Emacs 22.2.50 on OS X 10.5.5, and I use shell mode 
> > extensively.  I don't have "." in my $PATH, so if I want to run a 
> > program in the current directory I need to type "./program-name".  I'd 
> > like to be able to type "./prog<TAB>" and have it complete it, but it 
> > doesn't.  I looked at the source code of shell-dynamic-complete-command, 
> > and it explicitly checks for "~" or "/" in the word being completed, and 
> > gives up.  And shell-dynamic-complete-filename gives up if it's being 
> > used for the first word of a command, it only works for arguments.
> >
> > This used to work, probably before I upgraded from 22.1 to 22.2.  Anyone 
> > know how to get the old behavior back?  Did it use 
> > comint-dynamic-complete-filename instead of 
> > shell-dynamic-complete-filename?  The former doesn't check for the 
> > location in the command, but it also doesn't care whether the file it 
> > completes to is an executable.
> 
> This was caused by this change:
> 
> 2008-04-03  Chong Yidong  <cyd@stupidchicken.com>
> 
> 	* shell.el (shell-dynamic-complete-filename): New fun.
> 	(shell-dynamic-complete-functions): Use it.
> 
> This was after the release of 22.2 but backported.  It was fixed by this
> change:
> 
> 2008-07-23  Chong Yidong  <cyd@stupidchicken.com>
> 
> 	* shell.el (shell-dynamic-complete-functions):
> 	Use comint-dynamic-complete-filename as well (bug#361).
> 
> and that is in 22.3.

So it will include all files in the completion, not just executables.  
It also seems to make shell-dynamic-complete-filename redundant, since 
it's basically the same as comint-dynamic-complete-filename except that 
it will not expand the first word of a command.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***


      parent reply	other threads:[~2008-10-31  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 16:57 shell-mode command completion with slashes Barry Margolin
2008-10-30 19:48 ` Stephen Berman
     [not found] ` <mailman.2518.1225396148.25473.help-gnu-emacs@gnu.org>
2008-10-31  1:56   ` Barry Margolin [this message]

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=barmar-D921C3.21565530102008@mara100-84.onlink.net \
    --to=barmar@alum.mit.edu \
    --cc=help-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.
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).