-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Current scope is not highlighted after the upgrade to v3 #643
Comments
Please use the minimal config template to provide a fully reproducible example. If you specifically mean the place in the screenshot, this is expected. The tables in the setup call are not scopes. Please read the definition in the docs, |
I'm also facing this issue, but I've noticed that "Scope" only applies to where variables are reachable, and it's language gnostic. |
You can add additional node types with |
Thank you, and this plugin is great, thank you for your hard work. |
This is my config right now: return {
"lukas-reineke/indent-blankline.nvim",
main = "ibl",
opts = {
scope = {
show_start = false,
include = {
node_type = { "*" },
},
},
indent = {
char = "│",
},
},
} ![]() I'm working with |
@lukas-reineke Would it be possible to implement a wild character as a value of the wild character table to indicate that all scopes should be highlighted ? Would performance be impacted considerably ? |
@Pandoks you need to setup the highlight groups for example: Check the documentation by typing -- edit -- also, the node_type should not contain ^ characters, this is something I did to turn on or off some node_types this example would be much better |
IMO It should default to all scopes like it used to then have an option to disable them, not the other way around, for now I'm sticking to mini.indentscope. |
What is |
That is not the point of scope. The scope is the actual program scope, as in https://en.wikipedia.org/wiki/Scope_(computer_science)
I added this in https://github.com/lukas-reineke/indent-blankline.nvim/releases/tag/v3.2.0 but it can lead to weird behavior, use it with a grain of salt.
They are |
There's indeed a problem with mismatching highlight groups in local config = {
custom_highlights = function(colors)
return {
IblIndent = { fg = colors.surface0 },
IblScope = { fg = colors.text },
}
end,
} These fixes combined with the most recent wildcard change in ![]() Thanks @lukas-reineke for a very nice plugin! P.S. In the original issue description, I used one of the standard built-in color schemes, which doesn't even have the needed highlight groups at all, thus, no highlighting of the current indentation level. No surprise here. |
Problem
This may be not a bug, but I couldn't find an answer in the documentation (by text search, at least) about how to highlight the current scope. Treesitter is, of course, configured in the main config.
Steps to reproduce
nvim --clean -u ./min-init.lua min-init.lua
Expected behavior
The current scope's indent line is bold or something.
Neovim version (nvim -v)
0.9.2
The text was updated successfully, but these errors were encountered: