| Did you know ... | Search Documentation: |
| Send methods |
->insert and text_buffer->format.-editorsno-change checkpoint in the undo buffer. If text_buffer->undo
reverts back to this point, text_buffer<-modified
will be reset to @off.<-contents
of the text_buffer
object. In addition, it resets the text_buffer->undo
system and deletes all associated
fragment objects.
See also text_buffer->insert_file.
Defaults:
By default, 1 character is deleted.
-editors<-find_fragment
and text_buffer<-find_all_fragments.
Arguments:
@arg1 The fragment object
->append
formatted text. See string->format
for the definition of the format string and its arguments.start is specified it will start scanning from
this index, assuming that the given index is not in a string or comment.
See
syntax_table->syntax
for defining the comment syntax.<->newline_mode
if it is set to detect at entry to simplify Windows/Unix interaction.
This is exploited by PceEmacs.
See also text_buffer->save, text_buffer->contents
and class editor.
See also file->encoding.
head
of the undo buffer. A subsequent undo will text_buffer->undo
all changes back to this mark. Normally set by editor->event.<-editors.
See editor->report
and‘visual
text_buffer->report’.from is 0 and the size will save to the end of
the buffer. If both
from and size are omitted, text_buffer<-modified
will be set to @off.
See also
editor->save
and editor->save_buffer.Bugs: Not very flexible and doubtfful, whether this is the right level for implementing this method.
->undo_mark.
If this is a text_buffer->reset_undo
checkpoint, reset text_buffer->modified
to @off.
Changes are stored in a buffer of size text_buffer<-undo_buffer_size.
Changes that exhaust the size of this buffer are lost.->lost_text_buffer
to all related text_buffer<-editors
and returns all alien resources to the system.