From lbocseg at yahoo.com.br  Wed Apr  8 09:39:14 2009
From: lbocseg at yahoo.com.br (Rodrigo Rosenfeld Rosas)
Date: Wed, 8 Apr 2009 06:39:14 -0700 (PDT)
Subject: Recent bug in RedCloth 4.1.9
Message-ID: <351578.87728.qm@web54103.mail.re2.yahoo.com>


Could someone confirm this bug?

RedCloth.new("!/image_r.jpg(description)!:image.jpg").to_html

<p><a href="image.jpg"><img src="/image_r.jpg" title="description" alt="description" /></a></p>

That is correct.

Then we just add an "a" (or anything else) to the end of the string:

RedCloth.new("!/image_r.jpg(description)!:image.jpg a").to_html

Incorrect result (link is missed):
<p><img src="/image_r.jpg" title="description" alt="description" /> a</p>

It only happens when "(description)" is present.
Maybe RedCloth should include this case on test suite.

 
Tested on last stable version (4.1.9).

The problem doesn't exist on 4.1.1.

P.S: a curiosity: why 4.1.9 follows 4.1.1, instead of 4.1.2?


      Veja quais s?o os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com

From jg at jasongarber.com  Wed Apr  8 12:05:36 2009
From: jg at jasongarber.com (Jason Garber)
Date: Wed, 8 Apr 2009 12:05:36 -0400
Subject: Recent bug in RedCloth 4.1.9
In-Reply-To: <351578.87728.qm@web54103.mail.re2.yahoo.com>
References: <351578.87728.qm@web54103.mail.re2.yahoo.com>
Message-ID: <8D759B2C-1F62-428B-ABBC-60A1D79ED55D@jasongarber.com>

Rodrigo, thanks for reporting the bug.  I've made a ticket for it at http://jgarber.lighthouseapp.com/projects/13054-redcloth/tickets/141-image-link-not-recognized-with-alt-text 
   If you want to follow the status, sign in to Lighthouse.

BTW, 4.1.9 followed 4.1.1 because I was trying to be cute.  RedCloth  
4.1.9 was the first release to be compatible with Ruby 1.9.  Get it?   
In the end, though, it was a mistake.  I've wanted to release another  
4.1.x but I don't want to do 4.1.10 because then you can't compare  
version numbers as strings. Not to mention the fact that it's just  
plain confusing  So, expect the next version to be 4.2.0.

On Apr 8, 2009, at 9:39 AM, Rodrigo Rosenfeld Rosas wrote:

>
> Could someone confirm this bug?
>
> RedCloth.new("!/image_r.jpg(description)!:image.jpg").to_html
>
> <p><a href="image.jpg"><img src="/image_r.jpg" title="description"  
> alt="description" /></a></p>
>
> That is correct.
>
> Then we just add an "a" (or anything else) to the end of the string:
>
> RedCloth.new("!/image_r.jpg(description)!:image.jpg a").to_html
>
> Incorrect result (link is missed):
> <p><img src="/image_r.jpg" title="description" alt="description" />  
> a</p>
>
> It only happens when "(description)" is present.
> Maybe RedCloth should include this case on test suite.
>
>
> Tested on last stable version (4.1.9).
>
> The problem doesn't exist on 4.1.1.
>
> P.S: a curiosity: why 4.1.9 follows 4.1.1, instead of 4.1.2?
>
>
>      Veja quais s?o os assuntos do momento no Yahoo! +Buscados
> http://br.maisbuscados.yahoo.com
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From jg at jasongarber.com  Wed Apr  8 12:12:07 2009
From: jg at jasongarber.com (Jason Garber)
Date: Wed, 8 Apr 2009 12:12:07 -0400
Subject: Timeframe for a 4.2 release
Message-ID: <93288BCE-9913-47A0-B812-7C4414CB73E5@jasongarber.com>

There are a whole lot of RedCloth tickets open right now and I wish I  
could be fixing them, but I'm all tied up with work on some Radiant  
CMS extensions.  I've spent too long perfecting RedCloth (which was  
justifiable since a bad experience with Textile will make users hate  
the CMS) and finally had to call it good enough for now and focus on  
some other parts of the CMS ? especially since I have an annual  
performance review in the next couple weeks!

Bil has been a great help managing the LaTeX tickets.  If anyone else  
wants to fix some bugs, please be my guest!  I'll apply patches/pull- 
requests promptly if they're clean and well-tested.

Otherwise, the bugs will just have to sit there for a few more weeks.   
I remain committed to making RedCloth the best it can be and I'm  
thankful for all the people who take time to report bugs.

Jason Garber

From stephen.bannasch at deanbrook.org  Wed Apr  8 13:15:01 2009
From: stephen.bannasch at deanbrook.org (Stephen Bannasch)
Date: Wed, 8 Apr 2009 13:15:01 -0400
Subject: looking for textile reference in textile source for benchmarking
Message-ID: <p06240801c6028a5d0cea@[192.168.1.106]>

Jason,

Do you have any of the longer textile reference documents online in 
textile source format.

I wanted to try benchmarking redcloth on them and comparing it to 
what Maurico found benchmarking bluecloth.

see: 
http://eigenclass.org/R2/writings/fast-extensible-simplified-markdown-in-ocaml

The markdown syntax document he is benchmarking is about 11k.

You can see my results duplicating the bluecloth results here:

   http://gist.github.com/gists/91477

and in a graph:

   http://img.skitch.com/20090408-fp1sxu3fu7dm4296kqrmskgaqt.png

I was curious how fast redcloth would be at a comparable task and 
whether redcloth would also show non-linear processing times as the 
input document got larger.

From stephen.bannasch at deanbrook.org  Wed Apr  8 13:16:40 2009
From: stephen.bannasch at deanbrook.org (Stephen Bannasch)
Date: Wed, 8 Apr 2009 13:16:40 -0400
Subject: looking for textile reference in textile source for benchmarking
Message-ID: <p06240802c6028c4b806b@[192.168.1.106]>

At 1:15 PM -0400 4/8/09, Stephen Bannasch wrote:
>You can see my results duplicating the bluecloth results here:
>
>   http://gist.github.com/gists/91477

correct gist url: http://gist.github.com/91477

From jg at jasongarber.com  Wed Apr  8 16:28:02 2009
From: jg at jasongarber.com (Jason Garber)
Date: Wed, 8 Apr 2009 16:28:02 -0400
Subject: looking for textile reference in textile source for benchmarking
In-Reply-To: <p06240801c6028a5d0cea@[192.168.1.106]>
References: <p06240801c6028a5d0cea@[192.168.1.106]>
Message-ID: <EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>

No, they're all in individual entries in the CMS, but it shouldn't  
take me long to have it loop over them and dump as plain text...

<r:find url="/textile/">
<r:children:each><r:children:each>
<r:content part="input" />

<r:children:each>
<r:content part="input" />

</r:children:each></r:children:each>
</r:children:each>
</r:find>

Easy enough!  The result is attached.

On Apr 8, 2009, at 1:15 PM, Stephen Bannasch wrote:

> Jason,
>
> Do you have any of the longer textile reference documents online in  
> textile source format.
>
> I wanted to try benchmarking redcloth on them and comparing it to  
> what Maurico found benchmarking bluecloth.
>
> see: http://eigenclass.org/R2/writings/fast-extensible-simplified-markdown-in-ocaml
>
> The markdown syntax document he is benchmarking is about 11k.
>
> You can see my results duplicating the bluecloth results here:
>
>  http://gist.github.com/gists/91477
>
> and in a graph:
>
>  http://img.skitch.com/20090408-fp1sxu3fu7dm4296kqrmskgaqt.png
>
> I was curious how fast redcloth would be at a comparable task and  
> whether redcloth would also show non-linear processing times as the  
> input document got larger.
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: textile-dump-of-manual.textile
Type: application/octet-stream
Size: 6282 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/redcloth-upwards/attachments/20090408/b87000a8/attachment-0001.obj>

From hgs at dmu.ac.uk  Thu Apr  9 08:46:40 2009
From: hgs at dmu.ac.uk (Hugh Sasse)
Date: Thu, 9 Apr 2009 13:46:40 +0100 (BST)
Subject: Recent bug in RedCloth 4.1.9
In-Reply-To: <8D759B2C-1F62-428B-ABBC-60A1D79ED55D@jasongarber.com>
References: <351578.87728.qm@web54103.mail.re2.yahoo.com>
	<8D759B2C-1F62-428B-ABBC-60A1D79ED55D@jasongarber.com>
Message-ID: <alpine.LFD.2.00.0904091304161.26531@trueman.cs.cse.dmu.ac.uk>

On Wed, 8 Apr 2009, Jason Garber wrote:

> BTW, 4.1.9 followed 4.1.1 because I was trying to be cute.  RedCloth 4.1.9 was
> the first release to be compatible with Ruby 1.9.  Get it?  In the end,
> though, it was a mistake.  I've wanted to release another 4.1.x but I don't
> want to do 4.1.10 because then you can't compare version numbers as strings.

Are we going to be stuck with this idea forever?  We ran into this
when the successor to Ruby 1.8 could not be Ruby 1.10, breaking the
odd/even as unstable/stable releases pattern.  Version numbers are
not strings, but even if they are (a) they should be parsed (Is
Debian version "Woody".to_i.zero? ?), and (b):

http://rubyforge.org/projects/natcmp/

Try searching for "natural order string comparison". 

I really think that Ruby needs a native class for versions.
That way it would not be a subclass of String.
I should have used Comparable for this, written about 7 months into
using Ruby:

http://www.cse.dmu.ac.uk/~hgs/ruby/revision.rb

My point being this is not something doable by only the advanced
programmer, even if this effort could do with improvement.

The other reason Ruby didn't have 1.10 as a stable release was C code
checking based on single bytes per {major, minor, teeny} (or whatever
you call the third one).

Do you have any evidence for people comparing these (Redcloth)
version numbers as if they were strings?  If nobody does, then why
worry about it?  The clue is in the nomenclature: "version *numbers*".

> Not to mention the fact that it's just plain confusing  So, expect the next

I don't see that as confusing: it's one of those things that is already
tradition in this field less than 100 years old.

> version to be 4.2.0.
> 

        Hugh

From jg at jasongarber.com  Fri Apr 10 07:53:06 2009
From: jg at jasongarber.com (Jason Garber)
Date: Fri, 10 Apr 2009 07:53:06 -0400
Subject: Recent bug in RedCloth 4.1.9
In-Reply-To: <alpine.LFD.2.00.0904091304161.26531@trueman.cs.cse.dmu.ac.uk>
References: <351578.87728.qm@web54103.mail.re2.yahoo.com>
	<8D759B2C-1F62-428B-ABBC-60A1D79ED55D@jasongarber.com>
	<alpine.LFD.2.00.0904091304161.26531@trueman.cs.cse.dmu.ac.uk>
Message-ID: <CB34CCA0-0121-453E-84FC-D5C643C75E07@jasongarber.com>

Thanks for the feedback.  I picked up on the whole comparing version  
numbers as strings from here: http://www.ruby-forum.com/topic/179119   
Right or wrong, being able to compare Ruby version numbers as strings  
was enormously helpful in that circumstance.  I wish they would build  
version comparison directly into Ruby too!

I have no evidence that people are comparing RedCloth version numbers  
as strings?and they probably aren't?so it's probably no big deal if I  
would make a 4.1.10.  There was a 2.0.10 before, so there you go.

