-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Bug report] Cannot programmatically delete abbreviations containing certain characters #118
Comments
This comment has been minimized.
This comment has been minimized.
^
)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
^
)^
) or exclamation point (!
)
^
) or exclamation point (!
)
Abbreviations with quotation marks also can't be deleted.
Looks relevant https://unix.stackexchange.com/a/626529/248959 |
add failing tests for erasure limitations [#118]
This comment has been minimized.
This comment has been minimized.
Thanks again for reporting // Going to hide most of the comments in this issue as "resolved" but leaving this open because there's still a little goofiness in
There are failing tests for those in the branch As always, can manually delete the abbreviation by editing Or use a session abbreviation ( |
@olets's maintainer edit: this generalized into several bugs related. Summarizing here.
erase
outputs a success message but doesn't actually delete if the abbreviation contains^
) (original report)#
)!
)"
)'
)For the ones not checked off, read #118 (comment) for workarounds.
Original report follows…
Is there an existing issue for this?
Update the issue title
Expected Behavior
The abbreviation should be deleted.
Actual Behavior
zsh-abbr claims the abbreviation was deleted, but it is not.
Steps To Reproduce
$ abbr e a^ Erased regular user abbreviation `a^`
Environment
Installation method
Homebrew
Installation method details
Homebrew 4.3.0-20-g1f603d3
Anything else?
No response
The text was updated successfully, but these errors were encountered: