Conversation

Notices

1. Embed this notice
   Sergey on FunctionalScript (functionalscript@techhub.social)'s status on Tuesday, 02-Apr-2024 06:27:54 JST Sergey on FunctionalScript

   in reply to

   • Axel Rauschmayer

   @rauschma I'm so tired of the platform-dependent EOL that I decided that all the files that I use are only `\n,` everywhere, on any platform (Git, text editors, my applications). My applications can read `\r\n` but they write only with `\n`.

   The biggest problem for me is that files with `\r\n` have different hashes/checksums.

   • Embed this notice
     Axel Rauschmayer (rauschma@fosstodon.org)'s status on Tuesday, 02-Apr-2024 06:27:55 JST Axel Rauschmayer

     EOL—'\n' vs. '\r\n':
     – With files and strings read from files, you can detect the EOL and use it when writing files.
     – On Node.js, you can use os.EOL.

     But what about multi-line strings in error messages that must work in browsers and Node.js? Always '\n'?