Page 249	Table of Contents	Index	Page 251
	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

The error that is signalled by simple-parse-error. This is a subclass of parse-error.

=> simple-parse-error format-string &rest format-arguments [Function]
Signals a simple-parse-error error while parsing an input token. Does not return. format-
string and format-args are as for format.

=> input-not-of-required-type [Error Condition]
The error that is signalled by input-not-of-required-type. This is a subclass of parse-error.

=> input-not-of-required-type object type [Function]
Reports that input does not satisfy the specified type by signalling an input-not-of-required- typeerror. object is a parsed object or an unparsed token (a string). type is a presentation type
specifier. Does not return.

24.4 Reading and Writing of Tokens

=> replace-input stream new-input &key start end buffer-start rescan [Generic Function]
Replaces the part of the input editing stream stream's input buffer that extends from buffer-start
to its scan pointer with the string new-input. buffer-start defaults to the current input position
of stream. start and end can be supplied to specify a subsequence of new-input; start defaults to
0 and end defaults to the length of new-input.

replace-input must queue a rescan by calling queue-rescan if the new input does not match
the old input, or rescan is true.

The returned value is the position in the input buffer.

All input editing streams must implement a method for this function.

=> presentation-replace-input stream object type view &key buffer-start rescan query-identifier
for-context-type [Generic Function]
Like replace-input, except that the new input to insert into the input buffer is gotten by
presenting object with the presentation type type and view view. buffer-start and rescan are as
for replace-input, and query-identifier and for-context-type as as for present.

All input editing streams must implement a method for this function. Typically, this will be
implemented by calling present-to-string on object, type, view, and for-context-type, and then
calling replace-input on the resulting string.

If the object does not have a readable representation (in the Lisp sense), presentation- replace-inputmay create an "accept result" to represent the object, and insert that into
the input buffer. For the purposes of input editing, "accept results" must be treated as a single
input gesture.

Page 249	Table of Contents	Index	Page 251
	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