From: phillip.lord@russet.org.uk
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Emacs 27.1 Windows Binaries -- testing wanted
Date: Mon, 24 Aug 2020 18:01:48 +0100 [thread overview]
Message-ID: <57cbba80f91fbadd932b94bfa8d353aa@russet.org.uk> (raw)
In-Reply-To: <83wo1o59kt.fsf@gnu.org>
On 2020-08-24 16:48, Eli Zaretskii wrote:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org,
>> phillip.lord@russet.org.uk
>> Date: Mon, 24 Aug 2020 11:14:47 -0400
>>
>> > The advantage of what I proposed is that it also detects the cases
>> > where HarfBuzz is available, but for some reason not used.
>>
>> That can be useful in some cases, but I think in the present case it's
>> a disadvantage: we want to know what the executable (and installed
>> libs)
>> provide, rather than what the ~/.emacs chose to use.
>
> No, we want to know what the executable and its environment, as
> provided in the bundle, will yield at run time.
>
> I agree that it might catch some irrelevant circumstances, but that's
> inevitable, at least if such simple tests are being sought.
At the moment, it is enough to tell me that the distribution I have
produced actually has the features that it has been compiled with.
I've picked simple tests because they do that and simple is better than
complicated. I'll make it complicated when it is clear that simple is
not complicated enough.
Phil
next prev parent reply other threads:[~2020-08-24 17:01 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 2:05 Emacs 27.1 Windows Binaries -- testing wanted Jonathan Mitchell
2020-08-18 4:55 ` Eli Zaretskii
2020-08-18 6:56 ` phillip.lord
2020-08-18 7:11 ` Jonathan Mitchell
2020-08-18 15:34 ` Eli Zaretskii
2020-08-18 15:57 ` Óscar Fuentes
2020-08-18 16:33 ` Eli Zaretskii
2020-08-18 16:48 ` Óscar Fuentes
2020-08-18 17:05 ` Eli Zaretskii
2020-08-18 19:32 ` Stefan Monnier
2020-08-19 2:32 ` Eli Zaretskii
2020-08-19 13:10 ` Stefan Monnier
2020-08-19 15:06 ` Eli Zaretskii
2020-08-19 15:30 ` Stefan Monnier
2020-08-19 16:39 ` Eli Zaretskii
2020-08-18 17:20 ` phillip.lord
2020-08-18 18:11 ` Daniel Brooks
2020-08-18 18:58 ` Eli Zaretskii
2020-08-18 19:54 ` Daniel Brooks
2020-08-18 18:15 ` Eli Zaretskii
2020-08-21 19:16 ` phillip.lord
2020-08-21 19:44 ` Eli Zaretskii
2020-08-21 21:37 ` phillip.lord
2020-08-21 22:53 ` Drew Adams
2020-08-22 6:46 ` Eli Zaretskii
2020-08-22 10:30 ` phillip.lord
2020-08-24 9:28 ` Robert Pluim
2020-08-24 10:40 ` Eli Zaretskii
2020-08-24 12:11 ` Robert Pluim
2020-08-24 15:14 ` Stefan Monnier
2020-08-24 15:48 ` Eli Zaretskii
2020-08-24 16:49 ` Stefan Monnier
2020-08-24 17:06 ` phillip.lord
2020-08-24 17:10 ` Eli Zaretskii
2020-08-24 18:35 ` Stephen Leake
2020-08-24 18:54 ` Stefan Monnier
2020-08-24 17:01 ` phillip.lord [this message]
2020-08-21 20:15 ` Alan Third
2020-08-21 21:56 ` phillip.lord
2020-08-22 6:37 ` Eli Zaretskii
2020-08-22 10:21 ` phillip.lord
2020-08-22 10:40 ` Eli Zaretskii
2020-08-22 10:53 ` phillip.lord
2020-08-22 11:15 ` Eli Zaretskii
2020-08-22 12:52 ` phillip.lord
2020-08-22 13:08 ` Eli Zaretskii
2020-08-22 13:53 ` phillip.lord
2020-08-22 14:35 ` Eli Zaretskii
2020-08-22 15:13 ` phillip.lord
2020-08-22 15:19 ` Eli Zaretskii
2020-08-22 17:28 ` phillip.lord
2020-08-22 17:32 ` Eli Zaretskii
2020-08-22 20:18 ` phillip.lord
2020-08-22 20:32 ` Stefan Monnier
2020-08-23 21:19 ` phillip.lord
2020-08-23 21:57 ` Stefan Monnier
2020-08-23 5:36 ` Eli Zaretskii
2020-08-23 7:53 ` phillip.lord
-- strict thread matches above, loose matches on Subject: below --
2020-08-10 23:00 Emacs 27.1 released Nicolas Petton
2020-08-12 12:01 ` phillip.lord
2020-08-15 17:49 ` Emacs 27.1 Windows Binaries -- testing wanted phillip.lord
2020-08-15 17:54 ` Eli Zaretskii
2020-08-15 18:38 ` Stephen Leake
2020-08-15 19:57 ` Alan Third
2020-08-17 4:44 ` Sivaram Neelakantan
2020-08-17 23:24 ` Tak Kunihiro
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=57cbba80f91fbadd932b94bfa8d353aa@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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.