possibility to customize look of the table of contents?

[DockterTeagle]

Howdy, first of love this plugin, it undersells its features imo (like vimtex#syntax#in_mathzone) but thats besided the point. I know that this plugin is meant to not be specific to neovim or vim,but to rather work on both. I was wondering if it was possible to customize the looks of the TOC, I know that looks are not a prioity but it looks a little too barebone for my taste is there an api for changing how it is drawn? Ive looked through the help and found only mentions of mappings and denite (which is deprecated btw, ddu.vim is the new one).

As a few sidenotes does being in lua make it more capable to redraw stuff (for neovim) as alot of the neovim plugins Ive seen that provide a UI seem to look "better" or more extensible. also why vim over neovim? I think I know why this is written in vimscript it would both be alot of work to rewrite and also drop support for vim afaik.

[lervag]

Howdy, first of love this plugin, it undersells its features imo …

<3

I was wondering if it was possible to customize the looks of the TOC, I know that looks are not a prioity but it looks a little too barebone for my taste

Well, sort of. You can't customize the look of the built-in TOC except through the limited keys in g:vimtex_toc_config.

You can also change the syntax highlight groups. This is not documented, so it would require some amount of skill on your side - the groups are defined here:

vimtex/autoload/vimtex/toc.vim

Line 347 in 85cb04f

function! s:toc.set_syntax() abort dict "{{{1

is there an api for changing how it is drawn?

No, but there is an API that you can use to build your own if you are an expert user. I would recommend looking at e.g. the fzf.vim TOC interface to see how the api is used, specifically, look for the call to vimtex#parser#toc().

Ive looked through the help and found only mentions of mappings and denite (which is deprecated btw, ddu.vim is the new one: https://github.com/Shougo/ddu.vim)

Ok. Adding support for ddu will require user contributions, as I don't use it. And keeping support for deprecated plugins is probably not a good idea, but I guess removing it could be annoying to some users. I'll have to think about that.

does being in lua make it more capable to redraw stuff (for neovim) as alot of the neovim plugins Ive seen that provide a UI seem to look "better" or more extensible

Nah, Lua is good - it is faster and generally a better language than Vimscript. But I would say it is rather the Neovim development and API that allows for better UIs. Still, you could claim that this development is made possible by Lua.

In any case, I have to admit UI is hard and VimTeX has a lot of baggage that makes it hard to modernize things in Lua. Or, at least it's a lot of work.

also why vim over neovim?

Because when VimTeX was started, Neovim was not a thing. VimTeX was created in 2013, Neovim only started in 2014. And I didn't start to use it before 2016 myself. And as a long-time Vim user I decided to keep development of VimTeX in Vimscript.

I think I know why this is written in vimscript it would both be alot of work to rewrite and also drop support for vim afaik.

Yes, precisely.

[DockterTeagle]

when I asked why vim over neovim I was asking about current holdouts, and thank you will look into fzf.vim

[DockterTeagle]

I know that there is some lua code for fzf-lua maybe allow TOC to be in that ui? idk I just really like Folkes plugins, and want it to look consistent(not that fzf-lua is folke)

[DockterTeagle]

and if not and if I decide to be usefull for once in this repo, could I write the api in lua? or would that be too much work and also go against your design philosphy? th is would be a massive undertaking for me, I have the time but all my contribs to open source that are not my repos are rather trivial, so help would be appreciated on this from anyone

[DockterTeagle]

furthermore, how do I test a (neo)vim plugin?

[lervag]

when I asked why vim over neovim I was asking about current holdouts

My current holdout is simply that I don't have the time. If I had loads of time, I could have been interested in pushing for a Neovim only version of VimTeX written in Lua.

Notice, though, I do still believe that the current version is quite good and that rewriting in Lua would not inherently improve VimTeX very much. It might get somewhat more snappy, of course, but this is mostly not a problem (in my experience).

and if not and if I decide to be usefull for once in this repo, could I write the api in lua? or would that be too much work and also go against your design philosphy? th is would be a massive undertaking for me, I have the time but all my contribs to open source that are not my repos are rather trivial, so help would be appreciated on this from anyone

furthermore, how do I test a (neo)vim plugin?

You've already started looking into this; thanks! For other readers, see #3167.

Feel free to ask about things in the PR thread. I'll be glad to help! And I'll show how to add tests if you did not already figured it out.