GNU nano - Bugs: bug #57696, in restricted mode, nano will...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57696: in restricted mode, nano will nevertheless write a lock file
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Wed 29 Jan 2020 06:46:36 PM UTC | ||
Severity: | 2 - Minor | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Mon 03 Feb 2020 01:31:59 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Wed 29 Jan 2020 06:46:36 PM UTC, original submission:
To reproduce, run:
|
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-10-08 | bens | Open/Closed | Open | Closed | |
2020-09-27 | bens | Status | Postponed | Wont Fix | |
Assigned to | bens | None | |||
2020-02-09 | bens | Status | None | Postponed | |
2020-02-03 | bens | Severity | 3 - Normal | 2 - Minor |
Powered by Savane 3.13-02a9.
Corresponding source code
I don't know what to do with this. Rvim writes lock files, so I think rnano should too. But if we want to do what it says in the man page ("don't read or write to any file not specified on the command line"), then we would have to suppress this. But... we read nanorc files in restricted mode (since version 3.2), and we've written lock files in restricted mode since lock files were introduced (in version 2.3.2), so... I'm going to let this be for now.