From: Cecilio Pardo <cpardo@imayhem.com>
To: 71909@debbugs.gnu.org
Subject: bug#71909: 30.0.60;
Date: Wed, 30 Oct 2024 16:49:44 +0100 [thread overview]
Message-ID: <a27b7acb-26ff-4083-8e8c-0c17497b52f1@imayhem.com> (raw)
In-Reply-To: <86r07x4n93.fsf@gnu.org>
On 30/10/2024 16:35, Eli Zaretskii wrote:
>> The ability to yank DIBV5 will be lost. If there is no alternative such
>> as PNG or image/*, then yank can't be done.
>
> Is this because w32-use-native-image-API set to nil disables loading
> of GDI+? If so, we could load it even if w32-use-native-image-API is
> nil, but just return false from w32_can_use_native_image_api. This
> would allow us to use the GDI+ functions needed for yanking, but not
> those needed for image display. Does this make sense?
Yes, I'll do that.
>>> Why a unibyte string? Is this always binary data or something? If
>>> this could be text (e.g., text/html), then a unibyte string is not the
>>> best choice.
>>
>> It can be binary, but not always. Is unibyte ok for binary cases?
>
> Yes. But we need to document that in the doc string.
>
>> I can
>> treat text/* differently, and make exceptions for types like image/svg+xml.
>
> That'd be much better.
Ok.
I'm on it.
prev parent reply other threads:[~2024-10-30 15:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <865xtnhyn6.fsf@foxmail.com>
2024-10-05 12:28 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-05 12:33 ` Eli Zaretskii
2024-10-05 12:42 ` Eli Zaretskii
2024-10-05 17:14 ` Cecilio Pardo
2024-10-05 19:31 ` Eli Zaretskii
2024-10-05 21:24 ` Cecilio Pardo
2024-10-06 5:59 ` Eli Zaretskii
[not found] ` <87ldz1h5s4.fsf@gmail.com>
2024-10-06 11:50 ` Eli Zaretskii
2024-10-06 12:15 ` Visuwesh
2024-10-20 13:09 ` Ihor Radchenko
2024-10-20 13:51 ` Eli Zaretskii
2024-10-20 13:59 ` Ihor Radchenko
2024-10-20 14:22 ` Eli Zaretskii
2024-10-20 15:02 ` Ihor Radchenko
2024-10-20 15:34 ` Eli Zaretskii
2024-10-20 15:57 ` Ihor Radchenko
2024-10-20 17:50 ` Visuwesh
2024-10-20 17:59 ` Eli Zaretskii
2024-10-20 17:16 ` Cecilio Pardo
2024-10-20 17:58 ` Eli Zaretskii
2024-10-07 10:24 ` Cecilio Pardo
2024-10-07 11:58 ` Eli Zaretskii
2024-10-09 12:52 ` Cecilio Pardo
2024-10-09 13:40 ` Eli Zaretskii
2024-10-23 23:13 ` bug#71909: 30.0.60; yank-media on MS-Windows Cecilio Pardo
2024-10-24 7:18 ` Eli Zaretskii
2024-10-24 8:39 ` Cecilio Pardo
2024-10-24 9:38 ` Eli Zaretskii
2024-10-24 10:43 ` Cecilio Pardo
2024-10-10 10:04 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-10 10:49 ` Eli Zaretskii
2024-10-28 21:46 ` Cecilio Pardo
2024-10-29 14:25 ` Eli Zaretskii
2024-10-29 14:55 ` Eli Zaretskii
2024-10-30 9:05 ` Cecilio Pardo
2024-10-30 15:35 ` Eli Zaretskii
2024-10-30 15:49 ` Cecilio Pardo [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=a27b7acb-26ff-4083-8e8c-0c17497b52f1@imayhem.com \
--to=cpardo@imayhem.com \
--cc=71909@debbugs.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.