-
Notifications
You must be signed in to change notification settings - Fork 76
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
Issue with Gorilla CLI on Windows 11 64-bit #34
Comments
Hey @zajcomm thanks for trying out Gorilla, and the detailed error log - appreciate it. |
@ShishirPatil I have the same issue How can I solve this by prefixing or suffixing "on a Windows PowerShell" or "on WSL" I googled it and didn't understand it. |
Hey @MTHALO @zajcomm I just merged #35 which I hope fixes it. Can you try this? @MTHALO yeah so you can try to ask your prompt along with the prefix. For example, $gorilla on a windows powershell list all files in my current directory
$gorilla generate 100 random characters into a file called test.txt on windows powershell Make sure you re-install from source before trying it out! |
@ShishirPatil Good day! I am also encountering the same issue, through CMD and Powershell.
Unexpected token 'on' in expression or statement. Any information would be completely appreciated |
Hey @Ab0rt3dF3tvs this is interesting. I was able to re-create the bug - I'm trying to fix it and will push a PR by Monday.
is the correct way I'd recommend ! Thanks for trying it out, and stay tuned!! |
File suffix works for me: "gorilla provide me x and transpile into .ps1". TextBlaze is a Godsend with cli tooling. Always a please @ShishirPatil Fam! 🙏 |
"@ShishirPatil C:\Users\D>gorilla do you have a help menu?
Unexpected token 'create' in expression or statement. |
Environment
Problem Description
When trying to execute the Gorilla command to generate random characters into a file, I encountered an issue with the command not being recognized.
Steps to Reproduce
make sure to change the path
]xxx
can be different for different prompts:Below is an example when selecting another option:
Expected Behavior
The command should successfully generate 100 random characters into a file called
test.txt
.Actual Behavior
The command prompts are not recognized, resulting in an error message.
Additional Context
This issue seems to be specific to Windows, as the commands mentioned are typical Unix/Linux commands that are not recognized in the Windows environment.
Please let me know if there's anything else I can assist you with!
The text was updated successfully, but these errors were encountered: