Markdown Here

Get it for Chrome.
Get it for Firefox, Thunderbird, and Postbox.
Discuss it and ask questions in the Google Group.

Markdown Here is a Google Chrome, Firefox, and Thunderbird extension that lets you write email^† in Markdown^‡ and render them before sending. It also supports syntax highlighting (just specify the language in a fenced code block).

Writing email with code in it is pretty tedious. Writing Markdown with code in it is easy. I found myself writing email in Markdown in the Github in-browser editor, then copying the preview into email. This is a pretty absurd workflow, so I decided create a tool to write and render Markdown right in the email.

To discover what can be done with Markdown in Markdown Here, check out the Markdown Cheatsheet and the other wiki pages.

^{†: And Google Groups posts, and Wordpress posts, and Evernote notes, and Postbox! See details.
‡: And TeX mathematical formulae!}

Table of Contents

Installation Instructions
Usage Instructions
Troubleshooting
Compatibility
Notes and Miscellaneous
Building the Extension Bundles
Next Steps, Credits, Feedback, License

Installation Instructions

Chrome

Chrome Web Store

Go to the Chrome Web Store page for Markdown Here and install normally.

After installing, make sure to reload your webmail or restart Chrome!

Manual/Development

1. Clone this repo.
2. In Chrome, open the Extensions settings. (Wrench button, Tools, Extensions.)
3. On the Extensions settings page, click the "Developer Mode" checkbox.
4. Click the now-visible "Load unpacked extension…" button. Navigate to the directory where you cloned the repo, then the src directory under that.
5. The Markdown Here extension should now be visible in your extensions list.
6. Reload your webmail page (and maybe application) before trying to convert an email.

Firefox and Thunderbird

Mozilla Add-ons site

Go to the Firefox Add-ons page for Markdown Here and install normally.

Or go to the "Tools > Add-ons" menu and then search for "Markdown Here".

After installing, make sure to restart Firefox/Thunderbird!

Note: It takes up to a month for Mozilla to approve changes to the Firefox/Thunderbird extension, so updates (features, fixes) will lag behind what is shown here. You can manually choose to install the newest version before it's reviewed from the list of versions: https://addons.mozilla.org/en-US/firefox/addon/markdown-here/versions/

Manual/Development

1. Clone this repo.
2. Follow the instructions in the MDN "Setting up an extension development environment" article.

Usage Instructions

Install it, and then…

1. In Chrome or Firefox, log into your Gmail, Hotmail, or Yahoo account and start a new email. In Thunderbird, start a new message.

2. Make sure you're using the rich editor.

   • In Gmail, click the "Rich formatting" link, if it's visible.
   • In Thunderbird, make sure "Compose messages in HTML format" is enabled in your "Account Settings", "Composition & Addressing" pane.

3. Compose an email in Markdown. For example:

   **Hello** `world`.
   
   ```javascript
   alert('Hello syntax highlighting.');
   ```
   

4. Right-click in the compose box and choose the "Markdown Toggle" item from the context menu. Or click the button that appears in your address bar. Or use the hotkey (CTRL+ALT+M by default).

5. You should see your email rendered correctly from Markdown into rich HTML.

6. Send your awesome email to everyone you know. It will appear to them the same way it looks to you.

Revert to Markdown

After rendering your Markdown to pretty HTML, you can still get back to your original Markdown. Just right-click anywhere in the newly rendered Markdown and click "Markdown Toggle" -- your email compose body will change back to the Markdown you had written.

Note that any changes you make to the pretty HTML will be lost when you revert to Markdown.

In Gmail, you can also use the browser's Undo command (CTRL+Z / CMD+Z, or from the Edit menu). Be warned that you might also lose the last few characters you entered.

Replies

In Gmail, Thunderbird, and Google Groups, you can use "Markdown Toggle" normally: just write your reply (top, bottom, inline, wherever) and then convert. The original email that you're replying to will be left alone. (Technically: Existing blockquote blocks will be left intact.)

