GNU nano - Bugs: bug #47975, saving a still nameless buffer...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47975: saving a still nameless buffer does not create a lock file
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sun 22 May 2016 10:01:53 AM UTC | ||
Votes: | 1 | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Sun 12 Sep 2021 08:08:34 AM UTC, comment #3: |
Benno Schulenberg <bens> |
Mon 13 Jan 2020 07:08:33 PM UTC, comment #2: Fixed in git, commit 497f126b. |
Benno Schulenberg <bens> |
Fri 24 Feb 2017 11:18:09 AM UTC, comment #1: The warning was disabled in commit 32719d64 (see bug #49875), and removed with commit 9e6e1ebe. But creating a file (or overwriting one) by saving a new buffer still does not create a lock file.
|
Benno Schulenberg <bens> |
Sun 22 May 2016 10:01:53 AM UTC, original submission:
To reproduce, run 'src/nano --ignore --locking' and type:
|
Benno Schulenberg <bens> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There is 1 vote 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 | Open/Closed | Open | Closed | |
2020-01-13 | bens | Status | None | Fixed | |
Assigned to | None | bens | |||
2018-10-23 | dolorous | Carbon-Copy | - | Added dolorous |
Powered by Savane 3.13-02a9.
Corresponding source code
Actually the issue was not fixed, and it was rereported in bug #61146. Commit 5cedb53c changes the code added in commit 497f126b to do the right thing in the case of a nameless buffer: write a lock file whenever LOCKING is true, not just when previously a lock file existed.