all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Alan Third <alan@idiocy.org>,
	Viktor Kharitonovich <viktor.kharitonovich@gmail.com>
Cc: 44333@debbugs.gnu.org
Subject: bug#44333: 27.1; macOS menu bar 2-clicks
Date: Sat, 31 Oct 2020 15:08:14 +0100	[thread overview]
Message-ID: <2B2932BB-DFD0-409C-9351-FACEC46927BB@acm.org> (raw)
In-Reply-To: <C98B22FD-791B-4049-B411-77E76FA2D669@gmail.com>

> IIRC you need to add Ruby to the accessibility permissions group in
> the privacy settings.

What are the privacy/security implications of doing so?

Since the Mac port reportedly doesn't suffer from this problem, could we learn from it and do the same?

(There should be a previous bug report.)






  parent reply	other threads:[~2020-10-31 14:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 17:53 bug#44333: 27.1; macOS menu bar 2-clicks Viktor Kharitonovich
2020-10-30 22:42 ` Alan Third
2020-10-31 14:08 ` Mattias Engdegård [this message]
2020-10-31 15:01   ` Alan Third
2020-11-01 10:50     ` Mattias Engdegård
2020-11-01 17:28       ` Alan Third
2020-12-23 20:33         ` Alan Third
2020-12-25 16:06           ` Mattias Engdegård
2020-12-25 17:26             ` Alan Third
2020-12-25 19:20               ` Alan Third
2020-12-25 22:28                 ` Mattias Engdegård
2020-12-26 17:07                   ` Alan Third
2020-12-26 17:42                     ` Mattias Engdegård
2020-12-26 21:52                       ` Alan Third
2020-12-27 16:56                         ` Alan Third
2020-12-27 17:14                         ` Mattias Engdegård
2020-12-27 18:21                           ` NS port menus (was: bug#44333: 27.1; macOS menu bar 2-clicks) Alan Third
2020-12-28 17:38                             ` Mattias Engdegård

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

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

  git send-email \
    --in-reply-to=2B2932BB-DFD0-409C-9351-FACEC46927BB@acm.org \
    --to=mattiase@acm.org \
    --cc=44333@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=viktor.kharitonovich@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.