Kun Ren

Looks like there's a notable gap between how knitr and lintr handles rmarkdown code chunks. ```` ```{r} x

I've already raised the linked issue above so there's no need for you to file a new one.

Are you using the latest dev of lintr? Could you try using the latest dev?

What do you get with the following: ```r file

Looks like your system locale is not consistent with your encoding in R? What happens if you use the following: ```r styler::style_file("your-file.R") ```

Looks like languageserver session and your typical R session does not have the same locale since language server is not started from a terminal with specific encoding settings.

This is more of inconsistencies between [styler](https://github.com/r-lib/styler) and [lintr](https://github.com/jimhester/lintr). We are using styler to do formatting and lintr for diagnostics.

It is perfectly possible to improve the parsing so that we also capture the internal structure of the R6 class definition by going through the syntax tree of `R6Class` calls.

The tricky part of this is handling the source refs of non-top level expressions in `parse_expr`. In `parse_expr`, we use R's language object representation of syntax tree so that it...

Looks like it is a bug of callr? Let me try if I could reproduce it.