Kangaxx-0

I've updated all your comments and it is ready to merge :)

@imsnif I do not why the local build did not see the break, I've fixed it, could you trigger the CI again, and help to merge it

> No worries @Kangaxx-0 - I wish my availability was better, but there's lots to do in the project, so I appreciate your patience! > > I think my main...

@imsnif My new iteration has been out one and half month. I do not mean to rush you, feel free to take a look and let me know if it...

> > Hey @Kangaxx-0 - I'm really sorry for taking so long to get to this and other PRs. It is definitely still on my TODO, but realistically I'm not...

Wants some insight to get this addressed in a clean fashion

> Is this a duplicate of #7653? I know you mentioned part of this in that issue, however, I could not reproduce the original #7653 . I left some investigations...

This is a hard stop for me to contribute `nu` repo without debugging code, I spent some time and still could not make it working, tried native windows which is...

> 0.71.0 includes the ENOTTY fix: https://www.nushell.sh/blog/2022-11-08-nushell-0.71.html https://github.com/nushell/nushell/pull/7001 Does it work for you? I built the dev binary against latest main, and it does not work

> @Kangaxx-0 I ran into the ENOTTY bug via a different shortcut (wayland keybindings triggering nushell scripts directly), so it's possible that there is some other problem specific to VSCode...