Skip to content

Conversation

@pascal-sauer
Copy link
Contributor

According to https://github.com/r-lib/lintr/releases with lintr 3.3.0-1:

lint() no longer picks up settings automatically in ad hoc invocations like lint("text\n") or lint(text = "str"). You should set parse_settings=TRUE to force settings to be read. Emacs ESS users may need to update to a recent version, e.g. ESS>20251003.

This means .lintr files are ignored for the linting vscode does in the background by default. Explicitly setting parse_settings = TRUE (as suggested in this PR) helps.

@pascal-sauer
Copy link
Contributor Author

I'm unsure how the maintainers (I guess @renkun-ken @randy3k) want to proceed with this PR. Do you want me to bring this PR into a state so it can be merged, and what steps would that entail? Or would you rather implement a fix yourself (totally fine by me!)?

@eitsupi
Copy link
Contributor

eitsupi commented Dec 19, 2025

@ManuelHentschel Sorry for bothering you, but could you take a look at this?
Other members with commit access appear to be inactive.

@mcanouil
Copy link

mcanouil commented Jan 29, 2026

In the absence of updates, see a workaround in:

Copy link
Member

@renkun-ken renkun-ken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants