At the end of the day I probably will maintain my own copy, with some
changes, of Markdown. I also don't want to break the syntax. One of my
previous mails I mentioned a way that makes the Markdown more useable (by
being able to usefully use nl2br on the Markdown'ed string) without breaking
the
Le 2008-07-22 à 2:47, Jurgens du Toit a écrit :
At the end of the day I probably will maintain my own copy, with some
changes, of Markdown. I also don't want to break the syntax. One of my
previous mails I mentioned a way that makes the Markdown more
useable (by
being able to usefully use
* Michel Fortin [EMAIL PROTECTED] [2008-07-22 12:40]:
Have you considered what will happen to code blocks with
`nl2br`?
That can be fixed by *replacing* newlines with break tags so
there aren’t any literal linebreaks. View Source won’t be pretty
but the browser rendering will be correct.
You can change [peg-markdown] to behave the way you want (without
problems in code blocks) just by adding one line:
--- a/markdown_parser.leg
+++ b/markdown_parser.leg
@@ -384,6 +384,7 @@ Entity =( HexEntity | DecEntity | CharEntity )
{ $$ = mk_str(yytext); $$-key = HTML; }
I'm just throwing ideas around...
I don't think that if something is difficult to test, it shouldn't be
implemented. It would be the same as saying that to bake is too difficult,
so I'll just go without the cake. I do, however, agree with the fact that if
you get different versions of Markdown
* Jurgens du Toit [EMAIL PROTECTED] [2008-07-21 09:05]:
I don't think that if something is difficult to test, it
shouldn't be implemented.
You mean it’s fine for people to give you software that might or
might not work, and they don’t know which? What happens if you
report a bug and they can’t
I mean that difficulty to test must not impair the development process.
Yes, sure, don't roll out software that hasn't been tested, but, as Markdown
is issued under an open source license, there's who knows how many people
who might want the untested functionality, and who will be willing to test
I think the answers you're getting here will make more sense if you re-
read John Gruber's description of Markdown's history and purpose, at
daringfireball.net.
On 21 Jul 2008, at 6:32 AM, Jurgens du Toit wrote:
I mean that difficulty to test must not impair the development
process.
Yes,
Le 2008-07-21 à 6:32, Jurgens du Toit a écrit :
I mean that difficulty to test must not impair the development
process.
Yes, sure, don't roll out software that hasn't been tested, but, as
Markdown
is issued under an open source license, there's who knows how many
people
who might want the
Jurgens du Toit wrote:
If you look at a formatter like tidy, it's got a lot of options where you
can turn certain behaviour on and off, making it much more useable for a lot
of people. Wouldn't it improve the usability of Markdown if these kind of
options were present?
No, it would be a
Kewl.
If you look at a formatter like tidy, it's got a lot of options where you
can turn certain behaviour on and off, making it much more useable for a lot
of people. Wouldn't it improve the usability of Markdown if these kind of
options were present?
J
On Fri, Jul 18, 2008 at 3:50 AM, Michel
Le 2008-07-18 à 5:13, Jurgens du Toit a écrit :
Kewl.
If you look at a formatter like tidy, it's got a lot of options
where you
can turn certain behaviour on and off, making it much more useable
for a lot
of people. Wouldn't it improve the usability of Markdown if these
kind of
options
Hey :)
Is it a bug or a feature that the following two texts get formatted
differently?
My shopping list
+ Bread
+ Milk
+ Cheese
My shopping list
+ Bread
+ Milk
+ Cheese
In the first one, the list doesn't get converted to an unordered list, while
in the second, it does...
It occurs in both
Ok.
Is it possible to modify the code to do that? Can you point me in the right
direction?
It's something I'd realy like to be able to do, even if it is a configurable
options.
Another thing, is it possible to convert newlines to br/ tags? I tried
nl2br before and after passing the string to
On Thu, Jul 17, 2008 at 9:49 AM, Jurgens du Toit
[EMAIL PROTECTED] wrote:
Ok.
Is it possible to modify the code to do that?
Very probably, but you may not want to. My impression is that there's
a lot of tradeoffs in Markdown between it trying to do what you mean
and it requiring non-ambiguous
On Thu, Jul 17, 2008 at 4:11 PM, John Gabriele [EMAIL PROTECTED] wrote:
On Thu, Jul 17, 2008 at 9:49 AM, Jurgens du Toit
[EMAIL PROTECTED] wrote:
Ok.
Is it possible to modify the code to do that?
Very probably, but you may not want to. My impression is that there's
a lot of tradeoffs
Jurgens du Toit [EMAIL PROTECTED] 08-07-17 20.12
Any special reason why single newlines don't get converted to br/? I'm
thinking that if it happens right at the end of the manipulations, and
newlines between closing and opening block tags (such as \p\np) get
ignored, it will work? Or, actually
Exactly that, yes.
On Thu, Jul 17, 2008 at 10:00 PM, Jan Erik Moström [EMAIL PROTECTED]
wrote:
Jurgens du Toit [EMAIL PROTECTED] 08-07-17 20.12
Any special reason why single newlines don't get converted to br/? I'm
thinking that if it happens right at the end of the manipulations, and
Jurgens du Toit [EMAIL PROTECTED] 08-07-17 22.13
Exactly that, yes.
Well, there is a good reason why Markdown doesn't do this. Many
prefer to use a plain text editor which doesn't wrap text (I for
example prefer my text files this way) and we insert hard new
lines to keep the lines from
Le 2008-07-17 à 10:11, John Gabriele a écrit :
On Thu, Jul 17, 2008 at 9:49 AM, Jurgens du Toit
[EMAIL PROTECTED] wrote:
Ok.
Is it possible to modify the code to do that?
Very probably, but you may not want to. My impression is that there's
a lot of tradeoffs in Markdown between it trying
Le 2008-07-17 à 16:41, Jan Erik Moström a écrit :
Well, there is a good reason why Markdown doesn't do this. Many
prefer to use a plain text editor which doesn't wrap text (I for
example prefer my text files this way) and we insert hard new lines
to keep the lines from becoming too long.
21 matches
Mail list logo
