Symptom:
If a file has no EOL (i.e., it is one line and there is no [CR][LF]), the lister word wrap becomes inoperable and makes the sound that's heard when there's a permissions problem.
Repeatability:
Always.
Version:
8.0 (May 23, 2012).
Solution:
The lister is interpreting the file as binary, not text. Select text mode to 'fix' the problem. - M.
1 line text file without EOL exposes lister bug. - Solved
Moderators: Hacker, petermad, Stefan2, white
-
MarkFilipak
- Member
- Posts: 164
- Joined: 2008-09-28, 01:00 UTC
- Location: Mansfield, Ohio
1 line text file without EOL exposes lister bug. - Solved
Last edited by MarkFilipak on 2012-07-27, 17:38 UTC, edited 1 time in total.
Hi Christian! Delighted customer since 1999. License #37627
Hi, check if the Lister treats the file as a text or binary. Looks like that if a file doesn't end with a newline, TC thinks it's a binary -> wrap mode is permanently enabled.
BTW, there is no such symbol/mark as EOL. It's just a notification that you reached the end of file. And CRLF at the end of a text file is mostly a *nix habit.
BTW, there is no such symbol/mark as EOL. It's just a notification that you reached the end of file. And CRLF at the end of a text file is mostly a *nix habit.
Windows 10 Pro x64, Windows 11 Pro x64
-
MarkFilipak
- Member
- Posts: 164
- Joined: 2008-09-28, 01:00 UTC
- Location: Mansfield, Ohio
Brilliant! Indeed, it was being interpreted as binary.umbra wrote:Hi, check if the Lister treats the file as a text or binary. Looks like that if a file doesn't end with a newline, TC thinks it's a binary -> wrap mode is permanently enabled.
(Hollering...) Christian! When in doubt, default to text, please.
Not so brilliant. There's no such thing as CRLF. It's [CR][LF]. Two bytes. Further, [CR][LF] at the end of a text file is NOT a *nix thing. It's an IBM thing. Unix uses [FF], one byte, to terminate a line.umbra wrote:BTW, there is no such symbol/mark as EOL. It's just a notification that you reached the end of file. And CRLF at the end of a text file is mostly a *nix habit.
Thanks for your help! - Mark.
Hi Christian! Delighted customer since 1999. License #37627
Ouch, that hurt.Not so brilliant.
Irrelevant. It's only a mater of taste if and how you separate those bytes - their meaning is still obvious.There's no such thing as CRLF. It's [CR][LF]. Two bytes.
So many types of line-endings ... Just today I had to work with three of them. No wonder I wrote the wrong one. Again.Further, [CR][LF] at the end of a text file is NOT a *nix thing. It's an IBM thing. Unix uses [FF], one byte, to terminate a line.
And I guess you meant LF, not FF. 
Windows 10 Pro x64, Windows 11 Pro x64
