From public at quillio.com  Fri Jun  1 19:21:05 2012
From: public at quillio.com (Lou Quillio)
Date: Fri, 1 Jun 2012 12:21:05 -0700
Subject: [kramdown-users] CLI Suppress coderay line-numbering
Message-ID: <CAKLxWRvKV2TGnDpgoOjnTdnqcoE1LUveWVYXeUAbTh3B21CHdg@mail.gmail.com>

The kramdown CLI tool (v0.13.6) seems to default the
`--coderay-line-numbers` argument to inline, rather than nil, and
insists on a `table`, `list` or `inline` value.  Is this a bug, or am
I missing something?

It's easy enough to suppress the generated line numbers (in HTML
output) on the CSS layer, but the tool also adds leading space to each
line of code, which is picked up in copy-paste operations from a
browser, so is undesirable.  Example:

<div>
  <div class="CodeRay">
    <div class="code">
<pre><span class="no">1</span> I am a line of code, with leading <span
style="color:#00D;font-weight:bold">space inserted</span>;
<span class="no">2</span> I am another line of code;
</pre>
    </div>
  </div>
</div>


My specific interest is to do something like ...

$ kramdown <infile> --template <template file> --coderay-css style > <outfile>

... and get HTML output with inline (`style` attribute) syntax
highlighting but no generated line numbers.  Currently I use this
workaround:

$ kramdown <infile> --template <template file> --coderay-css style | \
  perl -p -e 's|<span class="no">.*?</span>\s||gm' > <outfile>

Any help appreciated.

Feature request:  The ability to specify, as a command line argument,
a default CodeRay syntax type for code blocks, to be applied to blocks
lacking a `:lang=` declaration.  In many cases (though not all), this
would allow markdown-text input to avoid embedded syntax declarations,
keeping the source a little cleaner.

Thanks again.  Great tool.

LQ


-- 
Lou Quillio
http://quillio.com/

From t_leitner at gmx.at  Sat Jun  2 04:59:35 2012
From: t_leitner at gmx.at (Thomas Leitner)
Date: Sat, 2 Jun 2012 06:59:35 +0200
Subject: [kramdown-users] CLI Suppress coderay line-numbering
In-Reply-To: <CAKLxWRvKV2TGnDpgoOjnTdnqcoE1LUveWVYXeUAbTh3B21CHdg@mail.gmail.com>
References: <CAKLxWRvKV2TGnDpgoOjnTdnqcoE1LUveWVYXeUAbTh3B21CHdg@mail.gmail.com>
Message-ID: <20120602065935.2deb8741@noweto>

On 2012-06-01 12:21 -0700 Lou Quillio wrote:
> The kramdown CLI tool (v0.13.6) seems to default the
> `--coderay-line-numbers` argument to inline, rather than nil, and
> insists on a `table`, `list` or `inline` value.  Is this a bug, or am
> I missing something?

This is just the default setting and it makes sense that the default
settings are the same regardless of the kind of invocation of kramdown.

One thing which is a bug is that the documentation of the options on
the CLI is wrong since you can't pass a Ruby Symbol type to the
options handler but one has to use a String.

Another thing which is not quite a bug but unfriendly behaviour is that
setting a nil value can only be done by providing a whitespace string
like ' ' to an option - I will fix this.

> My specific interest is to do something like ...
> 
> $ kramdown <infile> --template <template file> --coderay-css style >
> <outfile>
> 
> ... and get HTML output with inline (`style` attribute) syntax
> highlighting but no generated line numbers.  Currently I use this
> workaround:
> 
> $ kramdown <infile> --template <template file> --coderay-css style | \
>   perl -p -e 's|<span class="no">.*?</span>\s||gm' > <outfile>
> 

You can use the following command line:

    $ kramdown <infile> --coderay-css style --coderay-line-numbers ' ' --template <template> 

> Feature request:  The ability to specify, as a command line argument,
> a default CodeRay syntax type for code blocks, to be applied to blocks
> lacking a `:lang=` declaration.  In many cases (though not all), this
> would allow markdown-text input to avoid embedded syntax declarations,
> keeping the source a little cleaner.

Noted on my TODO list. Will probably become some option like
coderay-default-syntax.

Cheers,
  Thomas

From t_leitner at gmx.at  Sun Jun  3 07:59:15 2012
From: t_leitner at gmx.at (Thomas Leitner)
Date: Sun, 3 Jun 2012 09:59:15 +0200
Subject: [kramdown-users] [ANN] kramdown 0.13.7
Message-ID: <20120603095915.1274b1c8@noweto>

## About kramdown

kramdown (sic, not Kramdown or KramDown, just kramdown) is a *free*
GPL-licensed [Ruby](http://www.ruby-lang.org) library for parsing a
superset of Markdown. It is completely written in Ruby, supports
standard Markdown (with some minor modifications) and various
extensions that have been made popular by the PHP Markdown Extra
package and Maruku.

Homepage for installation instructions and documentation:
   http://kramdown.rubyforge.org

## kramdown 0.13.7 released

This release, aside from fixing bugs and some other minor changes, adds
a new converter for removing HTML tags from an element tree. This means
that one can now do

    kramdown -i html -o remove_html_tags,kramdown my_document.html

and get a nice kramdown document from a full HTML document!

## Changes

* 1 major change

  - Implemented [RemoveHtmlTags converter] for removing HTML tags from
    an element tree (fixes bug [RF#29282] requested by Bernard Potocki)

* 3 minor changes

  - Updated kramdown binary to support multiple, chained output formats
  - Added a new option for setting a default coderay highlighting
    language (requested by Lou Quillio)
  - Feature request [RF#29575]: Added support for `&shy;` soft-hyphen
    entity (requested by Alexander Gro?)

* 5 bug fixes

  - Fixed bug [RF#29576]: Footnotes in headers resulted in duplicated
    `id` attr in TOC (reported by korthaerd)
  - Multi-line titles in links are now correctly parsed
  - DOCTYPE declaration is now correctly parsed independent of case
  - Setting of `nil` options works now by using the String 'nil'
  - Fixed table-of-content test cases (test went green although the
    meaning of the test was not satisfied due to copy-paste - d'oh!)

* 1 documentation fix

  - Fixed bug [RF#29577]: sidebar link to news page was broken for HTML
    pages in sub directories (reported by korthaerd)

[RF#29577]: http://rubyforge.org/tracker/index.php?func=detail&aid=29577&group_id=7403&atid=28673
[RF#29576]: http://rubyforge.org/tracker/index.php?func=detail&aid=29576&group_id=7403&atid=28673
[RF#29575]: http://rubyforge.org/tracker/index.php?func=detail&aid=29575&group_id=7403&atid=28676
[RF#29282]: http://rubyforge.org/tracker/index.php?func=detail&aid=29282&group_id=7403&atid=28673
[RemoveHtmlTags converter]: http://kramdown.rubyforge.org/converter/remove_html_tags.html

From public at quillio.com  Tue Jun  5 05:04:50 2012
From: public at quillio.com (Lou Quillio)
Date: Mon, 4 Jun 2012 22:04:50 -0700
Subject: [kramdown-users] CLI Suppress coderay line-numbering
In-Reply-To: <20120602065935.2deb8741@noweto>
References: <CAKLxWRvKV2TGnDpgoOjnTdnqcoE1LUveWVYXeUAbTh3B21CHdg@mail.gmail.com>
	<20120602065935.2deb8741@noweto>
Message-ID: <CAKLxWRtq_4idcfGyVx=6FwbA4XeTUmMRDk8Nz=kY4jLy7bgrLg@mail.gmail.com>

On Fri, Jun 1, 2012 at 9:59 PM, Thomas Leitner <t_leitner at gmx.at> wrote:
> On 2012-06-01 12:21 -0700 Lou Quillio wrote:
>> The kramdown CLI tool (v0.13.6) seems to default the
>> `--coderay-line-numbers` argument to inline, rather than nil, and
>> insists on a `table`, `list` or `inline` value. ?Is this a bug, or am
>> I missing something?
>
> This is just the default setting and it makes sense that the default
> settings are the same regardless of the kind of invocation of kramdown.
>
> One thing which is a bug is that the documentation of the options on
> the CLI is wrong since you can't pass a Ruby Symbol type to the
> options handler but one has to use a String.
>
> Another thing which is not quite a bug but unfriendly behaviour is that
> setting a nil value can only be done by providing a whitespace string
> like ' ' to an option - I will fix this.
>
>> My specific interest is to do something like ...
>>
>> $ kramdown <infile> --template <template file> --coderay-css style >
>> <outfile>
>>
>> ... and get HTML output with inline (`style` attribute) syntax
>> highlighting but no generated line numbers. ?Currently I use this
>> workaround:
>>
>> $ kramdown <infile> --template <template file> --coderay-css style | \
>> ? perl -p -e 's|<span class="no">.*?</span>\s||gm' > <outfile>
>>
>
> You can use the following command line:
>
> ? ?$ kramdown <infile> --coderay-css style --coderay-line-numbers ' ' --template <template>
>
>> Feature request: ?The ability to specify, as a command line argument,
>> a default CodeRay syntax type for code blocks, to be applied to blocks
>> lacking a `:lang=` declaration. ?In many cases (though not all), this
>> would allow markdown-text input to avoid embedded syntax declarations,
>> keeping the source a little cleaner.
>
> Noted on my TODO list. Will probably become some option like
> coderay-default-syntax.
>
> Cheers,
> ?Thomas

Thank you, Thomas.  kramdown is especially well-designed, and the
supplied command line binary lets it reach far beyond Ruby deployment.
 Clearly best of breed, for years now, IMO.  Congratulations on a very
fine product.

LQ


-- 
Lou Quillio
http://quillio.com/

From t_leitner at gmx.at  Tue Jun  5 06:53:25 2012
From: t_leitner at gmx.at (Thomas Leitner)
Date: Tue, 5 Jun 2012 08:53:25 +0200
Subject: [kramdown-users] CLI Suppress coderay line-numbering
In-Reply-To: <CAKLxWRtq_4idcfGyVx=6FwbA4XeTUmMRDk8Nz=kY4jLy7bgrLg@mail.gmail.com>
References: <CAKLxWRvKV2TGnDpgoOjnTdnqcoE1LUveWVYXeUAbTh3B21CHdg@mail.gmail.com>
	<20120602065935.2deb8741@noweto>
	<CAKLxWRtq_4idcfGyVx=6FwbA4XeTUmMRDk8Nz=kY4jLy7bgrLg@mail.gmail.com>
Message-ID: <20120605085325.7b0158ef@noweto>

On 2012-06-04 22:04 -0700 Lou Quillio wrote:
> Thank you, Thomas.  kramdown is especially well-designed, and the
> supplied command line binary lets it reach far beyond Ruby deployment.
>  Clearly best of breed, for years now, IMO.  Congratulations on a very
> fine product.

Thanks! Btw. the new 0.13.7 version of kramdown fixes the problem with
setting some command line option values and introduces the
--coderay-default-lang option, as per your request.

Cheers,
  Thomas