Pablo Aguiar

> @scorphus Do you want to keep backwards compatibility with older fish shells? Or can I simply update the history file location? @mainrs: I thought about that. Then I went...

> Oh I think I found the culprit. `git` is an alias/wrapper to `hub` on my machine: > > ```fish > $ type git > git is a function with...

Please check this out: https://github.com/nvbn/thefuck/wiki/Shell-aliases#fish

Please, have a look into 891fbe7 for the motivation. One other thing is that I now see that Fish's `alias` is not so slow as it used to be and...

> I think I will go with that until I run into some errors at which point I can still switch to the `THEFUCK_OVERRIDDEN_ALIASES` solution. It might as well work...

They don't need that because they can speak the same language (or mostly the same). Whereas Fish has a different language.

More in the way of the `pyenv` command in Bash, that turns out to be a [function in Fish](https://github.com/oh-my-fish/plugin-pyenv/blob/master/functions/pyenv.fish): ```fish function pyenv set cmd $argv[1] set -e argv[1] switch "$cmd"...

Let me have a look at this again.

So, there are two reasons I think we should avoid changing the shell function. The main one is backward compatibility. A considerable number of users have the function hardcoded either...

Hey, @davidhart82! I went ahead – as we usually squash commits by the same author that represent one single, “atomic” change – and squashed the two commits you had. So,...