Closed zhelenskiy closed 8 months ago
This might be a combination of both node version && CRLF issues. See #16 for the parsing error as this is a duplicate of that. Which node version are you using @zhelenskiy?
@cpendery mentioned it in the description: 16.0.0.
@zhelenskiy, can you try again with 0.0.1-rc.3
once it gets published to npm?
The same
The same
@zhelenskiy you try running the is uninstall
command to clear the key bindings and then create a fresh binding for zsh via is bind
. It may still have left over CRLFs from the first time you created the binding
Ok, now it doesn't show anything in the new terminal, but it also does nothing at all. I use iTerm by the way.
Great, so you can start a new inshellisense session by running ^A
or via running is -s zsh
. It won't start one for you automatically on shell start
It still doesn't work.
You'll need at least node 16.6.0 & higher based on Mozilla's docs for the .at
function. This is the same issue as #14.
Describe the bug The app fails with
.inshellisense/key-bindings.zsh:10: parse error near `__inshellisense'
when I open terminal after the installation.To Reproduce Steps to reproduce the behavior:
Expected behavior Everything works fine
Environment
inshellisense --version
: 0.0.1-rc.1Additional context