Skip to content
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

If you have a line with tabs it causes a bug in infix_spaces_linter #44

Closed
jimhester opened this issue Feb 3, 2015 · 1 comment
Closed
Labels
bug an unexpected problem or unintended behavior

Comments

@jimhester
Copy link
Member

    if(a == b) {
    1
}
bad.R:1:1: style: Use two spaces to indent, never tabs.
    if(a == b) {
^
bad.R:1:11: style: Place a space before left parenthesis, except in a function call.
    if(a == b) {
          ^
bad.R:1:14: style: Put spaces around all infix operators.
    if(a == b) {
            ~^~~

The arrows are lined up properly on my machine, but there should not be any lint for infix operators in this case.

@jimhester jimhester added the bug an unexpected problem or unintended behavior label Mar 5, 2015
@kgryte
Copy link

kgryte commented May 20, 2017

What is the timeline for pushing these (and other changes) to CRAN? Working with a codebase which uses tab indentation and seeing the false positives noted above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants