[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: --non-interactive still invokes editor?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-07-05 22:38:36 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> On May 2, 2005, at 4:06 AM, Ulrich Eckhardt wrote:
> > Cheers!
> >
> > I stumbled over the fact that an invocation of 'svn mkdir --non-
> > interactive
> > $URL' in a script still fires up the editor. Yes, one could
> > consider it a
> > programming mistake to not supply any logentry at all, but I would
> > have
> > expected svn to then fail unless --force-log is supplied.
> >
> > The Book only talks about credentials/authentication, maybe that
> > should be
> > clarified that it really only applies to those.
> You're right, Uli. It seems that --non-interactive currently means
> "don't prompt for authentication" and nothing else. It has no effect
> on *any* subcommand's ability to launch $EDITOR. (That is, $EDITOR
> is always launched, no matter what.)
> Developers: should we document --non-interactive more precisely? Or
> should we fail to launch $EDITOR in the presence of this option?

I know this conversation has been had before, and that some folks
(perhaps/probably even myself) were thinking that --non-interactive
doesn't need to affect the use of $EDITOR because one can always do
--editor-cmd=/bin/false or something. Whatever I used to think, I've
since come around to thinking --non-interactive should be a one-stop
shop for making an invocation of the command-line client completely
scriptable, free of auth, log message, or any other kinds of prompts.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 5 23:09:58 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.