You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mentioned this on IRC but when saving a csv file on linux, I get CRLF endings instead of LF which messes up git diff etc.
$ vd --version
saul.pw/VisiData v2.5
To reproduce open a csv, edit a column and save the file with Ctrl+s . cat -A toto.csv shows vstruct,,,,,$ before edition, after it shows vstruct,,,,,^M$ (notice the ^M). Is it possible to change the behavior to avoid this one way or another ?
NB: for now I run dos2unix after saving the csv.
The text was updated successfully, but these errors were encountered:
Hi @teto, VisiData uses the csv.writer from Python stdlib, and exposes the various dialect options. In this case, Dialect.lineterminator is set by default to '\r\n', and you can set it to what you want with --csv-lineterminator=$'\n'.
Hi,
I mentioned this on IRC but when saving a csv file on linux, I get CRLF endings instead of LF which messes up git diff etc.
To reproduce open a csv, edit a column and save the file with Ctrl+s .
cat -A toto.csv
showsvstruct,,,,,$
before edition, after it showsvstruct,,,,,^M$
(notice the ^M). Is it possible to change the behavior to avoid this one way or another ?NB: for now I run
dos2unix
after saving the csv.The text was updated successfully, but these errors were encountered: