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

Tab characters are handled differently from current implementations #2

Closed
roop opened this issue Oct 7, 2013 · 0 comments
Closed
Assignees

Comments

@roop
Copy link
Member

roop commented Oct 7, 2013

Tab characters should be expanded based on their position in the line, similar to how text editors do tab-expansion (like 'set expandtab' in vim). This is how almost all current implementations handle it. Handling unexpanded tabs in the parser is possible and more correct but complex, and potentially inconsistent with almost all current implementations.

The syntax guide (user documentation) should also be updated to reflect this. Particularly, the syntax guide should not mention optional tab-based syntactic constructs (i.e. instead of "use 4 spaces or 1 tab", just say "4 spaces").

Ref: http://six.pairlist.net/pipermail/markdown-discuss/2013-October/002956.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant