all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master cb45fff0cb: Minor cleanups in X Windows drag-and-drop code
Date: Sun, 10 Apr 2022 16:19:08 +0200	[thread overview]
Message-ID: <871qy5f2cj.fsf@gnus.org> (raw)
In-Reply-To: <87lewd83dx.fsf@yahoo.com> (Po Lu's message of "Sun, 10 Apr 2022 21:38:34 +0800")

Po Lu <luangruo@yahoo.com> writes:

> You have to enable `mouse-drag-and-drop' too, I think the manual does
> say this in the paragraph above the one where
> `mouse-drag-and-drop-region' is explained.
>
> But please suggest a better wording if that's confusing.  Also, please
> report crashes, there are occasionally BadWindow errors which only occur
> on GTK.

Thanks, with

(setq mouse-drag-and-drop-region t
      mouse-drag-and-drop-region-cross-program t)

this does indeed work.  I think what's confusing about that node is that
the start of the node goes into details about dragging *to* Emacs (what
with dnd-indicate-insertion-point etc).  And then midway through the
node, it starts talking about dragging *from* Emacs.

Perhaps it should be split into two subsections -- one about dragging to
Emacs, and one about dragging from Emacs (after the first paragraph
which talks about dragging and dropping in general).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-04-10 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164947536434.655.3851445578620763636@vcs2.savannah.gnu.org>
     [not found] ` <20220409033605.8A5D7C009A8@vcs2.savannah.gnu.org>
2022-04-10 13:29   ` master cb45fff0cb: Minor cleanups in X Windows drag-and-drop code Lars Ingebrigtsen
2022-04-10 13:38     ` Po Lu
2022-04-10 14:19       ` Lars Ingebrigtsen [this message]
2022-04-11  1:02         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qy5f2cj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --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 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.