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

Re: Subversion 1.10 RC1?

From: Branko ─îibej <brane_at_apache.org>
Date: Tue, 5 Dec 2017 22:45:01 +0100

On 05.12.2017 22:12, Evgeny Kotkov wrote:
> Stefan Fuhrmann <stefan2_at_apache.org> writes:
>
>> There seems to be little that could be done here (suggestions welcome).
>> The problem is that the asterisk is being expanded by the shell itself.
>> I made SVN print its command line parameters and this is the result:
>>
>> $ ./subversion/svn/svn ls svn://localhost/kde --search M*
>> 0: ./subversion/svn/svn
>> 1: ls
>> 2: svn://localhost/kde
>> 3: --search
>> 4: Makefile
>> 5: Makefile.in
>>
>> That can be prevented by adding quotation marks:
>>
>> $ ./subversion/svn/svn ls svn://localhost/kde --search "M*"
>> 0: ./subversion/svn/svn
>> 1: ls
>> 2: svn://localhost/kde
>> 3: --search
>> 4: M*
> Unfortunately, on Windows both `--search M*` and (quoted) `--search "M*"`
> would expand the asterisk. While this is not the default shell behavior,
> currently it's enabled for svn and a couple of other binaries by linking
> to setargv.obj.

We do that for the command-line client and in a few other places, too.
It was the easy way out for Windows.

It's unfortunate, really ... ideally, we'd remove setargv.obj and do the
wildcard expansion ourselves, but someone has to do the work; it's very
Windows-specific and there are probably nasty edge cases around argument
quoting.

-- Brane
Received on 2017-12-05 22:45:06 CET

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