@anon73440385
Well, I generate a .csv file from calc. The csv file ends with , and the interferes with using cygwin tools. Doesn’t happen often, but it does happen. For example, regular expressions depend on the EOL are not treated properly without insertion of a control character. For example, "sed -e ‘s/something$/change/’ " will fail because “sed” expects the EOL to by and the EOL is .
This issue is fixed when I use cygwin:dos2unix filenames. But I am looking for an internal solution within LO if it is available.
So one answer to your question is that the line endings affect all regular expressions which depend on detecting an EOL.
Another issue is that in some Unix routines, the is treated as a binary character. This translates into the entire file being considered as a binary file and most ASCII functions will abandon execution when the first is seen.