,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
, be necessary to use unregistered
experimental types. Therefore, use of both x- and x.
forms is discouraged.
[1]: http://tools.ietf.org/html/rfc4288#section-3.4
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
:
I'm not volunteering (I'd be horrible)... just seeing if it's
time to have that discussion.
If you’re not volunteering and no one else does, then “having
that discussion” is pretty pointless.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
that we can have the freedom
to reduce the flexibility of the syntax.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
* Yuri Takhteyev [EMAIL PROTECTED] [2008-03-03 02:20]:
What about setting value on each li instead?
Equally deprecated.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
to agree on all possible cases, would this
spec not be unambiguous? And is it not yet obviously the case
that such a spec would not need to be inflexible about the syntax
it admits?
Why then does the fallacious argument that a spec would represent
a loss for the user continue?
Regards,
--
Aristotle
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
to this:
emhello strongdear/strong boy/em
Really.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
to specify.
* Waylan Limberg [EMAIL PROTECTED] [2008-03-06 17:00]:
Aristotle Pagaltzis wrote:
a human reader see in that text? Based on the visual
apperance I think I would make it translate to this:
emhello strongdear/strong boy/em
Ah, so your assuming the parser should
to handle Markdown.pl.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
doesn’t cross the language barrier right along
with the code, it breaks down at these points.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman
an unbreak-me config
option to make it recognise the semicolon.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
and Markdown Extra processors. The scope of the problem is much
smaller in such a scenario, enough so to be perfectly tractable.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
* Yuri Takhteyev [EMAIL PROTECTED] [2008-05-23 08:35]:
* Aristotle Pagaltzis [EMAIL PROTECTED] [2008-05-23 05:40]:
I also agree with your opposition to them; if anything, one
should filter the *output* of a Markdown-to-HTML conversion
so that it won't matter whether people write literal `em
* Yuri Takhteyev [EMAIL PROTECTED] [2008-05-24 21:35]:
* Aristotle Pagaltzis [EMAIL PROTECTED] [2008-05-24 11:15]:
If your XHTML parser has a streaming input mode, you can
couple your Markdown converter directly to the XHTML parser
and feed the HTML output to it as you go. If the XHTML
postprocessing.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
* Kragen Javier Sitaker [EMAIL PROTECTED] [2008-06-08 18:00]:
On Sat, 7 Jun 2008 17:42:53 +0200, Aristotle Pagaltzis wrote:
* Kragen Javier Sitaker [EMAIL PROTECTED] [2008-06-07 09:40]:
Stylesheeting comes naturally. I just put a `style`
element at the top with a few lines inside
test whether their bugfix breaks
previously working stuff?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
with an ordered list nested inside its 2nd
item.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
, that makes it easier for people,
because it demands that they be clear in their thought.
if they are ambiguous about what they want, do nothing!
This entirely contradicts Markdown’s purpose and philosophy.
That is my opinion too.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
* Waylan Limberg [EMAIL PROTECTED] [2008-09-08 17:15]:
On Sun, Sep 7, 2008 at 10:14 PM, Aristotle Pagaltzis [EMAIL PROTECTED]
wrote:
Any inferred nesting would have to subordinate them to an implied
3rd item in the surrounding unordered list that is not written
out in these examples
, as far as I saw, with the
exception of “Bowerbird” who made up option D, everyone voted for
C, with some of us calling A a reasonable secondary option. (Did
I misread the discussion?)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown
the items
anyway
If you kept Markdown documents in a version control system, you
would avoid that. :-) (Renumbering items when shifting them
around can cause a lot of noise in diffs from spurious changes.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
/dive_into_markdown
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
* Louis-David Mitterrand [EMAIL PROTECTED] [2008-10-23 13:55]:
What is the fix?
You have to patch Text::Markdown to add that line to the block
the regex is in. I see you have already filed a bug against
Text::Markdown, excellent.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
* David E. Wheeler da...@kineticode.com [2009-02-19 02:00]:
Yeah, okay. […] D’oh! Oh yeah!
Told you it is a thorny problem. :-( It *looks* simple, yeah…
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
* Aristotle Pagaltzis pagalt...@gmx.de [2009-02-28 16:18]:
You can make a lot easier to write with a very simple tweak:
Sorry for the noise. Someday I’ll consistently remember to read
the whole thread before following my impulse to respond.
Regards,
--
Aristotle Pagaltzis // http
* Suraj Kurapati sun...@gmail.com [2009-09-09 06:20]:
What if Markdown used Unicode characters to express tables
in this manner?
Then I would still write my tables using HTML tags.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
importantly, the problem was not to display a header across
two lines in the rendered document, it was being able to write
the header across several lines in the source document (and still
have a single tag in the rendered document), so your solutions
aren’t.
Regards,
--
Aristotle Pagaltzis // http
* Waylan Limberg way...@gmail.com [2010-03-02 18:25]:
To be honest, I can't think of any elegant way to do multi-line
setext headers,
Exactly.
but multi-line hash headers should be easy.
I’ll agree with that.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
any run of ticks, not just the one or two that I read
from the standard.
According to the spec it *is* supposed to match any number of
ticks – but they are supposed to be the *same* number on both
ends.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
a principal designer with a good enough sense
for its spirit and enough of a voice to gain the authority to
have his or her mandates followed.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss
* Dietrich Epp d...@zdome.net [2010-03-06 22:40]:
I think it's about time that markdown had its own IANA media
type.
Most people just use text/x-markdown, I think.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss
only be done badly, and so should not be
done at all.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
it is as above: I think that
tables fundamentally cannot be both easy to edit and easy to read
within the constraints of plaintext.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss
’ mix of good and bad to
Betamax’ mix of good and bad. End of story.
It’s like saying webmail is inferior to desktop mail clients.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
the header tags for smaller/bigger text, people will abuse
them for setting large or small text that’s not a headline.
For similar reasons, I’d also whitelist `tt`.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing
formats, just omit
them from your supported subset of HTML. That way you support
real Markdown, not a crippled Markdown-lookalike syntax.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss
spits out HTML. Any highlighter that can fish `pre`
and `code` out of HTML and highlight it will work on the
Markdown’s output. There is no need to wedge any of this into
Markdown itself.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
advertises Markdown support.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
* Waylan Limberg way...@gmail.com [2011-05-05 03:25]:
However, most projects I'm aware of use '.md' or '.markdown'.
`.mkd` and `.mkdn` are also popular. I’ve seen `.mdwn` also,
and I think even `.mdn` though I’m not sure about that one.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
. not triggering emphasis on word-internal
underscores.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
* Michel Fortin michel.for...@michelf.com [2011-05-14 23:40]:
Le 2011-05-14 à 15:55, Aristotle Pagaltzis a écrit :
An anatomy of a loss of interest:
2004 279
2005 153
2006 78
2007 25 (21 in the first half of the year)
20086 (2 in Feb; 4 in a row in mid-March
* bowerb...@aol.com bowerb...@aol.com [2011-10-15 22:00]:
brett has accomplished more in the last three months than this
listserve accomplished in the last three years.
Well, we can agree he has achieved more in three months than you
have in a decade of talking.
* bowerb...@aol.com bowerb...@aol.com [2011-10-16 21:40]:
how will i ever be able to manage without your valuable input?
You don’t need it. You’ll take the world by storm same as you did
the last five times you created a revolution. With or without my
participation, the outcome won’t differ.
* Clint Laskowski clint.laskow...@gmail.com [2011-12-11 16:15]:
Thoughts?
You are looking for orgmode. Markdown is the wrong tool.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
* Sherwood Botsford sgbotsf...@gmail.com [2013-04-18 17:20]:
(I wish that this was a toggle that could be set in a .mmdrc file.
There are a lot of things that I wish I could set in an .mmdrc file.)
That would be bad for Markdown.
___
Markdown-Discuss
* Sherwood Botsford sgbotsf...@gmail.com [2013-04-20 16:20]:
It's actually worse than that, because for me MMD is actually a module
in Template Toolkit. So my information is MD markup wrapped in
a preface and epilog of template toolkit.
[% FILTER replace('[^/][^]*\K', ' markdown=1') # Perl
* 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.
Markdown
document in unformatted form.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
they have to go through before they can assign a truthful MIME type to
their documents?
Metadata is hard. Let’s go shopping.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
fenced code blocks. (I feel this is
especially so for backtick fences. Tilda fences seem to have some remote
likelihood of being used as an innocuous part of a non-fenced-code-block
document.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
that’s invalid in the
same way, to then be interpreted by the browser however the browser may.
My guess is that the majority of implementations behave equivalently to
this, though depending on their design they could differ completely.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org
evident because I already
have directories full of files with nothing but Markdown in them.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman
it chooses
(it could use parsing, or not).
I would argue that the only sufficiently generic term that will apply to
software in all of these cases is, in fact, “processor”.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss
by the existing implementations.
That would exclude parsers, indexers, etc. whose output is not another
form of the document.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
and not anyone else’s. There is no “ecosystem”
about that.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
on that.
Great, now you just need to convince some sufficient number of Markdown
converter authors/maintainers to support this extension. :-)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
, their derivation *must* be
performed by code from the environment which has sufficient information
to be able to do that.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https
arkdown/tree/sources
I have been intending to ping John about this, as well as to put out
a public call for anyone who happens to still have other releases,
but that hasn’t happened yet. Nevertheless, what’s there is at least
a start.
Regards,
--
Aristotle Pagaltzis // <http://
by introducing an
exception, that trimming spaces from code spans only applies when more
than a single backtick is used as the delimiter. But that would make the
rules more complicated, and it only allows you to use your workaround,
which is pretty cruddy
65 matches
Mail list logo
