-
-
Notifications
You must be signed in to change notification settings - Fork 23
Closed as not planned
Labels
👎 phase/noPost cannot or will not be acted onPost cannot or will not be acted on🙅 no/wontfixThis is not (enough of) an issue for this projectThis is not (enough of) an issue for this project
Description
Initial checklist
- I read the support docs
- I read the contributing guide
- I agree to follow the code of conduct
- I searched issues and couldn’t find anything (or linked relevant results below)
Problem
Some folks like hard tabs. Markdown isn’t good at hard tabs. Maybe there’s a way to support it though.
The problem is that tabs don’t work well with whitespace sensitive languages, because well, certain indentation has meaning, which is sometimes unexpected, or can look different because tabs are displayed differently between team members.
Other languages (say, python) solve this by throwing errors and disallowing mixing tabs and spaces, but we can’t.
Solution
- It’s unclear when tabs should be used.
- It’s unclear if there are some edge cases where roundtripping would fail, there probably are though?
Alternatives
n/a
Metadata
Metadata
Assignees
Labels
👎 phase/noPost cannot or will not be acted onPost cannot or will not be acted on🙅 no/wontfixThis is not (enough of) an issue for this projectThis is not (enough of) an issue for this project