unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Retrieving the "include" directory for Emacs Modules
Date: Fri, 20 Dec 2024 09:09:44 +0200	[thread overview]
Message-ID: <86msgqkeyv.fsf@gnu.org> (raw)
In-Reply-To: <87ttazmdvc.fsf@> (message from Björn Bidar on Fri, 20 Dec 2024 01:50:31 +0200)

> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 20 Dec 2024 01:50:31 +0200
> 
> Why not install the Emacs module header to PREFIX/include on these
> platforms

We already do that.

> and deduct the path of the header similarly to how eln-dest-dir is
> determined?

This very complicated, due to the various ways people install Emacs,
the use of symlinks, and other similar issues.  We work very hard to
find the eln files; adding yet another similar (but different) code
path at startup is not my idea of fun.

And again, this list is the wrong place to discuss these issues.



  parent reply	other threads:[~2024-12-20  7:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.624.1733687129.13738.help-gnu-emacs@gnu.org>
2024-12-09  9:58 ` Retrieving the "include" directory for Emacs Modules Marco Antoniotti
2024-12-09 14:56   ` Eli Zaretskii
2024-12-09 15:50     ` Rudolf Schlatte
2024-12-09 22:10     ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-10  3:29       ` Eli Zaretskii
2024-12-11  3:23         ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-11 13:01           ` Eli Zaretskii
2024-12-19 23:50           ` Björn Bidar
     [not found]           ` <87ttazmdvc.fsf@>
2024-12-20  7:09             ` Eli Zaretskii [this message]
2024-12-20  9:01               ` Basile Starynkevitch
2024-12-23  0:47               ` Björn Bidar
2024-12-20 15:41             ` Stefan Monnier
2024-12-23  1:00               ` Björn Bidar
     [not found]               ` <871pxzxlfe.fsf@>
2024-12-24  5:06                 ` Stefan Monnier
2024-12-24 12:36                   ` Eli Zaretskii
2024-12-24 15:30                     ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-24 16:38                       ` Eli Zaretskii
2024-12-24 20:39                         ` Björn Bidar
2024-12-25 17:35                         ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-29  1:03                           ` Björn Bidar
2024-12-22 22:17     ` Arsen Arsenović
     [not found] <mailman.2138.1735192985.7155.help-gnu-emacs@gnu.org>
2024-12-26  9:01 ` Marco Antoniotti
     [not found] <mailman.81.1734714033.1948.help-gnu-emacs@gnu.org>
2024-12-21 20:04 ` Marco Antoniotti
2024-12-23 20:15   ` Björn Bidar
     [not found]   ` <6769c4ea.170a0220.d60c5.1423SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-23 20:56     ` Marco Antoniotti
2024-12-24  5:58       ` Stefan Monnier via Users list for the GNU Emacs text editor
     [not found] <mailman.87.1733936470.18564.help-gnu-emacs@gnu.org>
2024-12-13 11:43 ` Marco Antoniotti
2024-12-13 12:23   ` Eli Zaretskii
     [not found] <mailman.606.1733669386.12711.help-gnu-emacs@gnu.org>
2024-12-08 15:18 ` Marco Antoniotti
2024-12-08 15:29   ` Jean Louis
2024-12-08 15:36     ` Marco Antoniotti
2024-12-08 15:50       ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:36       ` Eli Zaretskii
2024-12-08 16:30   ` Eli Zaretskii
     [not found] <mailman.77.1733590872.28947.help-gnu-emacs@gnu.org>
2024-12-08  9:59 ` Marco Antoniotti
2024-12-08 11:40   ` Eli Zaretskii
2024-12-08 15:47     ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:39       ` Eli Zaretskii
2024-12-08 16:48         ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 17:46           ` Eli Zaretskii
2024-12-09 14:11             ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-07 16:27 Marco Antoniotti
2024-12-07 16:43 ` Eli Zaretskii
2024-12-07 19:09 ` 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=86msgqkeyv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
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).