From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Cc: auctex-devel@gnu.org
Subject: Re: [script vs ICon: latex binaries not found]
Date: Mon, 04 Apr 2022 22:03:47 +0200 [thread overview]
Message-ID: <87wng4obto.fsf@mat.ucm.es> (raw)
In-Reply-To: CAO2hHWaqXi+1Wm07rAZuip6JWer4hnfAVmUFttr=c_5mUQPc2A@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
>>> "c" == chad <yandros@gmail.com> writes:
> The other side of the coin is this: macOS uses an ever-tightening security
> system that is intended to prevent users from unintentionally running
> "dangerous" processes. I stopped using macOS before the current generation
> of these systems, but they do fairly typical security-system things,
I am not really a MacOS user (although it is much better than MS
windows) I prefer GNU/Linux, but since I also use frequently an iPad, a
Mac is useful to say the least.
> As an alternative to the wrapper-script approach, there used to be an emacs
> package that helped with some of these issues. IIRC, it's currently called
> exec-path-from-shell.
That is a good suggestion, thanks. I will give it a try.
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2022-04-04 20:03 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 ` [script vs ICon: latex binaries not found] (was: Emacs on macOS) Uwe Brauer
[not found] ` <m2k0c6ozgm.fsf@mat.ucm.es>
2022-04-04 3:05 ` 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 [this message]
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=87wng4obto.fsf@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).