Mercurial > hg > xemacs-beta
annotate man/xemacs/undo.texi @ 5043:d0c14ea98592
various frame-geometry fixes
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-02-15 Ben Wing <ben@xemacs.org>
* EmacsFrame.c:
* EmacsFrame.c (EmacsFrameResize):
* console-msw-impl.h:
* console-msw-impl.h (struct mswindows_frame):
* console-msw-impl.h (FRAME_MSWINDOWS_TARGET_RECT):
* device-tty.c:
* device-tty.c (tty_asynch_device_change):
* event-msw.c:
* event-msw.c (mswindows_wnd_proc):
* faces.c (Fface_list):
* faces.h:
* frame-gtk.c:
* frame-gtk.c (gtk_set_initial_frame_size):
* frame-gtk.c (gtk_set_frame_size):
* frame-msw.c:
* frame-msw.c (mswindows_init_frame_1):
* frame-msw.c (mswindows_set_frame_size):
* frame-msw.c (mswindows_size_frame_internal):
* frame-msw.c (msprinter_init_frame_3):
* frame.c:
* frame.c (enum):
* frame.c (Fmake_frame):
* frame.c (adjust_frame_size):
* frame.c (store_minibuf_frame_prop):
* frame.c (Fframe_property):
* frame.c (Fframe_properties):
* frame.c (Fframe_displayable_pixel_height):
* frame.c (Fframe_displayable_pixel_width):
* frame.c (internal_set_frame_size):
* frame.c (Fset_frame_height):
* frame.c (Fset_frame_pixel_height):
* frame.c (Fset_frame_displayable_pixel_height):
* frame.c (Fset_frame_width):
* frame.c (Fset_frame_pixel_width):
* frame.c (Fset_frame_displayable_pixel_width):
* frame.c (Fset_frame_size):
* frame.c (Fset_frame_pixel_size):
* frame.c (Fset_frame_displayable_pixel_size):
* frame.c (frame_conversion_internal_1):
* frame.c (get_frame_displayable_pixel_size):
* frame.c (change_frame_size_1):
* frame.c (change_frame_size):
* frame.c (generate_title_string):
* frame.h:
* gtk-xemacs.c:
* gtk-xemacs.c (gtk_xemacs_size_request):
* gtk-xemacs.c (gtk_xemacs_size_allocate):
* gtk-xemacs.c (gtk_xemacs_paint):
* gutter.c:
* gutter.c (update_gutter_geometry):
* redisplay.c (end_hold_frame_size_changes):
* redisplay.c (redisplay_frame):
* toolbar.c:
* toolbar.c (update_frame_toolbars_geometry):
* window.c:
* window.c (frame_pixsize_valid_p):
* window.c (check_frame_size):
Various fixes to frame geometry to make it a bit easier to understand
and fix some bugs.
1. IMPORTANT: Some renamings. Will need to be applied carefully to
the carbon repository, in the following order:
-- pixel_to_char_size -> pixel_to_frame_unit_size
-- char_to_pixel_size -> frame_unit_to_pixel_size
-- pixel_to_real_char_size -> pixel_to_char_size
-- char_to_real_pixel_size -> char_to_pixel_size
-- Reverse second and third arguments of change_frame_size() and
change_frame_size_1() to try to make functions consistent in
putting width before height.
-- Eliminate old round_size_to_char, because it didn't really
do anything differently from round_size_to_real_char()
-- round_size_to_real_char -> round_size_to_char; any places that
called the old round_size_to_char should just call the new one.
2. IMPORTANT FOR CARBON: The set_frame_size() method is now passed
sizes in "frame units", like all other frame-sizing functions,
rather than some hacked-up combination of char-cell units and
total pixel size. This only affects window systems that use
"pixelated geometry", and I'm not sure if Carbon is one of them.
MS Windows is pixelated, X and GTK are not. For pixelated-geometry
systems, the size in set_frame_size() is in displayable pixels
rather than total pixels and needs to be converted appropriately;
take a look at the changes made to mswindows_set_frame_size()
method if necessary.
3. Add a big long comment in frame.c describing how frame geometry
works.
4. Remove MS Windows-specific character height and width fields,
duplicative and unused.
5. frame-displayable-pixel-* and set-frame-displayable-pixel-*
didn't use to work on MS Windows, but they do now.
6. In general, clean up the handling of "pixelated geometry" so
that fewer functions have to worry about this. This is really
an abomination that should be removed entirely but that will
have to happen later. Fix some buggy code in
frame_conversion_internal() that happened to "work" because it
was countered by oppositely buggy code in change_frame_size().
7. Clean up some frame-size code in toolbar.c and use functions
already provided in frame.c instead of rolling its own.
8. Fix check_frame_size() in window.c, which formerly didn't take
pixelated geometry into account.
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Mon, 15 Feb 2010 22:14:11 -0600 |
| 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. |