On Mar 23, 2009, at 2:13 PM, tomc...@googlemail.com wrote:
You got a point. I do this more because I do not master the feeds issue than by conviction. On windows I used Scite as editor and I just added a config file at the root of my project (folder) and line feeds and other stuff were set (encoding). In the editor I would see these infos for every file opened. Now on the Mac, the only editor I found dealing with big quantities of files without the need of creating projects is TextMate. Unfortunately it does not show the line feed style and has a poor management for it. The only way I found is : 1. I use TextWrangler to view line feeds and encodings 2. I use the command line with a perl command to batch convert directories, which is VERY new to me, and it does not work for nested directories. This is one of the issues which make me sometimes wish to return to Windows/Scite Editor. So, if You know a better way ... ;)
I'm not sure I know answers for all the issues you mention, and I also don't deal with multiple EOL styles as much as you have, but I'll give it a shot.
SubEthaEdit has a handy sub-menu for viewing and converting EOL styles, and it's a nice little lightweight editor as well.
BBEdit is a venerated Mac editor that might have better support for line endings than TextMate — I'm not positive since I don't use either of them near as much as SubEthaEdit or Xcode.
And here are some random hints I scraped up, which might be of use. http://forums.macosxhints.com/showthread.php?t=125 http://ccrma-www.stanford.edu/~craig/utility/flip/Are these projects with Windows EOL already all in SVN, or are you adding them as you go? If it's the latter, the auto-props will save you grief in the future, but won't help with already-set properties. Still, a decent script that set prop for the file type would work.
Good luck, - Quinn
smime.p7s
Description: S/MIME cryptographic signature