{5} Assigned, Active Tickets by Owner (Full Description) (22 matches)

BlueCloth breaks with a stack overflow if it tries to parse a list (either ordered or unordered) that is too long:

RegexpError: Stack overflow in regexp matcher: /
        ^						# Start of line
        <(p|div|h[1-6]|blockquote|pre|table|dl|ol|ul|script)	# Start tag: \2
        \b						# word break
        (.*\n)*?				# Any number of lines, minimal match
        <\/\1>					# Matching end tag
        [ ]*					# trailing spaces
        (?=\n+|\Z)				# End of line or document
      /ix
    from ./bluecloth.rb:342:in `gsub!'
    from ./bluecloth.rb:342:in `hide_html_blocks'
    from ./bluecloth.rb:248:in `apply_block_transforms'
    from ./bluecloth.rb:202:in `to_html'

The number of list items it can handle is inversely related to how long the list items are. With 26-character lines (eg. 'a'..'z'), BlueCloth will break on 78 items or above.

I've attached a little script to hopefully help test this. You can vary the item length and test a range to see how many list items BlueCloth can handle.

This might be a bug in ruby itself, in which case I request that you pass it upstream. Even then, there might be a way that BlueCloth could get around it.

I originally noticed this while maintaining a wiki running on Instiki 0.9.1 (http://www.instiki.org). The version string for the BlueCloth source used by Instiki is:

#  $Id: bluecloth.rb,v 1.3 2004/05/02 15:56:33 webster132 Exp $

When executing a program in DEBUG mode (-d flag), error occurs when creating a BlueCloth document: ArgumentError?: too many arguments for format string Backtrace: /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:969:in `%' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:969:in `transform_images' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:266:in `apply_span_transforms' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:731:in `form_paragraphs' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:723:in `collect' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:723:in `form_paragraphs' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:252:in `apply_block_transforms' /usr/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:204:in `to_html'

The offending line has obvious error: '@… " Transforming images " % str' should be changed to: '@… " Transforming images %s" % str'

- testing hyphens list
- testing hyphens list
- testing hyphens list
- testing hyphens list

This does not generate a bullet list.

The attached patch does two things:

• It replaces calls to the the deprecated StringScanner#empty? method with calls to StringScanner#eos?
• It moves all HTML rendering into public render methods.

The latter is the key reason for the patch. I want to be able to change the output from a subclass of BlueCloth without having to duplicate a lot of its code, so I thought it easiest to break out the rendering of HTML into separate methods that can then be overriden.

Any chance you'd accept this patch?

Thanks,

David

If you use a ` in a string, BlueCloth will throw an exception. Example:

irb(main):004:0> BlueCloth.new("In effetti e` un po' cicciotto...").to_html
BlueCloth::FormatError: Bad markdown format near " un po' cicciotto...": No "`" found before end
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:919:in `transform_code_spans'
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:264:in `apply_span_transforms'
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:731:in `form_paragraphs'
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:723:in `form_paragraphs'
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:252:in `apply_block_transforms'
        from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/BlueCloth.rb:204:in `to_html'
        from (irb):4
irb(main):005:0> 

surrounding single characters with double-asterixes doesn't result with them being treated as bold.

For example these should be interpreted as being bold:

**this should be in bold**
**a**

The first line is seen as bold, but not the second single line, instead the plain text: "*a*" is printed (omit quotes).

BlueCloth seems to require that the previous line ends with a colon for the code block to be recognised.

For example...

Here is a line that might describe the following codeblock

    here is the actual codeblock. This should be seen as a codeblock
    yet as the first line didn't end with a : it is just treated as normal
    text :-(

whereas this example works...

Here is another line that might describe the following codeblock:

    hooray the codeblock is recognised!

Hi.

I'm using BlueCloth to automate the generation of a website. I have a bunch of Markdown files (such as INDEX, README, INSTALL etc.) that I process with BlueCloth into a website (containing index.html, readme.html, install.html etc.).

I've extended BlueCloth (0.0.4b) with some code that allows me to plug in an external URL resolver for links that can not be resolved in the current document. This makes it easy for me to reference pages in my website without cluttering the Markdown text with links like [this][readme.html].

Instead I can put the following in my document:

some text with an un-resolved [link][README] 
that should point to the README document.

The above is transformed to:

some text with an un-resolved <a href="readme.html" title="Readme">link</a> 
that should point to the README document.

My extension to BlueCloth allows me to code something like:

class Resolver
    def resolve(link_id)
        if link_id == "readme"
           ["readme.html", "Readme"] #URL and Title
        else
            nil
        end
    end
end

parser = BlueCloth.new(some_text)
parser.url_resolver = Resolver.new
puts parser.to_html

Allowing users to extend BlueCloth with custom url-resolvers would be a nice feature IMO.

My modification of BlueCloth is pretty trivial - but let me know if you want me to send in the code as a patch :)

Best Regards //Anders

I don't think BlueCloth should throw an exception if the backtick-style code spans aren't properly terminated (line 918 of lib/bluecloth.rb): Gruber's original doesn't. In fact, BC#to_html should always return HTML, because Gruber didn't define a syntax that must be followed. Remember, Markdown is a *writing* format, not a *publishing* format.

I really like Markdown with TabWidth?=2. However, I'd rather not maintain my own fork of the codebase just to change the class-eval-time constant.

So I pulled it out into an instance variable. This had a few side effects, most notably that a few regular expressions that depended on TabWidth? could not be class level anymore either.

I've attached a patch.

Oh. I should do a unit test too. But I've been fighting with this enough for this morning. Perhaps I'll do it later. Prod me if its important.

I've seen BlueCloth choke on some html-comments. I've narrowed the problem down to this test-program:

require_gem 'BlueCloth'

bc = BlueCloth::new('<!--')
puts bc.to_html