Jan Klass

I implemented #4520 and #4521. I hope it can be reviewed for hacktoberfest. @matchai can you take a look?

Looks like this is fixed in master 49995301ce90a0f63b2d5f9cbb30021a0f08f6ff, so the next starship release should be fine (and existing envs after updating the generated init script). [`term size`](https://www.nushell.sh/book/commands/term_size.html) had the parameters...

> This only works for Unix systems 😭 Didn't find a bypass for windows though... On Windows you can in the nu shell use `config env` and comment out ```...

Rebased onto merged #4520

[@andytom comment](https://github.com/starship/starship/issues/1631#issuecomment-892986126) suggests this has been resolved. Is that the case, or is this still open? @micc83 did you have a chance to look into that?

I think the two best alternative solutions are showing only the icon (current behavior) or showing the icon with a short human-speaking info like ‘no toolset’ or ‘missing toolset’. ---...

I was just curious. And thought maybe I’d add them.

I ran into another issue that sheds some light. It looks like sections (`{{#child}}`) do not actually get the section context but instead retain the partial root context. This seems...

Do you want me to test that PR or something? I don't know how I would use and test a library locally that I otherwise get via package manager.

I don’t have anything more involved.