Not that I have time right now to do anything that would deserve a new  
version. :-(  Wish I did because I really enjoy hacking on RedCloth!

Jason

On Apr 9, 2009, at 8:46 AM, Hugh Sasse wrote:

> On Wed, 8 Apr 2009, Jason Garber wrote:
>
>> BTW, 4.1.9 followed 4.1.1 because I was trying to be cute.   
>> RedCloth 4.1.9 was
>> the first release to be compatible with Ruby 1.9.  Get it?  In the  
>> end,
>> though, it was a mistake.  I've wanted to release another 4.1.x but  
>> I don't
>> want to do 4.1.10 because then you can't compare version numbers as  
>> strings.
>
> Are we going to be stuck with this idea forever?  We ran into this
> when the successor to Ruby 1.8 could not be Ruby 1.10, breaking the
> odd/even as unstable/stable releases pattern.  Version numbers are
> not strings, but even if they are (a) they should be parsed (Is
> Debian version "Woody".to_i.zero? ?), and (b):
>
> http://rubyforge.org/projects/natcmp/
>
> Try searching for "natural order string comparison".
>
> I really think that Ruby needs a native class for versions.
> That way it would not be a subclass of String.
> I should have used Comparable for this, written about 7 months into
> using Ruby:
>
> http://www.cse.dmu.ac.uk/~hgs/ruby/revision.rb
>
> My point being this is not something doable by only the advanced
> programmer, even if this effort could do with improvement.
>
> The other reason Ruby didn't have 1.10 as a stable release was C code
> checking based on single bytes per {major, minor, teeny} (or whatever
> you call the third one).
>
> Do you have any evidence for people comparing these (Redcloth)
> version numbers as if they were strings?  If nobody does, then why
> worry about it?  The clue is in the nomenclature: "version *numbers*".
>
>> Not to mention the fact that it's just plain confusing  So, expect  
>> the next
>
> I don't see that as confusing: it's one of those things that is  
> already
> tradition in this field less than 100 years old.
>
>> version to be 4.2.0.
>>
>
>        Hugh
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From lbocseg at yahoo.com.br  Fri Apr 10 11:07:50 2009
From: lbocseg at yahoo.com.br (Rodrigo Rosenfeld Rosas)
Date: Fri, 10 Apr 2009 12:07:50 -0300
Subject: Recent bug in RedCloth 4.1.9
In-Reply-To: <CB34CCA0-0121-453E-84FC-D5C643C75E07@jasongarber.com>
References: <351578.87728.qm@web54103.mail.re2.yahoo.com>	<8D759B2C-1F62-428B-ABBC-60A1D79ED55D@jasongarber.com>	<alpine.LFD.2.00.0904091304161.26531@trueman.cs.cse.dmu.ac.uk>
	<CB34CCA0-0121-453E-84FC-D5C643C75E07@jasongarber.com>
Message-ID: <49DF60C6.7040502@yahoo.com.br>

Jason Garber escreveu:
> ...
> Not that I have time right now to do anything that would deserve a new 
> version. :-(  Wish I did because I really enjoy hacking on RedCloth!
You could find out what broke RedCloth, regarding this bug, for instance 
;) I don't know what version control system you are using but, on git, 
there is the "git blame" that could give you a hint of what broke 
RedCloth in 4.1.9 that was not present in 4.1.1. Fixing this but on 
4.1.10 would be enough for a new version :)

Best Regards,

Rodrigo.


	

	
		
_______________________________________________________ 
Yahoo! Mail - Sempre a melhor op??o para voc?! 
Experimente j? e veja as novidades. 
http://br.yahoo.com/mailbeta/tudonovo/

From stephen.bannasch at deanbrook.org  Sat Apr 11 03:08:36 2009
From: stephen.bannasch at deanbrook.org (Stephen Bannasch)
Date: Sat, 11 Apr 2009 03:08:36 -0400
Subject: looking for textile reference in textile source for benchmarking
In-Reply-To: <EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>
References: <p06240801c6028a5d0cea@[192.168.1.106]>
	<EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>
Message-ID: <p06240810c605f21b89c8@[192.168.1.106]>

Thanks Jason,

Here are some interesting results testing in MRI 1.8.6 and JRuby.

Testing BlueCloth:

http://img.skitch.com/20090411-fp1sxu3fu7dm4296kqrmskgaqt.png

Testing RedCloth:

http://img.skitch.com/20090411-5is73f52ftck2h3pyiiyjiu2m.png

From jg at jasongarber.com  Mon Apr 13 21:41:56 2009
From: jg at jasongarber.com (Jason Garber)
Date: Mon, 13 Apr 2009 21:41:56 -0400
Subject: looking for textile reference in textile source for benchmarking
In-Reply-To: <p06240810c605f21b89c8@[192.168.1.106]>
References: <p06240801c6028a5d0cea@[192.168.1.106]>
	<EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>
	<p06240810c605f21b89c8@[192.168.1.106]>
Message-ID: <610A16A8-A667-467B-AD0B-42E950FD75CA@jasongarber.com>

Interesting.  Care to offer any interpretation?

On Apr 11, 2009, at 3:08 AM, Stephen Bannasch wrote:

> Thanks Jason,
>
> Here are some interesting results testing in MRI 1.8.6 and JRuby.
>
> Testing BlueCloth:
>
> http://img.skitch.com/20090411-fp1sxu3fu7dm4296kqrmskgaqt.png
>
> Testing RedCloth:
>
> http://img.skitch.com/20090411-5is73f52ftck2h3pyiiyjiu2m.png
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From stephen.bannasch at deanbrook.org  Mon Apr 13 22:54:09 2009
From: stephen.bannasch at deanbrook.org (Stephen Bannasch)
Date: Mon, 13 Apr 2009 22:54:09 -0400
Subject: looking for textile reference in textile source for benchmarking
In-Reply-To: <610A16A8-A667-467B-AD0B-42E950FD75CA@jasongarber.com>
References: <p06240801c6028a5d0cea@[192.168.1.106]>	<EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>
	<p06240810c605f21b89c8@[192.168.1.106]>
	<610A16A8-A667-467B-AD0B-42E950FD75CA@jasongarber.com>
Message-ID: <p06240806c609a845a79c@[63.138.152.192]>

At 9:41 PM -0400 4/13/09, Jason Garber wrote:
>Interesting.  Care to offer any interpretation?

BlueCloth is much slower and the time for processing increases 
quadratically as the input document get's larger. I haven't looked at 
why.

RedCloth is about 15x faster and scales linearly -- again I'm not 
sure why but I like that behavior ;-)

When most of the processing time is spent in Ruby regex's (bluecloth) 
JRuby is about twice as fast.

Running RedCloth in JRuby however is only about 10% faster. From 
previous benchmarking of Hpricot I suspect that the ragel code in 
Java is just a bit slower than the C and the speedup is due to other 
areas where JRuby is faster.

The context for the benchmarking is a blog post here:

 
http://eigenclass.org/R2/writings/fast-extensible-simplified-markdown-in-ocaml

Mauricio's implementation of a simple markdown processor in OCaml 
appears to be about 20x faster than RedCloth.

I'd like to know a good way of measuring "real" memory use when 
running a benchmark like this in Ruby especially one that involves a 
native library. Mauricio's reports very low memory usage from his 
OCaml implementation.

>On Apr 11, 2009, at 3:08 AM, Stephen Bannasch wrote:
>
>>Thanks Jason,
>>
>>Here are some interesting results testing in MRI 1.8.6 and JRuby.
>>
>>Testing BlueCloth:
>>
>>http://img.skitch.com/20090411-fp1sxu3fu7dm4296kqrmskgaqt.png
>>
>>Testing RedCloth:
>>
>>http://img.skitch.com/20090411-5is73f52ftck2h3pyiiyjiu2m.png
>>_______________________________________________
>>Redcloth-upwards mailing list
>>Redcloth-upwards at rubyforge.org
>>http://rubyforge.org/mailman/listinfo/redcloth-upwards
>
>_______________________________________________
>Redcloth-upwards mailing list
>Redcloth-upwards at rubyforge.org
>http://rubyforge.org/mailman/listinfo/redcloth-upwards


From jg at jasongarber.com  Tue Apr 14 14:40:01 2009
From: jg at jasongarber.com (Jason Garber)
Date: Tue, 14 Apr 2009 14:40:01 -0400
Subject: looking for textile reference in textile source for benchmarking
In-Reply-To: <p06240806c609a845a79c@[63.138.152.192]>
References: <p06240801c6028a5d0cea@[192.168.1.106]>
	<EE988A0B-A5ED-49E5-BEBC-955176E3F3C8@jasongarber.com>
	<p06240810c605f21b89c8@[192.168.1.106]>
	<610A16A8-A667-467B-AD0B-42E950FD75CA@jasongarber.com>
	<p06240806c609a845a79c@[63.138.152.192]>
Message-ID: <51CE82C0-358D-4D47-8F4A-198CF93F122F@jasongarber.com>

Awesome.  Thanks, Stephen!

On Apr 13, 2009, at 10:54 PM, Stephen Bannasch wrote:

