Apparently, there was a design decision to make navigation apply to all pane history. I think there is a strong case where navigation that is based on the history of the focused pane is much more usable and effective. Either way, please provide an option so that each individual can decide how navigation should behave.
Ideally, if keyboard shortcuts are more effective so that pane focus and maneuverability can be done more predictably and intuitively from the keyboard, then providing the option to make navigation pane specific would be a very powerful supplement in increasing user experience/productivity.
Agree that the toggle makes the most sense. There are use cases where traversing the sequence across multiple panes allows for tracing one’s mental steps. There are also simple editing use cases where pane-specific history is of more utility. Perhaps a similar functionality to that of pinning, but where the toggle is at a file-specific vs. pane-specific or vault-specific level.
Come here to search for this as well. Would appreciate a fix for this.
As in all application with multiple pane/tabs, navigation between panes and navigating the history of a pane should ideally be separated.
Since Obsidian has already provided “Focus pane on the left/right/…” already, I think separate history is expected.
Yes, so much this! I’m a heavy user of the back/forward hotkeys, and when working with multiple panes this throws me off terribly. I imagine it doesn’t make sense to change the existing hotkeys, but adding new hotkeys for this would be a godsend.
ETA: Does the plugin framework provide the right hooks to be able to do this? Worst case, could it be implemented that way?
Yes, yes, 1000 times yes. I do not get the justification for the existing, default behavior. As you say, it may be “useful in specific situations”, but much more often (in my experience) you want each pane to have its own history! Clearly that should be the default, and I don’t know why it would be a technical issue for it to work that way. Obsidian team have already worked plenty of magic elsewhere.
I’ll also take this moment to point out that this has been requested several times before. Other mentions are archived, but this is clearly a need for many people and it has not been addressed. Can we get some discussion about why there is this seemingly unintuitive default @Licat and whether pane-specific history nav can be an option? (apologies if tagging Licat is frowned on here, I wasn’t sure who else to call attention to this)
We strongly recommend you to search the forum with possible keywords before making a new feature request. If your request is very similar to an existing one, consider liking it and/or making a comment rather than making a new one. Once you’ve searched and determined that this is a new request, delete this line.
Use case or problem
if i have multiple panes open and i select on some of them, using back and forward function in obsidian switches between then instead of going back and forward in the pane/tab history.
change it so that back and forward work like any web-browser, just going back in the history on that pane/tab
The Pane Relief plugin implements this; you can find it in the “Community Plugins” section of your Obsidian settings (click “Browse”, then search for Pane Relief).
The plugin provides you with per-pane history, makes the back and forward buttons in the title bar display what file(s) they go to, and you can right-click them to display a list of forward and back destinations (which you can then right-click to do things to, drag links from, or ctrl/cmd-click to open in a new pane with an identical history trail).
Each pane will have its own history, separate from the others. The history is also saved with the workspace, in a way compatible with both the built-in Workspaces plugin and the community Workspaces Plus plugin.
Pane-specific navigation history is certainly what’s intuitive, and as various others have stated, this is the way any browser or other text editor works. I strongly agree that this should be core functionality.
In the meantime, thanks very much for the Pane Relief plugin, @pjeby.