![]() ||Row Hdr 4 |v|rowspan the next cell down|| || Column 3 || rowspan on col1 and an empty cell ||Row Hdr 3 |>|colspan the next two cells || Merge the cells in Col1, 2, and 3 ||Row Hdr 2 |>|colspan the next cell ||Row 2, Col 3 || Merge the cells in Col1 and 2 ||Row Hdr 1 ||Left Aligned||Centre Aligned||Right Aligned|| whitespace should not matter ||-:||:-||:-:||-:|| : to indicate default column alignment as per ME || || Column Header One || Column Header Two || Column Header Three || if this line is followed by a line of ||-|| then it is a header, also, Row Headers are indicated by an optional *empty* A1 cell Idea: Make the divider a double pipe to allow more command flexibility and enable formatting directives within the pipes.Support for colspan and rowspan are considered nice to have by many, but critical for those that need them.Pipe delimited tables appear to be the most common implementation.If enough people are interested, I’m willing to start work on the actual spec for the ideas below and submit them to the project. I have a job need for tables and I am concerned that without them, this specification will have less support than it might (and make life harder for those that need tables where the spec is implemented).Īs this is something relevant to my interests, I’ve started working on building up the ideas I have. I agree CSV makes the writer’s life easier, but I’ll argue that if somebody decides to use Markdown, it’s because it’s as easy to read as it is to write. I think it also makes it more readable in pure text, which is a huge plus when comparing in Git. Even though colspan, rowspan and cell alignment are very nice to have, allowing basic table formatting (creating columns, maybe headers) would still be much better than nothing.Īnd my humble opinion: if I ask someone to make a table using a basic text editor, I expect them to create it using pipes and dashes.Anyway, most IDEs have multiple cursors, so adding/removing spaces on all rows is usually as easy as clicking on the last character of the first row you want to expand, Ctrl+Alt+Click on the last one, then add spaces. The pain of maintaining Markdown tables is smaller than the advantages they bring.This can be shown in a bullet list but becomes very hard to read it’s much better to create columns. As an example, if we create a feature list, me may have the feature ID, the component and the description. Tables are used as a way to show information, not a way to structure it (i.e.Being able to format table has come up fairly early in each case. I thought I’d chime in we use Markdown for public documentation, internal documentation as well as a quick way to keep notes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |