You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be nice to be able to configure this, e.g. for subsections subsec:baz, or or if someone wanted to use a different abbreviation, say \label{chpt:foo} (I'm not sure whether there's an 'official' guide on what abbreviations to use, or whether it's just a convention 😄). Basically, something like g:vimtex_toc_todo_labels but for sections instead of todos. (probably simpler than the todo labels, actually)
Right now subsections especially tend to get a little bit messed up because the syntax matches the second half of subsec:baz, e.g.
The text was updated successfully, but these errors were encountered:
It might be nice to be able to configure this, e.g. for subsections subsec:baz, or or if someone wanted to use a different abbreviation, say \label{chpt:foo}
Thanks, I agree that subsec: should also be highlighted and that should be fixed now. But I'm not 100% sure if we need any additional configuration possibilities here. If you want to, you can add your own rules, e.g. like this:
Is your feature request related to a problem? Please describe it.
In the ToC, chapter/section labels like
chap:foo
orsec:bar
get special syntax highlighting as defined inautoload/vimtex/toc.vim
vimtex/autoload/vimtex/toc.vim
Lines 373 to 376 in e429bb6
It might be nice to be able to configure this, e.g. for subsections
subsec:baz
, or or if someone wanted to use a different abbreviation, say\label{chpt:foo}
(I'm not sure whether there's an 'official' guide on what abbreviations to use, or whether it's just a convention 😄).Basically, something like(probably simpler than the todo labels, actually)g:vimtex_toc_todo_labels
but for sections instead of todos.Right now subsections especially tend to get a little bit messed up because the syntax matches the second half of
subsec:baz
, e.g.The text was updated successfully, but these errors were encountered: