Post
[UPDATE: this issue was already fixed in {languageserver} 0.3.17, no need for workarounds]
If you write R code with an LSP-powered text editor, you probably use {languageserver}, which delegates diagnostics to {lintr}. If you customize your {lintr} settings at all, perhaps you noticed that your settings are being disregarded.
But there's a fix!
+
@leonardof
I noticed that in Emacs as well. Is the fix coming to languageserver or lintr?
@Mehrad AFAICT the issue was introduced by
https://github.com/r-lib/lintr/commit/58a5c4431702e3ecea75197d38ca7e125358894b
which mentions "Emacs ESS users may need to update to a recent version, e.g. `ESS>20251003`."
So, this is intended behavior, and software relying on {lintr} will have to adjust themselves.
{languageserver} has its own fix since February:
https://github.com/REditorSupport/languageserver/pull/706
UPDATE: it was released in March, but I hadn't updated it yet
…
This is happening because the lintr::lint() function stopped reading its configuration file when it is given string (as opposed to a filename). A workaround has been merged in the {languageserver} source code, but it was not released yet.
Meanwhile, we can include another workaround in our .Rprofile files:
https://github.com/REditorSupport/languageserver/issues/700#issuecomment-3817032792
Os dados dos usuários serão deletados em algumas semanas. Vamos subir uma instância definitiva após finalizar os testes.
