From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Preloading xwidget.el on xwidget builds?
Date: Thu, 16 Dec 2021 06:46:54 +0100 [thread overview]
Message-ID: <877dc5je41.fsf@gnus.org> (raw)
In-Reply-To: <87mtl1kud0.fsf@yahoo.com> (Po Lu's message of "Thu, 16 Dec 2021 13:10:35 +0800")
Po Lu <luangruo@yahoo.com> writes:
>> We've been trying to move to a different architecture for detecting
>> whether Emacs has been built with, and currently has access to, external
>> libraries -- `*-available-p'. It'd be nice if xwidget had that
>> function, too.
>
> The problem is `xwidget' isn't really a library, it's a feature that
> makes use of many different external libraries.
Sorry, I mean "optionally build features".
> Ideally, people would test for the named feature `xwidget-internal',
> but the amount of people who refrained from reading the first
> paragraph of the xwidget node in the Lisp reference manual is
> astonishing.
The first rule of programming is that nobody reads the manual.
(xwidget-available-p 'webkit) could say whether webkit was available,
etc.
>> suggestion -- make `make-xwidget' require widget.el -- is the way to go.
>
> Is calling require okay from C code? If so, that's what I'll do.
It's unusual, but to work around unfortunate dependencies like this, it
should be OK.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-16 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8zpml5d.fsf.ref@yahoo.com>
2021-12-16 0:46 ` Preloading xwidget.el on xwidget builds? Po Lu
2021-12-16 4:33 ` Stefan Monnier
2021-12-16 4:41 ` Po Lu
2021-12-16 4:50 ` Stefan Monnier
2021-12-16 4:51 ` Stefan Monnier
2021-12-16 4:52 ` Po Lu
2021-12-16 5:06 ` Lars Ingebrigtsen
2021-12-16 5:10 ` Po Lu
2021-12-16 5:46 ` Lars Ingebrigtsen [this message]
2021-12-16 7:46 ` Eli Zaretskii
2021-12-16 7:54 ` Po Lu
2021-12-16 7:39 ` Eli Zaretskii
2021-12-16 7:47 ` Po Lu
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=877dc5je41.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).