-
Notifications
You must be signed in to change notification settings - Fork 0
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
Markdownish "header blocks" #56
Comments
Comments need to work between the header and the name:
Allowing a multiline comment to be ended by
Making a multiline comment like the above, but allowing the ==== to start with a hash, seems to capture the fact that "the prior stuff was a comment" succinctly, as well:
|
Because of ___ ending a block, optional separators can be used to enhance clarity, as well:
|
The comment suggestions above make it too hard to scan for the name of the current thing (you scan for the ====, but that's at the end of the comment block). One way we could do comments that even further reduces eye weirdness: anything that's indented after the declaration becomes a comment. Sort of looks like a "sidebar" or quoted comment inn markdown.
|
The markdown syntax has always made me a little uncomfortable because I have to update the number of "=" and "-" when I change the length of the title, making copy/paste difficult. It also takes up more vertical space than I'd like. An alternative that solves both of these concerns:
|
Like this:
===
is a top level header;---
is a second level header; and===
or---
are ended by===
,---
,___
, or EOF.Indent is significant as well:
The text was updated successfully, but these errors were encountered: