SuperRedCloth 1.160 Gems #
With the help and goodwill of the RedCloth mailing list, it has been decided that RedCloth 4 will end up being the polished finished code for SuperRedCloth. There is still a little ways to go, but I think it could happen within February. If, that is, you help goof around with Super.
gem install superredcloth --source http://code.whytheluckystiff.net
And to use it, do:
require 'superredcloth'
p SuperRedCloth.new("h1. The Legend of Zu").to_html
All textile syntax should work. Options like :hard_breaks and :filter_html are still underway.
tilman
Compiling with -Wall makes gcc bitch that “reg” might not be initialized. I only had a quick look at the (scary) code, but it seems valid: teh patch
kjell
Any chance of bopping (Super)RedCloth up to textile 2? The extended blocks are to die for.
why
tilman: Great, that’s it.
kjell: I had no idea. But, yeah. It’s not exactly clear to me how all the Textile 2 stuff works—for example “better escaping” and “better quoting.” But the gist of it is good.
fat
Return sanity to my house and return the single return. Return the return…
Return hard_breaks to its home in The Chapel of Defaults. I beg you in the name of sanity.
And if I ever get my hands on the fowl scum that advised against the acknowledgment of RedCloth’s hapless single returns, I’ll eat their heart. I’ll eat their fucking heart _why.
fat
fat
sorry that was stupid.
but when the return key is pressed by the user, it should mean something. Just like all the other keys.
Personally, Id say that if a user hits return three times it should also mean exactly what the user intended.
yup
Has anyone noticed Maruku?
randomsel
ah, but fat, you’re thinking wysiwyg! I think we’re talking markup here…
fat
You might be right randomsel. My estimation of the semantic value of a break tag within a paragraph is probably fubar. Grammar is a funny fish. Maybe we should all use an ellipsis instead of a break tag. Dunno.
But wow. The hoops. Hope you have your jumping shoes on because people hit return when they want to make a pause within a paragraph. I know I do.
Im just thinking that the keys we press should not be ignored. If I want to state something with the stroke of a return key, why ignore it? Even if a new line were interpreted as an ellipsis I would be happier than it being ignored completely by redcloth. Or a span tag with an id of pause. ANYTHING . But how can it just be ignored?
I am thinking about markup and Im also thinking about semantics. Im also thinking that redcloth should serve it’s user and not semantic fanatics. When I write a paragraph with lots of line breaks in it and you tell me thats not semantic and it’s not the proper way to write a paragraph I want redcloth to say “oh no, another person who hasn’t figured out how to write without these silly line breaks… OK Ill humor them”. What I don’t understand is that suddenly when a user hit’s a single return, redcloth says “oh dear, that line break wasn’t up to par with the latest opinions about semantics and grammar rules. Ill just ignore it and hope they learn their lesson.”
Is it just a matter of “opinionated software”? Maybe. Unfortunately Its a pretty hard opinion to put to any good use. And I think it’s ridiculous.
??? ... !
unfortunately you do not write redcloth
why
Wait a minute, hey, I like what fat is saying!
stoly
I think fat’s right on the money. I can’t think of a more fundamental, universal, and intuitive token of markup than a return. Once you pervert the return, there’s no telling where it’ll stop. You might even have to click Start to stop…
why
Well and then what if you had to click on the Enter key? That would be seriously effed.
yup
Smart breaks?
mole
I like fat’s idea. But what is a difference between what fat said and hard-breaks option?
If a single return is converted to br and dobule return is considered to a paragraph, it’s good enough for me.