-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Formatting preferences and options #17
Comments
Wow thanks for this detailed issue! 👍
Not at all, thanks for your ideas! I'm sure we can make this addon better and better 😄
No this is a personal preference but we should avoid the extra space because Asciidoctor lists don't need space before
Indeed a blank line is required, this need to be fixed.
If you check your document you should see a blank line with an heading 2 format. |
Yeah I didn't want to spam you with tickets ;-) I'll make some new tickets tonight! |
Tell me if I'm stepping on any toes, or if you have a better place for this discussion, but I was thinking maybe we could just use a thread to list some things we may or may not consider less-than-optimal about the current formatting, and maybe a wishlist of changes? We can spin issue tickets off for the ones we want to implement, if we want...
\s
before*
?The first thing I noticed is you put spaces before list markup (ordered and unordered).
So:
Instead of:
Is there a reason for this convention? I find it really awkward.
Blank lines before lists?
The conversions are also missing blank lines between the preceding line and the list (ordered or unordered).
So:
This kind of thing:
Parses to:
I think a blank line is required. This just dumps the asterisks and text inline.
Extraneous
==
Sometimes I'm getting
==
on a line on its own. I haven't investigated, but I'm guessing it's maybe from deleted headings or something? We could probably stand to clean up stray^\=\=\n
or something. I don't think this was intentional, right?I'll leave it there for now. Let me know if this is helpful, and create tickets (or I will) to implement these? I'll gladly take some on :-)
The text was updated successfully, but these errors were encountered: