Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

lineendings #18

Closed
camillobruni opened this Issue Mar 9, 2012 · 5 comments

Comments

Projects
None yet
3 participants
Contributor

camillobruni commented Mar 9, 2012

I think we have to take custom line endings into account.
might be that urgent for now, but most people will prefer using the system specific line-endings.

Owner

dalehenrich commented Mar 9, 2012

good point...

----- Original Message -----
| From: "Camillo Bruni" reply@reply.github.com
| To: "Dale Henrichs" dhenrich@vmware.com
| Sent: Friday, March 9, 2012 11:11:32 AM
| Subject: [filetree] lineendings (#18)
|
| I think we have to take custom line endings into account.
| might be that urgent for now, but most people will prefer using the
| system specific line-endings.
|
| ---
| Reply to this email directly or view it on GitHub:
| #18
|

cdlm commented Apr 6, 2012

Git can be configured to convert them automatically, and all reasonably good text editors detect them correctly.

Owner

dalehenrich commented Apr 6, 2012

In FileTree I'm consistently writing everything out using Character lf. Source is converted to the line-ending expected by the implementation on read ...

cdlm commented Apr 6, 2012

utf-8 + unix convention has all my approval :)

Owner

dalehenrich commented Jun 25, 2012

Character lf is the 'standard' for Cypress ... platforms can convert to native line endings on load from disk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment