Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: _cvs and .cvsignore
- X-seq: zsh-workers 16746
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Clint Adams <clint@xxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: Re: _cvs and .cvsignore
- Date: Fri, 1 Mar 2002 03:19:34 +0000
- In-reply-to: <20020228234911.GA10402@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020228234911.GA10402@xxxxxxxx>
On Feb 28, 6:49pm, Clint Adams wrote:
} Subject: _cvs and .cvsignore
}
} What is the code in _cvs_files_unmaintained supposed to do with regard
} to the contents of .cvsignore? If _cvs_nonentried_files is ignoring
} those files, but _cvs_strict_nonentried_files is adding them, why ignore
} them in the first place? What am I missing?
That the || operator is short-circuiting? _cvs_files_unmaintained will
first attempt to complete files that are neither in CVS nor in .cvsignore
(_cvs_nonentried_files); if that doesn't find anything (||) it attempts
to complete existing directories; and if there are none of those, then
it completes files that aren't in CVS whether they are ignored or not.
I have the feeling I must be misinterpreting your question. Perhaps you
mean "why bother completing them when cvs won't do anything with them?"
I think the answer to *that* is "principle of least surprise" -- so that
we don't get lots of "why can't I complete this file? It's right there
in the directory" questions mailed to zsh-users, among other things.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author