GNU nano - Bugs: bug #34898, [Wish] jump to existing buffer...
You are not allowed to post comments on this tracker with your current authentication level.
bug #34898: [Wish] jump to existing buffer when opening an already-open file
Submitter: | Kelsey Hightower <kelseyhightower> | ||
Submitted: | Fri 25 Nov 2011 04:49:47 PM UTC | ||
Votes: | 100 | ||
Severity: | 1 - Wish | Status: | None |
Assigned to: | None | Open/Closed: | Closed |
Mon 28 Nov 2022 08:40:26 AM UTC, comment #4: |
Benno Schulenberg <bens>![]() |
Wed 23 Nov 2022 04:44:00 PM UTC, comment #3: My preferred outcome would be, if the file is already open elsewhere, to provide an option to open the file in view mode (like with the -v switch).
|
Tasos Papastylianou <tpapastylianou> |
Sun 26 Dec 2021 09:22:30 PM UTC, comment #2: The goal the user has in mind when they are using multibuffer mode and try to open a file is to view (and possibly edit) that file's contents. For that reason, a "nothing happens" outcome from the "File xx is being edited; open anyway?" prompt is the least useful outcome.
|
Duncan Holm <holmdunc> |
Sat 14 Jun 2014 04:19:10 PM UTC, comment #1: With the new locking code, trying to open (into a new buffer) a file that nano already has opened, now results in the statusbar message "File being edited (...) continue?" So you will not accidentally have the same file opened twice.
|
Benno Schulenberg <bens>![]() |
Fri 25 Nov 2011 04:49:47 PM UTC, original submission:
When using multiple buffers, nano creates a new buffer for each file that I open, even if that file is already open in an existing buffer.
|
Kelsey Hightower <kelseyhightower> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 100 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 |
---|---|---|---|---|---|
2022-11-28 | bens | Open/Closed | Open | ![]() |
Closed |
2022-03-14 | bens | Summary | [Request] reuse existing buffers when adding files | ![]() |
[Wish] jump to existing buffer when opening an already-open file |
2021-12-26 | holmdunc | Carbon-Copy | - | ![]() |
Added holmdunc |
2018-02-18 | bens | Severity | 3 - Normal | ![]() |
1 - Wish |
2014-06-14 | bens | Summary | [Feature Request] Reuse existing buffers when adding files | ![]() |
[Request] reuse existing buffers when adding files |
Powered by Savane 3.12.
Corresponding source code
The original request was about avoiding to open the same file in two separate buffers and instead jump to the existing buffer when the user attempts to open an already-open file again. Wishing to have multiple viewports open on the same file (and in the same nano) is an entirely different request. It also has nothing to do with file locking -- that was just a suggestion to help the user to avoid opening the same file twice. How file locking behaves is not the subject of this issue. Closing this as too polluted.