Re: CR/LF
- To: debian-user@lists.debian.org
- Subject: Re: CR/LF
- From: Kamil Jońca <kjonca@o2.pl>
- Date: Sun, 11 Dec 2022 18:07:38 +0100
- Message-id: <[🔎] 87zgbtuaw5.fsf@alfa.kjonca>
- In-reply-to: <FBxGx-9XLD-7@gated-at.bofh.it> (Jim Popovitch's message of "Sun, 11 Dec 2022 17:50:01 +0100")
- References: <FBjWV-9PfR-3@gated-at.bofh.it> <FBkpX-9Pp5-3@gated-at.bofh.it> <FBkSZ-9POQ-11@gated-at.bofh.it> <FBl2F-9PY3-7@gated-at.bofh.it> <FBm8p-9QzE-5@gated-at.bofh.it> <FBvbH-9Wnq-5@gated-at.bofh.it> <FBxGx-9XLD-7@gated-at.bofh.it>
Jim Popovitch <jim@k4vqc.com> writes:
> Ahh, sorry for using a descriptive acronym that I have used for decades
> to define an end-of-line. Whether it's in-fact a CR/LF, or just a LF,
> doesn't really change the original question about the addition of a end-
For me - changes. I was confused why linux machine can generate cr/lf
line endings, and only later I did understand you mean "line ending" in
general, and problem lies somewhere else.
Moreover line endings are important sometimes.
For example I have problems with thunderbird and it seems that (one of)
causes is cr/lf in artticle body ... instead of just lf.
(https://bugzilla.mozilla.org/show_bug.cgi?id=1788102)
KJ
--
http://wolnelektury.pl/wesprzyj/teraz/
Reply to: