all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: completion-ignored-extensions: match full file names
Date: Thu, 13 Jan 2011 21:00:57 -0500	[thread overview]
Message-ID: <2E854FFB-5FAF-4778-9296-F3E2BBF1E577@gmail.com> (raw)
In-Reply-To: <E1PdYok-0002X5-Pp@fencepost.gnu.org>

On Jan 13, 2011, at 8:51 PM, Eli Zaretskii wrote:
>  But I think we could make a change whereby if an element of
> completion-ignored-extensions begins with a slash, that means match at
> the beginning.  Then we could have "/.git/" as an element, and that
> would ignore only the standard ".git" subdirectories, not any
> directory that happens to end in ".git".

Yes.  I originally thought of "^.git" to mirror regexps, but not to implement regexps for the reason you state.

I like your idea better, given that it really isn't a regexp.

The only (minor) issue I see is the name of the customization variable - at that point, the string no longer represents an extension of the file name.  Perhaps we'd argue that it's an extension (suffix) of the whole path name.

We might want to go through the default set of extension and update it.  "/.bzr/", for instance, and the other VCS directories. 

BTW, this functionality as well as the Emacs 23 completion mechanism are very well conceived and quite useful!




  reply	other threads:[~2011-01-14  2:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  0:54 completion-ignored-extensions: match full file names David Reitter
2011-01-14  1:51 ` Eli Zaretskii
2011-01-14  2:00   ` David Reitter [this message]
2011-01-14  2:50     ` Eli Zaretskii
2011-01-14 15:26   ` Stefan Monnier
2011-01-16  0:13     ` Eli Zaretskii
2011-01-16  4:40       ` Stefan Monnier
2011-01-14  2:53 ` Stefan Monnier

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=2E854FFB-5FAF-4778-9296-F3E2BBF1E577@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.