From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Patrick Mahan <plmahan@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
"Gene B. Gragg" <gbgg@uchicago.edu>
Subject: Re: Can't open Emacs
Date: Fri, 11 Dec 2020 16:21:53 +0530 [thread overview]
Message-ID: <m2360cwr7a.fsf@codeisgreat.org> (raw)
In-Reply-To: <CAFDHx1+tzD_sKwSXdFtKMLrHSGw49oeY7cHP08NG6wASxF_U0g@mail.gmail.com> (Patrick Mahan's message of "Thu, 10 Dec 2020 23:25:15 -0800")
Patrick Mahan <plmahan@gmail.com> writes:
> On Thu, Dec 10, 2020 at 6:06 PM Gene B. Gragg <gbgg@uchicago.edu> wrote:
>
>> I have been trying to reinstall GNU Emacs (my principal text editor for at
>> least the last ten years) on a recently acquired MacBook Pro (macOS
>> Catalina Version 10.15.7). I unfortunately first trashed the existing
>> version. I have tried both installing with home-brew (brew cask install
>> emacs) and downloading from emacsformacosx.com. When I try to open the
>> application in either case I get, again and again, the message:
>>
>> “Emacs” can’t be opened because Apple cannot check it for malicious
>> software.
>> This software needs to be updated. Contact the developer for more
>> information.
>>
>>
> I have under Security & Privacy the following set -
>
For a newly downloaded App, MacOS will block the application. So the
user will have to launch the app, read the warning, click OK and then
goto below panel to allow Emacs.
System Preferences > Security & Privacy > (Tab) General
The warning for Emacs will be exactly below the radio button that you
have specified.
> Allow apps downloaded from:
> x App Store and identified developers
>
> And I am running Catalina (10.15.7) on my macbook pro.
next prev parent reply other threads:[~2020-12-11 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 23:02 Can't open Emacs Gene B. Gragg
2020-12-11 3:04 ` Stefan Monnier
2020-12-11 5:22 ` Pankaj Jangid
2020-12-11 7:25 ` Patrick Mahan
2020-12-11 10:51 ` Pankaj Jangid [this message]
2020-12-11 13:44 ` Robert Pluim
2020-12-11 18:58 ` Pankaj Jangid
2020-12-13 15:50 ` Robert Pluim
2020-12-13 15:51 ` Tomas Nordin
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=m2360cwr7a.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=gbgg@uchicago.edu \
--cc=help-gnu-emacs@gnu.org \
--cc=plmahan@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.
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).