237dmitry

> already undergone several enhancements It shows warning but does not automatically set desired depth

The depth indication is not intuitive for the user. In fact, this is a real problem; there is a high probability of corrupting the resulting json file. Previously, when I...

> This is an old discussion Has anything changed in six years?

I do not view `PS>` in cmdlet's help examples... ``` ------------- Example 1: Get the current directory ------------ Get-Item . Directory: C:\ Mode LastWriteTime Length Name ---- ------------- ------ ----...

> I can provide cut-down versions I tried simple function and it reproduces your issue. Workaround: 

This is because `.\` can be a part of filename: ``` $ ./.\test CommandType Name Version Source ----------- ---- ------- ------ ExternalScript .\test.ps1 /home/herz/Desktop/.\test.ps1 $ cat ./.\test.ps1 $MyInvocation.MyCommand ```

> Maybe the answer is to give users a table of 162 color combinations and just let them tweak the values in whatever way they prefer. This is a good...

> it should be readable IMO. I don't know how to implement it. 16x16 colors in some combinations will be hard to read:  _This can only be done with...

``` export MICRO_TRUECOLOR=1 ``` Or add `MICRO_TRUECOLOR=1` to `/etc/environment` for permanent true color everywhere you run micro. This is in the micro's inner help. `Ctrl+E`, `help colors`

You can find examples of colorschemas and syntax files [here](https://github.com/zyedidia/micro/tree/master/runtime) and help topics on the [main page](https://github.com/zyedidia/micro) micro. I customized editor by that help.