From woody.peterson at gmail.com  Mon Mar 10 02:47:58 2008
From: woody.peterson at gmail.com (Woody Peterson)
Date: Sun, 9 Mar 2008 23:47:58 -0700
Subject: [Maruku-users] bad patchfile in last email
Message-ID: <62B536CA-8914-401B-89F9-FF60EE927F76@gmail.com>

After noticing that sending the email took a while, it turns out that  
I diff'd against gem versions I had frozen into vendor/gems and  
checked into svn, and I included the -N flag in the diff (habit), so  
it'll re-create all my svn files when you try the patch - boy is my  
face red :-)

Here's a more reasonable patch.

Oh, looks like my message is awaiting moderation 'cuz of my sub-1M  
patch. Cool. I'll paste the body of my last message here and the mod  
can just discard my original.

### Original message ###

First of all, nice ruby gem. It looks like a great implementation of  
Markdown (and company).

There were two things I ran in to with Markdown/Maruku that I wished  
were different, so I took the liberty to fix them for myself and  
thought I would share:

First of all, a Markdown issue. I don't like that you have to indent 4  
spaces to get code blocks because when you paste in a chunk of code  
you have to pre-indent all the lines. Not really a big deal with any  
decent text editor, but still it bugged me. Then, not sure if this a  
maruku or Markdown issue, but it tries to read stuff in <pre><code>  
blocks and freaks out, so I couldn't just do it the old fashioned way.  
So, I fixed both issues; I chose "{{{" and "}}}" to set off pre-code  
blocks as seen in tiddlywiki syntax (http://www.tiddlywiki.com/), but  
if anyone has any more mainstream suggestions I don't really care what  
it is (now that I think about it, something like "---" or "+---+"  
would be prettier and probably more markdown-ish). Also, when it finds  
<pre><code> or <code><pre> blocks it sets off the same trigger as  
"{{{"'s. Note that there's a restriction that both {{{'s and  
<pre><code>'s have to be on their own line (was lots easier for me to  
implement that way).

Second, I didn't like that it would italicize *any* emphasis triggers,  
even ones in the middle of words (such as ruby variable names  
possibly_like_this). At first I escaped them or wrapped them in code  
ticks, but it started becoming really hard to watch for _'s 'cuz I  
just use them all over the place when writing about ruby code. And  
markdown is supposed to be a natural extension of your meaning  
anyways, right? So, I made it so that emphasis triggers require  
whitespace around them. So _something like this_ would be emphasized,  
but a_variable_like_this wouldn't trigger any emphasis. And for  
consistency same goes for something*like*this (no emphasis), but I  
don't really have any problem with *'s. Note that in the (presumably)  
rare case that someone wants some word to have emphasis within the  
word, they can use <em>'s (I know, html in your markdown... eeew, but  
an acceptable price for me).

Thoughts?

-Woody


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/maruku-users/attachments/20080309/c66c145a/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: maruku_enhancements.real_patch
Type: application/octet-stream
Size: 6760 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/maruku-users/attachments/20080309/c66c145a/attachment.obj 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/maruku-users/attachments/20080309/c66c145a/attachment-0001.html