On Jul 13, 2011, at 1:12 PM, Alan Hogan wrote:
On Wednesday, July 13, 2011 at 12:54 PM, David Parsons wrote:
Adding classes ids are kind of hideous. What I did with discount
was to extend the []() syntax to allow class: and id: pseudo-classes
(like [postoffice](class:caps) or version
On Jul 13, 2011, at 8:33 PM, Alan Hogan wrote:
On Wednesday, July 13, 2011 at 8:00 PM, David Parsons wrote:
You're looking at markdown like some sort of intermediate
language that's not designed for writing; I'm trying to
use existing constructs to add marginally useful features
without
. As markdown sits
right now, stripping away the css just results in a more vanilla
presentation.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
On Jun 6, 2011, at 11:23 PM, David Chambers wrote:
David Parsons o...@pell.portland.or.us wrote:
John Gruber might have some opinions about this; I'd certainly be
more attentive about list merging if the reference dingus changed to
split them.
Every member of this group writes a lot
behavior or the other :-)
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
it. It took me ages to figure out where that list
was coming from in the middle of the paragraph. Eventually found the
hard return and deleted it.
That's a different issue, though, which has bitten
enough people so that it's actually mentioned in the
syntax document on daring fireball.
-david
: 2011-05-30T15:00-07:00
Heck, Waylan, you've done it again. This is extremely readable and
allows the `pubdate` attribute to be included if desired.
But you don't like:
David Parsons o...@pell.portland.or.us wrote:
That looks like it would be a good place for a pseudo-protocol:
[two
for a pseudo-protocol:
[two days ago](time:2011-05-30T15:00-07:00 May 30th, if you care)
This would have the advantage of being fairly unambiguous, instead
of superimposing a magic time string over the existing linkyformat.
-david parsons
to the interesting part of testing
it and making sure it works to his satisfaction.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
.)
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
that support a please markdownify me! flag for html block elements;
if you add those flags to your generated
html, you will have a program that can be pipelined like:
simontable document.text | markdown document.html
Don't convince us with words. Convince us with code.
-david
to maintain my web pages.
The existance of the markdown discussion list is pretty good evidence
that there's a desire to work together.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo
text into a table, but the *readers* are in
inconvenienced n many times by having to read tables of HTML.
I presume that the readers will be reading the
entire document in html, via a viewer that renders
html into a more pleasing format.
-david parsons
useful for getting
ones fingers into the pie.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
an idea if it's too
complicated. Working code is the best test of the complexity of a
design.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
, just because that's now it works.a clean new syntax
that
doesn't take how people mark up text documents into consideration is a
syntax that needs to be taken back for revision.
-david parsons
___
Markdown-Discuss mailing list
Markdown
about putting a dummy html comment in the middle, like:
Code block
One
!-- two code blocks, please --
Code block
Two
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
with the first one
(the extra-inelegant replacement is code /code, which
will sail happily through at least one markdown processor.)
-david parsons
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net
On Feb 13, 2011, at 6:19 PM, Sherwood Botsford wrote:
How _would_ you emphasize a single asterisk?
_*_ ?
-David Parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown
compresses
nbsp;
no matter how many codes and pres I wrap around them.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
want to share with you.
Old Syntax: (mailto:$mailadress@$mailhost)
New Syntax: (mailto:$mailadress@$mailhost[ My Name)
How is this better than the traditional [name](mailto:address)
syntax?
-david parsons
___
Markdown-Discuss mailing list
:/~orc/klaxon.wav)
without introducing (another form of) ascii spaghetti to the language.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
markdown from a general-purpose writers tool
into some sort of boutique plugin. I can't really see that this
would count as an advantage to _anyone_ who currently uses markdown.
-david parsons
___
Markdown-Discuss mailing list
Markdown
in a dozen languages. I am
unsure about how a common tool can be made here.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
in the community which uses it.
He's got a Perl implementation that works for him, and there are many
other implementations that are basically compatable with his code
test suites. There's not much he needs to do, so why should he run
around and do busywork?
-david parsons
, but
still easy. It will give me an excuse to release a 1.6.3
sometime next week.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
). Backslashes don't escape `s inside code spans.
Backslash? Wait, is that ^A I see supposed to be
the character 01h or a backslash?
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net
with a text editor that forces line-wrap at 80 characters.
-david parsons
But, well, we can't change it now.
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
that somebody has, but where are you going to find a keyboard
that has all of those unicode glyphs on it, or would you have to write
a markdown preprocessor that takes a table made up of symbols found on
a keyboard and convert it into the unicode characters?
-david parsons
for threaded discussions.
It looks like what Wikipedia does is to use lists for indentation.
I don't know if the indentation is done by the wiki or if people
are expected to hand-format their followups, but it seems a bit
out of the scope of what markdown is capable of doing.
-david
In article 3561cc6d0908042326j34319e38wc333e41e3a074...@mail.gmail.com,
Dan Dascalescu markdown-discuss@six.pairlist.net wrote:
How could one indent (not quote) a block of text?
This is commonly done in Wikipedia with one or more colons at the
beginning of the line, and is very handy for
parsing unusual lists (I can get it to generate
improper html by putting ''s inside of a list:
- hi
- there
...) and you might be better off just having your implementation
do list processing in the way you see best.
-david parsons
a table of contents from the headers and lets you get to it
via a library call,) the python implementation has one, as
does pandoc.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net
recent version of the test suite, or is
there a newer one out there?
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
In article 712ee2f9-aa00-46ec-b4e2-ea5924ae1...@kineticode.com,
David E. Wheeler markdown-discuss@six.pairlist.net wrote:
On Feb 26, 2009, at 5:00 AM, bowerb...@aol.com wrote:
i hope you will agree with _my_ obvious counter:
monospaced fonts aren't the only way to do that.
indeed, they aren't
to unreadable, so the bizarre reformatting of the list is a good way
to encourage cleanup of the source text.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown
to the leading
indent.
so it would be bad if that broke nesting.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
In article [EMAIL PROTECTED],
John Fraser markdown-discuss@six.pairlist.net wrote:
On Mar 5, 2008, at 2:38 PM, david parsons wrote:
When I write a really long list,
* sometimes, after a particularly long and
detailed list item, I'll lose track of the
exact indentation
invalid XHTML for this case:
***strong** in emph*
I can't say I'm terribly surprised at this; the code that parses
emphasis blocking is fairly naive and needs to be changed from a
railway signalling generator into one that does proper blocking.
-david parsons
will need to follow the spec because that's not
how Markdown works.I can't imagine any other way to actually write
the language.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo
as it might seem.And plain english has the advantage
that it doesn't require knowledge of the implementation language to
understand the document.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http
, which are squirreled away by the
library and can be retrieved by web-page generators.
Despite all this, discount still passes MarkdownTest_1.0 when
I turn extensions off and turn --tidy on.
-david parsons
___
Markdown-Discuss mailing list
In article [EMAIL PROTECTED],
John Fraser markdown-discuss@six.pairlist.net wrote:
On Mar 1, 2008, at 1:19 PM, david parsons wrote:
I agree that Markdown needs to be defined unambiguously, but I don't
think that's feasible with plain English in the loop. For something
as complex and flighty
In article [EMAIL PROTECTED],
Tomas Doran markdown-discuss@six.pairlist.net wrote:
On 29 Feb 2008, at 01:00, david parsons wrote:
In article [EMAIL PROTECTED],
Tomas Doran markdown-discuss@six.pairlist.net wrote:
On 27 Feb 2008, at 23:36, Joseph Lorenzo Hall wrote:
Has anyone thought
a stationary reference that can be used for auditing.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
that contain
wonky items? I ignored that behavior of the standard when I
wrote my markdown, and use as wrap everything for urls.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman
with their and they're) coming over in
[a](ed: was `an` -- `an` is only before a vowel) quarter-hour.
might be a little more readable than the thicket of []'s that
Mr. Raskin proposed.
-david parsons
___
Markdown-Discuss mailing list
Markdown-Discuss
47 matches
Mail list logo
