zsh-workers
 help / color / mirror / code / Atom feed
From: Tanaka Akira <akr@m17n.org>
To: zsh-workers@sunsite.dk
Subject: Re: cvs completion does not support partial path completion
Date: 01 May 2001 18:39:11 +0900	[thread overview]
Message-ID: <hvoy9shpfwg.fsf@flux.etl.go.jp> (raw)
In-Reply-To: <1010430165626.ZM4866@candle.brasslantern.com> (Bart Schaefer's message of "Mon, 30 Apr 2001 16:56:26 +0000")

In article <1010430165626.ZM4866@candle.brasslantern.com>,
  "Bart Schaefer" <schaefer@candle.brasslantern.com> writes:

> Hmm.  There actually are calls to _files and _path_files sprinkled about
> though the _cvs function family.  I suspect at least some subset of the
> commands actually does complete partial paths.  On the other hand, there
> are some cvs subcommands for which files should not be completed.
> 
> That makes it more difficult to decide where to put a call to _files.

The functions which have troubles with partial path completion are
functions which use CVS/Entries: _cvs_files, _cvs_files_modified,
_cvs_files_removed and _cvs_files_unmaintained.  So fallback call to
_files should be placed at end of them.  However _cvs_files_removed is
more problematic since it completes non-existing (but listed in
CVS/Entries) files, though.
-- 
Tanaka Akira


  reply	other threads:[~2001-05-01  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 14:05 Andrej Borsenkow
2001-04-27 12:20 ` Sven Wischnowsky
2001-04-27 13:08   ` Andrej Borsenkow
2001-04-27 13:22     ` Sven Wischnowsky
2001-04-27 17:54   ` Bart Schaefer
2001-04-30  8:17     ` Sven Wischnowsky
2001-04-30 16:56       ` Bart Schaefer
2001-05-01  9:39         ` Tanaka Akira [this message]
2001-05-04  5:16           ` PATCH: " Bart Schaefer
2001-05-04 16:26             ` Bart Schaefer
2001-05-07  7:58               ` Sven Wischnowsky
2001-05-07 14:52                 ` Bart Schaefer
2001-05-08  8:45                   ` Sven Wischnowsky
2001-05-04 16:39             ` Bart Schaefer

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=hvoy9shpfwg.fsf@flux.etl.go.jp \
    --to=akr@m17n.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).