From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: CVS directories in completion-ignored-extensions
Date: 01 Jan 2004 07:49:41 +0200 [thread overview]
Message-ID: <uwu8c5ibu.fsf@elta.co.il> (raw)
In-Reply-To: <20031231013407.GC19084@fencepost> (message from Miles Bader on Tue, 30 Dec 2003 20:34:07 -0500)
> Date: Tue, 30 Dec 2003 20:34:07 -0500
> From: Miles Bader <miles@gnu.org>
>
> So sure, without a better mechanism, there will be some annoying side-effects
> in completion, but let's program for the common case, and _keep_ CVS in
> completion-ignored-extensions.
How about if we change "CVS/" to "/CVS/" and modify the code to match
the whole name if the member of the list begins with a slash?
The only problem with that approach, AFAICT, is when a user wants to
ignore files under the root directory. If that sounds like a serious
problem, we could have something like "//foo/" to DTRT in such cases.
What do you-all think?
next prev parent reply other threads:[~2004-01-01 5:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 8:01 CVS directories in completion-ignored-extensions Eli Zaretskii
2003-12-30 23:44 ` Eric Hanchrow
2003-12-31 1:08 ` Luc Teirlinck
2003-12-31 1:34 ` Miles Bader
2003-12-31 5:51 ` Eli Zaretskii
2004-01-01 5:49 ` Eli Zaretskii [this message]
2004-01-01 21:10 ` Richard Stallman
2004-01-02 0:31 ` Miles Bader
2004-01-02 1:06 ` Kim F. Storm
2004-01-02 9:21 ` Eli Zaretskii
2004-01-03 11:52 ` Eli Zaretskii
2004-01-04 18:53 ` Richard Stallman
2004-01-04 23:17 ` Stefan Monnier
2004-01-04 23:59 ` Miles Bader
2004-01-05 17:56 ` Richard Stallman
2004-01-06 0:08 ` Miles Bader
2004-01-06 0:52 ` Kenichi Handa
2004-01-06 1:54 ` Miles Bader
2004-01-06 3:00 ` Kenichi Handa
2005-01-19 11:34 ` Kim F. Storm
2005-01-19 14:57 ` Stefan Monnier
2005-01-19 15:52 ` Kim F. Storm
2005-01-19 16:07 ` Stefan Monnier
2004-01-06 5:55 ` Eli Zaretskii
2004-01-06 6:26 ` Miles Bader
2004-01-07 2:40 ` Richard Stallman
2004-01-01 21:27 ` Kim F. Storm
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=uwu8c5ibu.fsf@elta.co.il \
--to=eliz@elta.co.il \
/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).