aboutsummaryrefslogtreecommitdiffstats
path: root/lsp/texlab.lua
Commit message (Collapse)AuthorAgeFilesLines
* fix(texlab): buf_change_env not taking input #4116Ian2025-10-091-17/+15
| | | | | | | Problem: `buf_change_env` uses `vim.ui.input` but the input prompt value is never used for `client:exec_cmd` (due to async). Solution: Call `client:exec_cmd` in `vim.ui.input`.
* chore: miscellaneous type fixesIgor2025-08-181-2/+0
|
* chore: add type annotation for configsIgor2025-08-181-0/+1
|
* fix(texlab): update config to 0.11+Dimitris Dimitropoulos2025-08-111-13/+12
| | | | | - Use bufnr and client as arguments of on_attach - Update documentation to indicate implemented commands
* fix(texlab): adapt commands to fit 0.11+ #3991Dimitris Dimitropoulos2025-08-091-70/+34
| | | | | | | - Drop support for <0.11 in vim.lsp.config version - Use vim.ui.input instead of vim.fn.input - Replace explicit border setting in favor to winborder option - Call request as method to avoid deprecation warning - Simplify command setup via for loop
* fix: some `on_attach` callbacks may act on the wrong buffer #3916Dmytro Meleshko2025-06-201-9/+9
| | | | | | | | | Problem: If a server is attached to a non-current buffer by `vim.lsp.buf_attach_client`, then the Language Server-related commands may be created in the current (wrong) buffer. Solution: Always use the `bufnr` arg provided to `on_attach`.
* fix(texlab): add "latexmkrc" root marker for Latexmk projects #3810Philipp Joram2025-04-301-1/+1
| | | | | | | | | | | | Problem: The root directory of Latexmk-based projects is not detected when the local configuration file is called `latexmkrc` (without leading `.`). Solution: Both `.latexmkrc` and `latexmkrc` are valid names for local Latexmk configuration files [1]. Add `latexmk` to the list of possible root markers. [1]: https://mgeier.github.io/latexmk.html#local-configuration-files
* ci(lint): use client:exec_cmd() #3755Justin M. Keyes2025-04-211-5/+5
| | | | Use `client:exec_cmd()` instead of calling `request("workspace/executeCommand")` directly.
* fix: use "Lsp" prefix for config-defined commandsJustin M. Keyes2025-04-211-8/+8
|
* docs: cleanupJustin M. Keyes2025-04-181-7/+8
| | | | | - brief should live at the top of each file - fix indentation for some docs
* fix(docs): docgen.lua reads from `lua/*.lua` #3708Justin M. Keyes2025-04-121-1/+1
| | | | | | | | Problem: Since configs now live in `lsp/`, the docgen needs to be updated. Solution: Read the configs from `lsp/`. Parse the `@brief` docstring to get the docs.
* feat: migrate to vim.lsp.config #3659Lorenzo Bellina2025-04-121-0/+220
Problem: Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy nvim-lspconfig "framework". Solution: Migrate all configs to `lsp/*` variants. The old configs in `lua/lspconfig/` are "frozen". The new configs include these changes: - `commands` field became raw calls to `vim.api.nvim_buf_create_user_command` inside `on_attach`. - `root_dir` became: - `root_markers` whenever the file list was simple didn't need to mach `*` - if the logic was complicated, or needed to match something like '\*.c', it was defined as a vim.lsp.Config `root_dir` callback. - `on_config_change` became `before_init`. I don't actually know if this is the correct approach, but looking around the documentation of `nvim-lspconfig` a saw that it was defined as the function that gets called as soon as the config have `root_dir`, and so I thought `before_init` might be the closest alternative. - `docs.description` became a luadoc `@brief` docstring. - `single_file_support = false`? Co-authored-by: Aliou Diallo <aliou@users.noreply.github.com> Co-authored-by: Justin M. Keyes <justinkz@gmail.com>