zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@sunsite.dk, 299950-forwarded@bugs.debian.org
Subject: Re: Bug#299950: zsh: Better completion for "svn revert"
Date: Thu, 31 Mar 2005 03:02:41 +0200	[thread overview]
Message-ID: <20050331010240.GU19392@ay.vinc17.org> (raw)
In-Reply-To: <20050327003652.GA20238@scowler.net>

On 2005-03-26 19:36:52 -0500, Clint Adams wrote:
> +(( $+functions[_svn_adm_files] )) ||
> +_svn_adm_files() {
> +  compadd ${${(M)${(f)"$(svn status)"}:#(#s)[ADM]*}##[ADM] ##}

Doing a recursive "svn status" is not a good idea, as it may take
a very long time. I suggest doing a "svn -N status" and completing
also on any directory containing a .svn subdirectory.

Moreover, the [ADM] pattern is incorrect. It should be ([ADM]|?M).
This would give:

  compadd ${${(M)${(f)"$(svn -N status)"}:#(#s)([ADM]|?M)*}##([ADM]|?M) ##}

+ the code to complete on directories (only those that contain a
.svn subdirectory, in fact).

When one tries to complete on

  svn revert path/to/dir/

zsh should do a "svn -N status path/to/dir", which returns lines like

A     path/to/dir/added_file
D     path/to/dir/deleted_file
M     path/to/dir/modified_file
 M    path/to/dir/modifprop_file

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA


  reply	other threads:[~2005-03-31  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050317142638.GA23797@dixsept.loria.fr>
     [not found] ` <20050325142839.GA32333@scowler.net>
     [not found]   ` <20050325161734.GT19392@ay.vinc17.org>
2005-03-27  0:36     ` Clint Adams
2005-03-31  1:02       ` Vincent Lefevre [this message]
2005-03-31 14:17       ` Oliver Kiddle

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=20050331010240.GU19392@ay.vinc17.org \
    --to=vincent@vinc17.org \
    --cc=299950-forwarded@bugs.debian.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).