A couple of weeks ago a user wrote in with an unusual problem. Although he was checking out his repositories from his Subversion server, Komodo wasn't recognising them as version-controlled files. The SCC context menu was showing all entries as...
A couple of weeks ago a user wrote in with an unusual problem. Although he was checking out his repositories from his Subversion server, Komodo wasn't recognising them as version-controlled files. The SCC context menu was showing all entries as disabled, and nothing he could do would change the situation. To make things a little bit stranger, I couldn't reproduce the problem on my end.
After some time writing back and forth he wrote back to tell me he had found the problem, and he asked me to post the solution to the web so others having the same problem could benefit from it. Of course, I am only too happy to do so.
When he installed Subversion, he selected an option called SVN_ASP_DOT_NET_HACK. The option sets an environment variable that causes the installed Subversion client to create Subversion private directories named _svn instead of the usual .svn (underscore instead of dot). Problem is, Komodo relies specifically on the presence of a file named with a dot, and when it does see that directory, it assumes no files in the current directory are version-controlled.
The fix is fairly simple -- remove the SVN_ASP_DOT_NECK_HACK environment variable and possibly reboot, depending on the version of Windows.
Thanks, Martin!
