Open ModProg opened 1 year ago
@ModProg were you able to get ltex running inside markdown files? Because I wasn't :/ Do you mind sharing your config with me? :D
@ModProg were you able to get ltex running inside markdown files? Because I wasn't :/ Do you mind sharing your config with me? :D
lspconfig.ltex.setup {
capabilities = capabilities,
filetypes = { "bib", "gitcommit", "markdown", "org", "plaintex", "rst", "rnoweb", "tex", "pandoc",
"typst" --[[ , "rust" ]] },
cmd = { "ltex-ls" },
settings = {
ltex = {
additionalRules = {
enablePickyRules = true,
motherTonge = "de-DE"
},
["ltex-ls"] = {
logLevel = "severe"
}
}
},
get_language_id = function(ft)
if ft == "typst" or ft == "rust" then
return "markdown"
end
return ft
end,
on_attach = function()
require("ltex_extra").setup {
load_langs = { "en-US" },
init_check = true,
path = "/home/modprog/.config/nvim/ltex",
}
end
}
Describe the bug Shows hint to replace
...
with…
inside Markdown links.Expected behavior More or less, all errors should be disabled inside links.
Sample document
Version information List here the version information of the relevant software.
Additional context/information This probably applies to all markup languages, i.e., LaTeX currently and something like Typst in the future.