Fix: help files use one style#3190
Conversation
Signed-off-by: Yevhen Babiichuk (DustDFG) <dfgdust@gmail.com>
Signed-off-by: Yevhen Babiichuk (DustDFG) <dfgdust@gmail.com>
Signed-off-by: Yevhen Babiichuk (DustDFG) <dfgdust@gmail.com>
| color support comes in three flavors. | ||
|
|
||
| * 16-color: A colorscheme that uses the 16 default colors will always work but | ||
| * `16-color`: A colorscheme that uses the 16 default colors will always work but |
There was a problem hiding this comment.
For 16-color, 256-color and true-color the backquotes might be a bit misleading, since these are not "proper names" (option names, terminal names etc)
Why?
I agree, spaces will suit better.
Currently they use spaces. Why change that? |
|
Furthermore, apparently YAML doesn't allow indentation with tabs. This is what happens if I change a space to tab in a syntax file: |
|
One more question. (Only) somewhere in |
Might be worth fixing too. Or maybe it's not really important at all. |
At least it grabs attention when opened in the editor but in the online github version it doesn't have much sense |
|
moved to #3193 |

I also plan:
Use tabs everywhere inside:
```json
```
Use tabs or spaces before
default value:inruntime/help/options.md. Currently there are both types of indents but I think spaces will suit better because tab can have different sizeYeah it is not about help files but about syntax files so I can then rename the PR to "Fix: runtime use one style". So should yaml files use tabs? I vote for tabs