[MlMt] strikethrough

[Guillaume Barrette]

One other point...

I've seen that we may be able to change the markdown processor of 
MailMate. This is a hack, so not the best option and I don't know what 
could break (not tested on my side), but if anyone want to have some 
information.

It seems that we should be able to change the processor by change the 
`sundown` processor for inside MailMate.app bundle (at: 
`/Applications/MailMate.app/Contents/SharedSupport/bin/sundown`) and get 
the results in MailMate. For example, to switch to multimarkdown or 
something else.

Here is a post of someone who did it: 
https://www.mail-archive.com/mailmate@lists.freron.com/msg05913.html

 From what I think, you should replace the `sundown` file with for 
example the `multimarkdown` file while changing its name to `sundown` so 
MailMate catch it. I recommend to backup the `sundown` file if you want 
to try or this should be reverted on each MailMate install/update (so 
you will need to do the procedure again on each update).

So, this is not the best solution and I won't recommend it since this 
could break MailMate, but I thought I would tell in case this could help 
someone.

With that said, another feature request to Benny, it could be great to 
allow a `custom` markup syntax from the MailMate Rich Text preference so 
we can switch to another one that we prefer. And also, adding this to 
the Composer markup drop-down menu could be great to write different 
email in different markup. This could allow to switch (for example) 
between:

- Plain text
- Markdown
- MultiMarkdown
- CriticMarkup
- org-mode
- or anything else that we wish to use

I think this could open some great opportunities with MailMate :)

Or maybe we could have some "tags" to define a section of an email to be 
processed with a specific markup language. For example, see how Marked 
do it for a `Fountain` section using the [scrippet] tag 
[here](https://marked2app.com/help/Fountain_for_Screenwriters.html)

Best,

--
Guillaume

On 13 May 2020, at 8:50, Guillaume Barrette wrote:

> Sorry, correcting last email, the default shortcut for strikethrough 
> is CMD+SHIFT+X`
>
> --
> Guillaume
>
> On 13 May 2020, at 8:48, Guillaume Barrette wrote:
>
>> Hi,
>>
>>   First, MailMate has a s̶t̶r̶i̶k̶e̶t̶h̶r̶o̶u̶g̶h̶ 
>> feature, but it seems it's not based on markdown, but on ASCII 
>> character. Which is great for people who want to read the plain text 
>> version of the email and don't know the markdown way of 
>> strikethrough.
>>
>> You can find this feature in the menubar at: `Format > Strikethrough` 
>> or CMD+X by default I think
>>
>> Regarding the markdown processor, from what I've seen, MailMate uses 
>> `sundown`. You can find the processor at:
>>
>> `/Applications/MailMate.app/Contents/SharedSupport/bin/sundown`
>>
>> However, I don't know if Benny customized it for MailMate.
>>
>> One thing worth noting, from the sundown GitHub page, we can see that 
>> is fully standard compliant, but has optional support for several 
>> non-standard Markdown extensions like:
>>
>> - non-strict emphasis
>> - fenced code blocks
>> - tables
>> - autolinks
>> - strikethrough
>> - and more...
>>
>> So, maybe the strikethrough extension is simply not activated by 
>> Benny? Maybe it would be great to activate this option from sundown 
>> (I'm asking Benny here as a feature request ;) )?
>>
>> Another point regarding aisrael question, that made me think of 
>> [CriticMarkup](http://criticmarkup.com). Maybe it would be great to 
>> add CriticMarkup as an extension like we have for the Math language 
>> or Highlight code feature or as a bundle (if possible)
>>
>> Best,
>>
>> --
>> Guillaume
>>
>> On 13 May 2020, at 8:29, Charlie Clark wrote:
>>
>>> On 13 May 2020, at 14:19, Bryce Wray wrote:
>>>
>>>> Ah, you are absolutely correct, sir. My mistake. As a Multi-MD fan 
>>>> myself, wish it were an option. Maybe someday…
>>>
>>> Two things:
>>> * the documentation should detail what is supported (and possibly 
>>> what isn't supported)
>>> * if we knew which library was being used we might be able to see if 
>>> it can be fixed upstream
>>>
>>> But basically, MailMate falls down frequently because of inadequate 
>>> documentation. It would be nice to "open source" the documentation 
>>> at least so that some power users could contribute to it. That said, 
>>> I fully understand that even just setting up a dedicated (sub?) repo 
>>> for this would be work.
>>>
>>> Charlie
>>>
>>> --
>>> Charlie Clark
>>> Kronenstr. 27a
>>> Düsseldorf
>>> D- 40217
>>> Tel: +49-211-938-5360
>>> Mobile: +49-178-782-6226
>>> _______________________________________________
>>> mailmate mailing list
>>> mailmate at lists.freron.com
>>> https://lists.freron.com/listinfo/mailmate


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20200513/d54a45ca/attachment.htm>