From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 32fe187bdf1: Install rcs2log within Emacs packages for Android
Date: Thu, 24 Aug 2023 20:24:08 +0800 [thread overview]
Message-ID: <87cyzc632v.fsf@yahoo.com> (raw)
In-Reply-To: <83ttsopvya.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Aug 2023 13:37:49 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Why isn't system-type or something similar enough for that?
Because that says nothing about Mailutils.
> And if that's not good enough, I think we should have a Lisp variable
> or function to do this job, because these issues will keep popping up,
> and doing all of that in C, just because we don't have the information
> in Lisp, is not a good idea. We do stuff like that in other cases,
> cf. noninteractive, window-system, daemonp, etc.
But it's cleaner to have them in C. It will consume less space in the
dump image, less Lisp will require revisions upon changes to the C build
system, and so on.
> First, it's cleaner.
How is it more elegant to incessantly pawn issues off into Lisp?
> And second, these issues will happen in Lisp code as well, and
> inventing a primitive for each one of them is not the best idea.
I must disagree: the only bearing such build details have upon process
execution is the name of the executables within exec-directory. Other
details can be adequately addressed through examining the values of
`system-type' and the feature list.
> I don't see how these are relevant. These variables are actually used
> in callproc.c, with the single exception of configure-info-directory.
And also Vshell_file_name. callproc.c's sole job is to set it, based on
build and system information.
prev parent reply other threads:[~2023-08-24 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 7:30 master 32fe187bdf1: Install rcs2log within Emacs packages for Android Eli Zaretskii
2023-08-24 8:42 ` Po Lu
2023-08-24 8:53 ` Eli Zaretskii
2023-08-24 9:30 ` Po Lu
2023-08-24 10:01 ` Eli Zaretskii
2023-08-24 10:11 ` Po Lu
2023-08-24 10:37 ` Eli Zaretskii
2023-08-24 10:51 ` Andreas Schwab
2023-08-24 11:08 ` Eli Zaretskii
2023-08-24 12:24 ` Po Lu [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyzc632v.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@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 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.