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

Re: Disabling automatic setting of svn:executable property

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 3 Jun 2011 23:01:11 -0400

On Tue, May 31, 2011 at 5:39 PM, Karl Heinz Marbaise <khmarbaise_at_gmx.de> wrote:
> Hi,
>> We just tried that.
>> One user complained that the Windows client didn't hide passwords
>>  he typed in (displayed the whole thing in plain text instead of
>> displaying *s),
> Sorry to say so, but this can't be cause the SVN client hides on console as
> well...and also on Windows...I don't know what the user really did?...May be
> he mistaken the username input with the password input?
>> and he couldn't commit because the client was
>>  unable to find "vim" although it was installed under Cygwin.
> First installed under Cygwin is not installed under windwos. These are two
> different worlds.
> Furthermore if the user has correctly set the SVN_EDITOR or EDITOR
> environment variable correctly to SVN_EDITOR=C:\...WhatEver\vim.exe this
> will work...But this has to be done first...usually on a Unix like system
> the EDITOR variable is set to default editor vi...
> This default does not exist on Windows systems....

Whether Cygwin is "Windows" is..... an interesting problem in
definitions. It's precisely the sort of problem I mentioned.

No idea why or how the passwords were appearing in CygWin. But CygWin
has "vim" available: Mine has it installed, and it works fine. I'm
really confused which "vim" he expected to use: one installed in
Windows natively, or the one in CygWin?

>>   In short, he found the Windows-native version unusable and went
>> back to the Cygwin version.
>> Any idea what might have caused those issues?
> As described above...

Sounds like your friend should be asking here himself.....
Received on 2011-06-04 05:01:45 CEST

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

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