GNU nano - Bugs: bug #61720, sample nanorc breaks if edited and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61720: sample nanorc breaks if edited and saved with certain editors
Submitter: | Maxxim <maxxim> | ||
Submitted: | Thu 23 Dec 2021 10:20:31 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | None | Open/Closed: | Closed |
Jump to the original submission
Thu 18 Aug 2022 03:47:00 PM UTC, comment #7: |
Maxxim <maxxim> |
Thu 18 Aug 2022 08:57:39 AM UTC, comment #6: Fixed in git, commit 2a515058, by replacing the control codes and escape sequences with {function} cartouches. |
Benno Schulenberg <bens> |
Fri 21 Jan 2022 11:20:46 AM UTC, comment #5: When the feature request from bug #61692 gets fulfilled, the problem in this issue can be avoided by rewriting the string binds with function names instead of control codes. |
Benno Schulenberg <bens> |
Thu 30 Dec 2021 04:51:36 PM UTC, comment #4: As another user, I disagree that control sequences should not appear in nanorc. Appropriate handling of control sequences is a feature, not a bug.
|
Tasos Papastylianou <tpapastylianou> |
Thu 23 Dec 2021 04:40:19 PM UTC, comment #3: Just to clarify what I mentioned before:
|
Maxxim <maxxim> |
Thu 23 Dec 2021 04:31:33 PM UTC, comment #2: Well, control characters are control characters, hence the name. They are not meant to appear within text files except for when they are used to actually serve their assigned function (e.g. tab, newline).
|
Maxxim <maxxim> |
Thu 23 Dec 2021 04:15:48 PM UTC, comment #1: True, it's unusual for a config file to contain control codes (other than Tab and LF). But in my opinion it's a bug in Kate (and in Gedit and in ne) that it replaces a lone CR with a LF. That's wrong. Vim and Emacs and Joe don't do that. (Nano itself used to do it too, because its heuristic for recognizing a DOS file was wrong. It was fixed a year and a half ago: https://git.savannah.gnu.org/cgit/nano.git/commit/?id=ac0f2c94.) |
Benno Schulenberg <bens> |
Thu 23 Dec 2021 10:20:31 AM UTC, original submission:
After updates, I usually migrate configuration files by comparing and editing them with KDE's Kate. Last time I did this for nano, I ended up with an invalid/broken config.
|
Maxxim <maxxim> |
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-08-18 | bens | Status | Wont Fix | Fixed | |
2022-02-01 | bens | Open/Closed | Open | Closed | |
2022-01-21 | bens | Status | None | Wont Fix | |
2021-12-23 | bens | Severity | 3 - Normal | 2 - Minor | |
Summary | Default nanorc breaks if edited and saved with different editor | sample nanorc breaks if edited and saved with certain editors |
Powered by Savane 3.13-f8d8.
Corresponding source code
comment #6:
That's a relief. This was REALLY annoying, I actually broke my nanorc again just a couple of days ago while migrating settings to a newer version (which is a regular occurrence on rolling-release distros).
Looking forward to the new release.