Failing to save with invalid encoding, "Retry" button is useless and breaks program/UI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the save failure with an ASCII-encoded document containing a Unicode character, then trace the error dialog's Retry and Cancel handling. Confirm that after Retry the document remains editable, Undo works, and the document can be closed without terminating xed.
Written by the indexing model from the issue text.
Description
Steps to repro:
- Create ascii text file ("Western" encoding)
- Enter Unicode character
- Attempt to save
Error box appears with buttons "Retry" and "Cancel". The document, at this point, is unable to be edited.
- Click "Retry" (with or without changing encoding drop-down)
Result:
Error box closes. Document remains unable to be edited. "Undo" is inoperative. Document is unable to be closed without closing xed completely and choosing "Close without Saving" from error dialog.
Expected:
Document would be able to be edited when encoding error box appears. "Retry" button would not destroy usability of the app.
This question was never answered:
EDIT: Nevermind, I guess you guys are using ~/.local/share/gedit/gedit-metadata.xml ?
Regardless, this is still a bug in xed when UI elements are unresponsive.
- Dominant language
- C
- Stars
- 551
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/xed
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Allow pkexec xed OpenFEATURE REQUEST
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·