Latex commands are completed with pair of parenthesis instead of curly bracket - texlab

[abzrg]

I'm using the texlab language server and I might be wrong but most likely I don't remember I had this issue when I was using nvim.cmp. It seems blink.cmp or perhaps texlab treats all the latex commands/macros as functions (even the lspkind symbol for latex comands is an italic-like f denoting a function). For example:

\textbf -----accepting-completion-----> \textbf()  % accepts one argument
\!      -----accepting-completion-----> \!()       % does not accept any argument

whereas the expected behaviour, in case the command accepts any argument, is to append a pair of curly brackets.

\textbf -----accepting-completion-----> \textbf{}   % or atleast \textbf
\!      -----accepting-completion-----> \!

Here's my texlab lsp settings:

lspconfig.texlab.setup {
  capabilities = capabilities,
  cmd = { "texlab" },
  filetypes = { "plaintex", "tex", "bib" },
  settings = {
    texlab = {
      auxDirectory = ".",
      bibtexFormatter = "texlab",
      build = {
        args = { "-pdf", "-dvi-", "-interaction=nonstopmode", "-synctex=1", "%f" },
        executable = "latexmk",
        forwardSearchAfter = false,
        onSave = false
      },
      chktex = {
        onEdit = false,
        onOpenAndSave = false
      },
      diagnosticsDelay = 300,
      formatterLineLength = 80,
      forwardSearch = {
        args = {}
      },
      latexFormatter = "latexindent",
      latexindent = {
        modifyLineBreaks = false
      }
    }
  },
  single_file_support = true
}

[Saghen]

Added definitions for latex, plaintex and context, but lmk if I got any of these wrong, I don't use latex myself: 9ffdb7b

[abzrg]

Thank you. It now do the right job and completes with {}

[gennaro-tedesco]

The environments that require curly brackets {} do indeed work as intended. However, there are other generic LaTeX commands that don't take any parentheses - for them the {} are unnecessary. What is the mechanism that one must hook into, here? Is blink.cmp getting all in-built functions from the relevant lsp and then appending the parentheses manually (which I would presume, for some languages specified here) or is this delegated to the lsp itself (in which case texlab is returning the wrong bracket "input")?

[gennaro-tedesco]

I will try to dig a little more in the specifics of texlab and search among their issues too: I suppose this problem must have come up in one way or the other independent of the text editor and completion engine.

Just for me to better understand: with this commit the auto-brackets are still active, only you're changing the default type from ( to { - is my understanding correct?

[Saghen]

Yep, that's the case

[abzrg]

I tried to disable auto_brackets for .tex files via the following code in after/ftplugin/tex.lua:

local completion = require('blink.cmp.completion')

completion.accept = {
  auto_brackets = {
    enabled = false,
  },
}

but It does not work. Am I writing a wrong Lua code or something else is wrong?

[gennaro-tedesco]

I am not sure that the spec will be merged to the general blink.cmp if you add it in your after/ftplugin/tex.lua. What I presume should be done is the following:

completion.accept = {
...
 kind_resolution = {
      enabled = true,
      blocked_filetypes = { 'typescriptreact', 'javascriptreact', 'vue', 'tex' }, <--- add tex filetype here
    },

in the general blink.cmp configuration. However the above just avoids adding parentheses altogether, likewise if done so in semantic_token_resolution. I have moreover tried to pass a function to

enabled = function() return vim.bo.filetype~='tex' end

to no avail either.

I will open an issue on texlab as soon as I have some time today to ask their opinion on the matter.

[abzrg]

Modifying the general config did the job. Thank you.

[gennaro-tedesco]

I have opened a discussion in texlab here.