Line
Link Here
|
0 |
-- xemacs-21.4.22-orig/man/custom.texi |
0 |
++ xemacs-21.4.22/man/custom.texi |
Lines 60-66
Link Here
|
60 |
|
60 |
|
61 |
@node Declaring Groups, Declaring Variables, Top, Top |
61 |
@node Declaring Groups, Declaring Variables, Top, Top |
62 |
@comment node-name, next, previous, up |
62 |
@comment node-name, next, previous, up |
63 |
@section Declaring Groups |
63 |
@chapter Declaring Groups |
64 |
|
64 |
|
65 |
Use @code{defgroup} to declare new customization groups. |
65 |
Use @code{defgroup} to declare new customization groups. |
66 |
|
66 |
|
Lines 92-98
Link Here
|
92 |
|
92 |
|
93 |
@node Declaring Variables, Declaring Faces, Declaring Groups, Top |
93 |
@node Declaring Variables, Declaring Faces, Declaring Groups, Top |
94 |
@comment node-name, next, previous, up |
94 |
@comment node-name, next, previous, up |
95 |
@section Declaring Variables |
95 |
@chapter Declaring Variables |
96 |
|
96 |
|
97 |
Use @code{defcustom} to declare user editable variables. |
97 |
Use @code{defcustom} to declare user editable variables. |
98 |
|
98 |
|
Lines 176-182
Link Here
|
176 |
|
176 |
|
177 |
@node Declaring Faces, Usage for Package Authors, Declaring Variables, Top |
177 |
@node Declaring Faces, Usage for Package Authors, Declaring Variables, Top |
178 |
@comment node-name, next, previous, up |
178 |
@comment node-name, next, previous, up |
179 |
@section Declaring Faces |
179 |
@chapter Declaring Faces |
180 |
|
180 |
|
181 |
Faces are declared with @code{defface}. |
181 |
Faces are declared with @code{defface}. |
182 |
|
182 |
|
Lines 228-234
Link Here
|
228 |
|
228 |
|
229 |
@node Usage for Package Authors, Utilities, Declaring Faces, Top |
229 |
@node Usage for Package Authors, Utilities, Declaring Faces, Top |
230 |
@comment node-name, next, previous, up |
230 |
@comment node-name, next, previous, up |
231 |
@section Usage for Package Authors |
231 |
@chapter Usage for Package Authors |
232 |
|
232 |
|
233 |
The recommended usage for the author of a typical emacs lisp package is |
233 |
The recommended usage for the author of a typical emacs lisp package is |
234 |
to create one group identifying the package, and make all user options |
234 |
to create one group identifying the package, and make all user options |
Lines 244-250
Link Here
|
244 |
|
244 |
|
245 |
@node Utilities, The Init File, Usage for Package Authors, Top |
245 |
@node Utilities, The Init File, Usage for Package Authors, Top |
246 |
@comment node-name, next, previous, up |
246 |
@comment node-name, next, previous, up |
247 |
@section Utilities |
247 |
@chapter Utilities |
248 |
|
248 |
|
249 |
These utilities can come in handy when adding customization support. |
249 |
These utilities can come in handy when adding customization support. |
250 |
|
250 |
|
Lines 276-282
Link Here
|
276 |
|
276 |
|
277 |
@node The Init File, Wishlist, Utilities, Top |
277 |
@node The Init File, Wishlist, Utilities, Top |
278 |
@comment node-name, next, previous, up |
278 |
@comment node-name, next, previous, up |
279 |
@section The Init File |
279 |
@chapter The Init File |
280 |
|
280 |
|
281 |
Customizations are saved to the file specified by @code{custom-file}, as |
281 |
Customizations are saved to the file specified by @code{custom-file}, as |
282 |
calls to @code{custom-set-variables} and @code{custom-set-faces}. |
282 |
calls to @code{custom-set-variables} and @code{custom-set-faces}. |
Lines 299-305
Link Here
|
299 |
|
299 |
|
300 |
@node Wishlist, , The Init File, Top |
300 |
@node Wishlist, , The Init File, Top |
301 |
@comment node-name, next, previous, up |
301 |
@comment node-name, next, previous, up |
302 |
@section Wishlist |
302 |
@chapter Wishlist |
303 |
|
303 |
|
304 |
@itemize @bullet |
304 |
@itemize @bullet |
305 |
@item |
305 |
@item |
306 |
-- xemacs-21.4.22-orig/man/info.texi |
306 |
++ xemacs-21.4.22/man/info.texi |
Lines 543-548
Link Here
|
543 |
@c If a menu appears at the end of this node, remove it. |
543 |
@c If a menu appears at the end of this node, remove it. |
544 |
@c It is an accident of the menu updating command. |
544 |
@c It is an accident of the menu updating command. |
545 |
|
545 |
|
|
|
546 |
@menu |
547 |
* Help-Cross:: |
548 |
@end menu |
549 |
|
546 |
@node Help-Cross, , , Help-Adv |
550 |
@node Help-Cross, , , Help-Adv |
547 |
@subsection The node reached by the cross reference in Info |
551 |
@subsection The node reached by the cross reference in Info |
548 |
|
552 |
|
549 |
-- xemacs-21.4.22-orig/man/lispref/edebug-inc.texi |
553 |
++ xemacs-21.4.22/man/lispref/edebug-inc.texi |
Lines 1103-1109
Link Here
|
1103 |
Here is a table of the possibilities for @var{specification} and how each |
1103 |
Here is a table of the possibilities for @var{specification} and how each |
1104 |
directs processing of arguments. |
1104 |
directs processing of arguments. |
1105 |
|
1105 |
|
1106 |
@table @bullet |
1106 |
@table @asis |
1107 |
|
1107 |
|
1108 |
@item @code{t} |
1108 |
@item @code{t} |
1109 |
All arguments are instrumented for evaluation. |
1109 |
All arguments are instrumented for evaluation. |
1110 |
-- xemacs-21.4.22-orig/man/lispref/packaging.texi |
1110 |
++ xemacs-21.4.22/man/lispref/packaging.texi |
Lines 600-606
Link Here
|
600 |
Does most of the work. Builds the elcs, infos at a minimum. |
600 |
Does most of the work. Builds the elcs, infos at a minimum. |
601 |
@end table |
601 |
@end table |
602 |
|
602 |
|
603 |
@subsection The targets that most people would be interested in would be: |
603 |
@section The targets that most people would be interested in would be: |
604 |
|
604 |
|
605 |
@itemize @bullet |
605 |
@itemize @bullet |
606 |
@item @code{all} |
606 |
@item @code{all} |
607 |
-- xemacs-21.4.22-orig/man/term.texi |
607 |
++ xemacs-21.4.22/man/term.texi |
Lines 4-10
Link Here
|
4 |
|
4 |
|
5 |
@titlepage |
5 |
@titlepage |
6 |
@sp 6 |
6 |
@sp 6 |
7 |
@center @titlefont(Notes about Emacs TERM Mode) |
7 |
@center @titlefont{Notes about Emacs TERM Mode} |
8 |
@end titlepage |
8 |
@end titlepage |
9 |
|
9 |
|
10 |
@ifinfo |
10 |
@ifinfo |
11 |
-- xemacs-21.4.22-orig/man/widget.texi |
11 |
++ xemacs-21.4.22/man/widget.texi |
Lines 38-44
Link Here
|
38 |
|
38 |
|
39 |
@node Introduction, User Interface, Top, Top |
39 |
@node Introduction, User Interface, Top, Top |
40 |
@comment node-name, next, previous, up |
40 |
@comment node-name, next, previous, up |
41 |
@section Introduction |
41 |
@chapter Introduction |
42 |
|
42 |
|
43 |
Most graphical user interface toolkits, such as Motif and XView, provide |
43 |
Most graphical user interface toolkits, such as Motif and XView, provide |
44 |
a number of standard user interface controls (sometimes known as |
44 |
a number of standard user interface controls (sometimes known as |
Lines 129-135
Link Here
|
129 |
|
129 |
|
130 |
@node User Interface, Programming Example, Introduction, Top |
130 |
@node User Interface, Programming Example, Introduction, Top |
131 |
@comment node-name, next, previous, up |
131 |
@comment node-name, next, previous, up |
132 |
@section User Interface |
132 |
@chapter User Interface |
133 |
|
133 |
|
134 |
A form consists of read only text for documentation and some fields, |
134 |
A form consists of read only text for documentation and some fields, |
135 |
where each of the fields contains two parts, a tag and a value. The |
135 |
where each of the fields contains two parts, a tag and a value. The |
Lines 175-181
Link Here
|
175 |
a form, namely editing the editable text fields and activating the |
175 |
a form, namely editing the editable text fields and activating the |
176 |
buttons. |
176 |
buttons. |
177 |
|
177 |
|
178 |
@subsection Editable Text Fields |
178 |
@section Editable Text Fields |
179 |
|
179 |
|
180 |
In the example, the value for the @samp{Name} is most likely displayed |
180 |
In the example, the value for the @samp{Name} is most likely displayed |
181 |
in an editable text field, and so are values for each of the members of |
181 |
in an editable text field, and so are values for each of the members of |
Lines 194-200
Link Here
|
194 |
Face used for other editing fields. |
194 |
Face used for other editing fields. |
195 |
@end deffn |
195 |
@end deffn |
196 |
|
196 |
|
197 |
@subsection Buttons |
197 |
@section Buttons |
198 |
|
198 |
|
199 |
Some portions of the buffer have an associated @dfn{action}, which can |
199 |
Some portions of the buffer have an associated @dfn{action}, which can |
200 |
be @dfn{invoked} by a standard key or mouse command. These portions |
200 |
be @dfn{invoked} by a standard key or mouse command. These portions |
Lines 259-265
Link Here
|
259 |
Face used for buttons when the mouse pointer is above it. |
259 |
Face used for buttons when the mouse pointer is above it. |
260 |
@end defopt |
260 |
@end defopt |
261 |
|
261 |
|
262 |
@subsection Navigation |
262 |
@section Navigation |
263 |
|
263 |
|
264 |
You can use all the normal Emacs commands to move around in a form |
264 |
You can use all the normal Emacs commands to move around in a form |
265 |
buffer, plus you will have these additional commands: |
265 |
buffer, plus you will have these additional commands: |
Lines 277-283
Link Here
|
277 |
|
277 |
|
278 |
@node Programming Example, Setting Up the Buffer, User Interface, Top |
278 |
@node Programming Example, Setting Up the Buffer, User Interface, Top |
279 |
@comment node-name, next, previous, up |
279 |
@comment node-name, next, previous, up |
280 |
@section Programming Example |
280 |
@chapter Programming Example |
281 |
|
281 |
|
282 |
Here is the code to implement the user interface example (see @ref{User |
282 |
Here is the code to implement the user interface example (see @ref{User |
283 |
Interface}). |
283 |
Interface}). |
Lines 369-375
Link Here
|
369 |
|
369 |
|
370 |
@node Setting Up the Buffer, Basic Types, Programming Example, Top |
370 |
@node Setting Up the Buffer, Basic Types, Programming Example, Top |
371 |
@comment node-name, next, previous, up |
371 |
@comment node-name, next, previous, up |
372 |
@section Setting Up the Buffer |
372 |
@chapter Setting Up the Buffer |
373 |
|
373 |
|
374 |
Widgets are created with @code{widget-create}, which returns a |
374 |
Widgets are created with @code{widget-create}, which returns a |
375 |
@dfn{widget} object. This object can be queried and manipulated by |
375 |
@dfn{widget} object. This object can be queried and manipulated by |
Lines 422-428
Link Here
|
422 |
|
422 |
|
423 |
@node Basic Types, Sexp Types, Setting Up the Buffer, Top |
423 |
@node Basic Types, Sexp Types, Setting Up the Buffer, Top |
424 |
@comment node-name, next, previous, up |
424 |
@comment node-name, next, previous, up |
425 |
@section Basic Types |
425 |
@chapter Basic Types |
426 |
|
426 |
|
427 |
The syntax of a type specification is given below: |
427 |
The syntax of a type specification is given below: |
428 |
|
428 |
|
Lines 635-641
Link Here
|
635 |
|
635 |
|
636 |
@node link, url-link, Basic Types, Basic Types |
636 |
@node link, url-link, Basic Types, Basic Types |
637 |
@comment node-name, next, previous, up |
637 |
@comment node-name, next, previous, up |
638 |
@subsection The @code{link} Widget |
638 |
@section The @code{link} Widget |
639 |
|
639 |
|
640 |
Syntax: |
640 |
Syntax: |
641 |
|
641 |
|
Lines 659-665
Link Here
|
659 |
|
659 |
|
660 |
@node url-link, info-link, link, Basic Types |
660 |
@node url-link, info-link, link, Basic Types |
661 |
@comment node-name, next, previous, up |
661 |
@comment node-name, next, previous, up |
662 |
@subsection The @code{url-link} Widget |
662 |
@section The @code{url-link} Widget |
663 |
|
663 |
|
664 |
Syntax: |
664 |
Syntax: |
665 |
|
665 |
|
Lines 672-678
Link Here
|
672 |
|
672 |
|
673 |
@node info-link, push-button, url-link, Basic Types |
673 |
@node info-link, push-button, url-link, Basic Types |
674 |
@comment node-name, next, previous, up |
674 |
@comment node-name, next, previous, up |
675 |
@subsection The @code{info-link} Widget |
675 |
@section The @code{info-link} Widget |
676 |
|
676 |
|
677 |
Syntax: |
677 |
Syntax: |
678 |
|
678 |
|
Lines 685-691
Link Here
|
685 |
|
685 |
|
686 |
@node push-button, editable-field, info-link, Basic Types |
686 |
@node push-button, editable-field, info-link, Basic Types |
687 |
@comment node-name, next, previous, up |
687 |
@comment node-name, next, previous, up |
688 |
@subsection The @code{push-button} Widget |
688 |
@section The @code{push-button} Widget |
689 |
|
689 |
|
690 |
Syntax: |
690 |
Syntax: |
691 |
|
691 |
|
Lines 709-715
Link Here
|
709 |
|
709 |
|
710 |
@node editable-field, text, push-button, Basic Types |
710 |
@node editable-field, text, push-button, Basic Types |
711 |
@comment node-name, next, previous, up |
711 |
@comment node-name, next, previous, up |
712 |
@subsection The @code{editable-field} Widget |
712 |
@section The @code{editable-field} Widget |
713 |
|
713 |
|
714 |
Syntax: |
714 |
Syntax: |
715 |
|
715 |
|
Lines 753-759
Link Here
|
753 |
|
753 |
|
754 |
@node text, menu-choice, editable-field, Basic Types |
754 |
@node text, menu-choice, editable-field, Basic Types |
755 |
@comment node-name, next, previous, up |
755 |
@comment node-name, next, previous, up |
756 |
@subsection The @code{text} Widget |
756 |
@section The @code{text} Widget |
757 |
|
757 |
|
758 |
This is just like @code{editable-field}, but intended for multiline text |
758 |
This is just like @code{editable-field}, but intended for multiline text |
759 |
fields. The default @code{:keymap} is @code{widget-text-keymap}, which |
759 |
fields. The default @code{:keymap} is @code{widget-text-keymap}, which |
Lines 761-767
Link Here
|
761 |
|
761 |
|
762 |
@node menu-choice, radio-button-choice, text, Basic Types |
762 |
@node menu-choice, radio-button-choice, text, Basic Types |
763 |
@comment node-name, next, previous, up |
763 |
@comment node-name, next, previous, up |
764 |
@subsection The @code{menu-choice} Widget |
764 |
@section The @code{menu-choice} Widget |
765 |
|
765 |
|
766 |
Syntax: |
766 |
Syntax: |
767 |
|
767 |
|
Lines 796-802
Link Here
|
796 |
|
796 |
|
797 |
@node radio-button-choice, item, menu-choice, Basic Types |
797 |
@node radio-button-choice, item, menu-choice, Basic Types |
798 |
@comment node-name, next, previous, up |
798 |
@comment node-name, next, previous, up |
799 |
@subsection The @code{radio-button-choice} Widget |
799 |
@section The @code{radio-button-choice} Widget |
800 |
|
800 |
|
801 |
Syntax: |
801 |
Syntax: |
802 |
|
802 |
|
Lines 856-862
Link Here
|
856 |
|
856 |
|
857 |
@node item, choice-item, radio-button-choice, Basic Types |
857 |
@node item, choice-item, radio-button-choice, Basic Types |
858 |
@comment node-name, next, previous, up |
858 |
@comment node-name, next, previous, up |
859 |
@subsection The @code{item} Widget |
859 |
@section The @code{item} Widget |
860 |
|
860 |
|
861 |
Syntax: |
861 |
Syntax: |
862 |
|
862 |
|
Lines 870-876
Link Here
|
870 |
|
870 |
|
871 |
@node choice-item, toggle, item, Basic Types |
871 |
@node choice-item, toggle, item, Basic Types |
872 |
@comment node-name, next, previous, up |
872 |
@comment node-name, next, previous, up |
873 |
@subsection The @code{choice-item} Widget |
873 |
@section The @code{choice-item} Widget |
874 |
|
874 |
|
875 |
Syntax: |
875 |
Syntax: |
876 |
|
876 |
|
Lines 886-892
Link Here
|
886 |
|
886 |
|
887 |
@node toggle, checkbox, choice-item, Basic Types |
887 |
@node toggle, checkbox, choice-item, Basic Types |
888 |
@comment node-name, next, previous, up |
888 |
@comment node-name, next, previous, up |
889 |
@subsection The @code{toggle} Widget |
889 |
@section The @code{toggle} Widget |
890 |
|
890 |
|
891 |
Syntax: |
891 |
Syntax: |
892 |
|
892 |
|
Lines 914-920
Link Here
|
914 |
|
914 |
|
915 |
@node checkbox, checklist, toggle, Basic Types |
915 |
@node checkbox, checklist, toggle, Basic Types |
916 |
@comment node-name, next, previous, up |
916 |
@comment node-name, next, previous, up |
917 |
@subsection The @code{checkbox} Widget |
917 |
@section The @code{checkbox} Widget |
918 |
|
918 |
|
919 |
The widget has two possible states, `selected' and `unselected', which |
919 |
The widget has two possible states, `selected' and `unselected', which |
920 |
corresponds to a @code{t} or @code{nil} value. |
920 |
corresponds to a @code{t} or @code{nil} value. |
Lines 927-933
Link Here
|
927 |
|
927 |
|
928 |
@node checklist, editable-list, checkbox, Basic Types |
928 |
@node checklist, editable-list, checkbox, Basic Types |
929 |
@comment node-name, next, previous, up |
929 |
@comment node-name, next, previous, up |
930 |
@subsection The @code{checklist} Widget |
930 |
@section The @code{checklist} Widget |
931 |
|
931 |
|
932 |
Syntax: |
932 |
Syntax: |
933 |
|
933 |
|
Lines 978-984
Link Here
|
978 |
|
978 |
|
979 |
@node editable-list, group, checklist, Basic Types |
979 |
@node editable-list, group, checklist, Basic Types |
980 |
@comment node-name, next, previous, up |
980 |
@comment node-name, next, previous, up |
981 |
@subsection The @code{editable-list} Widget |
981 |
@section The @code{editable-list} Widget |
982 |
|
982 |
|
983 |
Syntax: |
983 |
Syntax: |
984 |
|
984 |
|
Lines 1030-1036
Link Here
|
1030 |
|
1030 |
|
1031 |
@node group, , editable-list, Basic Types |
1031 |
@node group, , editable-list, Basic Types |
1032 |
@comment node-name, next, previous, up |
1032 |
@comment node-name, next, previous, up |
1033 |
@subsection The @code{group} Widget |
1033 |
@section The @code{group} Widget |
1034 |
|
1034 |
|
1035 |
This widget simply groups other widgets together. |
1035 |
This widget simply groups other widgets together. |
1036 |
|
1036 |
|
Lines 1044-1050
Link Here
|
1044 |
|
1044 |
|
1045 |
@node Sexp Types, Widget Properties, Basic Types, Top |
1045 |
@node Sexp Types, Widget Properties, Basic Types, Top |
1046 |
@comment |
1046 |
@comment |
1047 |
@section Sexp Types |
1047 |
@chapter Sexp Types |
1048 |
|
1048 |
|
1049 |
A number of widgets for editing s-expressions (lisp types) are also |
1049 |
A number of widgets for editing s-expressions (lisp types) are also |
1050 |
available. These basically fall in the following categories. |
1050 |
available. These basically fall in the following categories. |
Lines 1058-1064
Link Here
|
1058 |
|
1058 |
|
1059 |
@node constants, generic, Sexp Types, Sexp Types |
1059 |
@node constants, generic, Sexp Types, Sexp Types |
1060 |
@comment node-name, next, previous, up |
1060 |
@comment node-name, next, previous, up |
1061 |
@subsection The Constant Widgets. |
1061 |
@section The Constant Widgets. |
1062 |
|
1062 |
|
1063 |
The @code{const} widget can contain any lisp expression, but the user is |
1063 |
The @code{const} widget can contain any lisp expression, but the user is |
1064 |
prohibited from editing it, which is mainly useful as a component of one |
1064 |
prohibited from editing it, which is mainly useful as a component of one |
Lines 1094-1100
Link Here
|
1094 |
|
1094 |
|
1095 |
@node generic, atoms, constants, Sexp Types |
1095 |
@node generic, atoms, constants, Sexp Types |
1096 |
@comment node-name, next, previous, up |
1096 |
@comment node-name, next, previous, up |
1097 |
@subsection Generic Sexp Widget. |
1097 |
@section Generic Sexp Widget. |
1098 |
|
1098 |
|
1099 |
The @code{sexp} widget can contain any lisp expression, and allows the |
1099 |
The @code{sexp} widget can contain any lisp expression, and allows the |
1100 |
user to edit it inline in the buffer. |
1100 |
user to edit it inline in the buffer. |
Lines 1115-1121
Link Here
|
1115 |
|
1115 |
|
1116 |
@node atoms, composite, generic, Sexp Types |
1116 |
@node atoms, composite, generic, Sexp Types |
1117 |
@comment node-name, next, previous, up |
1117 |
@comment node-name, next, previous, up |
1118 |
@subsection Atomic Sexp Widgets. |
1118 |
@section Atomic Sexp Widgets. |
1119 |
|
1119 |
|
1120 |
The atoms are s-expressions that does not consist of other |
1120 |
The atoms are s-expressions that does not consist of other |
1121 |
s-expressions. A string is an atom, while a list is a composite type. |
1121 |
s-expressions. A string is an atom, while a list is a composite type. |
Lines 1192-1198
Link Here
|
1192 |
|
1192 |
|
1193 |
@node composite, , atoms, Sexp Types |
1193 |
@node composite, , atoms, Sexp Types |
1194 |
@comment node-name, next, previous, up |
1194 |
@comment node-name, next, previous, up |
1195 |
@subsection Composite Sexp Widgets. |
1195 |
@section Composite Sexp Widgets. |
1196 |
|
1196 |
|
1197 |
The syntax for the composite are |
1197 |
The syntax for the composite are |
1198 |
|
1198 |
|
Lines 1265-1271
Link Here
|
1265 |
|
1265 |
|
1266 |
@node Widget Properties, Defining New Widgets, Sexp Types, Top |
1266 |
@node Widget Properties, Defining New Widgets, Sexp Types, Top |
1267 |
@comment node-name, next, previous, up |
1267 |
@comment node-name, next, previous, up |
1268 |
@section Properties |
1268 |
@chapter Properties |
1269 |
|
1269 |
|
1270 |
You can examine or set the value of a widget by using the widget object |
1270 |
You can examine or set the value of a widget by using the widget object |
1271 |
that was returned by @code{widget-create}. |
1271 |
that was returned by @code{widget-create}. |
Lines 1353-1359
Link Here
|
1353 |
|
1353 |
|
1354 |
@node Defining New Widgets, Widget Browser, Widget Properties, Top |
1354 |
@node Defining New Widgets, Widget Browser, Widget Properties, Top |
1355 |
@comment node-name, next, previous, up |
1355 |
@comment node-name, next, previous, up |
1356 |
@section Defining New Widgets |
1356 |
@chapter Defining New Widgets |
1357 |
|
1357 |
|
1358 |
You can define specialized widgets with @code{define-widget}. It allows |
1358 |
You can define specialized widgets with @code{define-widget}. It allows |
1359 |
you to create a shorthand for more complex widgets. This includes |
1359 |
you to create a shorthand for more complex widgets. This includes |
Lines 1565-1571
Link Here
|
1565 |
|
1565 |
|
1566 |
@node Widget Browser, Widget Minor Mode, Defining New Widgets, Top |
1566 |
@node Widget Browser, Widget Minor Mode, Defining New Widgets, Top |
1567 |
@comment node-name, next, previous, up |
1567 |
@comment node-name, next, previous, up |
1568 |
@section Widget Browser |
1568 |
@chapter Widget Browser |
1569 |
|
1569 |
|
1570 |
There is a separate package to browse widgets. This is intended to help |
1570 |
There is a separate package to browse widgets. This is intended to help |
1571 |
programmers who want to examine the content of a widget. The browser |
1571 |
programmers who want to examine the content of a widget. The browser |
Lines 1589-1595
Link Here
|
1589 |
|
1589 |
|
1590 |
@node Widget Minor Mode, Utilities, Widget Browser, Top |
1590 |
@node Widget Minor Mode, Utilities, Widget Browser, Top |
1591 |
@comment node-name, next, previous, up |
1591 |
@comment node-name, next, previous, up |
1592 |
@section Widget Minor Mode |
1592 |
@chapter Widget Minor Mode |
1593 |
|
1593 |
|
1594 |
There is a minor mode for manipulating widgets in major modes that |
1594 |
There is a minor mode for manipulating widgets in major modes that |
1595 |
doesn't provide any support for widgets themselves. This is mostly |
1595 |
doesn't provide any support for widgets themselves. This is mostly |
Lines 1606-1612
Link Here
|
1606 |
|
1606 |
|
1607 |
@node Utilities, Widget Wishlist, Widget Minor Mode, Top |
1607 |
@node Utilities, Widget Wishlist, Widget Minor Mode, Top |
1608 |
@comment node-name, next, previous, up |
1608 |
@comment node-name, next, previous, up |
1609 |
@section Utilities. |
1609 |
@chapter Utilities. |
1610 |
|
1610 |
|
1611 |
@defun widget-prompt-value widget prompt [ value unbound ] |
1611 |
@defun widget-prompt-value widget prompt [ value unbound ] |
1612 |
Prompt for a value matching @var{widget}, using @var{prompt}.@* |
1612 |
Prompt for a value matching @var{widget}, using @var{prompt}.@* |
Lines 1621-1627
Link Here
|
1621 |
|
1621 |
|
1622 |
@node Widget Wishlist, Widget Internals, Utilities, Top |
1622 |
@node Widget Wishlist, Widget Internals, Utilities, Top |
1623 |
@comment node-name, next, previous, up |
1623 |
@comment node-name, next, previous, up |
1624 |
@section Wishlist |
1624 |
@chapter Wishlist |
1625 |
|
1625 |
|
1626 |
@itemize @bullet |
1626 |
@itemize @bullet |
1627 |
@item |
1627 |
@item |
Lines 1693-1699
Link Here
|
1693 |
@end itemize |
1693 |
@end itemize |
1694 |
|
1694 |
|
1695 |
@node Widget Internals, , Widget Wishlist, Top |
1695 |
@node Widget Internals, , Widget Wishlist, Top |
1696 |
@section Internals |
1696 |
@chapter Internals |
1697 |
|
1697 |
|
1698 |
This (very brief!) section provides a few notes on the internal |
1698 |
This (very brief!) section provides a few notes on the internal |
1699 |
structure and implementation of Emacs widgets. Avoid relying on this |
1699 |
structure and implementation of Emacs widgets. Avoid relying on this |
Lines 1701-1707
Link Here
|
1701 |
To the extent that it actually describes APIs, the information will be |
1701 |
To the extent that it actually describes APIs, the information will be |
1702 |
moved to appropriate sections of the manual in due course. |
1702 |
moved to appropriate sections of the manual in due course. |
1703 |
|
1703 |
|
1704 |
@subsection The @dfn{Widget} and @dfn{Type} Structures |
1704 |
@section The @dfn{Widget} and @dfn{Type} Structures |
1705 |
|
1705 |
|
1706 |
Widgets and types are currently both implemented as lists. |
1706 |
Widgets and types are currently both implemented as lists. |
1707 |
|
1707 |
|