-
Notifications
You must be signed in to change notification settings - Fork 39
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
Unable to run setup hook for gitsigns #143
Comments
I guess it has to do with bootstrapping. After consulting nvim-test.sh:
init.lua:
Now I only wonder if |
OK I figured it out, I can (ab)use |
You are confused. In general, Paq is just the plugin manager, it's not a "configuration framework". In particular, to configure your plugins you can just write the code after calling This is a very common misunderstanding tho. I'll probably rename the option to |
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for these renames is explained in #143. Internals: - Refactor build related functions to ensure the build are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - To ensure only the necessary builds - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for these renames is explained in #143. Internals: - Refactor build related functions to ensure the build are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - To ensure only the necessary builds - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for these renames is explained in #143. Internals: - Refactor build related functions to ensure the build are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - To ensure only the necessary builds - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for these renames is explained in #143. Internals: - Refactor build related functions to ensure the build are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - To ensure only the necessary builds - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for renaming these is explained in #143. Internals: - Refactor build related functions to ensure builds are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for renaming these is explained in #143. Internals: - Refactor build related functions to ensure builds are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
Public API: - Rename `run` option to `build`. - Rename `PaqRunHook` command to `PaqBuild`. Paq will print a deprecation notice if the old names are used. The reason for renaming these is explained in #143. Internals: - Refactor build related functions to ensure builds are executed after all packages have been installed/updated and loaded: - If the hook is a function, it might require a module inside a recently installed package. - If a is package is installed successfully and the build fails, it's better to notify that in two separate messages, instead of notifying the install failed. - Rename `run_hook` to `run_build`, and refactor to make it clear there's 3 possible cases: function, ex command, shell commmand. - Refactor `new_counter` to take a callback (passed in `exe_op`).
I'm not able to run the setup hook for gitsigns by providing it to the
run
parameter in the paq manifest.To Reproduce
Use the following init.lua
And test the installation with e.g.
Expected behavior
Paq runs the post-install hook and the default setup for gitsigns is configured.
Environment:
nvim --version
: 0.8.3git --version
: 2.40.0The text was updated successfully, but these errors were encountered: