From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: The display margin Date: 24 Nov 2003 00:12:50 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <16080.60869.212521.952911@nick.uklinux.net> <200305251636.h4PGa1ll021935@rum.cs.yale.edu> <16082.42589.935105.932019@nick.uklinux.net> <16321.14941.117864.117597@nick.uklinux.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1069629340 9397 80.91.224.253 (23 Nov 2003 23:15:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 23 Nov 2003 23:15:40 +0000 (UTC) Cc: emacs-devel@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Nov 24 00:15:37 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AO3S5-0005Hp-00 for ; Mon, 24 Nov 2003 00:15:37 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AO3S5-0006aw-00 for ; Mon, 24 Nov 2003 00:15:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AO4P6-0004WA-LF for emacs-devel@quimby.gnus.org; Sun, 23 Nov 2003 19:16:36 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AO4Ng-0003JJ-Fu for emacs-devel@gnu.org; Sun, 23 Nov 2003 19:15:08 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AO4N4-00030p-4f for emacs-devel@gnu.org; Sun, 23 Nov 2003 19:15:02 -0500 Original-Received: from [62.226.12.185] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AO4N3-00030P-91 for emacs-devel@gnu.org; Sun, 23 Nov 2003 19:14:29 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hANNCt1k024358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Nov 2003 00:12:55 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hANNCoZH024354; Mon, 24 Nov 2003 00:12:50 +0100 Original-To: Nick Roberts In-Reply-To: <16321.14941.117864.117597@nick.uklinux.net> Original-Lines: 45 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18063 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18063 Nick Roberts writes: > > I have just checked in fixes to improve event handling for mouse > > clicks in the marginal areas and on the fringes. Events now have > > additional information: > > > > (WINDOW AREA-OR-POS (X . Y) TIMESTAMP OBJECT POS (COL . ROW)) > > > > AREA-OR-POS is not changed as such -- but it may now contain > > left-fringe and right-fringe. > > > > For clicks in the text area, POS is the same as AREA-OR-POS (the > > buffer position clicked on). For clicks in other areas, POS is > > the buffer position of the first visible glyph on the > > corresponding row. > > > > As an example, try M-x gdba and click mouse-1 on the left margin > > or fringe of a source window [it should toggle breakpoint on that > > line]. > > Kim, > > I like this very much. The click information for GNU Emacs is quite insufficient, anyway. XEmacs, as far as I can remember, can tell from an event what object has been clicked on and what pixel relative to the object's origin has been hit. With GNU Emacs, in contrast, you have to set up a separate keymap for every object in order to have a chance to find out which of several ones have been clicked, and no chance of finding the relative position at all. And the object/click correlation is done at the time when you query the event, not when the click was done: if you click in order to do a cut&paste operation on some buffer, and Emacs churns away internally at the time, finally places a dialog box "Explode now?" on the screen, then finally processes the click event, it will associate at it with the exploding object instead of what was on the screen at the time of the click. I digress. Anyway, I want more information from clicks. At the very least, the object they appeared on. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum