[Tracker-discuss] [issue388] Code highlighting blocks in messages

[anatoly techtonik]

anatoly techtonik <techtonik at gmail.com> added the comment:

On Wed, Apr 6, 2011 at 6:53 PM, Georg Brandl
<metatracker at psf.upfronthosting.co.za> wrote:
>
>> Don't you think that markup processing can greatly improve the quality of
>> information presented in the bug tracker? If code blocks are at least have
>> different background - it will simplify reading a lot.
>
> No, I don't. You can immediately see what is code and what is text even if
> they have the same background.

That's why we need more people to reach a consensus.

> I also never have seen any code in Trac where the highlighting was really
> needed.  I'm not against code highlighting in general (it would be strange
> for me as the author of Pygments), but here I just don't see the point.

So, it is just useless for you, but you won't object if anybody will
do this. Am I right?

> And since it means that you have to introduce a new markup language where
> previously there was none, it's just another thing for people to know when
> using the tracker.

I'm just introducing a {{{ }}} code block. Well, bullet points is a
good addition for choices and summaries in discussions, but it is a
featurecreeping in the scope of this ticket.

>> So, do you know how to approach this to make code blocks in messages work?
>
> Use the same hook we use for linking to issues, extract the code blocks and
> highlight them with Pygments.

Thanks. I hope that's not too hardcore.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________