From: Cecilio Pardo <cpardo@imayhem.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 3468@debbugs.gnu.org
Subject: bug#3468: drag and drop text
Date: Sun, 29 Sep 2024 13:45:52 +0200 [thread overview]
Message-ID: <55f3d9b3-4a46-4ca1-9f84-c3bf99d1c403@imayhem.com> (raw)
In-Reply-To: <86msjq4rp5.fsf@gnu.org>
On 29/09/2024 13:36, Eli Zaretskii wrote:
> What did you see on Windows 11? Do we always receive "wide" file
> names?
Yes, always wide on Windows 11 on my tests.
> Did you try dragging file names whose characters are not supported by
> the current ANSI codepage, and if so, did it work?
I just tried and it works fine.
>> It runs indeed on the "shell thread". I'll move all the processing to
>> the message handler.
>
> Thanks. By "message handler" you mean w32_read_socket, yes?
Yes.
next prev parent reply other threads:[~2024-09-29 11:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 7:03 bug#3468: drag and drop text Erdkern Erdkern
2019-09-30 15:29 ` Lars Ingebrigtsen
2019-09-30 15:49 ` Eli Zaretskii
2024-09-28 21:52 ` Cecilio Pardo
2024-09-29 7:19 ` Eli Zaretskii
2024-09-29 11:17 ` Cecilio Pardo
2024-09-29 11:36 ` Eli Zaretskii
2024-09-29 11:45 ` Cecilio Pardo [this message]
2024-09-30 21:20 ` Cecilio Pardo
2024-10-05 11:07 ` Eli Zaretskii
2024-10-05 12:07 ` Cecilio Pardo
2024-10-05 12:30 ` Eli Zaretskii
2024-10-05 12:34 ` Eli Zaretskii
2024-10-05 21:41 ` Cecilio Pardo
2024-10-05 21:43 ` Cecilio Pardo
2024-10-06 6:10 ` Eli Zaretskii
2024-10-07 10:28 ` Cecilio Pardo
2024-10-07 12:00 ` Eli Zaretskii
2024-10-08 13:15 ` Eli Zaretskii
2024-10-08 18:51 ` Cecilio Pardo
2024-10-23 17:16 ` Cecilio Pardo
2024-10-24 7:37 ` Eli Zaretskii
2024-10-24 7:56 ` Cecilio Pardo
2024-10-24 8:16 ` Eli Zaretskii
2024-10-24 8:46 ` Cecilio Pardo
2024-10-24 9:40 ` Eli Zaretskii
2024-10-24 16:52 ` Cecilio Pardo
2024-10-25 10:43 ` 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=55f3d9b3-4a46-4ca1-9f84-c3bf99d1c403@imayhem.com \
--to=cpardo@imayhem.com \
--cc=3468@debbugs.gnu.org \
--cc=eliz@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).