This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7: svn/bash can't find $EDITOR after 1.7 upgrade
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 30 Apr 2010 22:41:19 +0200
- Subject: Re: 1.7: svn/bash can't find $EDITOR after 1.7 upgrade
- References: <27D7F4C907BCB14FAF95CC4E25AB1FE601E4BF@ex2.AdBriteInc.local>
- Reply-to: cygwin at cygwin dot com
On Apr 30 13:29, Bill Ross wrote:
> Svn was working ok just before I upgraded to 1.7, e.g. 'svn status' showed paths in unix form (forward slashes), and on commit vi opened ok.
> Now svn status shows paths with backslashes:
> MÂÂÂÂÂÂ test\xls\qa1\ZonePos.xls
> And on commit:
> -bash-3.2$ svn commit file.txt
> The system cannot find the path specified.
> svn: Commit failed (details follow):
> svn: system('/usr/bin/vi svn-commit.tmp') returned 1
> This is after 'export EDITOR=/usr/bin/vi' (it was vim before, same error but no vim per se w/ 1.7).
> Svn used to have problems like this with the first version of cygwin I installed, but after an update it all started working. 1.7 seems to have reverted that improvement.
> -bash-3.2$ svn --version
> svn, version 1.6.2 (r37639)
Here's your problem.
Cygwin Configuration Diagnostics
Current System Time: Fri Apr 30 12:19:26 2010
Windows XP Professional Ver 5.1 Build 2600 Service Pack 3
Path: C:\Program Files\CollabNet Subversion Client
and here. You're using a native Win32 version of subversion instead
of the Cygwin version, which, btw., you have installed and is much
Also keep in mind that /usr/bin/vi as well as /usr/bin/vim are Cygwin
*symlinks*, pointing to /usr/bin/vim-nox.exe. I doubt that the native
subversion in C:\Program Files\CollabNet Subversion Client actually
understands Cygwin symlinks.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple