The current functionality of opening a file that is already present in an open tab behaves unintuitively in the presence of pinned tabs.
Currently observed behavior when opening a new file that is already shown in a tab:
When the newly opened file is already open in a pinned tab: The file is reopened in another unpinned tab.
When the currently active tab is not pinned: An unpinned tab already showing that file is activated.
When the currently active tab is pinned: The newly opened file is opened into a new tab, even if already present in another.
It doesn’t seem intuitive that what happens to a newly opened document depends on the pinning status of the currently active tab, as the opening can occur entirely outside of the context of the active tab, and the user is not necessarily even aware of its status, or even of which tab is actually currently active.
It also doesn’t make sense that an unpinned existing tab is activated, but a pinned existing tab isn’t, as the user most likely has pinned that file especially to always keep it visible specifically in that particular tab, and this can be easily overridden using the ctrl/command keys, if the user actually want to open a second tab for the same file.
I would intuitively assume that pinning only affects the potential replacement of the contents of the active tab, instead of affecting a behavior that would not result in such replacement even in the absence of a pin on the active tab.
Suggested behavior: When opening an existing file via any command or UI, the default should be to primarily activate any existing tab already showing the file, regardless of its pinning status. If an existing tab for the file is not already present, the pinning status of the active tab should decide whether its contents are replaced, or the file is opened in a new tab.
That’s not what happens. Try in the sandbox vault.
Strange. I could swear that certain that this was happening to me yesterday, but I must have been somehow confused.
Anyway, that is what should be happening. It is not reasonable to assume that just clicking on a file in the Files tab should open a second view of the same file, if it happens to be already open.
Seem like you are asking for this
Yes. That seems to match the behavior that I suggested above. That seems to have been already requested in 2022 and widely supported. I guess that there are no plans to implement it as an option.
I tried the Mononote community plugin, but it doesn’t seem to function across window panels.
My current workflow involves keeping the current daily note in a pinned pane that is always open, while keeping tabs related to tasks open in another panel. When a task-related tab is active and I click on the Daily Note button, it just reuses the task tab.
It would be nice to be able to use the daily note button as a quick shortcut to getting back to editing the daily note exactly at the position you worked on earlier, usually at the end of the note. This can be achieved by just moving back to its pinned tab, but it would be nice to be able to use the daily note button or keyboard shortcut to achieve the same.