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

windows install instructions (?????) #747

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

User670
Copy link

@User670 User670 commented Mar 27, 2024

I hope that's an acceptable way of "installing" cheat, because it feels hacky

I hope that's an acceptable way of "installing" cheat, because it feels hacky
I saw `cheat ffmpeg` suggest Linux `for` and `cat`. Might as well say something here so that people are expecting what's coming.
@User670
Copy link
Author

User670 commented Mar 27, 2024

Duplicate of #743. Closing.

@User670 User670 closed this Mar 27, 2024
@User670 User670 reopened this Mar 27, 2024
@User670
Copy link
Author

User670 commented Mar 27, 2024

Reopening. #743 has a powershell script but I'm on command prompt most of the time. It doesn't hurt to mention the dumb way I suppose.

To any maintainers, if you want to accept both this and #743, you might need to manually merge stuff

@danbromberg
Copy link

I'm a Windows 10 Pro user and am very confused about where the 'cheat.exe' executable comes from. Upon reading the doc I installed GO, which did create a 'cheat.exe' in a go\bin directory. However, as soon as I executed 'cheat.exe' from that library, it disappeared! I think Windows saw it as a virus!? So if someone can point me in the right direction on the proper way to install CHEAT on Windows, I'd like to take it for a spin.
Thanks in advance to all who reply.
Dan

@User670
Copy link
Author

User670 commented May 30, 2024

I'm a Windows 10 Pro user and am very confused about where the 'cheat.exe' executable comes from. Upon reading the doc I installed GO, which did create a 'cheat.exe' in a go\bin directory. However, as soon as I executed 'cheat.exe' from that library, it disappeared! I think Windows saw it as a virus!? So if someone can point me in the right direction on the proper way to install CHEAT on Windows, I'd like to take it for a spin. Thanks in advance to all who reply. Dan

@danbromberg Oops, didn't see.

What I added was under "install manually" section. The exe is in cheat-windows-amd64.exe.zip in the releases.

Go is something else.

@danbromberg
Copy link

danbromberg commented May 30, 2024 via email

@User670
Copy link
Author

User670 commented May 31, 2024

Where is the INSTALL MANUALLY section? A URL would help. Thnx, Dan

current version, my proposed change

Also alsd4git proposed a change to the install instruction that uses Chocolatey package manager.

@danbromberg
Copy link

danbromberg commented May 31, 2024

Thanks for the link, User670, you've been very helpful.
BTW, is there a way I could've found this link myself from the main github's CHEAT page?
(I often find navigating around GitHub very unintuitive).

@User670
Copy link
Author

User670 commented Jun 2, 2024

Thanks for the link, User670, you've been very helpful. BTW, is there a way I could've found this link myself from the main github's CHEAT page? (I often find navigating around GitHub very unintuitive).

Go to the cheat repository (https://github.com/cheat/cheat ).

In the readme below the list of files, there is an "installing" section that has a link to an "INSTALLING.md". That gives you the current version of the install guide (which lacks an instruction for Windows).

For my version or alsd4git's version, go to the respective pull request, select the "files changed" tab, and on the diff for the file, use the three dots icon, and select "view file" in the drop down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants