GNU bug report logs -
#34014
Make mouse-drag-copy-region support immediate yanking at point
Previous Next
Full log
Message #32 received at 34014 <at> debbugs.gnu.org (full text, mbox):
No, this does not work - it kills between the original mouse position
and the position where the S-mouse1 went down.
Funny is, it works on Emacs24 - probably because the mouse-drag-track
in mouse-stay-and-copy keeps the S-drag-mouse-1 binding from
receiving events.
It seems that mouse-drag-track is broken, what concerns my
expectations to it. And it can be reimplemented, as I mentioned before
that I did - I just did not bother to reimplement the multiple-click
logic that is part of it.
On Sat, Aug 15, 2020 at 4:20 AM Stefan Kangas <stefan <at> marxist.se> wrote:
>
> Adolf Mathias <adolf.mathias <at> gmail.com> writes:
>
> > On Emacs Post 24, this stopped to work.
>
> Could you also explain what exactly your code is supposed to be doing?
>
> And did you try the following?
>
> (define-key global-map '[S-down-mouse-1] 'mouse-stay-and-copy)
> (define-key global-map '[S-drag-mouse-1] 'mouse-set-region)
>
> Best regards,
> Stefan Kangas
This bug report was last modified 4 years and 299 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.