rainloop-webmail: Linebreak/paragraph in mail-editor

I just found this years later.

At least now I know that if I use enter and shift+enter the other way around than in any rich-text (and even some Markdown) editor, it inserts the tags I want other clients to parse.

I agree with @deMattin, it was a stupid decision to invert the most widespread word processor way: it creates an interference for anyone who have done serious work in a word processor. (and is older than 20 I guess?). At least a settings entry should have been made for it.

@ervee: two enter is not a paragraph, it is the indicator of sloppiness in a document. When I was a kid in elementary school, (before everybody had internet even at home), that was the first thing to teach in informatics class’s word processing lectures: if you ever place two or more consecutive paragraph breaks (by pressing enter), you are doing something wrong. I think your reply just shows how this client also encourages bad patterns.

I decided to leave it as is.

Reasons:

• RainLoop exists for a long time and no one asked to fix this thing (except @deMattin 😃).
• RainLoop has some problems with <p> when it trying convert HTML to TEXT and back. This is another very large and complex problem.
• I like <br /> more that <p>. If I want <p> I usually press Enter two times.

Btw.: Rainloop uses ckeditor for mails. I checked http://ckeditor.com/demo and it also does it the right way (also can use numbered paragraphs correct).

And I found: http://ckeditor.com/demo#enter

It is still possible to configure the editor to produce <br> or <div> on ENTER. This is not a recommendation (let’s make the web good!)

😉

http://sdk.ckeditor.com/samples/enterkey.html

Changing the Enter Mode setting to BR or DIV is not recommended. The default CKEDITOR.ENTER_P mode is fully supported by all editor features and plugins and is also the most correct one in terms of best practices for creating web content.

If you want to change it to control paragraph spacing, you should use stylesheets instead. Edit the contents.css file and set up a suitable margin value for elements, for example:

p { margin: 0; }