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
Consider converting simple aliases to abbreviations #41
Comments
@shinriyo Should I give this a stab? I can provide a PR, which might help clarify what this change will mean for the project. |
@bingocaller Thank you for your pullrequest. |
Hello, can you run
So, I reopened the issue. |
@shinriyo Yes, it works for me. I'm on the latest version of shinriyo/breeze, installed through fisher. |
Thank you for replying. I didn't know I ran it.
So, how do I use |
I don't know what it is 😄 . but it may resove.
but, I wanted to know the one-liner remove command 👍 |
@shinriyo |
@bingocaller I didn't try it yet. but I guess like this
|
@shinriyo Yeah, that could probably work! But I don't think it's a problem for other users than you and I, since we're the only ones (that I know of) who have tested the |
I forgot to close |
What?
Since fish supports abbreviations, perhaps we should convert the simple aliases (like
gf
forgit fetch
) to abbreviations?For example, with an abbreviation in place, the input g f Space will result in the full text
git fetch
on the command line; from here the user can keep typing to append stuff to the command. Alternatively, if the user ends the abbreviation with Enter, the full text gets unfolded and the command is issued immediately.Why?
git rebase
rather thangrb
).functions
directory with non-namespaced functions.However!
Depending on how we handle it, this might be a breaking change if people use their breeze aliases inside functions or other aliases.
Also, I'm not entirely sure how to get this to the users since each abbreviation is stored as a global or universal variable and not as a function. Maybe we can add it in a
conf.d
script which runs as part of thefisher
install process?The text was updated successfully, but these errors were encountered: