The keyboard to control navigation of the graph view as it does when it’s in a normal pane rather than a sidebar.
The keyboard graph view navigation controls do not function.
When note is docked in a sidebar, focused and in edit mode, shortcuts for
(and possibly other shortcuts) work on a currently open note in main area and not on the focused note in a sidebar.
Just chiming in, have just struck this bug as well - shortcut keys (Cmd E, Cmd B, Cmd Enter etc ) when used for a note in the sidebar are applied to the last focused pane in the main area. Annoying because I’ve moved all my “management” daily/task list notes and so on into the sidebar so I can minimise it away and have my real work front and center.
because that arrangement/workflow would be ideal for me to maintain focus on actually working. Workaround is to have a second workspace with the daily setup present, but that’s annoying because I have to update it every day with the new daily note.
EDIT: had the thought that maybe I could trigger the commands via the palette and that might work - have just tested trying to set selected text to bold, and it doesn’t work either, same behaviour as with the shortcut keys.
EDIT #2: On OSX 11.1, Obsidian 0.10.1 Installer 0.9.17
I think this issue likely arises from the fact that app.workspace.setActiveLeaf() does not support setting a sidebar document as the active leaf, and presumably commands are always applied to the active leaf.
Specifically, setActiveLeaf() checks whether the new leaf’s getRoot() is equal to the workspace root, but a sidebar document’s getRoot() is the top-level split of its associated ribbon.
ISTM setActiveLeaf() should be checking for rightSplit and leftSplit as well as rootSplit. I’ve tested this with a quick monkeypatch from the developer console, and it allows both commands and hotkeys to work, and also allows the cycle-through-panes plugin to cycle properly, even cycling through the sidebar documents.
There does seem to be one other glitch that it doesn’t fix, though: toggling the edit mode of a sidebar document causes the first pane in the main split to become active. Clicking again in the sidebar document returns it to an active state, however.
There is also no visual indication that a sidebar document is active, and activating a document whose tab isn’t selected doesn’t cause that tab to become selected. Similarly, selecting the tab of a sidebar document doesn’t cause it to become active.
So, it looks like more work will be needed to fix this besides just making it possible for a sidebar pane to be set active… although just supporting that would be a big help.
While investigating this issue I also discovered why the history behaves so oddly in 0.9.x; it apparently includes navigation between panes as part of the history. It sounds like that might have been changed in 0.10.x, though.
Create 2 new notes.
Open both of them up.
Drag one into one of the side panels.
Focus the note in the side panel.
Try editor shortcuts (e.g. bold, delete line, etc) or the same shortcut form the command palette.
Editor commands are only apply to the panel in focus regardless of where it’s placed.
Commands are applied to the last focused editor that is not in a side panel at the last place the cursor was focused regardless of whether an editor is focused in the side panel.
Strangely as you can see at the end of the recording, copy/paste do work correctly.
Just a quick note on this… it’s basically because setActiveLeaf() explicitly doesn’t allow leaves to be active if they’re in a side pane. At one point I played around with having pane-relief patch it to allow sidebar panes to be active, but I ran into some difficulty with the question of whether moving to the “next” or “previous” panes should include the panes in the sidebars, and if so, which ones, etc.
Anyway, the majority of commands in Obsidian do something to the “active” pane, and since sidebar panes can’t be “active”, that produces this result.
(What I don’t know is why they’re specifically disallowed from being active.)
This is a very annoying bug. Is there any chance the Obsidian devs could implement @pjeby’s fix by patching setActiveLeaf() as described above, even if it’s not a perfect fix? Or is this something that could be done with a plugin? I’d love for command-return etc to work properly in my sidebar notes…
+1, not being able to create checklists in the sidebar via cmd-return is a bit of a pain, would love to see this fixed
Thanks!
Would love a fix for this. Thanks!
Would love a fix for this too!
+1 Recently ran into this issue as well jumping into a new workflow. I was trying to do a slash command to insert templates (time, date, etc).
Looking forward to a fix.
+1 for me as well.
I’m toying around with porting some workflows from Roam, and having an active sidebar so I can use various plugin mechanisms for it is pretty key.
Still experiencing this bug in Feb 2022. I hope there’s a resolution soon! It seems like hotkeys should be applied to any pane/file in which the cursor is active/blinking.
If a file is a fixed part of the right pane, then executing CMD+ENTER will actually put the task notation in that file
Executing CMD+ENTER in the right pane fixed file, will insert the task notation in an active other file.
RECOMMENDATIONS:
none
+1
Running into this same issue
+1 on macos
Exactly the issue I’m running into. Not just this hotkey, but also moving lines up and down.
This will be worked on in v0.15.x
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
