Re: Block quotes with a blank line between them get merged

Jacob Rus <[EMAIL PROTECTED]> wrote on 10/20/06 at 12:37 AM: > But I posit that this is really a non-issue, as there is > almost no use for multiple consecutive code blocks with no > commentary in between. I have never seen such a pattern used, > and if in the one time in a million it comes up, t

Re: Block quotes with a blank line between them get merged

A. Pagaltzis <[EMAIL PROTECTED]> wrote on 10/19/06 at 7:44 PM: > > ~ function db_like($first, $pattern) { > > ~ $pattern = preg_quote($pattern); > > ~ $pattern = preg_replace('/(? > ~ $pattern = preg_replace('/(? > ~ return preg_match('{^'.$pattern.'$}

Re: Doubt about standard syntax

A. Pagaltzis <[EMAIL PROTECTED]> wrote on 12/29/06 at 7:21 PM: > > In other words, a paragraph, once started, eats everything > > until a blank line? > > Except blockquotes and headings. And I think that should change. I think every block-level element should be separated by a blank line. -J.G.

Re: Escaping inside code blocks?

Andrea Censi <[EMAIL PROTECTED]> wrote on 12/30/06 at 11:13 AM: > Consider the input: > --- > `There is a literal backtick (\`) here.` > > `There is a literal backtick (\\`) here.` > > ``There is a literal backtick (`) here.`` > --- > > The documentation says that line 2 and 3 are equivalent. >

Re: Leading blank lines in codeblocks ignored?

Andrea Censi <[EMAIL PROTECTED]> wrote on 12/29/06 at 10:49 PM: > Markdown.pl ignores the leading blank line in the code block. > Is this intended behaviour? Yes. -J.G. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pair

Re: Maruku: a better Markdown interpreter for Ruby.

Bob Hutchison <[EMAIL PROTECTED]> wrote on 12/29/06 at 12:04 PM: > > While I can live with the HTML style it would be really nice to > > have something else > > Especially something that didn't pass the comment through to the > generated HTML. Right. That would clearly be the biggest reason to

Re: Markdown markup question

Jan Erik Moström <[EMAIL PROTECTED]> wrote on 12/29/06 at 5:30 PM: >Note that there are two code tags for the list, is this to be >expected? have I missed something? is it a bug? or should I >just learn to live with it? Bug, for sure. First time I've seen it, though. Thanks for the report. --

Re: problems with escaping backticks

On Sun, 31 Dec 2006, A. Pagaltzis wrote: > Get the 1.0.2 beta. > > You can confirm with the Dingus on the Markdown project pages > that this is fixed in the latest version. Thanks. What is the download URL for this? ___ Markdown-Discuss mailing list M

Re: best way to use emphasis within code?

On Sat, 30 Dec 2006, Michel Fortin wrote: > Le 2006-12-30 à 14:13, Jeremy C. Reed a écrit : > > > I want to use fixed font like a code block but also use italics and > > bold > > at same time. > > > > For example in HTML: > > > > $ mail -u user > > > > What is the best way to do this in markdow

Re: best way to use emphasis within code?

Le 2006-12-30 à 14:13, Jeremy C. Reed a écrit : > I want to use fixed font like a code block but also use italics and > bold > at same time. > > For example in HTML: > > $ mail -u user > > What is the best way to do this in markdown, especially if I have > several > lines of content that needs

Re: problems with escaping backticks

* Jeremy C. Reed <[EMAIL PROTECTED]> [2006-12-30 20:15]: > What is the fix for this? Get the 1.0.2 beta. You can confirm with the Dingus on the Markdown project pages that this is fixed in the latest version. Regards, -- Aristotle Pagaltzis // _

Re: Revised 2005 proposal for meta-data

Le 2006-12-30 à 11:48, Andrea Censi a écrit : >> ## Header ## {boo class="override"} >> >> {boo}: .boo style=color:green;font-weight:bold > > Seems reasonable. So the special case is: ".class1" adds "class1" to > the class attribute. Exact. > OK - I didn't like "tag". So formally "boo"

Re: best way to use emphasis within code?

* Jeremy C. Reed <[EMAIL PROTECTED]> [2006-12-30 20:15]: > I want to use fixed font like a code block but also use italics > and bold at same time. > > For example in HTML: > > $ mail -u user > > What is the best way to do this in markdown, especially if I > have several lines of content that ne

Re: Maruku: a better Markdown interpreter for Ruby.

Reply to A. Pagaltzis <[EMAIL PROTECTED]> 06-12-30 17:17: >That doesn't seem problematic to me. If you write documents that >use features that are not part of Markdown, and the formatter >documentation makes it clear that the features you are using are >not part of Markdown, then you know what you

[jo...@debian.org: Bug#405058: does not properly support nested divs in inlined html]

Howdy, The attached bug report was sent to the Debian bug tracking system. If you please preserve the CC to [EMAIL PROTECTED] on any responses? - Forwarded message from Joey Hess <[EMAIL PROTECTED]> - From: Joey Hess <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]>

problems with escaping backticks

I can't escape backticks if on a line with other code: $ echo 'maybe use `fixed face` for `/path/to/file` by using \`back ticks\` around it' | /usr/pkg/bin/Markdown maybe use fixed face for /path/to/file by using \back ticks\ around it and this is even more wrong: $ echo 'maybe use `fixed face

best way to use emphasis within code?

I want to use fixed font like a code block but also use italics and bold at same time. For example in HTML: $ mail -u user What is the best way to do this in markdown, especially if I have several lines of content that needs to be spaced out correctly? Thanks Jeremy C. Reed

Re: Revised 2005 proposal for meta-data

> {#myid .class1 .class2} > {id=myid class=class1 class=class2} > {id=myid class="class1 class2"} > > In my current implementation, the first and the last one are > equivalent, but not the one in the middle: the second class will > override the first one. I think it's more coherent t

Re: Maruku: a better Markdown interpreter for Ruby.

* Jan Erik Moström <[EMAIL PROTECTED]> [2006-12-30 16:40]: > Reply to A. Pagaltzis <[EMAIL PROTECTED]> 06-12-30 16:30: > >The problem is that there is effectively no spec. There is a > >format documentation, but there are many cases it does not > >specify precisely (or at all). In that case, only t

Re: Maruku: a better Markdown interpreter for Ruby.

Reply to A. Pagaltzis <[EMAIL PROTECTED]> 06-12-30 16:30: >The problem is that there is effectively no spec. There is a >format documentation, but there are many cases it does not >specify precisely (or at all). In that case, only the behaviour >of Markdown.pl can be of guidance; but it is not cle

Re: Maruku: a better Markdown interpreter for Ruby.

* Jan Erik Moström <[EMAIL PROTECTED]> [2006-12-30 16:05]: > Reply to Andrea Censi <[EMAIL PROTECTED]> 06-12-30 12:24: > >Again, I understand you concern that all Markdown > >implementations should give the same results. But at the > >moment, and I think that is not only my opinion, the Markdown >

Re: Maruku: a better Markdown interpreter for Ruby.

Reply to Andrea Censi <[EMAIL PROTECTED]> 06-12-30 12:24: >Again, I understand you concern that all Markdown implementations >should give the same results. But at the moment, and I think that is >not only my opinion, the Markdown specification has a lot of holes. So >even if wanted, I could not ma

Re: Maruku: a better Markdown interpreter for Ruby.

On 12/28/06, John Gruber <[EMAIL PROTECTED]> wrote: > If you're going to support syntax extensions like PHP Markdown > Extra's and MultiMarkdown's, you shouldn't call Maruku a Markdown > interpreter. By default, "Markdown" should mean Markdown. I know > there are a few features that I haven't yet o

Escaping inside code blocks?

I am doing unit-tests for Maruku and every once in a while I run into some doubts. I am posting a lot to the list, but all of these messages should be in-topic (tell me if not). Consider the input: --- `There is a literal backtick (\`) here.` `There is a literal backtick (\\`) here.` ``There is

Re: Doubt about standard syntax

* Michel Fortin <[EMAIL PROTECTED]> [2006-12-29 21:05]: > while PHP Markdown use John's Perl implementation as a > reference, that doesn't necessarily mean that's the right thing > to do. But until that changes, I'll probably follow what is > done in Perl for the sake of compatibility. The problem