From: "Alfred M. Szmidt" <ams@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should Emacs define site-lisp load-path for Dynamically-Loaded Modules?
Date: Fri, 29 Sep 2023 08:36:51 -0400 [thread overview]
Message-ID: <E1qmCjj-0007u7-9X@fencepost.gnu.org> (raw)
In-Reply-To: In-Reply-To: <87h6ngd8or.fsf@thaodan.de> (message from Björn Bidar on Tue, 26
Sep 2023 22:40:52 +0300)
The link you refer to doesn't contain any reference to site-lisp besides *lispdir*.
I thought it was clear that I don't mean to define site-lisp but define
a second site-lisp as you say your self.
site-lisp lives under datadir, hence the reference.
> That makes me ask the questions should there be a second site-lisp for
> dynamic modules in <libdir> by default?
>
> Are they architecture-dependent? Are they libraries or other object
> files? Seems so, off the cuff sounds reasonable.
Did you read the manual?
I've read the manual many times, doesn't mean I remeber each thing in
it. So please use a kinder tone, and assume that not everyone
remebers everything.
Yes dynamic modules are per definition architecture-dependent after
they have been compiled as they use compiled languages such as C or
C++.
next prev parent reply other threads:[~2023-09-29 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:41 Should Emacs define site-lisp load-path for Dynamically-Loaded Modules? Björn Bidar
2023-09-26 16:10 ` Alfred M. Szmidt
2023-09-26 19:40 ` Björn Bidar
2023-09-29 12:36 ` Alfred M. Szmidt [this message]
2023-09-29 20:56 ` Björn Bidar
2023-09-29 10:49 ` Eli Zaretskii
2023-09-29 21:04 ` Björn Bidar
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=E1qmCjj-0007u7-9X@fencepost.gnu.org \
--to=ams@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).