From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Andrew Schein <andrew@andrewschein.com>
Cc: emacs-devel@gnu.org
Subject: Re: drag events should be defined as a movement to a different buffer position (Bug 9186)
Date: Sun, 21 Aug 2011 11:58:33 +0200 [thread overview]
Message-ID: <4E50D6C9.9080307@swipnet.se> (raw)
In-Reply-To: <CAE49FEe-4s-RGduKdVoSHSRpPnz4OCFx2KkHmm_S4a+8CbwMCA@mail.gmail.com>
Can you drag-copy one character with your change?
Jan D.
Andrew Schein skrev 2011-08-19 19:48:
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2011-08/msg00405.html
>
> Back in 2001, the following revision defined the behavior of mouse
> movements to cause a drag-copy to occur even when the position within
> a buffer does not change:
>
> revno: 40721
> committer: Richard M. Stallman<rms@gnu.org>
> timestamp: Mon 2001-11-05 04:19:56 +0000
> message:
> (read_char): Use Fcar and Fcdr, not Fnth.
> (record_char): Likewise.
>
> (make_lispy_event): Don't insist a drag event must move to a different
> buffer position. Instead, check for moving at least double_click_fuzz.
>
> As a result, even clicking on the emacs window is enough to blow away
> a pre-existing drag copy buffer if your hand moves even slightly...
> making the pasting a drag-copy from a separate window a gamble. This
> is the case if you use your mouse to activate the emacs window instead
> of alt-tab or some other mechanism. Also, the current emacs behavior
> is contrary to the user experience of other x-based applications such
> as firefox.
>
> Options for fixing this include reverting to a position-based rule or
> else creating an emacs lisp variable that controls this behavior (as
> exists for turning on/off drag copy altogether). My patch takes the
> former approach.
>
> Cheers,
>
> Andrew
>
next prev parent reply other threads:[~2011-08-21 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 17:48 drag events should be defined as a movement to a different buffer position (Bug 9186) Andrew Schein
2011-08-21 9:58 ` Jan Djärv [this message]
2011-08-22 16:24 ` Andrew Schein
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=4E50D6C9.9080307@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=andrew@andrewschein.com \
--cc=emacs-devel@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.