From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Starting Emacs (For Mac OS X) from the command line
Date: Thu, 4 Nov 2021 16:32:46 +0100 [thread overview]
Message-ID: <20211104153246.GB2017@tuxteam.de> (raw)
In-Reply-To: <CEE14A30-3A25-42C5-98E4-44C04B8C626E@traduction-libre.org>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Thu, Nov 04, 2021 at 11:46:34PM +0900, Jean-Christophe Helary wrote:
>
>
> > On Nov 4, 2021, at 23:09, Johannes Brauer <brauer@nordakademie.de> wrote:
> >
> >
> >> Am 04.11.2021 um 14:57 schrieb Jean-Christophe Helary <lists@traduction-libre.org>:
> >>
> >>
> >>
> >>> On Nov 4, 2021, at 22:35, Johannes Brauer <brauer@nordakademie.de> wrote:
> >>>
> >>> Warning: arch-dependent data dir '/Users/build/workspace/Emacs-Multi-Build/label/macos10.14/emacs-source/nextstep/Emacs.app/Contents/MacOS/libexec/': No such file or directory
[...]
To me, libexec sounds like a place where Emacs looks for
external executables (which probably come with the Emacs
distribution itself).
> I checked on my side and MacOS/libexec does not seem to contain extremely important files:
> /MacOS/libexec/rcs2log
[...]
Exactly. So your Emacs might complain if you do anything
it would need one of those external programs for.
Perhaps your installation has put them elsewhere? Or
perhaps the ever-stranger OS has somehow blocked access
to it in a weird way?
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-11-04 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 13:35 Starting Emacs (For Mac OS X) from the command line Johannes Brauer
2021-11-04 13:57 ` Jean-Christophe Helary
2021-11-04 14:09 ` Johannes Brauer
2021-11-04 14:46 ` Jean-Christophe Helary
2021-11-04 15:32 ` tomas [this message]
2021-11-04 21:08 ` Johannes Brauer
2021-11-04 21:19 ` Jean-Christophe Helary
2021-11-05 6:47 ` Yuri Khan
2021-11-05 9:03 ` Jean-Christophe Helary
2021-11-04 14:49 ` 2QdxY4RzWzUUiLuE
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=20211104153246.GB2017@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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 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.