> At 9:41 PM -0400 4/13/09, Jason Garber wrote:
>> Interesting.  Care to offer any interpretation?
>
> BlueCloth is much slower and the time for processing increases  
> quadratically as the input document get's larger. I haven't looked  
> at why.
>
> RedCloth is about 15x faster and scales linearly -- again I'm not  
> sure why but I like that behavior ;-)
>
> When most of the processing time is spent in Ruby regex's  
> (bluecloth) JRuby is about twice as fast.
>
> Running RedCloth in JRuby however is only about 10% faster. From  
> previous benchmarking of Hpricot I suspect that the ragel code in  
> Java is just a bit slower than the C and the speedup is due to other  
> areas where JRuby is faster.
>
> The context for the benchmarking is a blog post here:
>
> http://eigenclass.org/R2/writings/fast-extensible-simplified-markdown-in-ocaml
>
> Mauricio's implementation of a simple markdown processor in OCaml  
> appears to be about 20x faster than RedCloth.
>
> I'd like to know a good way of measuring "real" memory use when  
> running a benchmark like this in Ruby especially one that involves a  
> native library. Mauricio's reports very low memory usage from his  
> OCaml implementation.
>
>> On Apr 11, 2009, at 3:08 AM, Stephen Bannasch wrote:
>>
>>> Thanks Jason,
>>>
>>> Here are some interesting results testing in MRI 1.8.6 and JRuby.
>>>
>>> Testing BlueCloth:
>>>
>>> http://img.skitch.com/20090411-fp1sxu3fu7dm4296kqrmskgaqt.png
>>>
>>> Testing RedCloth:
>>>
>>> http://img.skitch.com/20090411-5is73f52ftck2h3pyiiyjiu2m.png
>>> _______________________________________________
>>> Redcloth-upwards mailing list
>>> Redcloth-upwards at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/redcloth-upwards
>>
>> _______________________________________________
>> Redcloth-upwards mailing list
>> Redcloth-upwards at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/redcloth-upwards
>
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From davidsouth at gmail.com  Sat Apr 18 09:39:37 2009
From: davidsouth at gmail.com (Dave South)
Date: Sat, 18 Apr 2009 07:39:37 -0600
Subject: GitHub switching to Markdown?
In-Reply-To: <6440DDEE-ED9E-4568-AADB-58B38F545406@jasongarber.com>
References: <6440DDEE-ED9E-4568-AADB-58B38F545406@jasongarber.com>
Message-ID: <D115D03D-485C-470D-BF77-5CA76EB13FD2@me.com>

If I mark my fie as

README.textile

It parses just fine on Github.

Dave

On Apr 18, 2009, at 6:21 AM, Jason Garber wrote:

> You know, I can see using Markdown in something like a README where  
> it will be read in plain-text (the plain text of markdown is  
> prettier than textile), but for issues, comments, and messages where  
> no one will be reading the plain text, GitHub is parsing it with  
> "GitHub Flavored Markdown":http://github.github.com/github-flavored-markdown/ 
>  and that makes me grumpy.
>
> I personally find it tedious to write in Markdown and I wish they'd  
> add a Textile option.  Do you too?  Then vote here: http://github.com/defunkt/github-issues/issues/#issue/ 
> 106 (click on the little vote arrow to the left of the issue title).
>
> Let's build a Textile coalition!  Maybe we can even get Stephen  
> Colbert to make a TV ad for us. ;-)
>
> Jason
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From jg at jasongarber.com  Sat Apr 18 12:27:01 2009
From: jg at jasongarber.com (Jason Garber)
Date: Sat, 18 Apr 2009 12:27:01 -0400
Subject: GitHub switching to Markdown?
In-Reply-To: <D115D03D-485C-470D-BF77-5CA76EB13FD2@me.com>
References: <6440DDEE-ED9E-4568-AADB-58B38F545406@jasongarber.com>
	<D115D03D-485C-470D-BF77-5CA76EB13FD2@me.com>
Message-ID: <108D1686-8348-485D-A5C0-E11DDC6AE318@jasongarber.com>

Yes, and wiki pages appear to be Textile too, but comments, issues,  
and messages are Markdown.

On Apr 18, 2009, at 9:39 AM, Dave South wrote:

