Does ltex-ls support neovim local dictionaries?
See original GitHub issueltex-ls
correctly highlights some words as not spelled correctly. Sometimes, it is wrong and the word is correctly spelled such as a name for example. Neovim
spell checker is fine since the weird word is in a spelling file…
ltex-ls
has a system for adding multiple spelling errors at the same time but I could not figure out if the bindings are available in neovim
. In any case, should we really have to define them twice? In addition, I could not figure how to do it with the neovim
binding 😁
How can I configure ltex-ls
to pick out the neovim spelling files?
Issue Analytics
- State:
- Created 2 years ago
- Comments:22 (6 by maintainers)
Top Results From Across the Web
ltex-ls support local dictionaries · Issue #1443 - GitHub
It basically queries neovim for the list of existing dict files and adds them to the config. I wonder why it does not...
Read more >How can I load a user dictionary into ltex-ls? : r/neovim - Reddit
I've done it using the built-in spellchecker. local path = vim.fn.stdpath("config") .. "/spell/en.utf-8.add" local words ...
Read more >Help wanted, trying to use ltex-ls server with nvim-lsp, code ...
Hello, I'm trying to use ltex-ls with nvim-lsp, the diagnostic works fine. ... Did you manage to let the server read the local...
Read more >Lsp - Neovim docs
Currently only supports a single client. This can be set viasetlocal formatexpr=v:lua.vim.lsp.formatexpr()` but will typically or in on_attach viavim.api.
Read more >Api - Neovim docs
Nvim :help pages, generated from source using the tree-sitter-vimdoc parser. ... Note: empty Array is accepted as a valid argument for Dictionary parameter....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kierun
US_SPELLING_RULE
doesn’t exist. The rules are defined by LanguageTool, most of them can be found on their website.LTEX LS supplies in the diagnostics returned via LSP the rule ID and also a link to the LanguageTool website with more info. VS Code displays this information (in your case, the rule ID
MORFOLOGIK_RULE_EN_US
and the link https://community.languagetool.org/rule/show/MORFOLOGIK_RULE_EN_US?lang=en-US). Don’t know if there’s a way to access the info with coc.nvim. If not, then it’s a coc.nvim issue.@kierun Probably best to just wait until 0.6, then everyone will be on the exact same version and it will be easier to get support from the Neovim collective 😃