So I don't forget, the bug I was trying to file was:
Summary: Code gets mangled when pasted into a bug report
Description: For example: MDL-6752. All the new code that I am being asked to consider has lost its indent, which is a pain in the neck. Is there any way round this?
(It's not that difficult to copy and paste the code into an editor, and reindent it, but it would be nice if I did not have to.)
And yet, it's invaluable to be able to post code, and post back comments on the code. Code as attachments means it's harder to review the actual code.
+1 for making it usable to post diffs straight there, without attachments.
+1 for making it usable to post diffs straight there, without attachments.
In reply to Martín Langhoff
Indenting lost from comments in the Moodle Tracker
by Martin Dougiamas -
It sort of works ... it seems to only collapse non-leading whitespace
See MDL-6732 (feel free to test in there)
See MDL-6732 (feel free to test in there)
In reply to Martin Dougiamas
Re: Indenting lost from comments in the Moodle Tracker
by Martín Langhoff -
I can see it. It messes up diffs! 
Looking at the html source, it's replacing spaces with but only leading/trailing spaces, not within the line -- maybe it could respect PRE tags in the comments to support pasting code?
{comment also in bug}
Looking at the html source, it's replacing spaces with but only leading/trailing spaces, not within the line -- maybe it could respect PRE tags in the comments to support pasting code?
{comment also in bug}
In reply to Martin Dougiamas
Re: Indenting lost from comments in the Moodle Tracker
by Martin Dougiamas -
This seems to be a bug in the renderer ... I've filed a bug at Jira. http://jira.atlassian.com/browse/JRA-11235