From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: Make org-notify support macOS without DBus
Date: Wed, 20 Oct 2021 22:54:48 +0700 [thread overview]
Message-ID: <skpe4b$qrf$1@ciao.gmane.io> (raw)
In-Reply-To: <PAXPR08MB6640CD0DA04F7206F393544DA3BE9@PAXPR08MB6640.eurprd08.prod.outlook.com>
On 20/10/2021 16:58, Christopher M. Miles wrote:
> Just update the email subject contains [PATCH]
>
> "Christopher M. Miles" writes:
>
> Mostly Emacs versions under macOS does not have compiled with DBus.
> Or still don't work even compiled with DBus even macOS installed
> dbus with homebrew. I'm under this situation and problem. Spend lot
> of time have not solution to solve this problem. So I give up on
> Emacs DBus support under macOS to make "notifications.el" work.
>
> I added patch on org-notify.el to make it invoke AppleScript command
> to display notifications. Hope it help some macOS users.
>
> [5. text/x-patch;
> 0001-org-attach.el-add-a-new-command-to-archive-web-page.patch]…
Christopher, the patch you attached is related to org-attach and e.g.
handling of monolith links. Does it really solve some notification problem?
Bastien committed your earlier patch for notification through
applescript (that does not protect backslashes in notification text):
b80b0a517de7be94c70d3d6537899a94ac046fab
org-clock.el: Make org-notify support macOS notification
I would expect that dbus-related options has lower priority than
applescript.
next prev parent reply other threads:[~2021-10-20 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 9:27 Make org-notify support macOS without DBus Christopher M. Miles
2021-10-20 9:58 ` [PATCH] " Christopher M. Miles
2021-10-20 15:54 ` Max Nikulin [this message]
2021-10-21 4:07 ` [PATCH] {the CORRECT patch} Christopher M. Miles
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='skpe4b$qrf$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).