Closed techstay closed 7 months ago
@techstay which shell is this in and you're still able to successfully run inshellisense --version
? Can you try directly running inshellisense
via inshellisense -s <shell>
I have same problem,i'm using pwsh7.3.9 and windows powershell now. but inshellisense -s pwsh does working,inshellisense bind doesn't working.
same problem
Same problem.
@techstay which shell is this in and you're still able to successfully run
inshellisense --version
? Can you try directly runninginshellisense
viainshellisense -s <shell>
I use pwsh and running inshellisense -s
Same problem. I use MSYS2-bash on Windows
I solve this problems by below steps:
npm config get prefix
to check where npm installkey-bindings-powershell.ps1
, replace $inshellisense
to your npm install pathfor example:
$inshellisense
in key-bindings-powershell.ps1
is $env:USERPROFILE\AppData\Roaming\npm\node_modules\@microsoft\inshellisense\build\index.js
C:\Program Files\nodejs\node_modules
$inshellisense
to c:\PROGRA~1\nodejs\node_modules\@microsoft\inshellisense\build\index.js
be aware of Program Files
, it has a whitespace, so need to write to PROGRA~1
.
hopes this answer helpful.
(this answer is based on this pull request, but copy-paste not work for me, write npm config get prefix
in .ps1
don't work)
os: win10 node: v20.2.0 inshellisence: 0.0.1-rc.4
https://github.com/microsoft/inshellisense/issues/50#issuecomment-1820566295 Refer to the above practice。
Change file's content in this picture.
Closing as the ctrl-a binding was removed in 0.0.1-rc.5
Describe the bug The prompt failed to find its dependencies to launch. When I use
Ctrl+A
to trigger the completion, it raises such errors.To Reproduce After installation, press
ctrl+a
and it raises the errors.Expected behavior proper completion
Environment
inshellisense --version
: 0.0.1-rc.3Additional context I use scoop to install nodejs-lts package, so the installation path may differ from the normal installation.