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: 28 Nov 2003 17:02:31 +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 1070035494 27610 80.91.224.253 (28 Nov 2003 16:04:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 Nov 2003 16:04:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Nov 28 17:04:52 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 1APl6y-0003cp-00 for ; Fri, 28 Nov 2003 17:04:52 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1APl6x-0007ZH-00 for ; Fri, 28 Nov 2003 17:04:51 +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 1APm3K-0003bS-IT for emacs-devel@quimby.gnus.org; Fri, 28 Nov 2003 12:05:10 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1APm2o-0003ax-53 for emacs-devel@gnu.org; Fri, 28 Nov 2003 12:04:38 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1APm2H-0003R6-LG for emacs-devel@gnu.org; Fri, 28 Nov 2003 12:04:36 -0500 Original-Received: from [217.80.160.96] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1APm2G-0003Qf-IJ for emacs-devel@gnu.org; Fri, 28 Nov 2003 12:04:04 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hASG2XWJ013899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Nov 2003 17:02:33 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hASG2VZe013895; Fri, 28 Nov 2003 17:02:31 +0100 Original-To: Thien-Thi Nguyen In-Reply-To: Original-Lines: 31 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:18192 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18192 Thien-Thi Nguyen writes: > David Kastrup writes: > > Actually, given that we now have a pixel-accurate position within > the object (maybe this is generalizable in some manner also for > text?), it would be nice having a way of knowing the > pixel-accurate size of a displayed object in the first place so > that one can calculate the relative position in the image easily, > too. > > it is difficult to generalize this to text because the same text can > be presented differently depending on font, overlays, display > properties and probably many other influences i can't think of at > the moment. a specific query (mouse click) can yield a specific > answer but such info is not inherently in the text (anymore). Well, it was just an idea. > w/ images it's easy of course. Is it? What if the image type is PostScript or some other scalable format, and the buffer is displayed on two frames on two different displays with different resolutions? Ok, I guess the answer is "this will break Emacs", anyway. Questions like that need the concerned window to be answerable, I guess. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum