Only highlights help norg, not any I write
tungstengmd opened this issue · 34 comments
Prerequisites
- I am using the latest stable release of Neovim
- I am using the latest version of the plugin
Neovim Version
10.0
Neorg setup
load = {
["core.defaults"] = {}, -- Loads default behaviour
["core.concealer"] = {}, -- Adds pretty icons to your documents
["core.dirman"] = { -- Manages Neorg workspaces
config = {
workspaces = {
notes = "~/notes",
},
default_workspace = "notes",
},
},
},
Actual behavior
The behaviour I experience is uhh... this.
Expected behavior
I expect it to also highlight my own file... but it doesn't.
Steps to reproduce
- Make a norg file.
- Write in it.
- It won't highlight or show pretty symbols or markup.
Potentially conflicting plugins
No response
Other information
No response
Help
No
Implementation help
No response
apart from :h conceallevel this looks completely fine to me
ik it looks fine it's directly from the kickstart
the conceallevel is set to 2 fyi
but except conceallevel the document looks completely normal
wdym
the top one is the help file, which is highlighted right
the bottom one is my file which isnt even highlighted
oh didn't see that there were two files
to make it significantly less confusing
oh didn't see that there were two files
fair
is treesitter highlighting enabled? (TSBufEnable highlight), and highlight={enabled=true} in treesitter config
also try :InspectTree to see if treesitter is attached and parsing works
hmm
also highlight is enabled
:set ft
seems like norg filetype isn't recognized even though that's now builtin to neovim
on the norg fyi
there you have the problem
the filetype isn't recognized
which isn't a neorg issue
because filetype detection should now be done by core
can you send the whole output of nvim --version?
prolly due to it being v10 not 11
no 0.10 should work, I also use it
do you by any chance use any special things for filetype detection?
wdym
well you're builtin filetype detection is messed up. so I'm asking if you perhaps did disable it
you could also try removing the neorg plugin, opening a *.norg file and see if the filetype is correct
if not we can be 100% sure that it's not a neorg issue
alr ill load it clean
my brother in christ it knows, this is a neorg issue
did you use nvim --clean? I'd also try to just remove the neorg plugin
yeah i used nvim --clean
...
after i remove neorg
what is the problem here
im gonna try and find anything hold on
well not neorg 😄
perhaps move this to a discussion since it's not related to neorg
fair enough
I'd suggest you to just start disabling plugins like 5 at a time and like that figure out which one is messing things up here
@tungstengmd you should close this issue
so the problem was vim-polyglot, there should be a section in readme showing anything that may conflict with neorg
Well we can't list all the things that might mess up neorg (because we simply can't know it all)
and this plugin just messes around with builtin filetype detection which isn't neorg's fault
you could open an issue there for norg filetype 🤷♂️
- at least put a list of what's known
- vim-polyglot hasn't been updated in 2 years