Mercurial > hg > xemacs-beta
view man/lispref/dialog.texi @ 5879:77d7b77909c2
Move extents.c to working in byte positions only; fix a bug, extent_detach()
src/ChangeLog addition:
2015-03-27 Aidan Kehoe <kehoea@parhasard.net>
Fix a small bug, extent_detach(); minimise needless char-byte
conversion, extents.c, sticking to byte positions in general in
this file.
* extents.c:
* extents.c (signal_single_extent_changed):
Pass byte endpoints to
gutter_extent_signal_changed_region_maybe(),
buffer_extent_signal_changed_region().
* extents.c (extent_detach):
Call signal_extent_changed() correctly, pass both extent endpoints
rather than just the byte and character variants of the start.
* extents.c (struct report_extent_modification_closure):
Do this in terms of byte positions.
* extents.c (report_extent_modification_mapper):
Use byte positions, only converting to characters when we are
definitely calling Lisp.
* extents.c (report_extent_modification):
Use byte positions in this API, move the byte-char conversion to
our callers, simplifying extents.c (it all now works in byte
positions).
* extents.h:
Update report_extent_modification's prototype.
* gutter.c (gutter_extent_signal_changed_region_maybe):
Use byte positions here, avoids needless byte-char conversion.
* gutter.h:
Update the prototype here.
* insdel.c:
* insdel.c (buffer_extent_signal_changed_region):
Implement this in terms of byte positions.
* insdel.c (signal_before_change):
* insdel.c (signal_after_change):
Call report_extent_modification() with byte positions, doing the
char->byte conversion here rather than leaving it to extents.c.
* insdel.h:
* insdel.h (struct each_buffer_change_data):
The extent unchanged info now describes bytecounts.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Fri, 27 Mar 2015 23:39:49 +0000 |
parents | 9fae6227ede5 |
children |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the XEmacs Lisp Reference Manual. @c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. @c See the file lispref.texi for copying conditions. @setfilename ../../info/dialog.info @node Dialog Boxes, Toolbar, Menus, Top @chapter Dialog Boxes @cindex dialog box @menu * Dialog Box Format:: * Dialog Box Functions:: @end menu @node Dialog Box Format, Dialog Box Functions, Dialog Boxes, Dialog Boxes @section Dialog Box Format A dialog box description is a list. @itemize @bullet @item The first element of the list is a string to display in the dialog box. @item The rest of the elements are descriptions of the dialog box's buttons. Each one is a vector of three elements: @itemize @minus @item The first element is the text of the button. @item The second element is the @dfn{callback}. @item The third element is @code{t} or @code{nil}, whether this button is selectable. @end itemize @end itemize If the callback of a button is a symbol, then it must name a command. It will be invoked with @code{call-interactively}. If it is a list, then it is evaluated with @code{eval}. One (and only one) of the buttons may be @code{nil}. This marker means that all following buttons should be flushright instead of flushleft. The syntax, more precisely: @example form := <something to pass to `eval'> command := <a symbol or string, to pass to `call-interactively'> callback := command | form active-p := <t, nil, or a form to evaluate to decide whether this button should be selectable> name := <string> partition := 'nil' button := '[' name callback active-p ']' dialog := '(' name [ button ]+ [ partition [ button ]+ ] ')' @end example @node Dialog Box Functions, , Dialog Box Format, Dialog Boxes @section Dialog Box Functions @defun popup-dialog-box dbox-desc This function pops up a dialog box. @var{dbox-desc} describes how the dialog box will appear (@pxref{Dialog Box Format}). @end defun @xref{Yes-or-No Queries}, for functions to ask a yes/no question using a dialog box.