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
Parsing Fish shell aliases seems to be broken #727
Comments
Same issue here. I have |
@andschwa any chance you could test my proposed change fixes your issue? |
Hi, @jberglinds! Can you please add Thanks! |
* Handle user defined fish aliases * Add more aliases to test * Revert unecessary Popen mock changes * Add test for fish aliasing Fixes #727
* Handle user defined fish aliases * Add more aliases to test * Revert unecessary Popen mock changes * Add test for fish aliasing Fixes nvbn#727
In
~/.config/fish/conf.d/aliases.fish
I havealias g 'git'
(a common alias, I think, forg -> git
). This alias works, and even Fish auto-completion recognizes it and works.I'm running
fish, version 2.6.0
withThe Fuck 3.24 using Python 3.6.3
, and just updated~/.config/fish/functions/fuck.fish
to be:The
fuck
alias works for me, except, it's not resolving aliases!I added a new rule to
~/.config/thefuck/rules/git_worktree_checkout.py
:To fix the scenario of checking out a branch that's already checked out in another Git worktree. Using the
@git_support
, my Git aliases (i.e.co -> checkout
) are expanded properly, but Fish gives meNo fucks given
if I try to useg
instead ofgit
.It looks to me that this scenario is supposed to be supported, but I cannot get it to work. The
g
alias is in the output offish -ic functions
:I have tried:
THEFUCK_OVERRIDDEN_ALIASES
but learned from another issue that is for the scenario ofgit
being aliased to something else (e.g.hub
)fish
is my login shell withchsh
Issue #479 seems to be the same problem, but it went away with a newer version of Python(?) I guess.
The text was updated successfully, but these errors were encountered: