headers
Duke Normandin | 4 Mar 2011 18:26

First-time user woes

Hello list ...

I read all that I could at:

http://daringfireball.net/projects/markdown/

as well as the man-page. I'm still not sure as to how to get the output
written to a file instead of the screen. For example, I did:

markdown --html4tags convert-this.txt

Should I be redirecting the output to a file, like:

markdown --html4tags convert-this.txt > convert-this.html

--
Duke
Permalink | Reply | 4 comments |
headers
David Kendal | 4 Mar 2011 21:05
Picon
Gravatar

Re: First-time user woes

On 4 Mar 2011, at 17:26, Duke Normandin <dukeofperl <at> ml1.net> wrote:

> Should I be redirecting the output to a file, like:
> 
> markdown --html4tags convert-this.txt > convert-this.html

Yes.

— dpk.
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
Permalink | Reply | 3 comments |
headers
Duke Normandin | 4 Mar 2011 21:17

Re: First-time user woes

On Fri, 4 Mar 2011, David Kendal wrote:

> On 4 Mar 2011, at 17:26, Duke Normandin <dukeofperl <at> ml1.net> wrote:
>
> > Should I be redirecting the output to a file, like:
> >
> > markdown --html4tags convert-this.txt > convert-this.html
>
> Yes.

Cool! Thanks. BTW, does it say as much in the Markdown site? Am I
blind in one eye, and can't see WAS out of the other? :)

--

-- 
Duke
Permalink | Reply | 2 comments |
headers
Waylan Limberg | 4 Mar 2011 21:49
Picon
Gravatar

Re: First-time user woes

On Fri, Mar 4, 2011 at 3:17 PM, Duke Normandin <dukeofperl <at> ml1.net> wrote:
> On Fri, 4 Mar 2011, David Kendal wrote:
>
>> On 4 Mar 2011, at 17:26, Duke Normandin <dukeofperl <at> ml1.net> wrote:
>>
>> > Should I be redirecting the output to a file, like:
>> >
>> > markdown --html4tags convert-this.txt > convert-this.html
>>
>> Yes.
>
> Cool! Thanks. BTW, does it say as much in the Markdown site? Am I
> blind in one eye, and can't see WAS out of the other? :)
>

Markdown outputs to 'stdout', which implies that basic command line
constructs will work. I imagine that if you're calling markdown from
the command line, it is assumed you know and understand this. However,
if the docs nowhere say markdown outputs to stdout, then that may be
an oversight.

On the other hand, markdown is generally considered a library first
and a command line script second. In other words, it is primarily
meant to be called from other code (cgi script, web framework, etc)
and the command line feature is a helpful afterthought. That means
documentation of the command line features may suffer a little. In my
personal observation, this applies to all the various implementations,
although some are better than others.

--

--
(Continue reading)

Permalink | Reply | 1 comment |
headers
Duke Normandin | 4 Mar 2011 22:49

Re: First-time user woes

On Fri, 4 Mar 2011, Waylan Limberg wrote:

> On Fri, Mar 4, 2011 at 3:17 PM, Duke Normandin <dukeofperl <at> ml1.net> wrote:
> > On Fri, 4 Mar 2011, David Kendal wrote:
> >
> >> On 4 Mar 2011, at 17:26, Duke Normandin <dukeofperl <at> ml1.net> wrote:
> >>
> >> > Should I be redirecting the output to a file, like:
> >> >
> >> > markdown --html4tags convert-this.txt > convert-this.html
> >>
> >> Yes.
> >
> > Cool! Thanks. BTW, does it say as much in the Markdown site? Am I
> > blind in one eye, and can't see WAS out of the other? :)
> >
>
> Markdown outputs to 'stdout', which implies that basic command line
> constructs will work. I imagine that if you're calling markdown from
> the command line, it is assumed you know and understand this. However,
> if the docs nowhere say markdown outputs to stdout, then that may be
> an oversight.

Maybe so ...

> On the other hand, markdown is generally considered a library first
> and a command line script second. In other words, it is primarily
> meant to be called from other code (cgi script, web framework, etc)
> and the command line feature is a helpful afterthought. That means
> documentation of the command line features may suffer a little. In my
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian Spann | 18 Mar 2011 16:36
Picon
Favicon

Bug using inline code blocks in nested lists?

Hi,

I am generating a nice document with some inline code blocks and came
around the following error:

1. asdf
    - \` asdf `` `asdf` ``

produces:

<ol>
<li>asdf
<ul><li>` asdf <code><code>asdf</code></code> </li></ul></li>
</ol>

instead of:

<ol>
<li>asdf
<ul><li>` asdf <code>`asdf`</code> </li></ul></li>
</ol>

Am I missing something or is this a bug?

Regards,

Chris
Attachment (smime.p7s): application/pkcs7-signature, 5765 bytes
(Continue reading)

Permalink | Reply | 2 comments |
headers
John MacFarlane | 18 Mar 2011 18:54
Picon
Favicon

Re: Bug using inline code blocks in nested lists?

+++ Christian Spann [Mar 18 11 16:36 ]:
> Hi,
> 
> I am generating a nice document with some inline code blocks and came
> around the following error:
> 
> 1. asdf
>     - \` asdf `` `asdf` ``
> 
> produces:
> 
> <ol>
> <li>asdf
> <ul><li>` asdf <code><code>asdf</code></code> </li></ul></li>
> </ol>
> 
> instead of:
> 
> <ol>
> <li>asdf
> <ul><li>` asdf <code>`asdf`</code> </li></ul></li>
> </ol>
> 
> Am I missing something or is this a bug?

It's a bug. Try another implementation.  You can see from
http://babelmark.bobtfish.net/ that many other implementations
parse this input correctly.

PS. Is babelmark still actively maintained?  The versions of pandoc
(Continue reading)

Permalink | Reply | 1 comment |
headers
Fletcher T. Penney | 18 Mar 2011 19:00

Re: Bug using inline code blocks in nested lists?

On Fri, Mar 18, 2011 at 1:54 PM, John MacFarlane <jgm <at> berkeley.edu> wrote:

> PS. Is babelmark still actively maintained?  The versions of pandoc
> and peg-markdown there are a couple of years old.
>
> John

I was curious about this, too.  I'll want to get MMD 3.0 in there as
well.  I've been using babelmark a lot as I test my changes to
peg-markdown to see what I've broken....

F-

--

-- 
Fletcher T. Penney
fletcher <at> fletcherpenney.net
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
Permalink | Reply | 0 comments |
headers
Rick Charon | 19 Mar 2011 23:41
Picon
Gravatar

Spaces following quotes disappear

I have a line that includes a double quotation mark followed by 5 spaces, and then some text, like so:
"     global"
when it is converted with markdown, the spaces disappear, so it results in
"global"
Is there a way to keep these spaces in there?
Thanks for any help.
Rick

_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
Permalink | Reply | 3 comments |
headers
Joel Sanda | 20 Mar 2011 00:09

Re: Spaces following quotes disappear

On 3/19/2011 4:41 PM, Rick Charon wrote:
> I have a line that includes a double quotation mark followed by 5
> spaces, and then some text, like so:
> "     global"
> when it is converted with markdown, the spaces disappear, so it results in
> "global"
> Is there a way to keep these spaces in there?
> Thanks for any help.
> Rick
>

Have you tried "&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;global"?

Using WriteMonkey's export to web browser the source from Firefox was this:

<p>"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;global"</p>

- joel
Permalink | Reply | 1 comment |

Gmane