Correct. So the current situation requires you to use binfile for Mac/Linux and file for Windows/Linux to get appropriate line endings. You can’t do it just one way, you have to check your OS. Notice that Linux works both ways.
(You also should encode/decode if using binfile) In ScriptTracker I use file for import since it handles everything and then let the user choose method for export (binfile would work fine for GitHub and Atom even on Windows). Now that I think about it I could even add a “native” option that would use file for Windows and binfile otherwise. Sent from my iPhone > On Mar 3, 2021, at 4:37 PM, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 3/3/21 1:51 PM, Brian Milby via use-livecode wrote: >> If you want to be the most accurate (clear for others reading code) you >> would use the LF constant instead of CR since that is how it actually >> evaluates. The only way to generate an actual CR within code is to use CRLF >> (which gets both) or use numtobyte(13). >> If you export as text, then you get what is expected on Win/Linux and get CR >> on Mac (which is wrong in my opinion). > > On the other hand, if you export text as binary you get whatever you wrote, > and automatic line endings aren't converted. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
