This topic likely will not affect users unless they are doing multi-line edit scripting or using the Explode feature.
Not all line breaks are equal. 2 different characters get used for line endings:
- Line feed. ASCII character #10. The designator for Explode, regular expressions, etc., is
\n. - Carriage return. ASCII character #13. The designator for Explode, regular expressions, etc., is
\r.
To muddy the waters, different OSs have used different line end encodings:
- Classic Mac OS: carriage return (\r).
- Unix, including macOS: (\n). (So, some longstanding Mac apps may still use \r as originally in Classic Mac OS.
- Windows uses a 2 character method: carriage return + line feed (\r\n).
Text generated in Tinderbox (except perhaps very early versions running pre-macOS) uses the Unix/macOS style line offered style of line end, \n.
When including a line end as part of an Explode delimiter, \r and r generally have the same effect so using \n as a 'default' is probably good working practice.
However, depending on the source of text brought into Tinderbox, e.g. text file dragged in for exploding, the designator used for line end may have to be adjusted.
See also—notes linking to here: