Page 241	Table of Contents	Index	Page 243
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E

---

Chapter 24

Input Editing and Completion Facilities

CLIM provides number of facilities to assist in writing presentation type parser functions, such
as an interactive input editor and some "completion" facilities.

24.1 The Input Editor

An input editing stream "encapsulates" an interactive stream, that is, most operations are
handled by the encapsulated interactive stream, but some operations are handled directly by the
input editing stream itself. (See Appendix D for a discussion of encapsulating streams.)
An input editing stream will have the following components:

• The encapsulated interactive stream.
  
  
• A buffer with a fill pointer, which we shall refer to as FP. The buffer contains all of the
  user's input, and FP is the length of that input.
  
  
• An insertion pointer, which we shall refer to as IP. The insertion pointer is the point in
  the buffer at which the "editing cursor" is.
  
  
• A scan pointer, which we shall refer to as SP. The scan pointer is the point in the buffer
  from which CLIM will get the next input gesture object (in the sense of read-gesture).
  
  
• A "rescan queued" flag indicating that the programmer (or CLIM) requested that a "res-
  can" operation should take place before the next gesture is read from the user.
  
  
• A "rescan in progress" flag that indicates that CLIM is rescanning the user's input, rather
  than reading freshly supplied gestures from the user.

---

Page 241	Table of Contents	Index	Page 243
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E