unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: w32-notification-notify and HAVE_DBUS
Date: Fri, 25 Aug 2023 12:37:18 +0200	[thread overview]
Message-ID: <871qfr1k81.fsf@gmx.de> (raw)
In-Reply-To: <877cpj4m3t.fsf@yahoo.com> (Po Lu's message of "Fri, 25 Aug 2023 15:28:22 +0800")

Po Lu <luangruo@yahoo.com> writes:

Hi,

>> You can tell them that they don't want w32-notification-notify when
>> D-Bus is available, since the latter is superior, AFAIU.
>
> D-Bus doesn't supply desktop notifications, it's just a remote procedure
> call system.  For desktop notifications to function, an X desktop
> environment is also required, and those aren't available on MS Windows.

I don't believe that an X desktop is mandatory. All what's needed is a
D-Bus session service "org.freedesktop.Notifications" under MS-Windows.

How it is implemented doesn't matter. I don't know the D-Bus
implementations under MS-Windows, perhaps they are based on X
desktop. But this would be an implementation detail, and not an D-Bus
requirement.

JFTR.

Best regards, Michael.



  parent reply	other threads:[~2023-08-25 10:37 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
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 [this message]
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=871qfr1k81.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=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).