In Hotmail and Yahoo (which don't put the original in a blockquote), and optionally in Gmail, Thunderbird, and Google Groups, you can ensure that only the part of the reply that you wrote gets converted by selecting what you want to convert and then clicking "Markdown Toggle" -- see the next section.

Selection/Piecemeal Conversion

Sometimes you don't want to convert the entire email; sometimes your email isn't entirely Markdown. To convert only part of the email, select the text (with your mouse or keyboard), right-click on it, and click the "Markdown Toggle" menu item. Your selection is magically rendered into pretty HTML.

To revert back to Markdown, just put your cursor anywhere in the block of converted text, right click, and click the "Markdown Toggle" menu item again. Now it's magically back to the original Markdown.

Things to know about converting/reverting a selection

• If you select only part of a block of text, only that text will be converted. The converted block will be wrapped in a paragraph element, so the original line will be broken up. You probably don't want to ever do this.

• You can select and revert multiple converted blocks at the same time. One upshot of this is that you can select your entire email, click "Markdown Toggle", and all portions of it that you had converted will be reverted.

• If you don't have anything selected when you click "Markdown Toggle", Markdown Here will check if there are converted blocks anywhere in the message and revert them. If there no converted blocks are found, it will convert the entire email.

Options

The Markdown Here Options page can be accessed via the Chrome, Firefox, or Thunderbird extensions list. The available options include:

• Styling modifications for the rendered Markdown.
• Syntax highlighting theme selection and modification.
• TeX math formulae processing enabling and customization.
• What the hotkey should be.

For Chrome and Firefox, any changes made in the Markdown Here Options are automatically synchronized between your other installations of that browser (if you have the sync feature enabled in the browser).

Troubleshooting

Here are some common problems that people run into.

Chrome/Firefox/Thunderbird: I just installed Markdown Here and the context menu item isn't showing up.

Make sure you restarted Firefox or Thunderbird, and either restarted Chrome or reloaded your webmail page.

Compatibility

Short answer: Gmail and Thunderbird are great. More info about some clients can be found in the wiki.

	Compose	Send	Receive	Notes
Gmail	✓	✓	✓
Thunderbird	✓	✓	✓
Hotmail	✓	✓	Email received from Yahoo does not display with properly separated paragraphs. (Hotmail strips styling off <p> and <div> tags, and Yahoo uses the latter for paragraphs.)	No reply exclusion.
Yahoo	✓	✓	✓	No reply exclusion.
Google Groups	✓	✓	✓	Rendered version doesn't show in digest email. But that's probably true of manually-rich-edited posts as well.
Wordpress	Editor not exactly WYSIWYG, but Preview is accurate			See the Compatibility wiki page for full details and tips
Evernote (web interface)	✓	Seems to strip newlines from <pre> blocks, which breaks display of code.	✓
Postbox	✓	Inserts newlines in raw email, which can mess up code blocks.	✓	No options page. No reply exclusion.

Compose

How Markdown Here behaves when composing an email. E.g., if rendering and reverting looks correct, styling is good, etc.

Send

Negative effect that may occur when sending a rendered email from this email client. E.g., stripped tags and styles.

Receive

How well this email client displays rendered email that it receives (assuming the sender is perfect).

Notes and Miscellaneous

• Markdown Here uses Github Flavored Markdown, with the limitation that GFM special links are not supported (issue #11); nor will they be, as MDH is not Github-specific.

• Available languages for syntax highlighting (and the way they should be written in the fenced code block) can be seen on the highlight.js demo page.

• Images embedded inline in your Markdown will be retained when you "Markdown Toggle". Gmail allows you to put images inline in your email -- this can be much easier than referencing an external image.

• Email signatures are automatically excluded from conversion. Specifically, anything after the semi-standard '-- ' (note the trailing space) is left alone.

  • Note that Hotmail and Yahoo do not automatically add the '-- ' to signatures, so you have to add it yourself.

• The "Markdown Toggle" menu item shows up for more element types than it can correctly render. This is intended to help people realize that they're not using a rich editor. Otherwise they just don't see the menu item and don't know why.

• Styling:

  • The use of browser-specific styles (-moz-, -webkit-) should be avoided. If used, they may not render correctly for people reading the email in a different browser from the one where the email was sent.
  • The use of state-dependent styles (like a:hover) don't work because they don't match at the time the styles are made explicit. (In email, styles must be explicitly applied to all elements -- stylesheets get stripped.)

Building the Extension Bundles

"Building" is really just zipping. Create all archives relative to the src directory.

An important preparatory step is to remove any system-generated hidden files that shouldn't be included in the release file (like Windows' desktop.ini and OS X's .DS_Store, etc.). This shell command will delete those unwanted files:

find . -name "desktop.ini" -or -name ".*" -and -not -name "." -and -not -name ".git*" -print0 | xargs -0 rm -rf

Chrome extension

Create a file with a .zip extension containing these files and directories:

manifest.json
common/
chrome/

Firefox/Thunderbird extension

Create a file with a .xpi extension containing these files and directories:

chrome.manifest
install.rdf
common/
firefox/

Next Steps

See the issues list and the Notes file. All ideas, bugs, plans, complaints, and dreams will end up in one of those two places.

Feel free to create a feature request issue if what you want isn't already there. If you'd prefer a less formal approach to floating an idea, post to the "markdown-here" Google Group.

It also takes a fair bit of work to stay up-to-date with the latest changes in all the applications and web sites where Markdown Here works.

Credits

Markdown Here was coded on the shoulders of giants.

• Markdown-to-HTML: chjj / marked
• Syntax highlighting: isagalaev / highlight.js
• HTML-to-text: mtrimpe / jsHtmlToText

Other stuff not used, but to keep an eye on

• Markdown-to-HTML:

  • evilstreak / markdown-js (There's currently a GFM dialect that seems almost finished. See issue #41.)
  • Pagedown
  • isaacs / github-flavored-markdown (A Showdown derivative)
  • Showdown

• HTML-to-Markdown

  • domchristie / to-markdown
  • leeoniya / reMarked.js

Feedback

All bugs, feature requests, pull requests, feedback, etc., are welcome. Create an issue. Or post to the "markdown-here" Google Group.

License

Code

MIT License: http://adampritchard.mit-license.org/ or see the LICENSE file.

Logo

Copyright 2013, Tatiana A. Fryntoff. Licensed under Creative Commons Attribution 3.0 Unported (CC BY 3.0).

Other images

Creative Commons Attribution 3.0 Unported (CC BY 3.0) License

---