John Kerl 3e366a2fde Honor --ors CRLF for CSV output (#1810) ... The full-CSV record writer validated ORS as newline or carriage-return/newline, but never propagated the choice to the forked Go CSV writer's UseCRLF field, so `--ors '\r\n'` (or `--ors crlf`) silently produced LF line endings. Set UseCRLF from the writer options so CRLF output is honored. Default behavior (LF) is unchanged, and other ORS values are still rejected. The CSV-lite and TSV writers already honored CRLF ORS. Also: fix a copy-paste "for CSV" in the TSV writer's ORS-validation message, add unit tests asserting byte-exact line endings (the regtest harness normalizes CR/LF, so this can't be asserted in test/cases), add CLI-level regression cases, and update the separators documentation. This substantially addresses #1722 as well: RFC-4180-style CRLF output can now be requested on any platform. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-05 20:03:46 -04:00
..
Makefile
manpage.txt	Honor --ors CRLF for CSV output (#1810)	2026-07-05 20:03:46 -04:00
mkman.rb
mlr.1	Honor --ors CRLF for CSV output (#1810)	2026-07-05 20:03:46 -04:00