unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Corwin Brust <corwin@bru.st>
Cc: mab@gnu.org, Emacs developers <emacs-devel@gnu.org>
Subject: Re: erc-burnt-toast - Provide Windows Notification Center to erc with burnt-toast and erc-match
Date: Wed, 04 Mar 2020 11:13:26 +0100	[thread overview]
Message-ID: <87v9nk77i1.fsf@gmx.de> (raw)
In-Reply-To: <CAJf-WoR1d9qf1QxWVMr0QzUoq=jATsxJhqhnrcKgXtznv4JaHw@mail.gmail.com> (Corwin Brust's message of "Tue, 3 Mar 2020 15:52:48 -0600")

Corwin Brust <corwin@bru.st> writes:

Hi Corwin,

> I'm sick in bed today and writing from my phone.  What's your excuse? ;)

No excuse, I'm on holidays this week :-)

I wish you the best for recovery!

>> In my experience, D-Bus on MS Windows isn't used so much. You cannot
>> expect it running for MS Windows users of Emacs in general.
>
> As you point out there is little likelihood we will implement enough
> of DBUS to create excitement among windows users inspire it's
> popularity for use outside Emacs.   Moreover, I think neither of us is
> motivated to do anything like a proper DBUS implementation that lives
> outside Emacs.  I wasn't really thinking about trying to do that,
> although it would be cool to help that effort along somehow.

And there's also another problem. D-Bus is just infrastructure,
providing interprocess communication means. On GNU/Linux, we use D-Bus
to speak with the service "org.freedesktop.Notifications", which offers
the API for desktop notifications. I haven't heard of a similar D-Bus
service implementation for MS Windows.

> Would it make sense to create am elisp package that installs advice on
> the functions that (for most users) invoke DBUS?  It seems like,
> especially, this could be the easiest way to get windows notification
> center support into core quickly.

I would oppose such an approach. We shouldn't fake D-Bus on MS Windows,
when it isn't D-Bus.

Instead of, we might try to implement the notifications.el interface
with other means but D-Bus on MS Windows.

But even this wouldn't be necessary, if we have alert.el as general
notification interface for Emacs. We could add just another package
which implements windows notification center, and integrate it into
alert.el like the other existing alert styles.

For MS Windows specific implementation options, I cannot speak seriously
about. However, ...

> This would look rather like the DBUS wrapper in C for GNU/Linus, Mac,
> and Cygwin but wrapping (probably) the Windows Community Toolkit.
> This would definitely allow us to properly associate Emacs as the
> originating process and probably opens the door to let users
> create/manage GUIDs on the fly, which can to differentiate toasts as
> from different logical processes within Emacs and/or different users
> of Emacs.

... this doesn't sound bad in my ears.

Best regards, Michael.



  reply	other threads:[~2020-03-04 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 19:17 Fwd: erc-burnt-toast - Provide Windows Notification Center to erc with burnt-toast and erc-match Michael Albinus
2020-03-03 21:52 ` Corwin Brust
2020-03-04 10:13   ` Michael Albinus [this message]
2020-03-04 15:38     ` Eli Zaretskii
2020-03-04 15:56       ` Michael Albinus
2020-03-04 22:09         ` Corwin Brust
2020-03-05  6:28           ` Eli Zaretskii

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=87v9nk77i1.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=mab@gnu.org \
    /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).