Crash upon load

[MikolasJanota]

Getting the following error (it seems repeatedly)

Error executing vim.schedule lua callback: function cmp_vimtex#count, line 3: Vim(let):E706: Argument of count() must be a List, String or Dictionary
stack traceback:
        [C]: in function 'cmp_vimtex#count'
        ...kickstart.nvim/lazy/cmp-vimtex/lua/cmp_vimtex/parser.lua:211: in function 'parse_entry'
        ...kickstart.nvim/lazy/cmp-vimtex/lua/cmp_vimtex/parser.lua:188: in function 'parse_type'
        ...kickstart.nvim/lazy/cmp-vimtex/lua/cmp_vimtex/parser.lua:116: in function 'callback'
        .../kickstart.nvim/lazy/cmp-vimtex/lua/cmp_vimtex/timer.lua:72: in function <.../kickstart.nvim/lazy/cmp-vimtex/lua/cmp_vimtex/timer.lua:66>

With the following setup in lazy

{
   'lervag/vimtex',
   lazy = false, -- lazy-loading will disable inverse search
   config = function()
     vim.g.vimtex_view_method = 'skim'
     vim.g.vimtex_quickfix_open_on_warning = 0
     vim.g.vimtex_quickfix_mode = 2
   end,
   keys = {
     { '<localLeader>l', '', desc = '+vimtex' },
   },
 },

 { 'micangl/cmp-vimtex', lazy = false },

and

        sources = {
          {
            name = 'lazydev',
            -- set group index to 0 to skip loading LuaLS completions as lazydev recommends it
            group_index = 0,
          },
          { name = 'nvim_lsp' },
          { name = 'luasnip' },
          { name = 'path' },
          { name = 'vimtex' },
        },

[micangl]

That seems a rather strange error. It would make sense, though, if the bibtex file were incorrectly formatted.

Is it contingent on opening files which source a specific bibtex source?

[MikolasJanota]

That seems a rather strange error. It would make sense, though, if the bibtex file were incorrectly formatted.

Is it contingent on opening files which source a specific bibtex source?

Yes you're right, it seems to work on other tex+bib files. However, on the one it crashes, bibtex runs without any complaints.

[micangl]

Sometimes, even non-strictly standard formatting can cause an error.

The only way to proceed is to take a close look at the file. If it's not confidential, I could try to do it.

[MikolasJanota]

I did some binary search and the issue was that there was an entry, where the key was on a new line, for reasons unknown. Somthing like@book{\nBla

[micangl]

Well, that explains it.

[MikolasJanota]

Sort of, it's weird that the parser would be sensitive to whitespace.

[micangl]

The parser operates on line-by-line basis since it works virtually always (yours is the first bug of this type which has been reported).

Moreover, it does seem to be uncovered, by the specification, if a key can be on a new line.

[pavelsivanovs]

Just had the same issue and the same problem. I am generating my .bib with Better BibTex plugin for Zotero, and for some reason it did not want to generate the citation key for Wav2Vec2.0 paper 🤔

Maybe a good idea would be to implement a .bib file validator? I spent quite some time in finding the root of the problem in cmp-vimtex and it turned out that the problem was coming from elsewhere. I would gladly do a PR, if such an idea seems feasible for implementation.

[micangl]

@pavelsivanovs Absolutely! Unfortunately, I do not have a lot of time on my hands, but I would be more than glad to review a potential PR.