From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, p.stephani2@gmail.com, 48228@debbugs.gnu.org
Subject: bug#48228: json-serialize should signal error when dll is not found [MS Windows]
Date: Thu, 6 May 2021 18:26:49 +0300 [thread overview]
Message-ID: <b7c6faab-4862-77e5-1121-af372deb3150@gmail.com> (raw)
In-Reply-To: <75507c21-1910-5f4d-76d7-63fc3c0dc2a9@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
I'd definitely enjoy a more standardized API for testing optional
feature presence.
We already have system-configuration-features, seems like it's
reasonable we get system-configuration-working-features(can't think of a
good name), which would do X-available-p for every X in
system-configuration-features.
But first we'd have to get X-available-p(or some other convention)
working for everything. Would it be acceptable for Emacs to ship with a
small image in every supported format? Then imageX-available-p can be
implemented by opening that image and catching the failure in
create-image. I know that the spash.* image is already shipped in most
formats, even in bmp for some reason.
This would let you quickly test which features are working... Now I have
to go through a checklist
<https://github.com/sg2002/ms-windows-builder.el#emacs-optional-feature-checklist>.
Then I'd be able to automate such a check, which would be pretty helpful.
[-- Attachment #2: Type: text/html, Size: 1256 bytes --]
next prev parent reply other threads:[~2021-05-06 15:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 15:25 bug#48228: json-serialize should signal error when dll is not found [MS Windows] Dmitry Gutov
2021-05-04 15:46 ` Philipp Stephani
2021-05-04 15:49 ` Dmitry Gutov
2021-05-04 16:08 ` Eli Zaretskii
2021-05-04 16:10 ` Dmitry Gutov
2021-05-04 16:43 ` Robert Pluim
2021-05-04 16:59 ` Dmitry Gutov
2021-05-04 17:42 ` Eli Zaretskii
2021-05-04 17:47 ` Dmitry Gutov
2021-05-04 18:07 ` Eli Zaretskii
2021-05-05 22:36 ` Dmitry Gutov
2021-05-06 15:26 ` Nikolay Kudryavtsev [this message]
2021-05-06 15:45 ` Eli Zaretskii
2021-05-06 16:13 ` Nikolay Kudryavtsev
2021-05-06 16:18 ` Eli Zaretskii
2021-05-06 16:29 ` Nikolay Kudryavtsev
2021-05-06 16:36 ` Eli Zaretskii
2021-05-06 16:42 ` Nikolay Kudryavtsev
2021-05-06 16:46 ` Eli Zaretskii
2021-05-06 17:02 ` Nikolay Kudryavtsev
2021-05-06 17:11 ` Dmitry Gutov
2021-05-06 17:36 ` Nikolay Kudryavtsev
2021-05-06 17:55 ` Eli Zaretskii
2021-05-08 4:48 ` Richard Stallman
2021-05-04 16:44 ` Eli Zaretskii
2021-05-04 17:00 ` Dmitry Gutov
2021-05-04 17:44 ` Eli Zaretskii
2021-07-20 12:50 ` Lars Ingebrigtsen
2021-07-20 12:51 ` Lars Ingebrigtsen
2021-07-20 13:22 ` Dmitry Gutov
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=b7c6faab-4862-77e5-1121-af372deb3150@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=48228@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=p.stephani2@gmail.com \
--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 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).