From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Cc: auctex-devel <auctex-devel@gnu.org>
Subject: [script vs ICon: latex binaries not found] (was: Emacs on macOS)
Date: Sun, 03 Apr 2022 19:20:57 +0200 [thread overview]
Message-ID: <m2k0c6ozgm.fsf__15471.7847982951$1649006522$gmane$org@mat.ucm.es> (raw)
In-Reply-To: 0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
>>> "PS" == Perry Smith <pedzsan@icloud.com> writes:
> I’m not sure if this is the best list for this:
> I have an M1 Max (arm based / Apple Silicon) MacBook Pro with the
> latest macOS of 12.3. I also have Homebrew installed with about 27
> items installed. I have not installed any libraries just to have the
> libraries but have only installed commands.
> In any case, building emacs was the usual drop dead easy: ./configure; make ; make install
> The one tiny hiccup is you need to do:
> sudo xattr -rds com.apple.quarantine Emacs.app
> to get the Emacs.app to launch. The GNU Emacs web site points users to
> EmacsForMacOSX. EmacsForMacOSX has problems opening files in
> ~/Desktop, ~/Downloads, and ~/Documents if the user is using Apple’s
> cloud solution. My belief is that these problems come up because the
> EmacsForMacOSX starts with a ruby script which eventually launches the
> emacs binary. I believe macOS at that point no longer trusts the
> executable — which seems totally reasonable.
Ah well, I run some tests. With your proposed xattr command, when
clicking on the Emacs icon, then I cannot access these three folders,
without further confirmation. When I start it via the script that
problem does not occur (I recall vaguely that I have to configure the
security setting of the Mac).
I found another strange problem (curious what other think), when
clicking on the icon and starting Emacs this way, then I have the
following problem.
Using auctex in a latex buffer auctex does not find the executable latex
binaries (I have Mac Latex installed with is basically texlive), while
it does when I start emacs with the rugby script. Not sure how is the
culprit here. I put the auctex-devel on the CC
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-04-03 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:52 Emacs on macOS Perry Smith
2022-04-01 7:55 ` Po Lu
2022-04-01 10:47 ` Eli Zaretskii
2022-04-03 7:04 ` [Add xattr to the INSTALLATION file?] (was: Emacs on macOS) Uwe Brauer
2022-04-03 13:45 ` Emacs on macOS Alan Third
2022-04-03 17:20 ` Uwe Brauer [this message]
[not found] ` <m2k0c6ozgm.fsf@mat.ucm.es>
2022-04-04 3:05 ` [script vs ICon: latex binaries not found] (was: Emacs on macOS) chad
2022-04-04 8:38 ` Tim Cross
2022-04-04 20:06 ` [script vs ICon: latex binaries not found] Uwe Brauer
2022-04-04 20:03 ` Uwe Brauer
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='m2k0c6ozgm.fsf__15471.7847982951$1649006522$gmane$org@mat.ucm.es' \
--to=oub@mat.ucm.es \
--cc=auctex-devel@gnu.org \
--cc=emacs-devel@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).