8000 Bug when using navi in windows terminal · Issue #926 · denisidoro/navi · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bug when using navi in windows terminal #926

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.

Sign up for GitHub

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

Jump to bottom
Open
hgftrdw45ud67is8o89 opened this issue Dec 19, 2024 · 8 comments
Open

Bug when using navi in windows terminal #926

hgftrdw45ud67is8o89 opened this issue Dec 19, 2024 · 8 comments
Assignees
@alexis-opolka
Labels
bug Something isn't working

Comments

@hgftrdw45ud67is8o89
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
I configured navi with powershell as call cmd according to the official documentation.
However there are error in runtime. After install cheatsheet I

Logs

navi
then pick>config

At line:2 char:2
+ [ -f "$f" ] || navi info
config-example > "$f"
+  ~
Missing type name after '['.
At line:2 char:13
+ [ -f "$f" ] || navi info
config-example > "$f"
+             ~~
The token '||' is not a valid statement
separator in this version.
    + CategoryInfo          : ParserErro
   r: (:) [], ParentContainsErrorRecord
  Exception
    + FullyQualifiedErrorId : MissingTyp
   ename

Versions:
latest

  • OS: Win11,native windows terminal that is in github. Not cmd

Additional context
I then setup git and then picked cheatsheet in the bottom to install it But now I cannot see the subcommand suggestion again.
@hgftrdw45ud67is8o89 hgftrdw45ud67is8o89 added the bug Something isn't working label Dec 19, 2024
@welcome Welcome
Copy link
welcome bot commented Dec 19, 2024

Thanks for opening your first issue here! In case you're facing a bug, please update navi to the latest version first. Maybe the bug is already solved! :)

@alexis-opolka
Copy link
Collaborator

Hi @hgftrdw45ud67is8o89, did you try once again with navi 2.24.0?
The new version fixed some issues related to navi and the windows terminal / PowerShell.

@hgftrdw45ud67is8o89
Copy link
Author

it is still the same

Image

8000
@hgftrdw45ud67is8o89
Copy link
Author
hgftrdw45ud67is8o89 commented Feb 28, 2025 •
edited
Loading

for as long as the command generated/ embedded is wrong syntax it will continue to crash.
Probably need someone experienced to take a look.
@denisidoro any idea?

@alexis-opolka
Copy link
Collaborator

This is the normal behaviour of PowerShell when it encounters a syntax error.
It means that the code used for the config command on the welcome cheatsheet is not adapted to PowerShell and from the looks of it is made with Bash and not PowerShell in mind.

@alexis-opolka
Copy link
Collaborator

Is your issue still active @hgftrdw45ud67is8o89? Even when not using bash cheatsheets? Have you tried using a cmd/PowerShell cheatsheet to see if the issue was still reproduced?

@alexis-opolka alexis-opolka mentioned this issue Mar 25, 2025
Open
@hgftrdw45ud67is8o89
Copy link
Author

?How do i even switch to that cmd cheatsheet?

@alexis-opolka
Copy link
Collaborator

There is no cheatsheet for windows to my knowledge, I'll make a quick one tomorrow.
I'll see what I can do.

@alexis-opolka alexis-opolka self-assigned this Mar 28, 2025
@alexis-opolka alexis-opolka mentioned this issue Apr 7, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexis-opolka alexis-opolka

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexis-opolka @hgftrdw45ud67is8o89
0