CRLF line endings
To facilitate review of the PEP 405 reference implementation, I want to update my sandbox repository on hg.python.org with the relevant changes, so I can create a patch for Rietveld. I've added some files with CRLF line endings: Lib/venv/scripts/nt/Activate.ps1 Lib/venv/scripts/nt/Dectivate.ps1 Lib/venv/scripts/nt/activate.bat Although these are text files, the CRLF line endings are needed because otherwise, the files won't be presented correctly on Windows, e.g. in Notepad. I'd like to update the .hgeol file to add these entries, as otherwise the commit hook rejects them. Can anyone please let me know if they object? Otherwise I'll go ahead and add them to .hgeol in the next hour or so. Regards, Vinay Sajip
On Thu, May 3, 2012 at 10:50 PM, Vinay Sajip
Although these are text files, the CRLF line endings are needed because otherwise, the files won't be presented correctly on Windows, e.g. in Notepad.
Not all Windows editors choke on \n line endings; when I'm on Windows and run into one, I open it in Wordpad (or, if I have one, a dedicated programming editor like SciTE or the Open Watcom editor). AFAIK only Notepad (of standard Windows utilities) has trouble. Not sure if that makes a difference or not. Chris Angelico
Chris Angelico
Not all Windows editors choke on \n line endings; when I'm on Windows and run into one, I open it in Wordpad (or, if I have one, a dedicated programming editor like SciTE or the Open Watcom editor). AFAIK only Notepad (of standard Windows utilities) has trouble.
Not sure if that makes a difference or not.
It's only really an issue for new / inexperienced users, I agree. Since these files are installed only on Windows systems, there's no reason for them not to have the native line endings. Regards, Vinay Sajip
On Fri, May 4, 2012 at 1:28 AM, Vinay Sajip
It's only really an issue for new / inexperienced users, I agree. Since these files are installed only on Windows systems, there's no reason for them not to have the native line endings.
Then sure, doesn't make a lot of difference that it's only Notepad. Somebody needs to rewrite that ancient editor and give Windows a better default... ChrisA
Zitat von Chris Angelico
On Thu, May 3, 2012 at 10:50 PM, Vinay Sajip
wrote: Although these are text files, the CRLF line endings are needed because otherwise, the files won't be presented correctly on Windows, e.g. in Notepad.
Not all Windows editors choke on \n line endings; when I'm on Windows and run into one, I open it in Wordpad (or, if I have one, a dedicated programming editor like SciTE or the Open Watcom editor). AFAIK only Notepad (of standard Windows utilities) has trouble.
Not sure if that makes a difference or not.
I think that .bat files strictly *have* to have CRLF line endings. Not sure about PowerShell, though. In any case, having CRLF for these files sounds good to me. Regards, Martin
On Fri, May 4, 2012 at 7:00 AM,
In any case, having CRLF for these files sounds good to me.
Right. While Windows has been getting much better at coping with LF only line endings over the years, being able to explicitly flag files for CRLF endings is the entire reason we held out for the EOL extension before making the switch to Mercurial. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (5)
-
Chris Angelico
-
Glenn Linderman
-
martin@v.loewis.de
-
Nick Coghlan
-
Vinay Sajip