Re: Visual Studio and the svn:eol-style property

Giulio Troccoli wrote:
> Unfortunately I don't think my company would be keen to "force"
> developers to use a 3rd party editor. And also I would like to find a
> more robust solution, if there is one, which doesn't rely on developers'
> choices.
>
I understand. However, they are already "forcing" use of VisualStudio on
Windows, are they not? Its fairly common for an organization to have a
standard set of VisualStudio Addins that are part of every install.

You may well find another solution that will work for you, and if so,
wonderful. However, the root of the problem here seems to be the crappy
editor that your Windows users are using. So why not attack the root of
the problem? This *won't* be the only issue that the VS editor is
causing either. I'll venture a guess that these cross-edited files are
also having trouble with the tabs that VisualStudio loves to insert
everywhere. This renders the code nigh-unreadable in another editor with
different tab stops. Perhaps your post-processing script will end up
having to fix those too. In fact, there's probably a way to make a VS
addin that does both whenever a file is saved.

-- 
T.E.D.   Work     -  mailto:dennison@ssd.fsi.com
         Home     -  mailto:dennison@telepath.com (Yahoo: Ted_Dennison)
         Homepage -  http://www.telepath.com/~dennison/Ted/TED.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org