[Feature] custom commands for updating/installing

[LordMZTE]

I'm looking to switch to paq, but I've got a bit of an exotic setup. I compile plugins in-place, meaning that the git working tree of the plugin clones is dirty. This is a problem with paq's approach to updating plugins, as git will refuse to overwrite the local changes. If there was a way to customize how paq updates plugins, I could reset the repo first, then pull and then compile the plugin again.

[potamides]

I ran into a similar problem where I ended up with a dirty working directory, too. With packer.nvim I can just add --autostash to the update command to solve it. Perhaps the git commands could be made configurable in paq as well? Alternatively allowing to run multiple shell commands in run could also work, e.g. git config merge.autoStash true && make work tree dirty

[craigmac]

put those two commands in a shell script and just call that: run = 'myupdater'. I don't think paq should widen its scope to dealing with git conflicts.

[LordMZTE]

I ran into a similar problem where I ended up with a dirty working directory, too. With packer.nvim I can just add --autostash to the update command to solve it. Perhaps the git commands could be made configurable in paq as well? Alternatively allowing to run multiple shell commands in run could also work, e.g. git config merge.autoStash true && make work tree dirty

Unfortunately, --autostash won't do it for me, because while it fixes the issue once, the merge will always fail, leaving behind a stash which prevents the next pull from working.

[saccarosium]

I currently we provide a clone_args configuration option. And I've literally just push on the nightly branch the possibility to modify the pull arguments.