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
Improve Windows support #3526
Comments
windows 32bit version not supporting..... |
Nit: CMD.exe (aka Command Prompt) is a shell, conhost.exe is the terminal |
Hey team :) By the way, this amazing extension makes it just too obvious when an item is done ;) |
This is still not resolved, but a wrong issue was linked. I've fixed the issue reference
Good catch. Thank you @bl-ue! |
Would ARM support require going for a higher Golang version? One that can build ARM Windows binaries? |
@kushagrarathore The team is still working on it. If you still want to install gh, Check this issue - #2182 |
That's going to PowerShell/Windows Terminal. As for WSL, just consider it the same as Linux. |
We won't be able to support Windows ARM64 until the next version of Go ships (but yes, you can use 32bit or WSL to get around until then as mentioned) |
This comment was marked as spam.
This comment was marked as spam.
Git flags don't work when using PowerShell 7.1.5 ei |
Closing this tracking issue since we've accomplished most of the tasks in this list 🎉 Some items are still tracked separately (e.g. Windows ARM support) but I feel there is no need for a tracking issue anymore. |
This is a tracking issue for rounding up everything related to Windows support in
gh
.Issues
Packaging
gh.exe
binaries in addition to signing the MSI installer #2111 Sign gh.exe within MSIBugs
gh pr diff
returns broken output when usingdelta
pager on Windows #3703 Pager issuesFeatures
repo garden
Docs
Notes
Part of what has made Windows support difficult is the variety of execution environments users might be using. We know we have many Windows users and can tell from within code when we're running on Windows; however, we have no insight right now into which of the many potential Windows environments someone is running
gh
in:Nor what terminal emulator might be in use:
Depending on the combination from the above two lists there may be issues with tab completion, unicode rendering, and color palettes. Our confusion around what environments people are actually in has led to some paralysis in improving Windows support.
I propose:
gh
(Primarily targeted at installing and using a proper unicode-supporting font)The text was updated successfully, but these errors were encountered: