From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Simon Friis Vindum Newsgroups: gmane.emacs.bugs Subject: bug#22163: Feature request: Add support for key release event Date: Tue, 15 Dec 2015 21:15:29 +0100 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1450210577 12255 80.91.229.3 (15 Dec 2015 20:16:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Dec 2015 20:16:17 +0000 (UTC) To: 22163@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Dec 15 21:16:08 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a8w11-0002Zk-GQ for geb-bug-gnu-emacs@m.gmane.org; Tue, 15 Dec 2015 21:16:07 +0100 Original-Received: from localhost ([::1]:38998 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w10-0002AI-KV for geb-bug-gnu-emacs@m.gmane.org; Tue, 15 Dec 2015 15:16:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57406) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w0x-0002AA-6L for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:16:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8w0w-0000iP-69 for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:16:03 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:45350) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w0w-0000iL-2S for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:16:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1a8w0v-0003ia-VD for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:16:01 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: Simon Friis Vindum Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 15 Dec 2015 20:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22163 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.145021054014264 (code B ref -1); Tue, 15 Dec 2015 20:16:01 +0000 Original-Received: (at submit) by debbugs.gnu.org; 15 Dec 2015 20:15:40 +0000 Original-Received: from localhost ([127.0.0.1]:52952 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1a8w0a-0003i0-JU for submit@debbugs.gnu.org; Tue, 15 Dec 2015 15:15:40 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:47339) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1a8w0Y-0003hl-Gq for submit@debbugs.gnu.org; Tue, 15 Dec 2015 15:15:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8w0S-0000fb-8G for submit@debbugs.gnu.org; Tue, 15 Dec 2015 15:15:33 -0500 Original-Received: from lists.gnu.org ([2001:4830:134:3::11]:35377) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w0S-0000fP-0X for submit@debbugs.gnu.org; Tue, 15 Dec 2015 15:15:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w0Q-000288-N4 for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:15:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8w0P-0000em-Vz for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:15:30 -0500 Original-Received: from mail-qk0-x22b.google.com ([2607:f8b0:400d:c09::22b]:34660) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8w0P-0000eg-QP for bug-gnu-emacs@gnu.org; Tue, 15 Dec 2015 15:15:29 -0500 Original-Received: by mail-qk0-x22b.google.com with SMTP id p187so31779428qkd.1 for ; Tue, 15 Dec 2015 12:15:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=TOrCB7BF/vhzbhc537poZ3nrr25sJYmK3+hWP7Bm6yo=; b=J59OcUkw5j9SiFtsX+/5M0S2TYjjgGkdAw2oNNEphLJmeBtFCEt6/WBh0gbdH7xbEw 8ftupKmrWadoeAgWvvM5c7UsP0zvQwwx9wFdNHAmolJOO7ha6K6QdyFWeBidrDDL9aW1 0QswI5H2Yp9lp+7vDf1xUzQLvgEXBBxcNYtYoOucgc9V3H8bYTSxh2OhileLBEiGrxdE U39kAVVNyNi+yJRNv4t3fgG10ztSktngdlpTnBIKHxFhIgHJSffZqggMgiGNhfZ4VeOL Jz7keC3cVrAyOstosmf0W77vJGGIxoSHU1Ok0lD08WSBDG8Y/ptBs6Dl0CaVdrRc8krt Rwvg== X-Received: by 10.129.101.5 with SMTP id z5mr24250421ywb.184.1450210529277; Tue, 15 Dec 2015 12:15:29 -0800 (PST) Original-Received: by 10.37.215.8 with HTTP; Tue, 15 Dec 2015 12:15:29 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:110031 Archived-At: >>>>> John Wiegley writes: > Those who understand the fundamentals of event handling would know better, but > doing this right could be a rather invasive change. For example: Should > `read-event' return once a key is pressed down; or should it wait until the > key has been released, and then also give both the press-down and release > times? At the moment, it just notifies the user of the key? I was thinking that one might define a new built-in function. It could for instance be called `define-key-release` and behave exactly like `define-key` except that the passed command would be triggered on key release instead of key press. It seems to me like that would be backwards compatible and non-invasive. > Because once you have sensitive to "length of press", I imagine that's just > the start of additional information you'd want about events and how they > relate in time to each other... I think that if you can get the press and release of a key then you have access to all information from the hardware. Everything else can be derived from that. Kind regards Simon Friis Vindum