Markup: editorconfig not respected in README.md

Created on 10 Apr 2017  路  14Comments  路  Source: github/markup

I added a .editorconfig and while browsing code in lib/ was affected, code in README.md was not.

https://github.com/socketry/async

Any ideas how to get tab-width set correctly in README.md?

Most helpful comment

Hire me to fix it !! :)

All 14 comments

This has been discussed here too: https://github.com/isaacs/github/issues/170#issuecomment-292793737

:wave: Hiya. Thanks for the link to the issue over there. Since this issue doesn't relate to the github-markup gem itself (which is what this repo is for), I'll close it, but the relevant teams are definitely informed. If you have any other questions or feature suggestions, please reach out to the support team with further questions.

Awesome, thanks!! I didn't know where to file the issue or what to do so I just filed it here, thanks for passing on the information.

@kivikakk This is still an issue - any update? Do you think we can reopen this so we can track the issue?

https://github.com/socketry/async/pull/19

@kivikakk Any update on this?

@ioquatix No update on this. If it gets made a priority we may work on it, but there's a lot going on and this isn't one currently.

@ioquatix This workaround might work (if you needed one): https://github.com/isaacs/github/issues/170#issuecomment-331916162

@iyerusad thanks for the suggestion. I tried it but it doesn't work.

The response I got from github was:

Hi there Samuel,

Thanks for sharing that information with us! After checking with the team, they let me know that we don't currently follow the .editorconfig for rendered markdown files. Other users have written in about this before and we've added this case internally so the team can consider this for future iterations of the product, though I can't make any promises of specific changes.

I hope that helps, but let me know if you have any other questions!

All the best,
Francis

So it sounds like "Yes we know about it, no we aren't doing anything about it right now". Which sucks.

@kivikakk Any update on this? It's been almost a year now :p

No update, alas.

Thanks. Super frustrating. Can I submit a PR somewhere?

The code that processes this stuff is all part of the github.com process itself, so unfortunately not. :(

Hire me to fix it !! :)

So, it's 3 years since the original issue. Any chance of an update?

It's still a problem/not fixed.

Was this page helpful?
0 / 5 - 0 ratings