Re: w32-notification-notify and HAVE_DBUS

[Eli Zaretskii <eliz@gnu.org>]

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 25 Aug 2023 08:26:38 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The notifications they support are different and look differently.
> > Compare notifications-notify in notifications.el with
> > w32-notification-notify.  But some of the symbols in these two
> > notification mechanisms clash, see
> >
> >   https://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01265.html
> 
> Wasn't that fixed by renaming QCdbus_notify to QCnotify?
> 
> > In general, w32-notification-notify was designed and implemented as a
> > subset of notifications-notify, which requires D-Bus, so if D-Bus is
> > actually compiled in, the fallback is not needed.
> 
> D-Bus, being a mechanism for desktop components to exchange information
> and procedure calls, provides no desktop notifications by itself, and a
> desktop notification server (normally supplied by an X desktop
> environment) must run on the session bus for them to be available.

Sorry, I don't understand the above.  You seem to be saying that
notifications are unrelated to D-Bus?  But doesn't
notifications-notify work by using D-Bus capabilities?

> MS-Windows builds with D-Bus are typically incapable of contacting a
> notification server, since none of the popular X desktop environments
> run on MS-Windows.
> 
> So both features should be made available simultaneously.

From my POV, w32-notification-notify thingy is not important enough to
care about it.  Newer Windows versions moved to a completely different
machinery for desktop notifications, which Emacs doesn't support (and
AFAICT cannot support, as using them requires C++).  In all the years
since I wrote that code, I've heard no complaints and no evidence of
this feature being used by anyone.  So I see no reason to risk
potential problems by removing the condition.