Mercurial > hg > xemacs-beta
annotate man/xemacs/undo.texi @ 938:0391335b65dc
[xemacs-hg @ 2002-07-31 07:14:49 by michaels]
2002-07-17 Marcus Crestani <crestani@informatik.uni-tuebingen.de>
Markus Kaltenbach <makalten@informatik.uni-tuebingen.de>
Mike Sperber <mike@xemacs.org>
configure flag to turn these changes on: --use-kkcc
First we added a dumpable flag to lrecord_implementation. It shows,
if the object is dumpable and should be processed by the dumper.
* lrecord.h (struct lrecord_implementation): added dumpable flag
(MAKE_LRECORD_IMPLEMENTATION): fitted the different makro definitions
to the new lrecord_implementation and their calls.
Then we changed mark_object, that it no longer needs a mark method for
those types that have pdump descritions.
* alloc.c:
(mark_object): If the object has a description, the new mark algorithm
is called, and the object is marked according to its description.
Otherwise it uses the mark method like before.
These procedures mark objects according to their descriptions. They
are modeled on the corresponding pdumper procedures.
(mark_with_description):
(get_indirect_count):
(structure_size):
(mark_struct_contents):
These procedures still call mark_object, this is needed while there are
Lisp_Objects without descriptions left.
We added pdump descriptions for many Lisp_Objects:
* extents.c: extent_auxiliary_description
* database.c: database_description
* gui.c: gui_item_description
* scrollbar.c: scrollbar_instance_description
* toolbar.c: toolbar_button_description
* event-stream.c: command_builder_description
* mule-charset.c: charset_description
* device-msw.c: devmode_description
* dialog-msw.c: mswindows_dialog_id_description
* eldap.c: ldap_description
* postgresql.c: pgconn_description
pgresult_description
* tooltalk.c: tooltalk_message_description
tooltalk_pattern_description
* ui-gtk.c: emacs_ffi_description
emacs_gtk_object_description
* events.c:
* events.h:
* event-stream.c:
* event-Xt.c:
* event-gtk.c:
* event-tty.c:
To write a pdump description for Lisp_Event, we converted every struct
in the union event to a Lisp_Object. So we created nine new
Lisp_Objects: Lisp_Key_Data, Lisp_Button_Data, Lisp_Motion_Data,
Lisp_Process_Data, Lisp_Timeout_Data, Lisp_Eval_Data,
Lisp_Misc_User_Data, Lisp_Magic_Data, Lisp_Magic_Eval_Data.
We also wrote makro selectors and mutators for the fields of the new
designed Lisp_Event and added everywhere these new abstractions.
We implemented XD_UNION support in (mark_with_description), so
we can describe exspecially console/device specific data with XD_UNION.
To describe with XD_UNION, we added a field to these objects, which
holds the variant type of the object. This field is initialized in
the appendant constructor. The variant is an integer, it has also to
be described in an description, if XD_UNION is used.
XD_UNION is used in following descriptions:
* console.c: console_description
(get_console_variant): returns the variant
(create_console): added variant initialization
* console.h (console_variant): the different console types
* console-impl.h (struct console): added enum console_variant contype
* device.c: device_description
(Fmake_device): added variant initialization
* device-impl.h (struct device): added enum console_variant devtype
* objects.c: image_instance_description
font_instance_description
(Fmake_color_instance): added variant initialization
(Fmake_font_instance): added variant initialization
* objects-impl.h (struct Lisp_Color_Instance): added color_instance_type
* objects-impl.h (struct Lisp_Font_Instance): added font_instance_type
* process.c: process_description
(make_process_internal): added variant initialization
* process.h (process_variant): the different process types
| author | michaels |
|---|---|
| date | Wed, 31 Jul 2002 07:14:49 +0000 |
| parents | 376386a54a3c |
| children |
| rev | line source |
|---|---|
| 0 | 1 |
| 2 @node Undo, Minibuffer, Basic, Top | |
| 3 @chapter Undoing Changes | |
| 4 @cindex undo | |
| 5 @cindex mistakes, correcting | |
| 6 | |
| 7 Emacs allows you to undo all changes you make to the text of a buffer, | |
| 8 up to a certain amount of change (8000 characters). Each buffer records | |
| 9 changes individually, and the undo command always applies to the | |
| 10 current buffer. Usually each editing command makes a separate entry | |
| 11 in the undo records, but some commands such as @code{query-replace} | |
| 12 make many entries, and very simple commands such as self-inserting | |
| 13 characters are often grouped to make undoing less tedious. | |
| 14 | |
| 15 @table @kbd | |
| 16 @item C-x u | |
| 17 Undo one batch of changes (usually, one command's worth) (@code{undo}). | |
| 18 @item C-_ | |
| 19 The same. | |
| 20 @end table | |
| 21 | |
| 22 @kindex C-x u | |
| 23 @kindex C-_ | |
| 24 @findex undo | |
| 25 The command @kbd{C-x u} or @kbd{C-_} allows you to undo changes. The | |
| 26 first time you give this command, it undoes the last change. Point | |
| 27 moves to the text affected by the undo, so you can see what was undone. | |
| 28 | |
| 29 Consecutive repetitions of the @kbd{C-_} or @kbd{C-x u} commands undo | |
| 30 earlier and earlier changes, back to the limit of what has been | |
| 31 recorded. If all recorded changes have already been undone, the undo | |
| 32 command prints an error message and does nothing. | |
| 33 | |
| 34 Any command other than an undo command breaks the sequence of undo | |
| 35 commands. Starting at this moment, the previous undo commands are | |
| 36 considered ordinary changes that can themselves be undone. Thus, you can | |
| 37 redo changes you have undone by typing @kbd{C-f} or any other command | |
| 38 that have no important effect, and then using more undo commands. | |
| 39 | |
| 40 If you notice that a buffer has been modified accidentally, the | |
| 41 easiest way to recover is to type @kbd{C-_} repeatedly until the stars | |
| 42 disappear from the front of the mode line. When that happens, all the | |
| 43 modifications you made have been canceled. If you do not remember | |
| 44 whether you changed the buffer deliberately, type @kbd{C-_} once. When | |
| 45 you see Emacs undo the last change you made, you probably remember why you | |
| 46 made it. If the change was an accident, leave it undone. If it was | |
| 47 deliberate, redo the change as described in the preceding paragraph. | |
| 48 | |
| 49 Whenever an undo command makes the stars disappear from the mode line, | |
| 50 the buffer contents is the same as it was when the file was last read in | |
| 51 or saved. | |
| 52 | |
| 53 Not all buffers record undo information. Buffers whose names start with | |
| 54 spaces don't; these buffers are used internally by Emacs and its extensions | |
| 55 to hold text that users don't normally look at or edit. Minibuffers, | |
| 56 help buffers, and documentation buffers also don't record undo information. | |
| 57 | |
| 58 Emacs can remember at most 8000 or so characters of deleted or | |
| 59 modified text in any one buffer for reinsertion by the undo command. | |
| 60 There is also a limit on the number of individual insert, delete, or | |
| 61 change actions that Emacs can remember. | |
| 62 | |
| 63 There are two keys to run the @code{undo} command, @kbd{C-x u} and | |
| 64 @kbd{C-_}, because on some keyboards, it is not obvious how to type | |
| 65 @kbd{C-_}. @kbd{C-x u} is an alternative you can type in the same | |
| 66 fashion on any terminal. |