-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
:type/feature-requestClosed at will. Feature requests are in Logseq forum https://discuss.logseq.com/Closed at will. Feature requests are in Logseq forum https://discuss.logseq.com/collapseRelated to collapsing, expanding or folding blocksRelated to collapsing, expanding or folding blocksshortcuts
Description
Search first
- I searched and no similar issues were found
What Happened?
Here https://github.com/logseq/logseq/blob/master/src/main/frontend/modules/shortcut/config.cljs:
:editor/toggle-open-blocks {:binding "t o"
--
517 | :fn editor-handler/toggle-open!}
"toggle-open" command is exposed, which toggles block starting from the root. I find that toggling of the currently selected block is way more practical and I suggest exposing "(defn toggle-open-block-children! [block-id]" in addition to that so that a shortcut could be assigned. Currently it's possible to assign shortcuts to "expand" and "collapse" of the current block, but it's quicker to just use toggle.
In addition to that it would be great if there was a shortcut for operation to collapse all the branches except of the current one. For example, before:
a
a1
a11
b
b1
b11 <-- cursor is here, we press "collapse-all-but-this-thread"
b22
b222
b223
c
c1
c11
after
a -- collapsed
b
b1
b11 <-- cursor is still here
b22 -- collapsed
c -- collapsed
Reproduce the Bug
None
Expected Behavior
No response
Screenshots
No response
Desktop or Mobile Platform Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
Metadata
Metadata
Assignees
Labels
:type/feature-requestClosed at will. Feature requests are in Logseq forum https://discuss.logseq.com/Closed at will. Feature requests are in Logseq forum https://discuss.logseq.com/collapseRelated to collapsing, expanding or folding blocksRelated to collapsing, expanding or folding blocksshortcuts