GNU nano - Bugs: bug #46894, changing the filename in ^O to an...
You are not allowed to post comments on this tracker with your current authentication level.
bug #46894: changing the filename in ^O to an existing one, does not ask whether the change is okay
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Thu 14 Jan 2016 11:30:17 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Sun 20 Mar 2016 02:38:38 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Thu 14 Jan 2016 11:30:17 AM UTC, original submission:
When in the WriteOut menu one (accidentally) changes to name of the file to be written to an existing one, nano does not ask (as it usually does) "Save file under DIFFERENT NAME ?" but just "File exists, OVERWRITE ?". In my opinion it should ask both questions, in the given order.
|
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-06-20 | bens | Open/Closed | Open | Closed | |
2016-03-20 | bens | Severity | 3 - Normal | 2 - Minor | |
Status | None | Fixed | |||
2016-01-21 | bens | Assigned to | None | bens |
Powered by Savane 3.13-d3ae.
Corresponding source code
Fixed in SVN, r5753.
In addition, nano now shows the name of the file that already exists, like Pico -- in case you forgot what you typed. And it will not ask a second time whether a name change is okay when the answer was Yes (for this WriteOut).