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

Figure out a way to support tabs #50

Closed
4 tasks done
wooorm opened this issue Jan 12, 2022 · 2 comments
Closed
4 tasks done

Figure out a way to support tabs #50

wooorm opened this issue Jan 12, 2022 · 2 comments
Labels
🙅 no/wontfix This is not (enough of) an issue for this project 👎 phase/no Post cannot or will not be acted on

Comments

@wooorm
Copy link
Member

wooorm commented Jan 12, 2022

Initial checklist

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

@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Jan 12, 2022
@wooorm
Copy link
Member Author

wooorm commented Feb 11, 2025

Closing, after looking at this for a day, and some discussion with @remcohaszing. The whole point of tabs is that different authors can choose 2 or 3 or 8 or something else. But markdown is whitespace sensitive and the tab stops are always 4. If users display differently, that leads to bugs.

@wooorm wooorm closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
@wooorm wooorm added the 🙅 no/wontfix This is not (enough of) an issue for this project label Feb 11, 2025

This comment has been minimized.

@github-actions github-actions bot added 👎 phase/no Post cannot or will not be acted on and removed 🤞 phase/open Post is being triaged manually labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙅 no/wontfix This is not (enough of) an issue for this project 👎 phase/no Post cannot or will not be acted on
Development

No branches or pull requests

1 participant