From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming
Date: Fri, 03 Jan 2025 08:42:42 +0200 [thread overview]
Message-ID: <86a5c8iejh.fsf@gnu.org> (raw)
In-Reply-To: <56f525ed-4540-4fd8-b563-7ea1fbd65064@cs.ucla.edu> (message from Paul Eggert on Thu, 2 Jan 2025 13:15:51 -0800)
> Date: Thu, 2 Jan 2025 13:15:51 -0800
> Cc: stefankangas@gmail.com, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> > Gnulib is a general-purpose library, so it cannot use some of
> > the enhanced functionality we use in Emacs because we have intimate
> > knowledge of what Emacs needs and which functionalities it actually
> > uses. For example, the emulation of pselect is tightly coupled to
> > what Emacs uses it for.
>
> That's understandable, and I wasn't suggesting that we migrate all of
> Emacs's stuff into Gnulib. All I was thinking is that Emacs could use
> lib/config.mk.in unchanged, even when Emacs is being built on
> MS-Windows. (Admittedly this is not a project I could help much with.)
Maybe I'm missing something, but I don't see how that could be done.
If we cannot use some Gnulib functionality on Windows, we cannot
possibly use and compile the corresponding module, can we? Or what am
I missing? Could you elaborate on what you had in mind?
next prev parent reply other threads:[~2025-01-03 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2001.1735773573.32144.emacs-diffs@gnu.org>
2025-01-02 17:30 ` master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming Eli Zaretskii
2025-01-02 17:57 ` Stefan Kangas
2025-01-02 19:38 ` Paul Eggert
2025-01-02 20:30 ` Eli Zaretskii
2025-01-02 21:15 ` Paul Eggert
2025-01-03 6:42 ` Eli Zaretskii [this message]
2025-01-03 19:06 ` Paul Eggert
2025-01-03 20:01 ` Eli Zaretskii
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=86a5c8iejh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/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.