unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Adolf Mathias <adolf.mathias@gmail.com>, 34014-done@debbugs.gnu.org
Subject: bug#34014: 25.2; binding down mouse event with modifier to mouse-drag-region does not work
Date: Thu, 13 Aug 2020 05:02:12 -0700	[thread overview]
Message-ID: <CADwFkmkvkH0QoVumOOfKsyHwWY60MNtfO3HG2RTs_RhOWimeZw@mail.gmail.com> (raw)
In-Reply-To: <83pnrbhvna.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Mar 2019 10:00:09 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Adolf Mathias <adolf.mathias@gmail.com>
>> Date: Tue, 8 Jan 2019 10:51:19 +0100
>>
>> >From 'emacs -Q' under X11, Ubuntu Bionic Beaver, enter:
>> M-: (define-key global-map '[S-down-mouse-1] 'mouse-drag-region)
>>
>> Now attempting to drag a region with held down shift key gives the
>> error message:
>>
>> <S-drag-mouse-1> is undefined
>>
>> Redefining the mouse key without shift modifier, and then dragging,
>> works as intended:
>> M-: (define-key global-map '[down-mouse-1] 'mouse-drag-region)
>>
>> This used to work in Emacs 24 and before.
>
> Sorry for such a long delay in responding to your report.
>
> Can you tell why you want to bind S-down-mouse-1 and not
> S-drag-mouse-1 to a drag command?

More information was requested, but none was given within 1.5 years, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

Best regards,
Stefan Kangas





  reply	other threads:[~2020-08-13 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08  9:51 bug#34014: 25.2; binding down mouse event with modifier to mouse-drag-region does not work Adolf Mathias
2019-03-01  8:00 ` Eli Zaretskii
2020-08-13 12:02   ` Stefan Kangas [this message]
     [not found]     ` <CACHJYuftHtcJ_ixA0vKbRavKstkaR8fkBaZxyoO_N41Zq7Qy4w@mail.gmail.com>
2020-08-14 14:29       ` Stefan Kangas
2020-08-14 18:58         ` Adolf Mathias
2020-08-15  2:20           ` Stefan Kangas
2020-08-15 11:53             ` Adolf Mathias
2020-08-16 14:34               ` Stefan Kangas
2020-08-16 16:20                 ` Adolf Mathias
2020-08-16 17:10                   ` Stefan Kangas
2020-08-16 20:54                     ` Adolf Mathias
2020-08-17 14:27                       ` Stefan Kangas
     [not found]                         ` <CACHJYue_KVWZ=wF-sa6nHCsAso0SDb0XSoXCRgW0teiR_Gt15Q@mail.gmail.com>
2020-08-18 13:26                           ` Stefan Kangas
2020-08-18 15:07                       ` Adolf Mathias
2020-08-18 15:32                         ` Stefan Kangas
2020-08-15 12:07             ` Adolf Mathias
2020-08-16 21:00 ` bug#34014: Adolf Mathias

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=CADwFkmkvkH0QoVumOOfKsyHwWY60MNtfO3HG2RTs_RhOWimeZw@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=34014-done@debbugs.gnu.org \
    --cc=adolf.mathias@gmail.com \
    --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).