GNU logs - #23732, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#23732: Emacs 25.0.96: Mouse button depress modifiers don't but should carry through to next release event if any intervening events.
Resent-From: Robert Weiner <rsw@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 08 Jun 2016 20:15:02 +0000
Resent-Message-ID: <handler.23732.B.146541690015674 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 23732 <at> debbugs.gnu.org
Reply-To: rswgnu@HIDDEN
MIME-Version: 1.0
From: Robert Weiner <rsw@HIDDEN>
Date: Wed, 8 Jun 2016 16:14:13 -0400
Message-ID: <CA+OMD9hUm_YeFYOTn2mxJbGzX061VSQJMhrnEtoqppS1yFMjGg@HIDDEN>
Content-Type: multipart/alternative; boundary=001a113d148cb7b4710534c9f465
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--001a113d148cb7b4710534c9f465
Content-Type: text/plain; charset=UTF-8

FYI, I am trying to get the mouse keys to act as modifiers, e.g. holding
down C-mouse-2, acts as a control key modifier.  I have this mostly working
but have run into a release event problem as outlined below.

Scenario 1: Bind C-down-mouse-2 and C-mouse-2 to commands.  Depress control
and mouse-2, release the control key, then release the mouse-2 button, you
will get a C-down-mouse-2 event and I believe a C-mouse-2 release event
even though the control key has been released, as desired.

Scenario 2: Depress control and mouse-2, release the control key, press a,
then release the mouse-2 button and you will get a mouse-2 release event,
not a C-mouse-2 release event, meaning there is no way to coordinate
modified press/release event pairs when there are intervening events unless
the modifier is held down throughout the entire sequence of events (which
is not very workable when other modified keys need to be pressed in the
interim).

I would suggest that once a modified key is depressed, the next release
event for that key, regardless of any modifiers now pressed, should match
the modifiers of the depress event, unless something a discard-events is
done prior to release.

Otherwise, one would have to affect all modified combinations of the button
to ensure that the associated release event is triggered whether or not the
modifiers are still held down.  That surely is not practical.  Neither does
it make much sense to program pairs of depress/release events where the
modifiers differ between press and release.

Can anyone address this?

Thanks,

Bob

--001a113d148cb7b4710534c9f465
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>FYI, I am trying to get the mouse keys to act as modi=
fiers, e.g. holding down C-mouse-2, acts as a control key modifier.=C2=A0 I=
 have this mostly working but have run into a release event problem as outl=
ined below.</div><div><br></div><div>Scenario 1: Bind C-down-mouse-2 and C-=
mouse-2 to commands.=C2=A0 Depress control and mouse-2, release the control=
 key, then release the mouse-2 button, you will get a C-down-mouse-2 event =
and I believe a C-mouse-2 release event even though the control key has bee=
n released, as desired.</div><div><br></div>Scenario 2: Depress control and=
 mouse-2, release the control key, press a, then release the mouse-2 button=
 and you will get a mouse-2 release event, not a C-mouse-2 release event, m=
eaning there is no way to coordinate modified press/release event pairs whe=
n there are intervening events unless the modifier is held down throughout =
the entire sequence of events (which is not very workable when other modifi=
ed keys need to be pressed in the interim).<div><br></div><div>I would sugg=
est that once a modified key is depressed, the next release event for that =
key, regardless of any modifiers now pressed, should match the modifiers of=
 the depress event, unless something a discard-events is done prior to rele=
ase.</div><div><br></div><div>Otherwise, one would have to affect all modif=
ied combinations of the button to ensure that the associated release event =
is triggered whether or not the modifiers are still held down.=C2=A0 That s=
urely is not practical.=C2=A0 Neither does it make much sense to program pa=
irs of depress/release events where the modifiers differ between press and =
release.</div><div><br></div><div>Can anyone address this?</div><div><br></=
div><div>Thanks,</div><div><br></div><div>Bob</div><div><br></div></div>

--001a113d148cb7b4710534c9f465--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: rswgnu@HIDDEN
Subject: bug#23732: Acknowledgement (Emacs 25.0.96: Mouse button depress
 modifiers don't but should carry through to next release event if any
 intervening events.)
Message-ID: <handler.23732.B.146541690015674.ack <at> debbugs.gnu.org>
References: <CA+OMD9hUm_YeFYOTn2mxJbGzX061VSQJMhrnEtoqppS1yFMjGg@HIDDEN>
X-Gnu-PR-Message: ack 23732
X-Gnu-PR-Package: emacs
Reply-To: 23732 <at> debbugs.gnu.org
Date: Wed, 08 Jun 2016 20:15:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 23732 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
23732: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D23732
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 15 Aug 2019 00:27:05 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Wed Aug 14 20:27:05 2019
Received: from localhost ([127.0.0.1]:49949 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1hy3bd-0004kS-Jy
	for submit <at> debbugs.gnu.org; Wed, 14 Aug 2019 20:27:05 -0400
Received: from quimby.gnus.org ([80.91.231.51]:58670)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <larsi@HIDDEN>) id 1hy3bc-0004kI-J5
 for control <at> debbugs.gnu.org; Wed, 14 Aug 2019 20:27:04 -0400
Received: from 24-104-73-23-ip-static.hfc.comcastbusiness.net ([24.104.73.23]
 helo=sandy)
 by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.89) (envelope-from <larsi@HIDDEN>) id 1hy3bZ-0005jq-MS
 for control <at> debbugs.gnu.org; Thu, 15 Aug 2019 02:27:03 +0200
Date: Wed, 14 Aug 2019 17:26:59 -0700
Message-Id: <875zmzs27g.fsf@HIDDEN>
To: control <at> debbugs.gnu.org
From: Lars Ingebrigtsen <larsi@HIDDEN>
Subject: control message for bug #23732
X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 @@CONTACT_ADDRESS@@ for details.
 Content preview:  forcemerge 23732 17140 quit 
 Content analysis details:   (-2.9 points, 5.0 required)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: control
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

forcemerge 23732 17140
quit

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.