all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ed Avis <eda@waniasset.com>
To: 'Eli Zaretskii' <eliz@gnu.org>
Cc: "19911@debbugs.gnu.org" <19911@debbugs.gnu.org>
Subject: bug#19911: 24.4; shell-mode command completion - smarter handling of backup files
Date: Fri, 20 Feb 2015 11:47:55 +0000	[thread overview]
Message-ID: <7E039918541B4C4183BFDB8F015C743032DD9184@WCL-EXCH02.wcl.local> (raw)
In-Reply-To: <83bnkolsfk.fsf@gnu.org>

>Does customizing shell-completion-fignore to include "~" do what you
>want?

It appears not to; I now have

'(shell-completion-fignore (quote ("~"))

in my custom-set-variables, but the behaviour on typing ./script TAB TAB is still the same.

But really this bug is about the different treatment of filename completion and command completion.
Whatever the shell-completion-fignore setting, it should apply the same way to both.
It appears that filename completion has special handling for backup files, even if shell-completion-fignore
is at its default empty values.  The backup files are not completely ignored for tab-completion, but
they do not provoke a completions buffer either.  They just require you to hit TAB a second time.
That is a sensible compromise as a default behaviour - it just needs to be applied consistently to
command completion too.

-- 
Ed Avis <eda@waniasset.com>

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________





      reply	other threads:[~2015-02-20 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 11:35 bug#19911: 24.4; shell-mode command completion - smarter handling of backup files Ed Avis
2015-02-20 11:43 ` Eli Zaretskii
2015-02-20 11:47   ` Ed Avis [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

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

  git send-email \
    --in-reply-to=7E039918541B4C4183BFDB8F015C743032DD9184@WCL-EXCH02.wcl.local \
    --to=eda@waniasset.com \
    --cc=19911@debbugs.gnu.org \
    --cc=eliz@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.