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
Funky to looks very promising, but it doesn't seem to cover my use case:
I'd like to commit the local .funk file into a CMS (ie: git). This would allow me to bundle up a bunch of custom aliases which only work within their respective git-repo.
I'd thought/hoped that the "@./" alias would work, but it appears to be written to disk in an expanded form.
One possible solution would be that funky provides a variable ($FUNK) when it executes aliases which would be the path relative to the .funk file. Then I could create my aliases as "$FUNK/bin/apply.sh $@"
The text was updated successfully, but these errors were encountered:
Funky to looks very promising, but it doesn't seem to cover my use case:
I'd like to commit the local .funk file into a CMS (ie: git). This would allow me to bundle up a bunch of custom aliases which only work within their respective git-repo.
I'd thought/hoped that the "@./" alias would work, but it appears to be written to disk in an expanded form.
One possible solution would be that funky provides a variable ($FUNK) when it executes aliases which would be the path relative to the .funk file. Then I could create my aliases as "$FUNK/bin/apply.sh $@"
The text was updated successfully, but these errors were encountered: