Disabling Markdown syntax for tickets generated by end users?
I love Markdown, but a few aspects of the syntax interfere with "normal" emails from your average end user. Ignoring single line breaks and automatically converting "1.", "2." etc into ordered lists, among other things, sometimes drastically alter the intended formatting in unintended ways.
Is there a way to turn off Markdown for new tickets by email and/or replies by email?
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Luke Andrews on 25 May, 2009 03:27 PM
Ah, I see there's already a conversation about this. Sorry for the dupe.
2 Posted by Luke Andrews on 25 May, 2009 03:34 PM
Although my question is more about email than the forum... maybe it is separate. :)
3 Posted by Kyle Neath (Git... on 29 May, 2009 02:55 AM
We actually just recently pushed out a fix to where email is plain formatting by default (no markdown). You can also edit any comment and choose to use markdown or plain text on a comment by comment basis.
Kyle Neath (GitHub Staff) closed this discussion on 29 May, 2009 02:55 AM.
Luke Andrews re-opened this discussion on 29 May, 2009 04:24 AM
4 Posted by Luke Andrews on 29 May, 2009 04:24 AM
Great! I don't see the option for comments, but I'll assume our account hasn't been updated yet.
5 Posted by rick on 29 May, 2009 07:32 AM
It's disabled by default on emails automatically. You can toggle the setting per comment in the 'edit comment' form (see screenshot).
6 Posted by Luke Andrews on 29 May, 2009 03:16 PM
Okay... I do see that, but the meaning of "Remove formatting" wasn't really clear to me.
What I thought you meant, and what I was hoping for, is if you could choose whether to use Markdown while composing the comment -- removing it afterwards seems like a strange way of approaching it.
7 Posted by Kyle Neath (Git... on 04 Jun, 2009 05:43 AM
Luke, I'll be improving the interface for this whole workflow in the next few weeks, so hopefully it'll be clearer then.
Kyle Neath (GitHub Staff) closed this discussion on 04 Jun, 2009 05:43 AM.