[GH-ISSUE #51] [Enhancement] Markdown toggle at run-time #48

New issue

Closed

opened 2026-03-03 01:19:22 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:19:22 +03:00

Owner

Originally created by @Kabouik on GitHub (Aug 4, 2020).
Original GitHub issue: https://github.com/d99kris/nmail/issues/51

While I try to avoid HTML emails as much as possible, I was very happy to see this new feature, that was a nice surprise!

My understanding is the option to either interpret or ignore the Markdown syntax in composed emails is set in main.conf, but cannot be toggled on or off on the fly depending on the emails you are sending. Do you think it would make sense/be worth it to allow that on a per-email basis, either from a toggle in the UI (the default value of which would be in main.conf), or from a magic command in the body of the message (e.g., /markdown followed by new line)?

I know I would need HTML conversion only when I want to send a table or embed images, but otherwise would prefer my emails to be text only even if there is a #, a >, or some --- somewhere in the text, however it is entirely possible that I would be the only one and it's not relevant to support this use case.

Originally created by @Kabouik on GitHub (Aug 4, 2020). Original GitHub issue: https://github.com/d99kris/nmail/issues/51 While I try to avoid HTML emails as much as possible, I was very happy to see this new feature, that was a nice surprise! My understanding is the option to either interpret or ignore the Markdown syntax in composed emails is set in `main.conf`, but cannot be toggled on or off on the fly depending on the emails you are sending. Do you think it would make sense/be worth it to allow that on a per-email basis, either from a toggle in the UI (the default value of which would be in `main.conf`), or from a magic command in the body of the message (*e.g.*, `/markdown` followed by new line)? I know I would need HTML conversion only when I want to send a table or embed images, but otherwise would prefer my emails to be text only even if there is a `#`, a `>`, or some `---` somewhere in the text, however it is entirely possible that I would be the only one and it's not relevant to support this use case.

kerem closed this issue

2026-03-03 01:19:22 +03:00

kerem commented

2026-03-03 01:19:23 +03:00

Author

Owner

@d99kris commented on GitHub (Aug 4, 2020):

Glad you like the feature! Yes, this is a very valid request. It makes sense to be able to toggle it on/off on a per-email basis.

I would be more inclined to enable it with some UI keyboard short-cut rather than an inlined magic command in the message. Let me see what can be done and update this Github issue.

@d99kris commented on GitHub (Aug 4, 2020): Glad you like the feature! Yes, this is a very valid request. It makes sense to be able to toggle it on/off on a per-email basis. I would be more inclined to enable it with some UI keyboard short-cut rather than an inlined magic command in the message. Let me see what can be done and update this Github issue.

kerem commented

2026-03-03 01:19:23 +03:00

Author

Owner

@d99kris commented on GitHub (Aug 20, 2020):

I've implemented support for toggling markdown editing at run-time, using CTRL-N.
Let me know if you encounter any issues with it.

@d99kris commented on GitHub (Aug 20, 2020): I've implemented support for toggling markdown editing at run-time, using `CTRL-N`. Let me know if you encounter any issues with it.

kerem referenced this issue

2026-03-03 01:19:23 +03:00

[GH-ISSUE #48] [Bug] Email reply to Github issue notifications is not showing up on Github #46