-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
feat: new :tree-sitter-tree
command
#12207
base: master
Are you sure you want to change the base?
Conversation
:tree-sitter-tree
command:tree-sitter-tree
command
For now - as the panel doesn't auto update - would it be possible for subsequent |
Ok, I just pushed a commit. it will replace the existing buffer now. |
And is it possible to prevent writing to the syntax tree buffer? Nvim's impl prevents modifying it, and I think especially now that we replace the buffer with a new one we should expect users not to edit it - and enforce that. |
It's not possible to make a file unwritable from what I can tell (readonly will still allow editing, but not saving). See also this comment by @the-mikedavis : #7128 (comment) |
`patchy` is a tool which makes it easy to declaratively manage personal forks by automatically merging pull requests. Check it out here: https://github.com/NikitaRevenco/patchy
ca6940e
to
5fff598
Compare
Using
%
to select entire file and then using:tree-sitter-subtree
which opens in a tiny window makes it difficult to inspect the entire tree.It would be nice if you could open the current file's entire tree in a separate buffer. Currently this is just a basic implementation, which gets the current file's tree and dumps it into a new buffer. In the future the command can be updated to be more like neovim's
:inspect-tree
command.Closes #12149