Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#431437: zsh: 'svn {ci, commit}' completion includes uncontrolled/unmodified files
- X-seq: zsh-workers 23647
- From: Jörg Sommer <joerg@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Bug#431437: zsh: 'svn {ci, commit}' completion includes uncontrolled/unmodified files
- Date: Tue, 3 Jul 2007 12:07:05 +0000 (UTC)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20070702151952.GA29891@xxxxxxxxxxxxxxxxxxxxx> <20070702153528.GA13937@xxxxxxxxxxx>
- Sender: news <news@xxxxxxxxxxxx>
Hi,
Clint Adams <schizo@xxxxxxxxxx> wrote:
> On Mon, Jul 02, 2007 at 10:19:52AM -0500, Michael Ekstrand wrote:
>> The completion routines for arguments to the subversion commit command
>> allow completion of uncontrolled and unmodified files. These files do
>> not show up in the list of available completions when Tab is hit twice,
>> but they are completed when typed.
>>
>> To reproduce, place a new file in a Subversion working directory and
>> attempt to tab-complete for svn ci without first adding it to the
>> repository.
>>
>> With the exception of the argument to the -F option (which will usually
>> be uncontrolled), I think that the commit completion should be
>> restricted to modified files under version control.
>
> Any svn users have any thoughts on this one?
I can confirm this behaviour and I like it. The svn completion maintains
an internal cache that really often get outdated. Than the completion of
these files is very handy.
Bye, Jörg.
--
MCSE = Minesweeper Consultant & Solitaire Expert
Messages sorted by:
Reverse Date,
Date,
Thread,
Author