Browse Source
Continue to mention that Markdown expands all tabs to spaces before doing anything else and that it guarantees to expaned tabs withing ```-delimited code blocks to 8-character tab-stop positions. Otherwise always talk about "indent" levels in terms of 4 spaces per level. There is far too much Markdown content in existence already that assumes indenting by 4 spaces gives a new indent level. That does not necessarily imply that all the creators of these documents have incorrectly attempted to alter the hard-coded terminal physical tab-stop settings from the fixed value of 8 to something else that the docs seemed to imply was 4. Users with some other tab-stop setting were left out in the cold by the docs. In particular, a tab-stop setting of 3 would have rendered the examples completely useless and the text just plain wrong. With this change the docs no longer assume anything in particular about the user's tab-stop settings. Signed-off-by: Kyle J. McKay <mackyle@gmail.com>master
Kyle J. McKay
8 years ago
2 changed files with 19 additions and 25 deletions
Loading…
Reference in new issue