Skip to content

Conversation

@arximboldi
Copy link

When the action is not supported by the given notification, we return an error condition and report this on the terminal.

It is useful to know whether the notification was successfully invoked, for example, I have this in my hyperland configuration to deal with the newest notification (similar to clicking on it):

bind = $MOD, period, exec, makoctl invoke || makoctl dismiss

An alternative approach for my use-case would be to have the InvokeAction dismiss the notification when the default action is sent to an action-less notification. The chosen approach is more versatile, as the user of makoctl invoke can decide what behavior to chose.

When the action is not supported by the given notification, we return
an error condition and report this on the terminal.

It is useful to know whether the notification was successfully
invoked, for example, I have this in my `hyperland` configuration to
deal with the newest notification (similar to clicking on it):
```
bind = $MOD, period, exec, makoctl invoke || makoctl dismiss
```

An alternative approach for my use-case would be to have the
`InvokeAction` dismiss the notification when the `default` action is
sent to an action-less notification.  The chosen approach is more
versatile, as the user of `makoctl invoke` can decide what behavior to
chose.
arximboldi added a commit to arximboldi/dotfiles that referenced this pull request Sep 3, 2025
@emersion
Copy link
Owner

emersion commented Sep 8, 2025

Rather than checking in makoctl (which is racy), could we check in dbus/mako.c?

@arximboldi
Copy link
Author

That makes sense. I was just inspired by the menu command to do it this way. I don't have time to do this this week though, maybe the next one or the one after.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants