Yeah it works like a charm!

Glad to see some snippets. I am terrible with markdown syntax still.

Glad to hear that… it makes my Espresso crash with other sugars installed. 

Solved the crashing problem.

Version 0.3.3

Added ability to check for updates. Unfortunately, I can’t execute a script on startup so you it doesn’t check automaticly.
Improved the Shorten URL feature, it is now much more sensitive and works better. It only shortens URLs and mail addresses.

Download

So it seems like simply nothing is happening for me. Perhaps I’m misunderstanding.

1. Download dc-markdown.sugar-##### and rename to dc-markdown.sugar. Move to ~/Libary/Application Support/Espresso/Sugars
2. Create a file, and name it filename.mardown.
3. Highlight all text, and use the menu option of cmd-shift-c to convert o Markdown.

Nothing happens. I don’t want to be **that** guy, but when I used to use Coda’s plugin, it was as simple as write your Markdown, regardless of the file extension, highlight it, and it converted to HTML. Is this possible with Espresso’s infrastructure?

Any idea where I’m missing out and doing this wrong?

You’re not doing anything wrong; looks like there’s a bug in TEA (which the Markdown.sugar leverages to run its text actions).  I’m looking into it, and will post back once I’ve got a fix.

Great, Ian, thanks so much. I’d love to hear whatever fix you find so I can move all of my writing into Espresso!

live markdown preview is not possible? is there are workaround? (of course i can use “edit in fraise”... but it should be possible with espresso as well?)

The is not currently any way to live preview Markdown documents. We will consider it for future versions, though!

Ian Beck - 13 February 2010 11:41 AM

You’re not doing anything wrong; looks like there’s a bug in TEA (which the Markdown.sugar leverages to run its text actions).  I’m looking into it, and will post back once I’ve got a fix.

So, uh, can’t help but notice that you wrote this in February, and I still can’t use Shift-Command-C to convert Markdown syntax to HTML.

Fortunately I have a workaround—I wrote a service with Automator months ago that converts Markdown to HTML anywhere in the system—but if this is an unresolved bug in TEA somewhere, I thought I would quietly bubble this thread back up.

N.B.: if this is a bug fixed in the mysterious TEA 1.2b3 that I only just bumbled across a reference to a minute or so ago, cheerfully ignore me here.