I'm starting to hit issues where the difference in how Windows and Linux write files in DM is causing parsing to get weird in certain places (Prometheus in this case, but anything following the OpenMetrics standard would fail to parse \r\n as a valid line termination), it would be nice if we had some say how line terminations were written to files.
Obviously we probably can't get this to work with <<, but text2file() could easily have an optional argument to determine how line terminations were done during the write.
This behavior is built into the operating system's file IO stuff so it might take some fiddling to make it work, but it would allow us to get rid of a discrepancy in what ends up inside of files when writing on different operating systems.
Additionally, DM doesn't even recognize "\r\n" as a valid text macro, only "\n".
(This wouldn't be an issue if you'd just give us real file handling stuff like we've been asking for for 20 years.)
ID:2920898
 Apr 13 2024, 5:41 pm
|
|||||||
| |||||||
|
Apr 29 2024, 11:50 am
|
|
Zewaka
 |
if you use Git this is not a problem
|
You have to actually push the files through git or run a tool on them first, which doesn't really work for files generated by a running server.
| |
Some old trick from ss13
/var/log_end = world.system_type == UNIX ? ascii2text(13) : "" But now some servers use own library for text output, in part because byonds << is slow on windows or something like this | |
