help: Exchange all indentations to spaces and remove trailing ws

[JoeKar]

To hopefully cleanup the mess.
It can be discussed, if tabs are preferred.

[JoeKar]

Argh, crap...duplicates #3190.
@dustdfg Please decide which one to take.
Sorry for that. :(

[dustdfg]

1. I see you did spaces for default values strings but you used indentation 2 spaces when it was 4. I think default value should be indented with 4 spaces to be more noticeable in contrast of other text which use only 2

2. Sorry for images but not links because I don't know how to make links for diffs. It is what you missed:
   
   

3. Currently most of the lines use following indentation:

* 'word' wooooooord
   word

Your PR use:

* 'word' woooooord
  word

I just sticked to the most used format but format of your PR is easier to write (at least for me). It is the reason why yours PR shows +494 −493 it modifies the most used lines and my +45 −45

4. You used spaces for the json blocks in the options file

5. It is also possible to convert all plain text key bindings to back quoted:
   back quotes: Ctrl-e
   plain text: Ctrl-e

[JoeKar]

1. I see you did spaces for default values strings but you used indentation 2 spaces when it was 4. I think default value should be indented with 4 spaces to be more noticeable in contrast of other text which use only 2

Yes and before it was a wild mixture of different approaches. The reason for using 2 spaces instead of 3 was it has base 2, which helps in the moment you work with detectindent and try to indent within the code parts. But we can use 4 or even tabs as well. It's just a matter of preferences.

3. Currently most of the lines use following indentation:

Yes and this in combination with detectindent can cause issues in the moment you extend the code parts.

4. You used spaces for the json blocks in the options file

I used spaces in the whole file to keep it consistent. In case of trouble we can change it again.

5. It is also possible to convert all plain text key bindings to back quoted:

Done.

[dmaluka]

@JoeKar

Yes and this in combination with detectindent can cause issues in the moment you extend the code parts.

I don't think this is enough justification for changing the existing style.

@dustdfg

I just sticked to the most used format but format of your PR is easier to write (at least for me).

While the currently used format (with 3 spaces) is easier to read (at least for me).

Honestly I see no reasons why need to change the current style.

[dustdfg]

It is not always 3 sometimes it is 2. If first word started from ` it will be 3 otherwise 2

[JoeKar]

Honestly I see no reasons why need to change the current style.

Consistency.
To be honest, for me it doesn't really matter for which indentation type and width we vote...we just need to be consistent at least within one file. AFAIK this wasn't the case. :)

[dmaluka]

If first word started from ` it will be 3 otherwise 2

Yes, and it makes sense for readability actually.

[dmaluka]

Thanks, now this PR does just what it says in the title, no extra ambitious changes.
Could you also squash the 3rd patch into the 1st one? For the ease of review, obviously.