-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Instructions on complete uninstallation? #455
Comments
Wow, sorry about that. It was still referenced in .bash_profile somewhere. It would still be nice if there were instructions for uninstallation though. |
I removed thefuck via pip3, and now I get this message whenever I start any terminal instance: `Command 'thefuck' not found, but can be installed with: sudo apt install thefuck` |
@adam993 : It seems that when you open a terminal, your shell tries to launch thefuck... have you removed the |
Thanks, It was in .bashrc |
* ~[Doc] Add Uninstall instructions As we need the package and to modify the shell config, users could have a pain in the ass when it comes to retire *The Fuck* from the system. * Update README.md * Update README.md Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Hello,
I do not use any of the supported package managers, so I used the wget command to install fuck. (I didn't realize that it was going to install pip as part of that command, but I guess I should have been paying more attention.)
Anyway, I decided that it's not for me, and removed the line about configuring it from my .bashrc and ran pip uninstall thefuck (or something similar) to uninstall it, which seemed to run successfully. I also removed the "thefuck" directory from my .config folder.
Unfortunately, now every time I open a terminal or access the console I immediately get the message "-bash: thefuck: command not found", so there is still something looking for thefuck every time I use a console. Any idea how to remove this behavior? There doesn't seem to be much included in the readme about uninstallation
The text was updated successfully, but these errors were encountered: