unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The display margin
Date: 28 Nov 2003 17:02:31 +0100	[thread overview]
Message-ID: <x5fzg8qy5k.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jksmk8po6m.fsf@glug.org>

Thien-Thi Nguyen <ttn@glug.org> writes:

> David Kastrup <dak@gnu.org> 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

  reply	other threads:[~2003-11-28 16:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 16:22 The display margin Nick Roberts
2003-05-25 16:36 ` Stefan Monnier
2003-05-26 23:42   ` Nick Roberts
2003-11-23  2:08     ` Kim F. Storm
2003-11-23 22:53       ` Nick Roberts
2003-11-23 23:12         ` David Kastrup
2003-11-24  9:52           ` Kim F. Storm
2003-11-24 15:33             ` Kim F. Storm
2003-11-27 23:08           ` Kim F. Storm
2003-11-27 22:30             ` David Kastrup
2003-11-27 23:17               ` Stefan Monnier
2003-11-28 11:09               ` Kim F. Storm
2003-11-28 10:53                 ` David Kastrup
2003-11-28 14:23                   ` Thien-Thi Nguyen
2003-11-28 16:02                     ` David Kastrup [this message]
2003-11-28 17:01                       ` Thien-Thi Nguyen
2003-11-29  3:15                   ` Kim F. Storm
2003-11-29 11:37                     ` David Kastrup
2003-12-01 10:15                       ` Kim F. Storm
2003-12-01 13:08                         ` David Kastrup
2003-12-28  1:43                           ` Kim F. Storm
2003-12-29 11:54                             ` Richard Stallman
2003-11-24  0:09         ` Kim F. Storm
2003-11-25 21:11           ` Nick Roberts
2003-11-25 22:42             ` Kim F. Storm
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28 12:47 David PONCE

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=x5fzg8qy5k.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@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).