GNU nano - Bugs: bug #44620, representation of a Mac file with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #44620: representation of a Mac file with --noconvert is not very useful
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Tue 24 Mar 2015 03:48:14 PM UTC | ||
Severity: | 2 - Minor | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Mon 02 Dec 2019 04:21:06 PM UTC, comment #3: |
Benno Schulenberg <bens> |
Mon 27 Jun 2016 07:34:39 PM UTC, comment #2: I've found this: http://www.unicode.org/reports/tr14/tr14-32.html#BreakingRules. See LB5: "Treat CR followed by LF, as well as CR, LF, and NL as hard line breaks."
|
Benno Schulenberg <bens> |
Wed 29 Apr 2015 08:17:52 AM UTC, comment #1: I guess the main reason why --noconvert exists is to override nano in the rare case it thinks a file is in Mac-format when it really isn't. |
Benno Schulenberg <bens> |
Tue 24 Mar 2015 03:48:14 PM UTC, original submission:
When opening a file that contains no other line endings than Mac line endings (bare 0x0d instead of 0x0a), the representation on the screen is as a single interminably long line. This does not seem very useful to me. Is this the intended behaviour? I would have expected the separate lines to be shown as separate lines.
|
Benno Schulenberg <bens> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-12-02 | bens | Severity | 3 - Normal | 2 - Minor | |
Status | Confirmed | Wont Fix | |||
Open/Closed | Open | Closed | |||
2016-06-27 | bens | Open/Closed | Closed | Open | |
2016-06-27 | bens | Status | Wont Fix | Confirmed | |
2015-04-29 | bens | Status | None | Wont Fix | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-4448.
Corresponding source code
This has become irrelevant by now: there should be fewer and fewer files that still use only a CR as line separator, as Macs have become Unix systems. So... let it be.