-
Notifications
You must be signed in to change notification settings - Fork 123
consistent hook names #677
Comments
spec does a cleanup then placed with the postget or preset cleanup placement though |
@tom-wa yes, but its not yet done by the mount tool. We should first get consistent names, and then do the integration. |
I have some questions regarding the hook names/semantics (from
Notes:
|
No, if something is missing, please add it to the proposal. Also if there are too many (which might be the case for the ones marked with ?), you can propose to remove them. Rollback is for the case when one of the set-plugins failed. Docu is in elektra-algorithm.md and elektra-plugins-ordering.md (in doc/help). About the exact placement: it is difficult to discuss it without code, maybe you can mark the positions in a PR for further discussions? |
E.g. the |
One more thing: I misled myself into thinking that I now realized that - I think - this is merely the configuration for the list plugin. |
Wait, not so fast ;)
No, you are right, currently that is the case. The The backend mounting ( From the global hooks point of view it does not matter if it is a single plugin or a list plugin. You invoke the function, the keyset might get modified and you get a return value in either way.
If it is needed (ergo: a hybrid plugin that actually needs different plugins for global and backend placement), we can add it. |
If Take the When I run |
Cannot reproduce (at least not by looking at |
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue. |
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue. |
I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue. |
The text was updated successfully, but these errors were encountered: