GNU nano - Bugs: bug #56524, when unable to read history files,...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56524: when unable to read history files, nano should not pause
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Thu 20 Jun 2019 09:28:06 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Sun 20 Oct 2019 12:41:57 PM UTC, comment #2: |
Benno Schulenberg <bens> |
Tue 20 Aug 2019 12:49:18 AM UTC, comment #1: I don't know what happened to my comment for this one. But jot_error needs nanorc to be set. Exporting the nanorc variable and having code outside rcfile.c set it would be confusing. The patch adds a set_error_file function which is clearer than setting a variable called 'nanorc'.
|
Brand Huntsman <brand> |
Thu 20 Jun 2019 09:28:06 AM UTC, original submission:
To reproduce, make nano's filepos_history or search_history file unreadable (chmod u-r ...). Then start nano. See that it reports an error and asks to press Enter to continue.
|
Benno Schulenberg <bens> |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-11-30 | bens | Open/Closed | Open | Closed | |
2019-10-20 | bens | Status | None | Fixed | |
Assigned to | None | bens | |||
2019-06-29 | brand | Attached File | - | Added log-history-files-errors-to-console-and-display-stat.patch, #47145 |
Powered by Savane 3.13-d3ae.
Corresponding source code
Sorry for leaving this unaddressed for so long. But I didn't like the somewhat incorrect error message that your patch produces when (for example) the file-position file is unreadable:
[ Mistakes in '/home/ben/.nano/filepos_history' ]
There are no mistakes in the file itself, it's a problem _about the file.
So I've implemented a different solution, one that renames and changes the meaning of a variable. Commit 95ae1248.