Georg Brandl <g.bra...@gmx.net> added the comment: > 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. > As for your fears about people posting big chunks of code just to make it > highlighted, I never seen any complaint about this in any Trac installation. > People are not that dumb to post a 64kB source code inline and if they do > this - I doubt that it is because of code highlighting. 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. 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. > 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. _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue388> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org http://mail.python.org/mailman/listinfo/tracker-discuss
