You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a fisher plugin developer, I'd like to have functionality for executing a script only once when the plugin is first installed, similar to how uninstall.fish is executed when the plugin is uninstalled. Yes, I could totally achieve the same functionality with a script in conf.d plus an if statement to check if it's already been run. But I find that inefficient and confusing. What do you think about adding support to execute a install.fish or similar on plugin install? Thanks Jorge for creating and maintaining Fisher! I truly enjoy using it a lot more than OMF!
The text was updated successfully, but these errors were encountered:
I think there's a PR to add just that. I don't want to complicate the package API, but I guess this makes sense. You can leave your review there. Thanks. #573
Hi, sorry for reopening this. Reopening because #573 was closed.
I just want to add support for doing this because as a fish package author, I want to be able to notify my users of backwards incompatible changes when they upgrade to new versions. Right now, I don't have a non-hacky way of doing this without spamming the user about the backwards incompatible changes.
As a fisher plugin developer, I'd like to have functionality for executing a script only once when the plugin is first installed, similar to how uninstall.fish is executed when the plugin is uninstalled. Yes, I could totally achieve the same functionality with a script in
conf.d
plus an if statement to check if it's already been run. But I find that inefficient and confusing. What do you think about adding support to execute ainstall.fish
or similar on plugin install? Thanks Jorge for creating and maintaining Fisher! I truly enjoy using it a lot more than OMF!The text was updated successfully, but these errors were encountered: