Hi,
Sure. At the moment (in our use case) it’s hard to tell the difference between code snippets/comments/stack traces in the body of the message/comment. It’s all sort of merges into dense text. It’s also useful to have list for tasks to do, or to outline summary. All to break down the flow into more visual sections. Basically, highlight different parts of the message body to stand apart from other parts. Currently, I think the only highlight that is supported is quoted text. This is essentially the same use case as github’s issues, but with the additional tracker capabilities, queues and all the goodness of the RT. Alex If we knew what we were doing, it wouldn't be called research, would it? -- Albert Einstein > On 17 May 2016, at 14:06, Jim Brandt <jbra...@bestpractical.com> wrote: > > Hi Alex, > > It's a possibility. Can you elaborate on how you would like to see markdown > support added? That is, where and how would you like to use it? > > Jim > > On 5/17/16 6:25 AM, Alex Jironkin wrote: >> Hi, >> >> I was wondering if markdown support is on the cards for RT? It’s popular and >> fairly lightweight. >> >> >> >> Alex >> >> >> If we knew what we were doing, it wouldn't be called research, would it? >> -- Albert Einstein >> >> >> >> --------- >> RT 4.4 and RTIR Training Sessions https://bestpractical.com/training >> * Washington DC - May 23 & 24, 2016 >> > --------- > RT 4.4 and RTIR Training Sessions https://bestpractical.com/training > * Washington DC - May 23 & 24, 2016
signature.asc
Description: Message signed with OpenPGP using GPGMail
--------- RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
