From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 2cec78254e: ; * nt/INSTALL.W64: Fix wording.
Date: Wed, 28 Dec 2022 20:32:52 +0100 [thread overview]
Message-ID: <86lemrtjbv.fsf@gnu.org> (raw)
In-Reply-To: <83tu1f8mtf.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Dec 2022 19:23:08 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arash Esbati <arash@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>
>> Date: Wed, 28 Dec 2022 18:10:50 +0100
>>
>> May I ask why the text above talks about "the resulting binary files"?
>> For me, the '--prefix' option behaves on Windows the same way it does on
>> Unix systems, as described in the INSTALL file[1]:
>
> As you could have seen, this wording was left unchanged from whoever
> wrote them back when this file was added to Emacs.
Yes, I didn't miss that; my question was more in the direction: Should
this be changed, while we're at it?
> Personally, I don't think "binary files" is that bad a choice of words
> for Windows users, because those aren't expected to be familiar with
> Unix-style installation trees.
Why not taking the part from INSTALL file I sent up-thread, adjust it to
Windows and change this part? Do you want me to make a suggestion?
>> P.S.: I admit I've never used '--exec-prefix' in addition to '--prefix'.
>
> There's no --exec-prefix in the text, is there?
No, I meant: I know what '--prefix' on Windows does, but can't tell
about '--exec-prefix' since I've never used it.
Best, Arash
next prev parent reply other threads:[~2022-12-28 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167195684526.24852.2768894906579002881@vcs2.savannah.gnu.org>
[not found] ` <20221225082725.87372C00613@vcs2.savannah.gnu.org>
2022-12-28 17:10 ` emacs-29 2cec78254e: ; * nt/INSTALL.W64: Fix wording Arash Esbati
2022-12-28 17:23 ` Eli Zaretskii
2022-12-28 19:32 ` Arash Esbati [this message]
2022-12-28 19:40 ` 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
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=86lemrtjbv.fsf@gnu.org \
--to=arash@gnu.org \
--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 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).