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
If you define a handler with acpid.handlers.foo.action, it writes the acpid config file using echo "action=${...contents of handler...}" >> $fn. This drops all information about the ACPI event on the floor. It should instead use echo "action=${...contents of handler...} '%e'" >> $fn in order to pass the text of the event to the handler.
The text was updated successfully, but these errors were encountered:
Previously the parameters were just dropped. Now they can be read
from within the handler script. An example to show this is added.
Makes use of the new writeShellScript function as suggested in:
issue NixOS#21557resolves: NixOS#21557
Previously the parameters were just dropped. Now they can be read
from within the handler script. An example to show this is added.
Makes use of the new writeShellScript function as suggested in:
issue #21557resolves: #21557
If you define a handler with
acpid.handlers.foo.action
, it writes the acpid config file usingecho "action=${...contents of handler...}" >> $fn
. This drops all information about the ACPI event on the floor. It should instead useecho "action=${...contents of handler...} '%e'" >> $fn
in order to pass the text of the event to the handler.The text was updated successfully, but these errors were encountered: