-
Notifications
You must be signed in to change notification settings - Fork 0
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
Preferred interface #1
Comments
Why not just handle both interfaces? I feel like I'll be needing system notifications for some of my scripts, so I was about to make a script that both handles earlyoom's notifications at |
You mean that systembus-notify could handle both? Yes, that would be nice. However, it seems that this project already has three different interfaces, and I'm not sure which one is preferred:
|
it depends, which Interfaces you define, on which the service should listen to... |
I couldn't figure out this project's code at all, so I just ignored this one's interfaces in favor of @rfjakob's interface and my own custom one: https://github.com/HugLifeTiZ/configs-scripts/blob/master/scripts/system-notify |
Hi! earlyoom is looking for a way out of mess that are gui notifications from a service. I found https://wiki.debianforum.de/Desktop-Notification_von_Systemservice_mittels_dbus and now this repo.
I have started a C implementation of basically the same thing you have done in Python: https://github.com/rfjakob/systembus-notify
However, I chose the D-Bus names independently (
net.nuetzlich.SystemNotifications
), which is stupid, as now the both are not compatible. Your project was here before, so I would try to make systembus-notify compatible toat.xundeenergie.notifications
.What do you think? Regards from Vienna.
The text was updated successfully, but these errors were encountered: