The handling of carriage return / linefeed in yellowgrass is problematic.
When I paste in a portion of text the result is “somewhat strange” in the Description Preview

^M
// TEMPORARY DEFINITIONS HERE;^M
^M

define configMAX_TASK_NAME_LEN 8 // somewhere^M

^M
// from Demo/AVR_ATMega323_WinnAVR/FreeRTOSConfig.h^M
// note: different for various architectures!^M
// #define configMAX_PRIORITIES (( unsigned portBASE_TYPE) 4)^M

define configMAX_PRIORITIES 4 // nazien!!^M

^M

Note: it is NOT the ^M which is giving problems here; see below:

typedef array {
bool y[7] = 0;
}

    array x[7]=0;

init{

int xx;
int yy;

for ( xx in x) {
for ( yy in x.y) {
x[xx].y[yy] = 1;
}
}
}

In the above, successive lines with only a newline separating them are joined onto one line.
Only when an extra newline is present, a newline is visible. I hope you can see it; otherwise copy paste some text innto the Description window.

As an aside, it would be better to be able use attachments for these blocks of text, particularly when they are large..

Submitted on 23 August 2011 at 14:18

The text for issue descriptions and comments is typeset in a wikitext variant (Markdown). Consequently, a newline is indeed ignored and a double newline triggers a new paragraph (like Latex). To enter a block of code, you can either use a verbatim block:

…
< /verbatim> (without the additional space before the slash)

or you can start a line with 4 spaces or a tab:

…

Both will give you a block of code. As for the carriage returns, they should be handled as newlines, I guess this is a Windows-specific issue. I will assign it to the upcoming release.

Oh right, the first code block above was interpreted, instead of shown. I fixed that.