Skip to content

Behavior of lintr before/after calling library #415

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

Closed
tvatter opened this issue Oct 1, 2019 · 4 comments
Closed

Behavior of lintr before/after calling library #415

tvatter opened this issue Oct 1, 2019 · 4 comments

Comments

@tvatter
Copy link

tvatter commented Oct 1, 2019

Apologies, I just wanted to make sure that #382 wouldn't be forgotten, since you seem to be almost ready for a release, but the issue has been closed without solution (I think)... Or is there something that I'm completely missing? In this case, sorry to waste your time!

@jimhester
Copy link
Member

It is not going to be addressed, sorry.

@tvatter
Copy link
Author

tvatter commented Oct 1, 2019

Even the Rscript -e 'lintr::lint("test.R")' vs Rscript -e 'library(purrr);lintr::lint("test.R")' behavior?

@tvatter
Copy link
Author

tvatter commented Oct 1, 2019

I mean, I understand that vim isn't a priority, but issues related to this behavior might happen in other editors no?

@MichaelChirico
Copy link
Collaborator

Not enough context in this issue; please open a new issue with a reprex if this is still a concern

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

No branches or pull requests

3 participants