Improved Markdown Support
Although the current support of the Markdown composer does allow you to compose emails in Markdown (the main reason I bought Airmail in the first place), the composer is limited in many ways:
If you ever switch off the Markdown view, or in any other way navigate away from the Markdown source view, your entire Markdown source is collapsed into the
[original-html]block. This is extremely dissatisfying. You lose the ability to edit the original Markdown source, which, really, is a huge problem.In Markdown mode, regardless of whether autocorrect is on or not, you cannot type ellipses (...), two dashes (--), or draw a line separator (---) without it being autocorrected. This is a definite bug. This is an issue when documenting options passed to shell commands (
git clone --recursive, etc.), and even just using the standard markdown features like the line separator.When typing in the Markdown composer, the cursor turns white, and is nearly invisible in the composer window.
One should be able to edit the signature as well, in case a modification needs to be made.
This is recognized in another issue, but support for GitHub Flavoured Markdown would be great.
Joe Gibson
shared this idea
3 comments
-
Fred
commented
I miss the table support. About 20% of all of my emails contain tables.
-
Fred
commented
Regarding (1), there are exiting tools (e.g. pandoc) for converting HTML to markdown. In addition to recovering the markdown that I wrote and converted to HTML is so easy, it would be fantastic to be able to convert incoming messages to markdown. This would allow plain text and rich text people to communicate with a full range of formatting, each reading and composing messages in their preferred manner.
-
John Pitchko
commented
I agree; the Markdown composer needs some love. Its quite frustrating, for example, to write your signature in Markdown, and have to recreate the whole thing again if you want to update your signature later because AirMail converts it to [original-html].