From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: bjorn.bidar@thaodan.de, 69662@debbugs.gnu.org
Subject: bug#69662: 30.0.50; PGTK Window system supports drag-and-drop but doesn't define x-begin-drag
Date: Fri, 15 Mar 2024 13:49:08 +0200 [thread overview]
Message-ID: <86h6h790ln.fsf@gnu.org> (raw)
In-Reply-To: <87bk7gvs2u.fsf@yahoo.com> (message from Po Lu on Thu, 14 Mar 2024 21:52:25 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 69662@debbugs.gnu.org
> Date: Thu, 14 Mar 2024 21:52:25 +0800
>
> > There must be ways around the issue.
>
> It's only that I'm not volunteering to find them with a band of
> unrepentant megalomaniacs waiting to frustrate me at every stage of the
> process. Patches welcome, as always, and thanks in advance.
Please also answer my question up-thread:
> What does this mean in practice, though? Does it mean drag-and-drop
> doesn't work at all in the PGTK builds? Or only some aspects of that
> don't work? We should at least document the limitations.
next prev parent reply other threads:[~2024-03-15 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87il1vy8rd.fsf.ref@yahoo.com>
[not found] ` <87cys42ixp.fsf@>
2024-03-09 10:55 ` bug#69662: 30.0.50; PGTK Window system supports drag-and-drop but doesn't define x-begin-drag Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-14 8:46 ` Eli Zaretskii
2024-03-14 11:22 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87cyrxys5z.fsf@>
2024-03-14 13:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 11:49 ` Eli Zaretskii [this message]
2024-03-15 12:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 12:51 ` Eli Zaretskii
2024-03-15 13:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 11:00 ` Eli Zaretskii
[not found] <65ebd4d3.050a0220.499d0.0a68SMTPIN_ADDED_BROKEN@mx.google.com>
2024-05-20 20:22 ` Stefan Kangas
2024-03-09 3:16 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86h6h790ln.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69662@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=luangruo@yahoo.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).