Hello,
As I am using markdown to write documentation, I am often tempted to make
links to terms in definition lists.
Since this is not possible for now (at least in php markdown extra), I was
wondering if this could be a common addition in major implementation
supporting definition lists.
the
This strikes me as a sound suggestion. It would allow us to use a
definition list where currently we'd be forced to use headings and
paragraphs.
On 1 July 2013 08:33, Matthieu Codron codronm+markd...@gmail.com wrote:
Hello,
As I am using markdown to write documentation, I am often tempted to
I don't know about the {#id} part, but MultiMarkdown recognizes that syntax for
definition lists.
Out of curiosity, do I understand correctly that
term
: definition
is already in common usage when people write plain text? I was not aware of
that, so if so, I may start adopting it in my own
* Andy Lee ag...@mac.com [2013-07-01 18:55]:
Out of curiosity, do I understand correctly that
term
: definition
is already in common usage when people write plain text? I was not
aware of that, so if so, I may start adopting it in my own emails etc.
I’ve never seen it in email.
On Jul 1, 2013, at 8:33 AM, Matthieu Codron codronm+markd...@gmail.com wrote:
As I am using markdown to write documentation, I am often tempted to make
links to terms in definition lists.
Since this is not possible for now (at least in php markdown extra), […]
It is. You just have to
I would even go further and (gradually) allow setting {#id .class attr=attr}
for *any* element.
For block elements it would be in the last or following line and for span
elements it would directly follow: e.g. *imporant text*{.special_emphasis}.
Am 01.07.2013 um 17:52 schrieb David Chambers
