GNU nano - Bugs: bug #42383, [Request] keep warning audibly and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #42383: [Request] keep warning audibly and visibly when editing unwritable file
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sat 17 May 2014 12:04:25 PM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | bens | Open/Closed: | Closed |
Sun 26 Jun 2016 07:54:27 PM UTC, comment #3: |
Benno Schulenberg <bens> |
Mon 03 Aug 2015 07:20:11 PM UTC, comment #2: I would also like this. However, I'd claim colors would be nice only if they can be disabled. |
Wyatt Ward <wyatt8740> |
Thu 03 Jul 2014 03:00:06 AM UTC, comment #1: I've frequently edited files on multi-user systems that I didn't have write access to, and then just saved to a new filename if Id come up with modifications worth keeping. If the user ignores the warning message that the file is unwritable, they do so at their own peril, and in some cases they are intentionally doing so.
|
Chris Allegretta <astyanax> |
Sat 17 May 2014 12:04:25 PM UTC, original submission:
When starting to modify an unwritable file, nano should warn on the statusbar for every modifying keystroke, preferrably in brightwhite on red, and audibly too. |
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-29 | bens | Open/Closed | Open | Closed | |
2016-06-26 | bens | Status | None | Wont Fix | |
Assigned to | None | bens | |||
2014-06-14 | bens | Summary | Keep warning audibly and visibly when editing unwritable file | [Request] keep warning audibly and visibly when editing unwritable file |
Powered by Savane 3.13-f8d8.
Corresponding source code
Now that the warning that a file is unwritable is a separate message (and not tacked onto the normal message of number of lines read) and accompanied by a beep, it is much harder to unawares edit an unwritable file. So it is hardly necessary to keep warning the user (and it would be annoying too).
(The only thing that might be nice to have is a tag of "Unwritable" in the upper right corner (instead of "Modified"). But that might be cumbersome to implement because the permissions of the file might change any time, so nano would have to keep checking those for every keystroke... Nah, not a good idea.)