From: Chong Yidong <cyd@stupidchicken.com>
To: alinsoar@voila.fr
Cc: "Emacs Help \[help-gnu-emacs\]" <help-gnu-emacs@gnu.org>,
"Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: help about the display iterator.
Date: Fri, 16 Jan 2009 10:21:37 -0500 [thread overview]
Message-ID: <874ozzz37i.fsf@cyd.mit.edu> (raw)
In-Reply-To: <3745216.88811232043706461.JavaMail.www@wwinf4607> (A. Soare's message of "Thu, 15 Jan 2009 19:21:46 +0100 (CET)")
"A. Soare" <alinsoar@voila.fr> writes:
> However, I do not understand the mechanism from `redisplay_ineternal'
> (I have the impression that it's this function that creates the
> desired_matrix of glyphs) and refresh the display.
You'll have to be more specific in asking these sorts of questions, I'm
afraid. Have you looked at the commentary at the beginning of xdisp.c?
prev parent reply other threads:[~2009-01-16 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 18:21 help about the display iterator A. Soare
2009-01-16 15:21 ` Chong Yidong [this message]
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=874ozzz37i.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=alinsoar@voila.fr \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@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.
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).