Bug Report
Summary
Under
- MacOS Big Sur 11.2.3
- iTerm2
- PowerShell 7.1.3
If you run n to get the pick list, while the list is visible, the arrow keys don't actually move the selection at all. It's unclear if this is due to some different handling for arrow keys inside PowerShell or if it's something else about console rendering there.
It does work fine if you use bash or zsh directly, like if you start iTerm2 with bash as the shell.
It does not work if you start bash from inside PowerShell - whatever has taken over the arrow keys has already happened by that time.
Steps to Reproduce
- Open a terminal with a PowerShell session. Not
bash and then run PowerShell, but actually start pwsh as the shell.
- Run
n
- Try to change the selection.
Expected Behaviour
I'd like the selection to change so I can switch Node versions.
Actual Behaviour
The selection doesn't change.
Other Information
As noted, I'm not sure if it's something to do with the arrow keys not coming through or if it's something else. I do notice that running n starts a bash session, and it may be that the nested bash inside PowerShell just doesn't work.
It may be nice to have some alternative input keys, things that aren't arrows/meta keys. Maybe angle brackets <, > or something? Unclear if that'd fix it.
I can work around it by doing
n list
n install [version-from-list]
but, again, would be nice to use the pretty menu. :)
Configuration Details
$ n --version
? 7.2.1
$ command -v node
? /usr/local/bin/node
$ node -p process.platform
? darwin
Bug Report
Summary
Under
If you run
nto get the pick list, while the list is visible, the arrow keys don't actually move the selection at all. It's unclear if this is due to some different handling for arrow keys inside PowerShell or if it's something else about console rendering there.It does work fine if you use
bashorzshdirectly, like if you startiTerm2withbashas the shell.It does not work if you start
bashfrom inside PowerShell - whatever has taken over the arrow keys has already happened by that time.Steps to Reproduce
bashand then run PowerShell, but actually startpwshas the shell.nExpected Behaviour
I'd like the selection to change so I can switch Node versions.
Actual Behaviour
The selection doesn't change.
Other Information
As noted, I'm not sure if it's something to do with the arrow keys not coming through or if it's something else. I do notice that running
nstarts abashsession, and it may be that the nestedbashinside PowerShell just doesn't work.It may be nice to have some alternative input keys, things that aren't arrows/meta keys. Maybe angle brackets
<,>or something? Unclear if that'd fix it.I can work around it by doing
but, again, would be nice to use the pretty menu. :)
Configuration Details