.Rmd not being recognised

[JamesOwers]

Just a quick note that files with extension .Rmd is not recognised as RMarkdown. RMarkdown is in languages.yml. Is this problem just because the case is incorrect? R Studio defaults to creating files with this extension.

[arfon]

Could you link to an example of where you're seeing an issue @kungfujam? Linguist is case-insensitive these days for extensions and so this should work. See this gist as an example.

[JamesOwers]

I've added you as a contributor to a private repo of mine exhibiting the issue. See the code folder for the files.

[arfon]

Could you please email a link to the repository? [email protected]

[arfon]

@kungfujam actually, forget that. I just saw the email.

The file is being parsed as Markdown but I don't think we support all of the functionality that comes with RMarkdown (see this thread for background: github/markup#343)

Can you tell me what you're expecting to see compared with what you are seeing?

[JamesOwers]

I'm expecting to see the language details bar include R Markdown.

[arfon]

Ahh OK. This is because RMarkdown is considered prose and so isn't included in repository language statistics. Sorry for any confusion caused by this!

[JamesOwers]

No problem. Thanks for letting me know, feel free to close this. As a side, this may be slightly unfair on github statistics with regards to the popularity of R. All my R code is written in files like this. Code chunks in RMarkdown have a language specifier so this could be leveraged in future.

Feel free to close this issue. Thanks again.

[JamesOwers]

Also, I didn't know you could link to file lines like that...cool!

[arfon]

All my R code is written in files like this.

Yeah this is a good point. Unfortunately we don't have a way to account for this kind of scenario right now.

[EarlGlynn]

Why hasn't GitHub fixed this glaring problem yet? My Rmd files are NOT "Jekyll using Docker image" or "SLSA Generic generator". If GitHub can't guess "right", why don't you let the author decide? Your excuses since 2015 seem weak and cause misleading information about a repository.

[lildude]

@EarlGlynn

If GitHub can't guess "right", why don't you let the author decide?

🤨 we do, and have done so for a very very long time.

A lot has changed in 9 years so it's possibly something easily explained. If you want specific help, please open a new discussion with a link to an example repo and we can take a look. You might want to also take a look at some of the other issues around Rmd first, particularly #5208

Aggressive commenting on a 9 year old issue is also uncalled for.