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

can't start in nu in windows 10 #322

Open
sontoriyama opened this issue Jan 3, 2025 · 0 comments
Open

can't start in nu in windows 10 #322

sontoriyama opened this issue Jan 3, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@sontoriyama
Copy link

i search "nu" ("" no, only nu) lattest press win key. and open a terminal: this is a text start and finish after basic commands of is -c etc

Environment config file created at: C:\Users\goku-i5\AppData\Roaming\nushell\env.nu
Config file created at: C:\Users\goku-i5\AppData\Roaming\nushell\config.nu
__ ,
.--()°'.' Welcome to Nushell,
'|, . ,' based on the nu language,
!-(\ where all data is structured!

Version: 0.101.0 (windows-x86_64)
Please join our Discord community at https://discord.gg/NtAbbGn
Our GitHub repository is at https://github.com/nushell/nushell
Our Documentation is located at https://nushell.sh
Tweet us at @nu_shell
Learn how to remove this at: https://nushell.sh/book/configuration.html#remove-welcome-message

It's been this long since Nushell's first commit:
5yrs 7months 24days 5hrs 56mins 9secs 300ns

Startup Time: 151ms 252µs 300ns

C:\Windows\system32> is init nu | save $nu.env-path --append
C:\Windows\system32> is doctor
✓ no legacy configurations found
✓ all shells have plugins
• the following shells have plugins incorrectly installed:

  • nu
    remove and regenerate the plugins according to the README, only whitespace can be after the shell plugins
    ✓ all shells have configurations
    C:\Windows\system32> is -c
    inshellisense session [not found]
    C:\Windows\system32> is
    C:\Users\goku-i5\AppData\Roaming\npm\node_modules@microsoft\inshellisense\node_modules@homebridge\node-pty-prebuilt-multiarch\lib\windowsPtyAgent.js:79
    term = this._ptyNative.startProcess(file, cols, rows, debug, this._generatePipeName(), conptyInheritCursor); ^

Error: File not found:
at new WindowsPtyAgent (C:\Users\goku-i5\AppData\Roaming\npm\node_modules@microsoft\inshellisense\node_modules@homebridge\node-pty-prebuilt-multiarch\lib\windowsPtyAgent.js:79:36)
at new WindowsTerminal (C:\Users\goku-i5\AppData\Roaming\npm\node_modules@microsoft\inshellisense\node_modules@homebridge\node-pty-prebuilt-multiarch\lib\windowsTerminal.js:53:24)
at Object.spawn (C:\Users\goku-i5\AppData\Roaming\npm\node_modules@microsoft\inshellisense\node_modules@homebridge\node-pty-prebuilt-multiarch\lib\index.js:30:12)
at new ISTerm (file:///C:/Users/goku-i5/AppData/Roaming/npm/node_modules/@microsoft/inshellisense/build/isterm/pty.js:38:25)
at Object.spawn (file:///C:/Users/goku-i5/AppData/Roaming/npm/node_modules/@microsoft/inshellisense/build/isterm/pty.js:291:12)
at async render (file:///C:/Users/goku-i5/AppData/Roaming/npm/node_modules/@microsoft/inshellisense/build/ui/ui-root.js:16:18)
at async Command. (file:///C:/Users/goku-i5/AppData/Roaming/npm/node_modules/@microsoft/inshellisense/build/commands/root.js:36:5)

Node.js v22.6.0
C:\Windows\system32> 1 03/01/25 23:55:49

@sontoriyama sontoriyama added the bug Something isn't working label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant