Many of the major MarkDown users (e.g. github and stackoverflow) automatically insert “<br>” on “\n”, yellowgrass should do the same.

Submitted by Sverre Rabbelier on 24 March 2010 at 13:50

On 7 April 2010 at 12:59 Eelco Visser commented:

Absolutely not!

One of the great features of markdown is that you can write readable ascii with
hard newlines as you might do in an email, while adapting to the paragraph width
of a webpage.

On 7 April 2010 at 13:05 Sverre Rabbelier commented:

Then my question is still, how do I easily put an entire block of text in ‘verbatim’?

On 7 April 2010 at 13:12 Sander Vermolen commented:

You can use html’s

 element, right?

On 7 April 2010 at 13:13 Sander Vermolen commented:

Right, of course I could have expected that that was not going to work. I meant to say: You can use HTML’s pre element, right?

On 7 April 2010 at 13:17 Eelco Visser commented:

Hmm, now we’re discussing this issue in two channels; just use <verbatim> and </verbatim>

On 7 April 2010 at 13:17 Sverre Rabbelier commented:

Ah, yes that does work I guess.

On 7 April 2010 at 13:18 Sverre Rabbelier commented:

But wow, does it mess up the site layout, see issue 102:

On 7 April 2010 at 13:29 Lennart Kats commented:

I’m not entirely sure if I like the idea, but Sverre’s suggestions would improve readability of things like stack traces and code when people don’t use the <verbatim> tag. Right now, more often than not people post here without using the tag, and every time I end up having to fix the posts myself.

On 7 April 2010 at 13:36 Lennart Kats commented:

I posted a related issue on the YellowGrass issue tracker, but Sander still seems a bit hesitant about it: YellowGrass/91

On 7 April 2010 at 13:52 Sander Vermolen commented:

Indeed. When a manual is needed to use a page, this should be a smell that the page is not user friendly. Adding a manual to the bottom of a page makes the situation worse by cluttering the user’s view. I know that using such a manual (or cheatsheet) at the bottom of an editing page is normal for wikis, but then again, I believe we should only use wikis for deciding how NOT to design a user interface. Furthermore, it is doubtful whether users will actually read the manual.

IMO, the best solution would be a graphical editor. Yet this may take time to become available in WebDSL.

[This comment primarily belongs to the YellowGrass project issue, I copied it]

On 7 April 2010 at 14:10 Danny Groenewegen commented:

I posted a workaround to get newline to br conversion in wikitext here:

On 21 May 2011 at 18:37 Eelco Visser tagged documentation

On 21 May 2011 at 18:37 Eelco Visser tagged markdown

On 21 May 2011 at 18:37 Eelco Visser closed this issue.

Log in to post comments