# HG changeset patch # User Pavel Jank # Date 1004524377 0 # Node ID 361c85774b8f2d14dcf6f05f50f274386ab330e6 # Parent 0b1d7078c08080651dd1b04328c032fd6dfd0a6b Fix typos in comments. diff -r 0b1d7078c080 -r 361c85774b8f src/xdisp.c --- a/src/xdisp.c Wed Oct 31 10:19:40 2001 +0000 +++ b/src/xdisp.c Wed Oct 31 10:32:57 2001 +0000 @@ -33,7 +33,7 @@ you as part of the interpreter's command loop or as the result of calling Lisp functions like `sit-for'. The C function `redisplay' in xdisp.c is the only entry into the inner redisplay code. (Or, - let's say almost---see the the description of direct update + let's say almost---see the description of direct update operations, below.). The following diagram shows how redisplay code is invoked. As you @@ -88,7 +88,7 @@ Direct operations. - You will find a lot of of redisplay optimizations when you start + You will find a lot of redisplay optimizations when you start looking at the innards of redisplay. The overall goal of all these optimizations is to make redisplay fast because it is done frequently. @@ -123,7 +123,7 @@ interface functions taking a iterator structure (struct it) argument. - Iteration over things to be be displayed is then simple. It is + Iteration over things to be displayed is then simple. It is started by initializing an iterator with a call to init_iterator. Calls to get_next_display_element fill the iterator structure with relevant information about the next thing to display. Calls to