> If I mark my fie as
>
> README.textile
>
> It parses just fine on Github.
>
> Dave
>
> On Apr 18, 2009, at 6:21 AM, Jason Garber wrote:
>
>> You know, I can see using Markdown in something like a README where  
>> it will be read in plain-text (the plain text of markdown is  
>> prettier than textile), but for issues, comments, and messages  
>> where no one will be reading the plain text, GitHub is parsing it  
>> with "GitHub Flavored Markdown":http://github.github.com/github-flavored-markdown/ 
>>  and that makes me grumpy.
>>
>> I personally find it tedious to write in Markdown and I wish they'd  
>> add a Textile option.  Do you too?  Then vote here: http://github.com/defunkt/github-issues/issues/#issue/ 
>> 106 (click on the little vote arrow to the left of the issue title).
>>
>> Let's build a Textile coalition!  Maybe we can even get Stephen  
>> Colbert to make a TV ad for us. ;-)
>>
>> Jason
>> _______________________________________________
>> Redcloth-upwards mailing list
>> Redcloth-upwards at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/redcloth-upwards
>
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From davidsouth at gmail.com  Sat Apr 18 13:24:53 2009
From: davidsouth at gmail.com (Dave South)
Date: Sat, 18 Apr 2009 11:24:53 -0600
Subject: GitHub switching to Markdown?
In-Reply-To: <108D1686-8348-485D-A5C0-E11DDC6AE318@jasongarber.com>
References: <6440DDEE-ED9E-4568-AADB-58B38F545406@jasongarber.com>
	<D115D03D-485C-470D-BF77-5CA76EB13FD2@me.com>
	<108D1686-8348-485D-A5C0-E11DDC6AE318@jasongarber.com>
Message-ID: <1D7F139A-CBC0-4D68-8572-F4EC63C37384@me.com>

Ah-ha. I didn't know that. Thanks for the clarification.


On Apr 18, 2009, at 10:27 AM, Jason Garber wrote:

> Yes, and wiki pages appear to be Textile too, but comments, issues,  
> and messages are Markdown.
>
> On Apr 18, 2009, at 9:39 AM, Dave South wrote:
>
>> If I mark my fie as
>>
>> README.textile
>>
>> It parses just fine on Github.
>>
>> Dave
>>
>> On Apr 18, 2009, at 6:21 AM, Jason Garber wrote:
>>
>>> You know, I can see using Markdown in something like a README  
>>> where it will be read in plain-text (the plain text of markdown is  
>>> prettier than textile), but for issues, comments, and messages  
>>> where no one will be reading the plain text, GitHub is parsing it  
>>> with "GitHub Flavored Markdown":http://github.github.com/github-flavored-markdown/ 
>>>  and that makes me grumpy.
>>>
>>> I personally find it tedious to write in Markdown and I wish  
>>> they'd add a Textile option.  Do you too?  Then vote here: http://github.com/defunkt/github-issues/issues/#issue/ 
>>> 106 (click on the little vote arrow to the left of the issue title).
>>>
>>> Let's build a Textile coalition!  Maybe we can even get Stephen  
>>> Colbert to make a TV ad for us. ;-)
>>>
>>> Jason
>>> _______________________________________________
>>> Redcloth-upwards mailing list
>>> Redcloth-upwards at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/redcloth-upwards
>>
>> _______________________________________________
>> Redcloth-upwards mailing list
>> Redcloth-upwards at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/redcloth-upwards
>
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From jg at jasongarber.com  Thu Apr 23 01:26:39 2009
From: jg at jasongarber.com (Jason Garber)
Date: Thu, 23 Apr 2009 01:26:39 -0400
Subject: try.redcloth.org
Message-ID: <B057BFB2-1BD5-4BAD-981C-0A4033BC8E4F@jasongarber.com>

I've been wanting to put up a RedCloth "dingus" like you find on  
Textism, but always thought it would take too much time and would be  
one more app taking up resources.

Then I got a reminder email from Heroku that I wasn't doing anything  
with my beta invitation.  So I took them up on it.  I wrote a simple  
Sinatra app, did a git push heroku, and basked in its glory.

Nothing fancy, but it's incredibly fast.  Check it out: http://try.redcloth.org/

I plan to style it and integrate it into the reference manual (try out  
the examples via AJAX) at some point, but not bad for a quick hack, eh?

Jason

P.S.: Here's the app:

require 'rubygems'
require 'sinatra'
require 'redcloth'

get '/' do
   haml :index
end

post '/' do
   RedCloth.new(params[:text]).to_html
end