From: "A. Soare" <alinsoar@voila.fr>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: help about the display iterator.
Date: Fri, 16 Jan 2009 18:24:23 +0100 (CET) [thread overview]
Message-ID: <17789087.255901232126663384.JavaMail.www@wwinf4623> (raw)
Thanks.
Yes, I have read the beginning of xdisp.c.
I have also saw the trace of redisplay_internal. I did saw that redisplay_internal is the function that created the desired_matrix, i.e. the new image of the next refresh of screen. And also from redisplay_internal are called the low-level graphical functions that send the image to the video card.
What confuses me very hard is the number of variables that appear inside redisplay_internal. I do not understand where to start reading this function. For example, when I see
/* The flag redisplay_performed_directly_p is set by
direct_output_for_insert when it already did the whole screen
update necessary. */
if (redisplay_performed_directly_p)
{
redisplay_performed_directly_p = 0;
if (!hscroll_windows (selected_window))
return;
}
I understand that when redisplay_internal is called after direct_output_for_insert, redisplay_internal stops here. But direct_output_for_insert is never called on my emacs. I use GTK+ now.
So it is almost impossible to understand what happens just looking at the code.
To be more specific, let us consider this simple case: suppose that I use the console, not graphics, and that I press the key 'x'; could you make me a brief description of the trace of the code, starting from the moment when the function read_char forces redisplay, until the character is send to the phisical display?
Thanks in advance for any help.
Alin.
>
> "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?
>
>
____________________________________________________Avec Voila, réalisez en toute simplicité votre videoblog ! http://video.voila.fr/mktg/?op=videoblog
next reply other threads:[~2009-01-16 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 17:24 A. Soare [this message]
2009-01-16 17:38 ` help about the display iterator joakim
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 18:21 A. Soare
2009-01-16 15:21 ` Chong Yidong
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=17789087.255901232126663384.JavaMail.www@wwinf4623 \
--to=alinsoar@voila.fr \
--cc=cyd@stupidchicken.com \
--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).