On 22 Mar 2008, at 18:04, Michel Fortin wrote:
2) Write a wrapper for mdtest.php to convert it's output into TAP
format so that it can/will be run as part of my test suite if php5
is available. (Or, I can write php - would you take a patch to
output TAP format as an option so that I don't h
Le 2008-03-22 à 8:49, Tomas Doran a écrit :
The problem with that is that it's pretty hard to require that
everyone installing (the perl version of) Markdown has php5
installed...
Obviously, I can make this optional (and you can only run these
tests if you have php5), however that would m
On 22 Mar 2008, at 02:32, Michel Fortin wrote:
Le 2008-03-21 à 16:39, Tomas Doran a écrit :
So, the *only* things that Text::Markdown currently fails on are
small whitespace changes..
Hum, have you written your own test script?
Yep.
Actually, I'd already written one - I can just 'requir
Le 2008-03-21 à 16:39, Tomas Doran a écrit :
So, the *only* things that Text::Markdown currently fails on are
small whitespace changes..
Hum, have you written your own test script?
I encourage you to use the mdtest.php script if you have PHP 5
installed on your computer. It'll normalize th
On 21 Mar 2008, at 20:39, Tomas Doran wrote:
On 29 Feb 2008, at 05:17, Michel Fortin wrote:
Le 2008-02-28 à 18:04, Yuri Takhteyev a écrit :
Perhaps there is a need for a better _perl_ implementation (or a
few,
competition is fun), but as far as "official" goes, we need a
comprehensive and
On 29 Feb 2008, at 05:17, Michel Fortin wrote:
Le 2008-02-28 à 18:04, Yuri Takhteyev a écrit :
Perhaps there is a need for a better _perl_ implementation (or a few,
competition is fun), but as far as "official" goes, we need a
comprehensive and up-to-date spec and a test suite against which al
* Tomas Doran <[EMAIL PROTECTED]> [2008-03-18 13:15]:
> My preferred solution would be for the 'original' (i.e.
> daringfireball brand) Markdown to have most of the code in a
> module called Text::Markdown, but to supply a script wrapper
> called Markdown.pl which provides the original functionalit
On 18 Mar 2008, at 05:22, John Gruber wrote:
On Mar 16, 2008, at 3:07 PM, Jacob Rus wrote:
It’s harsh but reasonable language in my opinion. If you are
going to make something which is not Markdown (i.e. has other bits
of syntax not specified in John's description of that language),
the
On Mar 16, 2008, at 9:31 PM, Yuri Takhteyev wrote:
If Gruber decides he
"despises" our specification, we should simply call it something other
than "Markdown".
Just to be clear: in that case, you *must* call it something other
than "Markdown".
-J.G.
___
On Mar 16, 2008, at 3:07 PM, Jacob Rus wrote:
It’s harsh but reasonable language in my opinion. If you are going
to make something which is not Markdown (i.e. has other bits of
syntax not specified in John's description of that language), then
you should call it by a name other than “Markd
On 3/16/08, John Gabriele <[EMAIL PROTECTED]> wrote:
> Those three things I think would pretty much satisfy a large swath of
> currently unsatisfied users.
You're close, IMO. Definition lists and an explicit code block
delimiter that doesn't depend on indents (yet nevertheless nests as
written)
> So, if the problem is confusion (or perceived confusion) over the
> name, perhaps the Perl modules could be something like `Text::MD` and
> `Text::MDX` (or `Text::MD::Extra`). I'm sure others here could come up
> with more creative names.
I don't think there is any practical confusion about
On 17 Mar 2008, at 00:37, John Gabriele wrote:
So, if the problem is confusion (or perceived confusion) over the
name, perhaps the Perl modules could be something like `Text::MD` and
`Text::MDX` (or `Text::MD::Extra`). I'm sure others here could come up
with more creative names.
Yeah, I see wh
On Sun, Mar 16, 2008 at 5:07 PM, Tomas Doran <[EMAIL PROTECTED]> wrote:
> On 16 Mar 2008, at 19:07, Jacob Rus wrote:
>
> > Tomas Doran wrote:
> >> John Gruber wrote:
> >>> Tomas Doran wrote:
> >>>
> I'm actively maintaining the CPAN modules Text::Markdown, and
> Text::MultiMarkdown,
On 16 Mar 2008, at 19:07, Jacob Rus wrote:
Tomas Doran wrote:
John Gruber wrote:
Tomas Doran wrote:
I'm actively maintaining the CPAN modules Text::Markdown, and
Text::MultiMarkdown, and longer term, I'd like these to become
the canonical distribution.
I despise what you've done with Te
On Sun, Mar 16, 2008 at 3:07 PM, Jacob Rus <[EMAIL PROTECTED]> wrote:
> Tomas Doran wrote:
>
> > John Gruber wrote:
> >> Tomas Doran wrote:
> >>
> >>> I'm actively maintaining the CPAN modules Text::Markdown, and
> >>> Text::MultiMarkdown, and longer term, I'd like these to become the
> >>> ca
Tomas Doran wrote:
John Gruber wrote:
Tomas Doran wrote:
I'm actively maintaining the CPAN modules Text::Markdown, and
Text::MultiMarkdown, and longer term, I'd like these to become the
canonical distribution.
I despise what you've done with Text::Markdown, which is to more or
less make it
On 16 Mar 2008, at 02:57, Seumas Mac Uilleachan wrote:
LOL that was actually funny :) (No the number is still 42)
Seriously, it is easy to get up in arms when your "creation" ends
up becoming bastardised, whatever the form that may take (for
better or for worse). To be honest, I have not r
LOL that was actually funny :) (No the number is still 42)
Seriously, it is easy to get up in arms when your "creation" ends up
becoming bastardised, whatever the form that may take (for better or for
worse). To be honest, I have not really seen for myself that
MultiMarkdown has a whole lot to
On Sat, Mar 15, 2008 at 7:25 PM, Joseph Lorenzo Hall <[EMAIL PROTECTED]> wrote:
> good stuff... gruber's an asshole, as far as I can tell. best, Joe
Damn. Well, I didn't intend for that to go out to the entire list. I
apologize, but I also found the recent response to be harsh. I'll be
more car
good stuff... gruber's an asshole, as far as I can tell. best, Joe
On Sat, Mar 15, 2008 at 5:27 PM, Tomas Doran <[EMAIL PROTECTED]> wrote:
>
> On 15 Mar 2008, at 02:55, John Gruber wrote:
>
> > On Feb 28, 2008, at 12:34 PM, Tomas Doran wrote:
> >
> >> I'm actively maintaining the CPAN modules
> Wow, that's pretty strong language. I'm glad I'm provoking strong
> opinions, and it's nice to see you actively contributing to
> Markdown's direction ;)
Yeah, that was totally uncalled for. I am sure John could give a rip
about what the list thinks about this kind of contributing, but I am
On 15 Mar 2008, at 02:55, John Gruber wrote:
On Feb 28, 2008, at 12:34 PM, Tomas Doran wrote:
I'm actively maintaining the CPAN modules Text::Markdown, and
Text::MultiMarkdown, and longer term, I'd like these to become the
canonical distribution.
I despise what you've done with Text::Mar
On Fri, Mar 14, 2008 at 11:13 PM, Lou Quillio <[EMAIL PROTECTED]> wrote:
> [snip] But `markdown.pl` is asleep.
Can anyone please point me to the very newest version of
`Markdown.pl`? Is it
http://daringfireball.net/projects/downloads/Markdown_1.0.2b8.tbz
(from May '07) ?
Thanks.
---John
On 3/14/08, John Gruber <[EMAIL PROTECTED]> wrote:
> I despise what you've done with Text::Markdown, which is to more or
> less make it an alias for MultiMarkdown, almost every part of which I
> disagree with in terms of syntax additions.
Agree. But `markdown.pl` is asleep. Bless Michel's (and
On Feb 28, 2008, at 12:34 PM, Tomas Doran wrote:
I'm actively maintaining the CPAN modules Text::Markdown, and
Text::MultiMarkdown, and longer term, I'd like these to become the
canonical distribution.
I despise what you've done with Text::Markdown, which is to more or
less make it an ali
Sorry for the delay in responding, the weekend happened - and it
mostly involved moving my brother in law house rather than reading
email...
On 29 Feb 2008, at 16:04, david parsons wrote:
In article <[EMAIL PROTECTED]>,
Tomas Doran wrote:
Text::Markdown *does not* extend the original Mar
On 29 Feb 2008, at 19:29, Yuri Takhteyev wrote:
Text::Markdown *does not* extend the original Markdown syntax *in
any
way*.
Well, I don't know if agree with this reading.
Good! My original comments were somewhat deliberately inflamatory to
try and provoke discussion - which seems to h
> Text::Markdown *does not* extend the original Markdown syntax *in any
> way*.
Well, I don't know if agree with this reading.
Text:Markdown just imports Text:MultiMarkdown and disables some
features. While it might behave like the original markdown, it goes a
long way in terms of blurring the
On 29 Feb 2008 08:04:31 -0800, david parsons <[EMAIL PROTECTED]> wrote:
>
> What I'd love, too, is to see is to have the spec nailed down and
> blessed by John Gruber, at the very least so people don't have to
> trawl through markdown.discuss and 30 or so individual
> implementation
In article <[EMAIL PROTECTED]>,
Tomas Doran wrote:
>
>On 29 Feb 2008, at 01:00, david parsons wrote:
>
>> In article <[EMAIL PROTECTED]>,
>> Tomas Doran wrote:
>>>
>>> On 27 Feb 2008, at 23:36, Joseph Lorenzo Hall wrote:
Has anyone thought of forking and maintaining Markdown.pl (hopefully
Le 2008-02-29 à 6:35, Tomas Doran a écrit :
On 29 Feb 2008, at 05:17, Michel Fortin wrote:
... And if Markdown.pm keeps evolving (which it should), does
this mean that we would now be on the hook for diffing Markdown.pm
code daily to find out what new features has become official?
That's h
Le 2008-02-29 à 0:23, Andrea Censi a écrit :
Hum, while it's difficult to spec Markdown because its author doesn't
seem so much interested, I think creating a spec for Markdown Extra
is
possible. I could host it on my website, alongside PHP Markdown
Extra,
and I could change PHP Markdown Ex
On 29 Feb 2008, at 01:00, david parsons wrote:
In article <[EMAIL PROTECTED]>,
Tomas Doran wrote:
On 27 Feb 2008, at 23:36, Joseph Lorenzo Hall wrote:
Has anyone thought of forking and maintaining Markdown.pl (hopefully
with Gruber's blessing) to fix some of the known bugs?
I'm actively
On 28 Feb 2008, at 23:04, Yuri Takhteyev wrote:
I'd like to get to a point where I'm a little more happy with the
code, and then I'll start promoting this as a 'true' fork, or, if I
can get John to agree and approve - I'd like to become the
'official'
maintained version which is linked f
On 29 Feb 2008, at 05:17, Michel Fortin wrote:
... And if Markdown.pm keeps evolving (which it should), does
this mean that we would now be on the hook for diffing Markdown.pm
code daily to find out what new features has become official?
That's how I've been keeping in sync with Markdown.pl
> Hum, while it's difficult to spec Markdown because its author doesn't
> seem so much interested, I think creating a spec for Markdown Extra is
> possible. I could host it on my website, alongside PHP Markdown Extra,
> and I could change PHP Markdown Extra to fit that spec.
If you do write a
Le 2008-02-28 à 18:04, Yuri Takhteyev a écrit :
I am sure Markdown.pm will make life much simpler for those using
Markdown with Perl. As a maintainer of a markdown module in a
different language, however, I am not as excited about the idea of a
new "official" implementation.
Same here.
...
In article <[EMAIL PROTECTED]>,
Tomas Doran wrote:
>
>On 27 Feb 2008, at 23:36, Joseph Lorenzo Hall wrote:
>
>> As many of you know, when a piece of open-source software languishes
>> with bugs for 3 years it's often forked Markdown.pl is licensed under
>> the BSD license. (do `>tail -35 /path/
> I'd like to get to a point where I'm a little more happy with the
> code, and then I'll start promoting this as a 'true' fork, or, if I
> can get John to agree and approve - I'd like to become the 'official'
> maintained version which is linked from daringfireball.
I am sure Markdown.pm will
On 27 Feb 2008, at 23:36, Joseph Lorenzo Hall wrote:
As many of you know, when a piece of open-source software languishes
with bugs for 3 years it's often forked Markdown.pl is licensed under
the BSD license. (do `>tail -35 /path/to/Markdown.pl`)
Has anyone thought of forking and maintaining
Hi,
On Feb 28, 2008, at 4:48 PM, Joseph Lorenzo Hall wrote:
On Thu, Feb 28, 2008 at 12:38 AM, Pedro Melo
<[EMAIL PROTECTED]> wrote:>
why not using other "versions" of Markdown, like MultiMarkdown for
example?
Yeah, after I wrote this I realized that the other versions were, in a
sense, fo
* Joseph Lorenzo Hall <[EMAIL PROTECTED]> [2008-02-28 00:40]:
> As many of you know, when a piece of open-source software
> languishes with bugs for 3 years it's often forked
No, that’s not what I know.
What I know is that projects get forked if they have developers
who irreconcilably disagree wi
On Thu, Feb 28, 2008 at 12:38 AM, Pedro Melo <[EMAIL PROTECTED]> wrote:>
> why not using other "versions" of Markdown, like MultiMarkdown for
> example?
Yeah, after I wrote this I realized that the other versions were, in a
sense, forks. One thing that hasn't been "forked" is the syntax
documen
Hi,
why not using other "versions" of Markdown, like MultiMarkdown for
example?
Best regards,
On Feb 27, 2008, at 11:36 PM, Joseph Lorenzo Hall wrote:
As many of you know, when a piece of open-source software languishes
with bugs for 3 years it's often forked Markdown.pl is licensed under
45 matches
Mail list logo
