| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version |
Arguments: cg-configuration
Returns whether source code colorization will be done automatically as
editing is done in a lisp-edit-pane
in which any colorization has
been done already.
Specifically, a call to colorize-source-code will be made when the user types a space, closing parenthesis, or newline, as well as the first time the text cursor is moved without colorization having otherwise been done since the most recent text change.
This incremental colorization is usually very fast because it colorizes only the text between the character position where the text was changed and the beginning of the innermost s-expression that contains that character position. There may be a significant delay, though, when that character range is large.
This option appears on the Editor Color tab on the
Options dialog
in the IDE, and may also be set programmatically by calling (setf
colorize-on-typing). The initial value is t
,
though it still does not do anything unless colorization has already
been done in the lisp-edit-pane
by some other means.
(setf (colorize-on-typing (configuration *system*)) t)
When this option is enabled, the Edit | Undo command will not work as expected just after typing has triggered an automatic recolorization. The reason is that the Undo command uses functionality that is built into the text-editing control that is supplied by the underlying window system, and this control cannot distinguish a change that was made by typing from a change that Common Graphics made as part of colorization. You could avoid this problem by using only the colorize-on-load-file option and/or the Colorize Definition and Colorize Buffer commands on the Edit menu.
Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version |