Daniel Shahaf wrote:
What version did you upgrade to 1.6.15 from?
From a 1.6.4 installation.
Are there any svn-commit.tmp, svn-commit.2.tmp preexisting?
No, there are none. I double checked and deleted all *.tmp in the
concerned directories.
What happens if you use the following script
Daniel Shahaf wrote:
BTW, with gvim you may have to use 'gvim -f' as your editor.
Besides totally not being the point: That is simply wrong. GVim.exe does
not require that parameter. And hasn't for years.
Greeting,
Andreas
Daniel Shahaf wrote:
BTW, with gvim you may have to use 'gvim -f' as your editor.
Besides totally not being the point: That is simply wrong. GVim.exe does
not require that parameter. And hasn't for years.
Greeting,
Andreas
stated what IS happening, just what you THINK is
happening. (Most of your assumptions regarding what should/shouldn't be
in cwd are wrong.)
The short answer is, svn runs 'gvim /path/to/file' and then reads
/path/to/file. The cwd isn't involved.
Feel free to follow up with more
Hello everybody,
Today I encountered an unusual behaviour with my newly updated
Subversion version (Win32, version 1.6.15):
Just as always, a simple commit, using 'svn ci', still fires up my
configured editor to edit a corresponding svn-commit.tmp file.
The problem is, that this file gets cre
