[Feature Request] Markdown Support for composing emails about mailspring HOT 13 CLOSED

Hey folks—thanks for reporting this! Version 1.1.0 shipped today which includes an overhauled composer with support for RTL text, font colors, sizes and styles, improved markdown formatting tag support (__, *, **, - for lists, single and triple ` for code blocks) and a lot of other small improvements. It also supports pasting HTML from other programs and preserves a wider range of basic styles. I'll be expanding the markdown support in the editor to include the link syntax and the header syntax soon, and I think that'll pretty much close this out. (Though there are some other great ideas here I think we could tackle separately in the future!)

Going to go ahead and close this since I think we're pretty close, but watch out for the few remaining markdown shortcuts in the next few minor releases.

You can grab the latest version from https://getmailspring.com/download.

from mailspring.

Any update on the extended markdown support, i.e. links and headers?

from mailspring.

It should be built-in? Mailspring keeps adding these lines to the config.json anytime there's a change, though:

    "disabledPackages": [
        "message-view-on-github",
        "personal-level-indicators",
        "phishing-detection",
        "nylas-private-salesforce",
        "github-contact-card",
        "keybase",
        "composer-markdown",
        "composer-scheduler",
        "composer-mail-merge",
        "send-and-archive",
        "main-calendar"
      ]

from mailspring.

Can confirm that it keeps disabling Markdown.

from mailspring.

Hi,

I'm accustomed to write email in markdown, and render with a Chrome extension Markdown Here.

With Mailspring, I have to cut out my content to chrome and paste back after rendering. It's not a "must have" feature but, every I do the pasting I wonder it would be great to have native markdown support!

That said, it doesn't stop Mailspring to be a great mail app! Loved it!

from mailspring.

@bengotow I'm running v1.1.5, but I could not manage to use single and triple ` for code blocks.
Am I doing something wrong?

from mailspring.

For me the single back-tick usually works if there is space before but not e.g like so:
(does not render fixed space)
Furthermore

Coding blocks do not work because MailSpring seems to recognise
the two back-ticks immediately and does not re-render text after third is added.

These two markdown things are the ones I use the most.

from mailspring.

Hi,

Although the current implementation allows for the ``` code block, i find that pasting in the block doesn't support carriage returns. It all sticks in one line, without word wrap.

What I miss the most is the # octothorpe heading style and --- for line separator, maybe most importantly the table syntax.. that allowed for nicely styled tables within email...

Loved it

^^^^
It looks the syntax works on Github as it rendered the table :D

from mailspring.

its verry inclear how markdown works and am unable to use it

from mailspring.

Yes, I agree that the instruction could be more clear.

Anyone with updates on this issue?

from mailspring.

As far as I can see, only code blocks (embedded by single or triple backticks) are recognized and rendered as expected markdown text. Neither headers nor tables do, so I don't think I can say Mailspring supports Markdown for composing. I don't understand why this ticket is closed.

from mailspring.

I don't understand why this ticket is closed.

Same. I know right?

from mailspring.

We are in the process of migrating issues to Discourse, which can better facilitate discussion and discovery, and so GitHub Issues can focus on issues that are confirmed and slated for resolution in the near term. Learn more about the changes here.

This issue appears to be related to one we've already migrated to Discourse:

https://community.getmailspring.com/t/markdown-support-in-composer/322

Please consider joining that community and continuing the discussion there! Votes on the feature suggestion on Discourse will increase the likelihood we implement this.

We're closing and locking the issue here as part of this migration. Rest assured, this doesn't mean the issue is being discarded or ignored. Please consider joining the Discourse community and continuing the discussion there.

We hope to see you on Discourse soon!

-The Mailspring Team

from mailspring.