GNU nano - Bugs: bug #50773, [Request] improve the handling of...
You are not allowed to post comments on this tracker with your current authentication level.
bug #50773: [Request] improve the handling of combining characters
Submitter: | Mike Frysinger <vapier> | ||
Submitted: | Mon 10 Apr 2017 05:04:38 AM UTC | ||
Severity: | 1 - Wish | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Thu 03 Dec 2020 11:15:13 AM UTC, comment #11: |
Benno Schulenberg <bens> |
Sun 22 Nov 2020 09:46:48 AM UTC, comment #10: Thanks for the feedback, Peter. Yes, the combining character "jumping back" onto the preceding character is the weird and confusing behavior that prompted me to implement the better behavior. (I myself don't use combining characters, and I can only enter them via M-V 0003xx, so for me personally it has never been an issue.)
|
Benno Schulenberg <bens> |
Sun 22 Nov 2020 06:39:16 AM UTC, comment #9: As someone who works routinely with zero-width characters in nano, I'd like to say that I love the patches, and they seem to work well.
|
Peter Passchier <pepa65> |
Tue 17 Nov 2020 10:44:42 AM UTC, comment #8: Improved versions of the patches have been pushed to master, commit 687efd21 and dc907bfe. |
Benno Schulenberg <bens> |
Wed 11 Nov 2020 03:26:44 PM UTC, comment #7: A first iteration of an implementation is attached. |
Benno Schulenberg <bens> |
Thu 04 May 2017 08:43:38 AM UTC, comment #6:
|
Benno Schulenberg <bens> |
Wed 03 May 2017 09:26:02 PM UTC, comment #5: Just FYI:
|
Egmont Koblinger <egmont> |
Tue 11 Apr 2017 08:33:52 PM UTC, comment #4: backspace-vs-delete sounds like a reasonable compromise. hopefully the user's keyboard provides both :).
|
Mike Frysinger <vapier> |
Tue 11 Apr 2017 08:54:37 AM UTC, comment #3: I've read a bit on the Unicode website and encountered this: "on a given system the backspace key might delete by code point, while the delete key may delete an entire cluster." [1] I think that is the perfect compromise: deleting the entire grapheme when <Delete> is pressed avoids the suprprise of combining character(s) jumping to the preceding character, but still allows to remove combining characters individually by using <Backspace>. So I don't think a config option is needed there.
|
Benno Schulenberg <bens> |
Mon 10 Apr 2017 08:09:21 PM UTC, comment #2: i think either behavior wrt deletion is defensible. i don't feel too strongly either way since i don't use/encounter them normally, so i can't speak to common workflows. being able to delete combining characters like emacs does seem like a reasonable position, but so does deleting an entire grapheme. maybe time for a config option ? :)
|
Mike Frysinger <vapier> |
Mon 10 Apr 2017 03:16:55 PM UTC, comment #1: When I open a file that contains just "0ax̊bc" (without the quotes and without a newline) with vim, it says "1L, 7C". Seven characters! That's even worse than nano, which correctly identifies six codepoints, six individual characters.
|
Benno Schulenberg <bens> |
Mon 10 Apr 2017 05:04:38 AM UTC, original submission:
consider this content:
|
Mike Frysinger <vapier> |
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 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-12-03 | bens | Open/Closed | Open | Closed | |
2020-11-17 | bens | Status | Ready For Test | Fixed | |
2020-11-11 | bens | Attached File | - | Added 0001-moving-skip-combining-characters-and-other-zero-widt.patch, #50247 | |
Attached File | - | Added 0002-prompt-skip-over-combining-characters-also-when-edit.patch, #50248 | |||
Status | None | Ready For Test | |||
Assigned to | None | bens | |||
2019-05-27 | bens | Severity | 3 - Normal | 1 - Wish | |
Summary | handling of combining characters | [Request] improve the handling of combining characters |
Powered by Savane 3.13-758e.
Corresponding source code
Released in nano-5.4.