Skip to content

Formatting preferences and options #17

@briandominick

Description

@briandominick

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:

 * item
 * item

Instead of:

* item
* item

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:

  • Item 1
  • Item 2

Parses to:

*This kind of thing:*
 * Item 1
 * Item 2

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 :-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions