Mercurial > hg > xemacs-beta
view man/xemacs/indent.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 |
line wrap: on
line source
@node Indentation, Text, Major Modes, Top @chapter Indentation @cindex indentation @c WideCommands @table @kbd @item @key{TAB} Indent current line ``appropriately'' in a mode-dependent fashion. @item @key{LFD} Perform @key{RET} followed by @key{TAB} (@code{newline-and-indent}). @item M-^ Merge two lines (@code{delete-indentation}). This would cancel out the effect of @key{LFD}. @item C-M-o Split line at point; text on the line after point becomes a new line indented to the same column that it now starts in (@code{split-line}). @item M-m Move (forward or back) to the first non-blank character on the current line (@code{back-to-indentation}). @item C-M-\ Indent several lines to same column (@code{indent-region}). @item C-x @key{TAB} Shift block of lines rigidly right or left (@code{indent-rigidly}). @item M-i Indent from point to the next prespecified tab stop column (@code{tab-to-tab-stop}). @item M-x indent-relative Indent from point to under an indentation point in the previous line. @end table @kindex TAB @cindex indentation Most programming languages have some indentation convention. For Lisp code, lines are indented according to their nesting in parentheses. The same general idea is used for C code, though details differ. Use the @key{TAB} command to indent a line whatever the language. Each major mode defines this command to perform indentation appropriate for the particular language. In Lisp mode, @key{TAB} aligns a line according to its depth in parentheses. No matter where in the line you are when you type @key{TAB}, it aligns the line as a whole. In C mode, @key{TAB} implements a subtle and sophisticated indentation style that knows about many aspects of C syntax. @kindex TAB In Text mode, @key{TAB} runs the command @code{tab-to-tab-stop}, which indents to the next tab stop column. You can set the tab stops with @kbd{M-x edit-tab-stops}. @menu * Indentation Commands:: Various commands and techniques for indentation. * Tab Stops:: You can set arbitrary "tab stops" and then indent to the next tab stop when you want to. * Just Spaces:: You can request indentation using just spaces. @end menu @node Indentation Commands, Tab Stops, Indentation, Indentation @section Indentation Commands and Techniques @c ??? Explain what Emacs has instead of space-indent-flag. If you just want to insert a tab character in the buffer, you can type @kbd{C-q @key{TAB}}. @kindex M-m @findex back-to-indentation To move over the indentation on a line, type @kbd{Meta-m} (@code{back-to-indentation}). This command, given anywhere on a line, positions point at the first non-blank character on the line. To insert an indented line before the current line, type @kbd{C-a C-o @key{TAB}}. To make an indented line after the current line, use @kbd{C-e @key{LFD}}. @kindex C-M-o @findex split-line @kbd{C-M-o} (@code{split-line}) moves the text from point to the end of the line vertically down, so that the current line becomes two lines. @kbd{C-M-o} first moves point forward over any spaces and tabs. Then it inserts after point a newline and enough indentation to reach the same column point is on. Point remains before the inserted newline; in this regard, @kbd{C-M-o} resembles @kbd{C-o}. @kindex M-\ @kindex M-^ @findex delete-horizontal-space @findex delete-indentation To join two lines cleanly, use the @kbd{Meta-^} (@code{delete-indentation}) command to delete the indentation at the front of the current line, and the line boundary as well. Empty spaces are replaced by a single space, or by no space if at the beginning of a line, before a close parenthesis, or after an open parenthesis. To delete just the indentation of a line, go to the beginning of the line and use @kbd{Meta-\} (@code{delete-horizontal-space}), which deletes all spaces and tabs around the cursor. @kindex C-M-\ @kindex C-x TAB @findex indent-region @findex indent-rigidly There are also commands for changing the indentation of several lines at once. @kbd{Control-Meta-\} (@code{indent-region}) gives each line which begins in the region the ``usual'' indentation by invoking @key{TAB} at the beginning of the line. A numeric argument specifies the column to indent to. Each line is shifted left or right so that its first non-blank character appears in that column. @kbd{C-x @key{TAB}} (@code{indent-rigidly}) moves all the lines in the region right by its argument (left, for negative arguments). The whole group of lines moves rigidly sideways, which is how the command gets its name.@refill @findex indent-relative @kbd{M-x indent-relative} indents at point based on the previous line (actually, the last non-empty line.) It inserts whitespace at point, moving point, until it is underneath an indentation point in the previous line. An indentation point is the end of a sequence of whitespace or the end of the line. If point is farther right than any indentation point in the previous line, the whitespace before point is deleted and the first indentation point then applicable is used. If no indentation point is applicable even then, @code{tab-to-tab-stop} is run (see next section). @code{indent-relative} is the definition of @key{TAB} in Indented Text mode. @xref{Text}. @node Tab Stops, Just Spaces, Indentation Commands, Indentation @section Tab Stops @kindex M-i @findex tab-to-tab-stop For typing in tables, you can use Text mode's definition of @key{TAB}, @code{tab-to-tab-stop}. This command inserts indentation before point, enough to reach the next tab stop column. Even if you are not in Text mode, this function is associated with @kbd{M-i} anyway. @findex edit-tab-stops @findex edit-tab-stops-note-changes @kindex C-c C-c (Edit Tab Stops) @vindex tab-stop-list You can arbitrarily set the tab stops used by @kbd{M-i}. They are stored as a list of column-numbers in increasing order in the variable @code{tab-stop-list}. The convenient way to set the tab stops is using @kbd{M-x edit-tab-stops}, which creates and selects a buffer containing a description of the tab stop settings. You can edit this buffer to specify different tab stops, and then type @kbd{C-c C-c} to make those new tab stops take effect. In the tab stop buffer, @kbd{C-c C-c} runs the function @code{edit-tab-stops-note-changes} rather than the default @code{save-buffer}. @code{edit-tab-stops} records which buffer was current when you invoked it, and stores the tab stops in that buffer. Normally all buffers share the same tab stops and changing them in one buffer affects all. If you make @code{tab-stop-list} local in one buffer @code{edit-tab-stops} in that buffer edits only the local settings. Below is the text representing ordinary tab stops every eight columns: @example : : : : : : 0 1 2 3 4 0123456789012345678901234567890123456789012345678 To install changes, type C-c C-c @end example The first line contains a colon at each tab stop. The remaining lines help you see where the colons are and tell you what to do. Note that the tab stops that control @code{tab-to-tab-stop} have nothing to do with displaying tab characters in the buffer. @xref{Display Vars}, for more information on that. @node Just Spaces,, Tab Stops, Indentation @section Tabs vs. Spaces @vindex indent-tabs-mode Emacs normally uses both tabs and spaces to indent lines. If you prefer, all indentation can be made from spaces only. To request this, set @code{indent-tabs-mode} to @code{nil}. This is a per-buffer variable; altering the variable affects only the current buffer, but there is a default value which you can change as well. @xref{Locals}. @findex tabify @findex untabify There are also commands to convert tabs to spaces or vice versa, always preserving the columns of all non-blank text. @kbd{M-x tabify} scans the region for sequences of spaces, and converts sequences of at least three spaces to tabs if that is possible without changing indentation. @kbd{M-x untabify} changes all tabs in the region to corresponding numbers of spaces.