unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: w32-notification-notify and HAVE_DBUS
Date: Thu, 24 Aug 2023 17:38:50 +0300	[thread overview]
Message-ID: <83lee0pksl.fsf@gnu.org> (raw)
In-Reply-To: <87zg2g4ms0.fsf@yahoo.com> (message from Po Lu on Thu, 24 Aug 2023 21:01:35 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 24 Aug 2023 21:01:35 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > D-Bus provides its own incompatible notifications
> 
> How are they incompatible when two distinct functions provide them?

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

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.



  reply	other threads:[~2023-08-24 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878ra062ua.fsf.ref@yahoo.com>
2023-08-24 12:29 ` w32-notification-notify and HAVE_DBUS Po Lu
2023-08-24 12:50   ` Eli Zaretskii
2023-08-24 13:01     ` Po Lu
2023-08-24 14:38       ` Eli Zaretskii [this message]
2023-08-25  0:26         ` Po Lu
2023-08-25  5:35           ` Eli Zaretskii
2023-08-25  6:35             ` Po Lu
2023-08-25  7:17               ` Eli Zaretskii
2023-08-25  7:28                 ` Po Lu
2023-08-25 10:18                   ` Eli Zaretskii
2023-08-25 11:44                     ` Po Lu
2023-08-25 10:37                   ` Michael Albinus
2023-08-25 11:43                     ` Po Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lee0pksl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).