Example Flexifilters page has too-wide code samples

That code block should probably be in a separate text file and linked in the doc body.
Could you please take care of that and report back?

Is this not also a Bluecheese issue that lets preformatted text flow over the right column?

It is possible to deal with wide code blocks in an elegant way. LIke e.g., done at the Lullabot.
http://www.lullabot.com/articles/jeffs-handy-dandy-drupal-login-bookmarklet

I went through the Bluecheese issue queue but couldn't find any related issues.

I suspect its more so an issue with codefilter not understanding how to format JSON. Those linked code blocks aren't blobs of JSON, they're formatted PHP and Javascript.

I ran it through JSON Beautify and previewed the change. It wrapped fine, though imo, they're both ugly and and aren't meant to be embedded in human-readable text. I would have attached it, which I still recommend, but d.o is being mean to me right now with uploads. I don't normally do this:

a: 9: {
    s: 5: "label";s: 15: "Link Formatting";s: 11: "description";s: 47: "You may format links in the format [link|title]";s: 2: "id";s: 1: "2";s: 7: "enabled";b: 1;s: 8: "advanced";b: 0;s: 5: "delta";s: 1: "0";s: 5: "cache";s: 1: "1";s: 10: "components";a: 3: {
        i: 0;a: 3: {
            s: 5: "class";s: 22: "flexifilter_chunk_grab";s: 8: "settings";a: 7: {
                s: 6: "starts";s: 1: "[";s: 4: "ends";s: 1: "]";s: 11: "pass_limits";i: 0;s: 14: "case_sensitive";i: 0;s: 12: "include_rest";i: 1;s: 4: "step";s: 7: "process";s: 10: "components";a: 3: {
                    i: 0;a: 3: {
                        s: 5: "class";s: 24: "flexifilter_text_prepend";s: 8: "settings";a: 2: {
                            s: 4: "text";s: 9: "<a href="";s:4:"
                            step ";s:7:"
                            process ";}s:2:"
                            id ";s:2:"
                            32 ";}i:1;a:3:{s:5:"
                            class ";s:24:"
                            flexifilter_text_replace ";s:8:"
                            settings ";a:3:{s:4:"
                            find ";s:1:" | ";s:7:"
                            replace ";s:2:"">";s: 4: "step";s: 7: "process";
                        }
                        s: 2: "id";s: 2: "33";
                    }
                    i: 2;a: 3: {
                        s: 5: "class";s: 23: "flexifilter_text_append";s: 8: "settings";a: 2: {
                            s: 4: "text";s: 4: "</a>";s: 4: "step";s: 7: "process";
                        }
                        s: 2: "id";s: 2: "34";
                    }
                }
            }
            s: 2: "id";s: 2: "31";
        }
        s: 7: "id_next";i: 35;s: 9: "id_prefix";s: 22: "flexifilter_component_";
    }
    s: 3: "fid";s: 3: "new";
}

If you confirm that the code above is correct I can add it as an attachment as you proposed in #1. Hopefully d.o. is less cruel to me.

:) The code should be fine, but I don't think it's my place to recommend formatting changes of flexifilter exports. That was just to see if the wrapping would work, which might be something to look at in the codefilter issue queue.

I think the best thing would be to put the standard export in a txt file attached to that docs page.