From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "A. Soare" Newsgroups: gmane.emacs.devel Subject: Re: help about the display iterator. Date: Fri, 16 Jan 2009 18:24:23 +0100 (CET) Message-ID: <17789087.255901232126663384.JavaMail.www@wwinf4623> Reply-To: alinsoar@voila.fr NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1232126685 3895 80.91.229.12 (16 Jan 2009 17:24:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Jan 2009 17:24:45 +0000 (UTC) Cc: "Emacs Dev \[emacs-devel\]" To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 16 18:25:56 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LNsS6-0002gL-5p for ged-emacs-devel@m.gmane.org; Fri, 16 Jan 2009 18:25:50 +0100 Original-Received: from localhost ([127.0.0.1]:36298 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNsQp-00030t-8F for ged-emacs-devel@m.gmane.org; Fri, 16 Jan 2009 12:24:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNsQl-00030o-05 for emacs-devel@gnu.org; Fri, 16 Jan 2009 12:24:27 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNsQj-00030c-9w for emacs-devel@gnu.org; Fri, 16 Jan 2009 12:24:26 -0500 Original-Received: from [199.232.76.173] (port=40941 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNsQj-00030Z-4G for emacs-devel@gnu.org; Fri, 16 Jan 2009 12:24:25 -0500 Original-Received: from smtp1.voila.fr ([193.252.22.174]:35176) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LNsQi-0001p7-IJ for emacs-devel@gnu.org; Fri, 16 Jan 2009 12:24:24 -0500 Original-Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf4018.voila.fr (SMTP Server) with ESMTP id 6923470000F3; Fri, 16 Jan 2009 18:24:23 +0100 (CET) Original-Received: from wwinf4623 (wwinf4623 [10.232.13.47]) by mwinf4018.voila.fr (SMTP Server) with ESMTP id 5F51570000EA; Fri, 16 Jan 2009 18:24:23 +0100 (CET) X-ME-UUID: 20090116172423390.5F51570000EA@mwinf4018.voila.fr X-Originating-IP: [92.80.91.237] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107910 Archived-At: Thanks. Yes, I have read the beginning of xdisp.c. I have also saw the trace of redisplay_internal. I did saw that redisplay_i= nternal 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 re= display_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 =3D 0; if (!hscroll_windows (selected_window)) =09return; } I understand that when redisplay_internal is called after direct_output_fo= r_insert, redisplay_internal stops here. But direct_output_for_insert is ne= ver called on my emacs. I use GTK+ now. So it is almost impossible to understand what happens just looking at the c= ode. To be more specific, let us consider this simple case: suppose that I use t= he 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. >=20 > "A. Soare" writes: >=20 > > 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. >=20 > 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? >=20 >=20 ____________________________________________________Avec Voila, r=C3=A9alis= ez en toute simplicit=C3=A9 votre videoblog ! http://video.voila.fr/mktg/?o= p=3Dvideoblog