Mercurial > hg > xemacs-beta
view man/xemacs/m-x.texi @ 4967:0d4c9d0f6a8d
rewrite dynarr code
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-02-03 Ben Wing <ben@xemacs.org>
* device-x.c (x_get_resource_prefix):
* device-x.c (Fx_get_resource):
* device-x.c (Fx_get_resource_prefix):
* device-x.c (Fx_put_resource):
* dialog-msw.c:
* dialog-msw.c (handle_question_dialog_box):
* dired-msw.c (mswindows_sort_files):
* dired-msw.c (mswindows_get_files):
* extents.c (extent_fragment_sort_by_priority):
* extents.c (Fset_extent_parent):
* file-coding.c (coding_reader):
* file-coding.c (coding_writer):
* file-coding.c (gzip_convert):
* frame.c (generate_title_string):
* gutter.c (calculate_gutter_size_from_display_lines):
* indent.c (vmotion_1):
* lread.c (read_bit_vector):
* mule-coding.c (iso2022_decode):
* rangetab.c:
* rangetab.c (Fcopy_range_table):
* rangetab.c (Fget_range_table):
* rangetab.c (unified_range_table_copy_data):
* redisplay-msw.c (mswindows_output_string):
* redisplay-output.c (output_display_line):
* redisplay-output.c (redisplay_move_cursor):
* redisplay-output.c (redisplay_clear_bottom_of_window):
* redisplay-tty.c (tty_output_ichar_dynarr):
* redisplay-tty.c (set_foreground_to):
* redisplay-tty.c (set_background_to):
* redisplay-xlike-inc.c (XLIKE_output_string):
* redisplay.c (redisplay_window_text_width_string):
* redisplay.c (redisplay_text_width_string):
* redisplay.c (create_text_block):
* redisplay.c (SET_CURRENT_MODE_CHARS_PIXSIZE):
* redisplay.c (generate_fstring_runes):
* redisplay.c (regenerate_modeline):
* redisplay.c (ensure_modeline_generated):
* redisplay.c (real_current_modeline_height):
* redisplay.c (create_string_text_block):
* redisplay.c (regenerate_window):
* redisplay.c (REGEN_INC_FIND_START_END):
* redisplay.c (point_visible):
* redisplay.c (redisplay_window):
* redisplay.c (mark_glyph_block_dynarr):
* redisplay.c (line_start_cache_start):
* redisplay.c (start_with_line_at_pixpos):
* redisplay.c (update_line_start_cache):
* redisplay.c (glyph_to_pixel_translation):
* redisplay.c (pixel_to_glyph_translation):
* sysdep.c (qxe_readdir):
* text.c (dfc_convert_to_external_format):
* text.c (dfc_convert_to_internal_format):
* toolbar-common.c (common_output_toolbar_button):
* window.c (window_modeline_height):
* window.c (Fwindow_last_line_visible_height):
* window.c (window_displayed_height):
* window.c (window_scroll):
* window.c (get_current_pixel_pos):
Use Dynarr_begin() in place of Dynarr_atp (foo, 0).
* dynarr.c (Dynarr_realloc):
* dynarr.c (Dynarr_lisp_realloc):
* dynarr.c (Dynarr_resize):
* dynarr.c (Dynarr_insert_many):
* dynarr.c (Dynarr_delete_many):
* dynarr.c (Dynarr_memory_usage):
* dynarr.c (stack_like_malloc):
* dynarr.c (stack_like_free):
* lisp.h:
* lisp.h (DECLARE_DYNARR_LISP_IMP):
* lisp.h (XD_DYNARR_DESC):
* lisp.h (Dynarr_pop):
* gutter.c (output_gutter):
* redisplay-output.c (sync_rune_structs):
* redisplay-output.c (redisplay_output_window):
Redo the dynarr code, add greater checks.
Rename the `len', `largest' and `max' members to `len_',
`largest_' and `max_' to try and catch existing places that might
directly modify these values. Make new accessors Dynarr_largest()
and Dynarr_max() and make them and existing Dynarr_length() be
non-lvalues by adding '+ 0' to them; fix a couple of places in the
redisplay code that tried to modify the length directly by setting
Dynarr_length(). Use the accessors whenever possible even in the
dynarr code itself. The accessors also verify that 0 <= len <=
largest <= max. Rename settor function Dynarr_set_size() to
Dynarr_set_length() and use it more consistently; also create
lower-level Dynarr_set_length_1(). This latter function should be
the only function that directly modifies the `len_' member of a
Dynarr, and in the process makes sure that the `largest' value is
kept correct.
Consistently use ERROR_CHECK_STRUCTURES instead of
ERROR_CHECK_TYPES for error-checking code. Reintroduce the
temporarily disabled verification code on the positions of
Dynarr_at(), Dynarr_atp() and Dynarr_atp_past_end().
Also create Dynarr_resize_if() in place of a repeated
code fragment. Clean up all the functions that modify Dynarrs to
use the new macros and functions and verify the correctness of the
Dynarr both before and after the change.
Note that there are two kinds of verification -- one for accessing
and one for modifying. The difference is that the modify
verification additionally checks to make sure that the Dynarr
isn't locked. (This is used in redisplay to check for problems
with reentrancy.)
* lrecord.h: Move XD_DYNARR_DESC to lisp.h, grouping with the dynarr code.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Wed, 03 Feb 2010 20:51:18 -0600 |
parents | 3ecd8885ac67 |
children |
line wrap: on
line source
@node M-x, Help, Minibuffer, Top @chapter Running Commands by Name The Emacs commands that are used often or that must be quick to type are bound to keys---short sequences of characters---for convenient use. Other Emacs commands that are used more rarely are not bound to keys; to run them, you must refer to them by name. A command name consists, by convention, of one or more words, separated by hyphens: for example, @code{auto-fill-mode} or @code{manual-entry}. The use of English words makes the command name easier to remember than a key made up of obscure characters, even though it results in more characters to type. You can run any command by name, even if it can be run by keys as well. @kindex M-x @cindex minibuffer To run a command by name, start with @kbd{M-x}, then type the command name, and finish with @key{RET}. @kbd{M-x} uses the minibuffer to read the command name. @key{RET} exits the minibuffer and runs the command. Emacs uses the minibuffer for reading input for many different purposes; on this occasion, the string @samp{M-x} is displayed at the beginning of the minibuffer as a @dfn{prompt} to remind you that your input should be the name of a command to be run. @xref{Minibuffer}, for full information on the features of the minibuffer. You can use completion to enter a command name. For example, to invoke the command @code{forward-char}, type: @example M-x forward-char @key{RET} @end example or @example M-x fo @key{TAB} c @key{RET} @end example @noindent After you type in @code{M-x fo TAB} emacs will give you a possible list of completions from which you can choose. Note that @code{forward-char} is the same command that you invoke with the key @kbd{C-f}. You can call any command (interactively callable function) defined in Emacs by its name using @kbd{M-x} regardless of whether or not any keys are bound to it. If you type @kbd{C-g} while Emacs reads the command name, you cancel the @kbd{M-x} command and get out of the minibuffer, ending up at top level. To pass a numeric argument to a command you are invoking with @kbd{M-x}, specify the numeric argument before the @kbd{M-x}. @kbd{M-x} passes the argument along to the function that it calls. The argument value appears in the prompt while the command name is being read. @findex interactive You can use the command @code{M-x interactive} to specify a way of parsing arguments for interactive use of a function. For example, write: @example (defun foo (arg) "Doc string" (interactive "p") ...use arg...) @end example to make @code{arg} be the prefix argument when @code{foo} is called as a command. The call to @code{interactive} is actually a declaration rather than a function; it tells @code{call-interactively} how to read arguments to pass to the function. When actually called, @code{interactive} returns @code{nil}. The argument of @var{interactive} is usually a string containing a code letter followed by a prompt. Some code letters do not use I/O to get the argument and do not need prompts. To prompt for multiple arguments, you must provide a code letter, its prompt, a newline, and another code letter, and so forth. If the argument is not a string, it is evaluated to get a list of arguments to pass to the function. If you do not provide an argument to @code{interactive}, no arguments are passed when calling interactively. Available code letters are: @table @code @item a Function name: symbol with a function definition @item b Name of existing buffer @item B Name of buffer, possibly nonexistent @item c Character @item C Command name: symbol with interactive function definition @item d Value of point as number (does not do I/O) @item D Directory name @item e Last mouse event @item f Existing file name @item F Possibly nonexistent file name @item k Key sequence (string) @item m Value of mark as number (does not do I/O) @item n Number read using minibuffer @item N Prefix arg converted to number, or if none, do like code @code{n} @item p Prefix arg converted to number (does not do I/O) @item P Prefix arg in raw form (does not do I/O) @item r Region: point and mark as two numeric arguments, smallest first (does not do I/O) @item s Any string @item S Any symbol @item v Variable name: symbol that is @code{user-variable-p} @item x Lisp expression read but not evaluated @item X Lisp expression read and evaluated @end table In addition, if the string begins with @samp{*}, an error is signaled if the buffer is read-only. This happens before reading any arguments. If the string begins with @samp{@@}, the window the mouse is over is selected before anything else is done. You may use both @samp{@@} and @samp{*}; they are processed in the order that they appear. Normally, when describing a command that is run by name, we omit the @key{RET} that is needed to terminate the name. Thus we may refer to @kbd{M-x auto-fill-mode} rather than @kbd{M-x auto-fill-mode} @key{RET}. We mention the @key{RET} only when it is necessary to emphasize its presence, for example, when describing a sequence of input that contains a command name and arguments that follow it. @findex execute-extended-command @kbd{M-x} is defined to run the command @code{execute-extended-command}, which is responsible for reading the name of another command and invoking it.