Suggestion: If "fuck" executes "thefuck", go back further in history

[blixt]

See the screenshot below for an example. It would be neat if instead of not giving a fuck, the command would be nice and execute the misspelled command that the user attempted to correct (but failed a second time).

[azze-r]

Did you execute the good command one time before?
If not ,Try this :
git clone myrepo
// it will save the command
and then you can try :

git clne myrepo

fuck

I believe you have to execute the good command at least onc, This will let thefuck to save the good command and can be used again. I will try it more late with my computer and I'll say you if it runs.

[nvbn]

Try 1.35+, probably it works like you want.

[azze-r]

maybe fixed in 1.35+

[boblinux@bobz ~]$ git clne https://github.com/boblinux/Algo_generique_cpp
git : 'clne' n'est pas une commande git. Voir 'git --help'.

Vouliez-vous dire cela ?
clone
[boblinux@bobz ~]$ fuck
git clone https://github.com/boblinux/Algo_generique_cpp
Clonage dans 'Algo_generique_cpp'...
remote: Counting objects: 283, done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 283 (delta 13), reused 0 (delta 0), pack-reused 250
Réception d'objets: 100% (283/283), 202.28 KiB | 351.00 KiB/s, fait.
Résolution des deltas: 100% (157/157), fait.
Vérification de la connectivité... fait.

[blixt]

It always works if writing fuck right after a misspelled command. This issue is about misspelling fuck itself and then calling it again a second time (correctly spelled). Today it just says echo No fuck given but ideally it would go back and correct the original command.

[SanketDG]

@blixt What's that shell?

[blixt]

zsh with oh-my-zsh

On Monday, May 4, 2015, Sanket Dasgupta notifications@github.com wrote:

@blixt https://github.com/blixt What's that shell?

—
Reply to this email directly or view it on GitHub
#103 (comment).

[jhoviatt]

possibly similar to #74

[scorphus]

Fixed in 9ba36c9