-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock outline to buffer/window/tab/ft #25
Comments
I had no idea augroup does all I tried to do with `self.autocmds`. Oh well. Also added sidebar.id, which is one step closer to #25
So today it's not possible to have the outline updating when changing buffer in the same tab page? Or maybe I missed something in the doc :) |
Currently you can only have one outline for each tabpage, which is what this issue is proposing to improve. Regardless of this issue, outline can still auto-update when changing buffers and windows. (See config By lock, I mean a single outline window that manages/attaches to a tab/buffer/window, and will not update on events that triggers from another tab/buffer/window. Whether it is tab, or buffer, or window, it could either be a config option or an argument to a command (described in issue description). Currently it is only tab. Perhaps I should've picked a better word for 'lock' 🤔 If this feature is implemented, say the user chooses to lock outline to window. Then the outline auto-updates when you open a new buffer in this window. But it won't auto-update when you switch to another window. When you switch to another window you then get to open another outline, which is 'locked' to this new window. Hope that makes sense! |
Ok I understand. But right now, I have 2 buffers opened, I open the outline with The same exercice but with tabs instead of buffers works. |
I can reproduce this and will push a fix soon. No need to open an issue on your end.
Apologies for any inconvenience caused, and thanks for letting me know 👍 UPDATE: It should be fixed now. |
Big thanks for your quick answer, it's so great to discuss with maintainers and have even a small impact on collaborative projects :) I confirm that it's fixed now |
Per-tab outlines was recently implemented in e705330.
Which means currently we have locked sidebars based on tabpage IDs, through
outline.sidebars[id]
. The idea of this issue is to let the user choose other options in locking the outline.After invoking a locking command, outline content will not automatically change.
these can be subcommands to
:OutlineLock
with no subcommands it could lock the outline content so it doesn't auto update on text change
:OutlineUnlock
restores current behaviourRunning lock after a previous lock command, is equivalent to running first lock, running unlock, then running second lock. (so no accumulation of lock rules)
there will be no cleverness or internal magic that lets
:OutlineLock
use the previous lock subcommand if second run did not provide subcommand.config:
outline_items.lock
: nil/false is current behaviour. a string value means a lock rule to be used by default when outline is first set up.The text was updated successfully, but these errors were encountered: