-
Notifications
You must be signed in to change notification settings - Fork 186
"error in callr subprocess": lintr-issue for excluded files #1530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @strengejacke, Try this, noting the terminal newline and the indented closing parentheses.
|
Thanks, this works, at least the initial issue is resolved. Now I get a new error:
Couldn't find anything clarifying on the internet yet... |
Line 9, the empty line seems to be causing the problem. By the way, I've read the documentation and I'm wondering if it is possible to specify files with wildcards ( |
Thanks, looks like everything is working as expected now! |
Definitely more evidence for #1210... these issues are hard to debug/explain. (also quite poorly documented at the moment) |
Uh oh!
There was an error while loading. Please reload this page.
I'm using vscode (on Windows) and R 4.2.1, and I have following issue when diagnostics (supported by
lintr
) are enabled. For files that are not yet saved (i.e. do not exist on hard disk), or for files listed in the exclusion list, I get following warning:It's always the first character in the first line that is highlighted (see screenshot).
My
.lintr
file looks like this:I'm not sure if this is a lintr-issue at all, but I thought starting an issue in this repo might be the most appropriate?
The text was updated successfully, but these errors were encountered: