feat: Add support for Windows CMD and easier setup for Powershell
#1329
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Some proof of how I tested it: On On |
|
No one interested in making it work on Windows? |
|
Hola, Gerardo!
Yes, definitely. Great to see some developments in that direction. I'll review this PR asap. Thanks for contributing! |
scorphus
requested changes
Mar 13, 2023
scorphus
approved these changes
Jul 9, 2023
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows CMD support is almost impossible without removing
c:\Python310\Scripts\fuck.exe, so I did (only affects windows installation), and added afuck.bat(mandatory for CMD support).This created a problem for first time users of
PowerShell/pwsh, so I createdfuck.ps1to solve it, and also auto configure the$PROFILERelated