Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use active profile for pwsh/powershell to support one drive directories #25

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

cpendery
Copy link
Member

@cpendery cpendery commented Nov 7, 2023

Description

Load the profile dynamically from pwsh/powershell in order to support OneDrive based $profile's.

Testing

  • verified all bindings can bind, work, and can be uninstalled
  • verified bindings actively work on OneDrive based pwsh/powershell profiles

Closes #4

@cpendery cpendery merged commit 8e997fc into main Nov 7, 2023
@AmirRezaei
Copy link

Still getting error:

Select your desired shell for keybinding creation
bash
zsh
fish

powershell
pwsh
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: ENOENT: no such file or directory, open 'C:\Users\itkom\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'] {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\Users\user1\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'
}

Node.js v21.1.0

@cpendery
Copy link
Member Author

cpendery commented Nov 7, 2023

Still getting error:

Select your desired shell for keybinding creation bash zsh fish

powershell
pwsh
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: ENOENT: no such file or directory, open 'C:\Users\itkom\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'C:\Users\user1\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1' }

Node.js v21.1.0

@AmirRezaei did you build/link it locally?

@AmirRezaei
Copy link

Still getting error:
Select your desired shell for keybinding creation bash zsh fish

powershell
pwsh
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: ENOENT: no such file or directory, open 'C:\Users\itkom\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'C:\Users\user1\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1' }
Node.js v21.1.0

@AmirRezaei did you build/link it locally?

I used "npm install -g @microsoft/inshellisense"

@cpendery
Copy link
Member Author

cpendery commented Nov 7, 2023

Still getting error:
Select your desired shell for keybinding creation bash zsh fish

powershell
pwsh
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: ENOENT: no such file or directory, open 'C:\Users\itkom\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'C:\Users\user1\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1' }
Node.js v21.1.0

@AmirRezaei did you build/link it locally?

I used "npm install -g @microsoft/inshellisense"

Ah, @AmirRezaei I haven't published a new release since I merged this fix. That'll be up shortly 0.0.1-rc.2 and you should be able to see it working then

@AmirRezaei
Copy link

Still getting error:
Select your desired shell for keybinding creation bash zsh fish

powershell
pwsh
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: ENOENT: no such file or directory, open 'C:\Users\itkom\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'C:\Users\user1\Documents\WindowsPowershell\Microsoft.PowerShell_profile.ps1' }
Node.js v21.1.0

@AmirRezaei did you build/link it locally?

I used "npm install -g @microsoft/inshellisense"

Ah, @AmirRezaei I haven't published a new release since I merged this fix. That'll be up shortly 0.0.1-rc.2 and you should be able to see it working then

Thank you!

@cpendery cpendery deleted the fix/pwsh-onedrive branch November 7, 2023 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

inshellisense bind does not work when powershell config file is within onedrive
2 participants