GNU nano - Bugs: bug #45874, searching for a string in a binary...
You are not allowed to post comments on this tracker with your current authentication level.
bug #45874: searching for a string in a binary file causes Babylon
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Fri 04 Sep 2015 10:27:14 AM UTC | ||
Severity: | 5 - Blocker | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Fri 04 Sep 2015 07:44:05 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Fri 04 Sep 2015 10:27:14 AM UTC, original submission:
Open a .odt file with nano -- the screen will be filled with binary garbage. Now search for some string that most likely does not exist in the document, say "owow". The screen will now be filled with reverse-video question marks, and even the status line will be garbled: [ ������ ��� ����� ].
|
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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-12-07 | bens | Open/Closed | Open | Closed | |
2015-09-04 | bens | Status | None | Fixed |
Powered by Savane 3.13-f8d8.
Corresponding source code
Fixed in SVN, r5369. It reverts the commit that said that UTF8 is a stateless encoding. Maybe only one of the resets is needed, hopefully wctomb_reset(), but I don't have the time to test that out thoroughly now.
Also, if these resets are needed, they may be required elsewhere in the code too: stepping a multibyte character to the left is likely to hit an invalid code, but it probably does not reset the state then. I haven't yet seen any ill effects, but...