Benedikt Heine

[I've pushed this now forward to have a few samples to test it with GLib](https://github.com/bebehei/dunst/commits/glib-testsuite). Enough to judge, but not too much to have real work lost. In combination with...

Sorry, but I fail to see your point. A few thoughts: - Why is it actually necessary to init/deinit for every test? Yeah, the order is undefined (which is IMHO...

Ok, so we have to init/deinit. That's ok. What about simple macros for test start and end? ```c #define TEST_START(name) static void test_##name(void) { #define TEST_END(name) } // END test_##name...

I fucked up #541 and I have to fix it. But I guess, writing tests for `queues.c` first might be the best choice. But before writing tests, I want to...

When you use fullscreen rules and have a fullscreen window. In some cases, unrelated notifications get inserted into displayed queue, too. I don't know the full details yet. And I...

I've moved this Issue to the next minor milestone. We definitely don't do it in 1.4. But I would ask: Do we really want to move our testing infrastructure to...

> I wouldn't put that in the X11 refactor that falls more into the settings redesign (#336 ), the implementation part of it is pretty straight-forward. Well, however we should...

I suspect, there is another (dysfunctional) Notification Manager running, started by either systemd or DBus. Please use `dunst -print` to start dunst. So dunst will print the actual notification content....

Have you sent notifications with `notify-send`. It seems, that there are no notifications sent at all. You have to send notifications. (Otherwise `dunst -print` won't be able to print any...

Well, the `dbus-monitor` clearly provides enough evidence, that there are no FDO-specific calls done. This must be a dbus-related problem.