Markdown syntax presents a strong pattern of using blank lines
to separate elements.
Does it?
I hadn’t noticed.
Good call, thank you; having concluded long ago that blank-line separation for
block elements is it a good idea, I had forgotten that most implementations*
were so lax
Not only is [Markdown] dead, it's starting to smell really bad. (Apologies to
Pike.)
It's author appears to have little interest in developing the tool and
participating in the community which uses it.
I'd like to see the community cooperate toward a specification which addresses
the
See this: http://github.github.com/github-flavored-markdown/
I think their assumptions about newlines is way off.
I don't know about their assumptions but I do know that I prefer that behaviour
and it was one of the first departures I made from Markdown syntax.
When I insert a newline in my
Is there a way Gruber could anoint someone ...
Yikes, this sounds ... ;}
I think the community can just cooperate and develop a common tool.
It need not be called Markdown nor strictly supeset Markdown. It simply needs
to be useful to the community. It needs no *one* to control it but without
It depends on what you are trying to do. If you want a simple
multi-column list of corresponding text such as:
Position Team P GD PTS
1 Man Utd 31 46 67
2 Arsenal 31 40 67
3
Clearly one option is to use the same syntax as for images but with
an extra `!`, but what would we use for audio in that case? `!!!`
would be ridiculous.
No need for more syntax. Overload image syntax instead; i.e., insert resource
at URL here.
One can certainly imagine a benefit to the commons if Markdown (and this
discussion list) were not frustrated by Gruber's shadow, but it is just a name.
Whatever it may be called, its associated dialogue and development need not
wither in that shadow.
Making core Markdown consistent may be
Considering the variation of syntax evident in different
implementations/extensions, and the importance of coherence rather than
idiosyncrasy, I imagine the emergence and vitality of a standard syntax (among
other things) would benefit if everyone were familiar with this book:
Basic Markdown (and other languages with even less syntax) may be semantically
sufficient for many applications but as semantic requirements increase, plain
text inevitably requires augmentation with additional metadata/syntax.
I imagine most prefer (as do I) that semantics be inferred, in
(http://daringfireball.net/projects/markdown):
Markdown is a text-to-HTML conversion tool [...]
That may be its author's vision. In any case, it's a pity that so many seem
limited by such.
For some, Markdown is (or at least implies) much more than that, and remains
useful with or without
[1]: http://maruku.rubyforge.org/proposal.html#attribute_lists
I don't understand why the leading colon should be present.
In any case, it seems reasonable to:
- enclose attributes in braces (to indicate text meant for authors/editors
rather than readers)
- append attributes to elements
That's actually what Jonh Gruber proposed a while back when he was
still participating on this list. In his view, only {ref} was
allowed, you couldn't specify attributes directly inline.
Thanks, I couldn't find that thread either and I forgot that he didn't like
inline attributes. I see no
12 matches
Mail list logo
