From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Clint Adams <schizo@debian.org>
Cc: zsh-workers@sunsite.dk,
Michael Ekstrand <mekstran@scl.ameslab.gov>,
431437-forwarded@bugs.debian.org
Subject: Re: Bug#431437: zsh: 'svn {ci, commit}' completion includes uncontrolled/unmodified files
Date: Mon, 2 Jul 2007 18:38:05 +0300 [thread overview]
Message-ID: <200707021838.09695.ismail@pardus.org.tr> (raw)
In-Reply-To: <20070702153528.GA13937@scowler.net>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Monday 02 July 2007 18:35:28 Clint Adams 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?
As an SVN user I agree with the original reporter.
Regards,
ismail
--
Perfect is the enemy of good
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2007-07-02 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070702151952.GA29891@debye.scl.ameslab.gov>
2007-07-02 15:35 ` Clint Adams
2007-07-02 15:38 ` Ismail Dönmez [this message]
2007-07-02 18:55 ` Wayne Davison
2007-07-03 10:25 ` Peter Stephenson
2007-07-03 12:07 ` Jörg Sommer
2007-07-03 15:28 ` Vincent Lefevre
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=200707021838.09695.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=431437-forwarded@bugs.debian.org \
--cc=mekstran@scl.ameslab.gov \
--cc=schizo@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).