dunsctl `history-pop` and `history-rm` doesn't emit a signal?

[bynect]

Discussed in https://github.com/dunst-project/dunst/discussions/1277

^{Originally posted by qxb3 February 8, 2024} Hello! I kinda assume that this actions will emit a events in d-bus but i guess not?

$ dbus-monitor --profile "interface='org.freedesktop.Notifications'"
#type	timestamp	serial	sender	destination	path	interface	member
#					in_reply_to
sig	1707417506.140839	4294967295	org.freedesktop.DBus	:1.73277	/org/freedesktop/DBus	org.freedesktop.DBus	NameAcquired
sig	1707417506.140853	4294967295	org.freedesktop.DBus	:1.73277	/org/freedesktop/DBus	org.freedesktop.DBus	NameLost
mc	1707417511.756545	6	:1.73318	:1.39	/org/freedesktop/Notifications	org.freedesktop.Notifications	GetServerInformation
mc	1707417511.757148	7	:1.73318	:1.39	/org/freedesktop/Notifications	org.freedesktop.Notifications	GetServerInformation
mc	1707417511.757979	8	:1.73318	:1.39	/org/freedesktop/Notifications	org.freedesktop.Notifications	Notify

[bynect]

@fwsmit

I think DBus is well suited for passing signals. For most other things we already pass a signal via DBus, so this just needs to be > added.