#701 Don't add comment constructs at beginning of empty lines

[Torquil Macdonald Sørensen]

When commenting out a large piece of code which includes empty lines (or lines with just whitespace), using CTRL-e, the resulting "comment constructs" (e.g. //~ in C/C++ code) are also added on the already empty lines.

It happens when using the function "Toggle commentation" with CTRL-e, but not when using "Comment/uncomment lines" using CTRL-d and CTRL-SHIFT-d.

It would be nice if empty/whitespace lines would remain intact when using "Toggle commentation".

[bryonak]

Strongly disagree.
If I have a table with verbose empty lines as an explanatory comment, these lines should be commented as well. If I write a info header with paragraphs, the empty lines belong to the comments, wich should be indicated, as it is right now. This is consistent with preprending * to every newline (even if it's going to be empty) in C-style /**/ comments.

Having completely white lines (without //~ or #~) implies semantical separation of comments, which is most often not desired in my use cases.