Re: help about the display iterator.

[joakim]

"A. Soare" <address@hidden> writes:

>  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.

I dont claim to understand how redisplay actually works, but I did
manage to make a patch that modifies redisplay so its possible to insert
GTK widgets inside the text of an emacs buffer.

I did this by sprinkling trace code inside emacs to see what happens
during redisplay. To have a clear view of what modifications I have
done, I have a local bzr branch.

I agree that its not possible to just read the code and understand what
it does.

This doesnt answer your question, but maybe you can get some ideas.

>
> Alin.
>
>
>
>
>
>> 
>> "A. Soare" <address@hidden> 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
>
>
>
>
-- 
Joakim Verona