GNU nano - Bugs: bug #57700, when a lock file cannot be read,...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57700: when a lock file cannot be read, nano should ignore it
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Thu 30 Jan 2020 06:00:00 PM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Thu 30 Jan 2020 06:13:02 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Thu 30 Jan 2020 06:00:00 PM UTC, original submission:
Currently, when an existing lock file is somehow unreadable, nano reports "[ Error opening lock file ./.README.swp: Permission denied ]" and refuses to open the file, it opens a blank buffer instead. This is not good. Lock files are meant to help the user, to warn her that someone else is editing the same; they are not meant to hinder or prevent the user from editing the file.
|
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 |
---|---|---|---|---|---|
2020-02-09 | bens | Severity | 3 - Normal | 2 - Minor | |
Open/Closed | Open | Closed | |||
2020-01-30 | bens | Summary | when a lock cannot be read, nano should ignore it | when a lock file cannot be read, nano should ignore it | |
2020-01-30 | bens | Status | In Progress | Fixed |
Powered by Savane 3.13-d3ae.
Corresponding source code
Fixed in git, commit f494bfcb.