From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Is there something like `on-display-functions'?
Date: Thu, 28 Jan 2010 07:54:34 -0500 [thread overview]
Message-ID: <E1NaTtK-0007Xj-W6@fencepost.gnu.org> (raw)
In-Reply-To: <20100128103856.GC2285@muc.de> (message from Alan Mackenzie on Thu, 28 Jan 2010 10:38:56 +0000)
> Date: Thu, 28 Jan 2010 10:38:56 +0000
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> As a zero order approximation, something like
> `before-display-functions', where an element would look like this:
>
> (defun foo-before-display (buffer beg end) .....)
>
> , BEG and END defining the piece of BUFFER about to be displayed. The
> hook would be called before fontification.
What do you mean by ``before fontification'', and why does it have to
be before that?
> (Is it possible in general to determine BEG and END before
> fontification?).
Only approximately. E.g., imagine a `display' property whose value is
a long string -- without computing how it will be displayed, there's
no way of knowing how much of the screen estate it will take. As
another, less exotic example, imagine font-lock definitions that
enlarge the font significantly: until you fontify that part, you
cannot know how much screen space it will take.
BEG and END are well known _after_ redisplay prepares what will be
shown on the glass, though. Therefore, please tell why do you ask to
call this hook _before_ fontifications.
next prev parent reply other threads:[~2010-01-28 12:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 13:57 Is there something like `on-display-functions'? Alan Mackenzie
2010-01-27 13:53 ` Lennart Borgman
2010-01-27 14:55 ` Alan Mackenzie
2010-01-27 15:11 ` Stefan Monnier
2010-01-27 15:37 ` Alan Mackenzie
2010-01-27 17:44 ` Eli Zaretskii
2010-01-27 19:24 ` Stefan Monnier
2010-01-27 20:08 ` Eli Zaretskii
2010-01-27 21:04 ` Stefan Monnier
2010-01-28 6:49 ` Eli Zaretskii
2010-01-28 19:37 ` Stefan Monnier
2010-01-28 20:53 ` Eli Zaretskii
2010-01-28 23:12 ` Stefan Monnier
2010-01-29 9:09 ` Eli Zaretskii
2010-01-29 18:08 ` Stefan Monnier
2010-01-28 6:55 ` Eli Zaretskii
2010-01-28 10:38 ` Alan Mackenzie
2010-01-28 12:54 ` Eli Zaretskii [this message]
2010-01-28 14:47 ` Alan Mackenzie
2010-01-28 19:18 ` Eli Zaretskii
2010-01-29 13:09 ` Alan Mackenzie
2010-01-28 19:37 ` Stefan Monnier
2010-01-29 13:17 ` Alan Mackenzie
2010-01-29 18:13 ` Stefan Monnier
2010-01-29 19:17 ` Alan Mackenzie
2010-01-30 21:02 ` Stefan Monnier
2010-01-27 17:55 ` Eli Zaretskii
2010-01-28 10:27 ` Alan Mackenzie
2010-01-28 11:30 ` Doc patch for `fontification-functions': [was: Is there something like `on-display-functions'?] Alan Mackenzie
2010-01-28 15:34 ` Doc patch for `fontification-functions': Chong Yidong
2010-01-28 16:40 ` Alan Mackenzie
2010-01-28 18:38 ` Doc patch for `fontification-functions': [was: Is there something like `on-display-functions'?] Eli Zaretskii
2010-01-28 19:44 ` Doc patch for `fontification-functions': Stefan Monnier
2010-01-27 14:16 ` Is there something like `on-display-functions'? alin.s
2010-01-27 14:27 ` David Kastrup
2010-01-27 15:20 ` Alan Mackenzie
2010-01-27 16:31 ` Stephen J. Turnbull
2010-01-27 14:59 ` Davis Herring
2010-01-28 1:41 ` Daniel Colascione
2010-01-28 10:14 ` Alan Mackenzie
2010-01-28 19:39 ` Stefan Monnier
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=E1NaTtK-0007Xj-W6@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).