zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Clint Adams <clint@zsh.org>, zsh-workers@sunsite.dk
Subject: Re: _cvs and .cvsignore
Date: Fri, 1 Mar 2002 03:19:34 +0000	[thread overview]
Message-ID: <1020301031934.ZM17708@candle.brasslantern.com> (raw)
In-Reply-To: <20020228234911.GA10402@dman.com>

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   


  reply	other threads:[~2002-03-01  3:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 23:49 Clint Adams
2002-03-01  3:19 ` Bart Schaefer [this message]
2002-03-01  3:32   ` Clint Adams

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=1020301031934.ZM17708@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=clint@zsh.org \
    --cc=zsh-workers@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).