\1f
Indirect:
cl.info-1: 1164
-cl.info-2: 46306
-cl.info-3: 89087
-cl.info-4: 137810
-cl.info-5: 175806
-cl.info-6: 218409
+cl.info-2: 46305
+cl.info-3: 89086
+cl.info-4: 137809
+cl.info-5: 175805
+cl.info-6: 218388
\1f
Tag Table:
(Indirect)
Node: Assignment\7f36505
Node: Generalized Variables\7f37746
Node: Basic Setf\7f39053
-Node: Modify Macros\7f46306
-Node: Customizing Setf\7f53515
-Node: Variable Bindings\7f60804
-Node: Dynamic Bindings\7f61385
-Node: Lexical Bindings\7f62275
-Node: Function Bindings\7f66379
-Node: Macro Bindings\7f68766
-Node: Conditionals\7f71689
-Node: Blocks and Exits\7f74772
-Node: Iteration\7f77828
-Node: Loop Facility\7f83301
-Node: Loop Basics\7f84228
-Node: Loop Examples\7f86828
-Node: For Clauses\7f89087
-Node: Iteration Clauses\7f100964
-Node: Accumulation Clauses\7f102805
-Node: Other Clauses\7f105149
-Node: Multiple Values\7f111218
-Node: Macros\7f113111
-Node: Declarations\7f116329
-Node: Symbols\7f124815
-Node: Property Lists\7f125096
-Node: Creating Symbols\7f127287
-Node: Numbers\7f129365
-Node: Predicates on Numbers\7f129845
-Node: Numerical Functions\7f130874
-Node: Random Numbers\7f135101
-Node: Implementation Parameters\7f137810
-Node: Sequences\7f141382
-Node: Sequence Basics\7f142055
-Node: Mapping over Sequences\7f145633
-Node: Sequence Functions\7f151487
-Node: Searching Sequences\7f157662
-Node: Sorting Sequences\7f160699
-Node: Lists\7f163247
-Node: List Functions\7f163672
-Node: Substitution of Expressions\7f167935
-Node: Lists as Sets\7f169821
-Node: Association Lists\7f173883
-Node: Hash Tables\7f175586
-Node: Structures\7f175806
-Node: Assertions\7f190589
-Node: Efficiency Concerns\7f193532
-Node: Common Lisp Compatibility\7f199859
-Node: Old CL Compatibility\7f203015
-Node: Porting Common Lisp\7f207398
-Node: Function Index\7f218409
-Node: Variable Index\7f229558
+Node: Modify Macros\7f46305
+Node: Customizing Setf\7f53514
+Node: Variable Bindings\7f60803
+Node: Dynamic Bindings\7f61384
+Node: Lexical Bindings\7f62274
+Node: Function Bindings\7f66378
+Node: Macro Bindings\7f68765
+Node: Conditionals\7f71688
+Node: Blocks and Exits\7f74771
+Node: Iteration\7f77827
+Node: Loop Facility\7f83300
+Node: Loop Basics\7f84227
+Node: Loop Examples\7f86827
+Node: For Clauses\7f89086
+Node: Iteration Clauses\7f100963
+Node: Accumulation Clauses\7f102804
+Node: Other Clauses\7f105148
+Node: Multiple Values\7f111217
+Node: Macros\7f113110
+Node: Declarations\7f116328
+Node: Symbols\7f124814
+Node: Property Lists\7f125095
+Node: Creating Symbols\7f127286
+Node: Numbers\7f129364
+Node: Predicates on Numbers\7f129844
+Node: Numerical Functions\7f130873
+Node: Random Numbers\7f135100
+Node: Implementation Parameters\7f137809
+Node: Sequences\7f141381
+Node: Sequence Basics\7f142054
+Node: Mapping over Sequences\7f145632
+Node: Sequence Functions\7f151486
+Node: Searching Sequences\7f157661
+Node: Sorting Sequences\7f160698
+Node: Lists\7f163246
+Node: List Functions\7f163671
+Node: Substitution of Expressions\7f167934
+Node: Lists as Sets\7f169820
+Node: Association Lists\7f173882
+Node: Hash Tables\7f175585
+Node: Structures\7f175805
+Node: Assertions\7f190588
+Node: Efficiency Concerns\7f193511
+Node: Common Lisp Compatibility\7f199838
+Node: Old CL Compatibility\7f202994
+Node: Porting Common Lisp\7f207377
+Node: Function Index\7f218388
+Node: Variable Index\7f229537
\1f
End Tag Table
strictly speaking redundant now that `setf' exists. Many
programmers continue to prefer `setq' for setting simple
variables, though, purely for stylistic or historical reasons.
- The macro `(setf x y)' actually expands to `(setq x y)', so
+ The form `(setf x y)' actually expands to `(setq x y)', so
there is no performance penalty for using it in compiled code.
* A call to any of the following Lisp functions:
(assert (> x 10) t "x is too small: %d")
- This usage of SHOW-ARGS is an extension to Common Lisp. In true
+ This usage of SHOW-ARGS is a change to Common Lisp. In true
Common Lisp, the second argument gives a list of PLACES which can
- be `setf''d by the user before continuing from the error. Since
- Emacs Lisp does not support continuable errors, it makes no sense
- to specify PLACES.
+ be `setf''d by the user before continuing from the error.
- - Special Form: check-type form type [string]
- This form verifies that FORM evaluates to a value of type TYPE.
+ - Special Form: check-type place type &optional string
+ This form verifies that PLACE evaluates to a value of type TYPE.
If so, it returns `nil'. If not, `check-type' signals a
- `wrong-type-argument' error. The default error message lists the
- erroneous value along with TYPE and FORM themselves. If STRING is
- specified, it is included in the error message in place of TYPE.
- For example:
+ continuable `wrong-type-argument' error. The default error
+ message lists the erroneous value along with TYPE and PLACE
+ themselves. If STRING is specified, it is included in the error
+ message in place of TYPE. For example:
(check-type x (integer 1 *) "a positive integer")
*Note Type Predicates::, for a description of the type specifiers
that may be used for TYPE.
- Note that in Common Lisp, the first argument to `check-type' must
- be a PLACE suitable for use by `setf', because `check-type'
- signals a continuable error that allows the user to modify PLACE.
+ Note that as in Common Lisp, the first argument to `check-type'
+ should be a PLACE suitable for use by `setf', because `check-type'
+ signals a continuable error that allows the user to modify PLACE,
+ most simply by returning a value from the debugger.
The following error-related macro is also defined:
*Note Overview of Texinfo: (texinfo)Top, to learn how to write a
Texinfo file.
- *Note Creating an Info File: (texinfo)Creating an Info File, to
-learn how to create an Info file from a Texinfo file.
+ *Note Creating an Info File: (texinfo)Create an Info File, to learn
+how to create an Info file from a Texinfo file.
- *Note Installing an Info File: (texinfo)Installing an Info File, to
+ *Note Installing an Info File: (texinfo)Install an Info File, to
learn how to install an Info file after you have created one.
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
\1f
Indirect:
-internals.info-1: 1776
-internals.info-2: 46627
-internals.info-3: 94463
-internals.info-4: 144160
-internals.info-5: 194051
-internals.info-6: 243655
-internals.info-7: 287722
-internals.info-8: 336589
+internals.info-1: 1777
+internals.info-2: 46638
+internals.info-3: 94563
+internals.info-4: 144260
+internals.info-5: 194151
+internals.info-6: 243752
+internals.info-7: 287819
+internals.info-8: 336686
\1f
Tag Table:
(Indirect)
-Node: Top\7f1776
-Node: A History of Emacs\7f7030
-Node: Through Version 18\7f8555
-Node: Lucid Emacs\7f12003
-Node: GNU Emacs 19\7f15021
-Node: GNU Emacs 20\7f17204
-Node: XEmacs\7f17631
-Node: XEmacs From the Outside\7f20810
-Node: The Lisp Language\7f22577
-Node: XEmacs From the Perspective of Building\7f32120
-Node: XEmacs From the Inside\7f38245
-Node: The XEmacs Object System (Abstractly Speaking)\7f46627
-Node: How Lisp Objects Are Represented in C\7f60713
-Node: Rules When Writing New C Code\7f65390
-Node: General Coding Rules\7f66194
-Node: Writing Lisp Primitives\7f71915
-Node: Adding Global Lisp Variables\7f83084
-Node: Coding for Mule\7f86722
-Node: Character-Related Data Types\7f87701
-Node: Working With Character and Byte Positions\7f90698
-Node: Conversion to and from External Data\7f94463
-Node: General Guidelines for Writing Mule-Aware Code\7f100604
-Node: An Example of Mule-Aware Code\7f103292
-Node: Techniques for XEmacs Developers\7f105273
-Node: A Summary of the Various XEmacs Modules\7f113220
-Node: Low-Level Modules\7f114040
-Node: Basic Lisp Modules\7f121501
-Node: Modules for Standard Editing Operations\7f128095
-Node: Editor-Level Control Flow Modules\7f133983
-Node: Modules for the Basic Displayable Lisp Objects\7f137494
-Node: Modules for other Display-Related Lisp Objects\7f140447
-Node: Modules for the Redisplay Mechanism\7f141788
-Node: Modules for Interfacing with the File System\7f144160
-Node: Modules for Other Aspects of the Lisp Interpreter and Object System\7f147858
-Node: Modules for Interfacing with the Operating System\7f153311
-Node: Modules for Interfacing with X Windows\7f160867
-Node: Modules for Internationalization\7f164350
-Node: Allocation of Objects in XEmacs Lisp\7f166987
-Node: Introduction to Allocation\7f167508
-Node: Garbage Collection\7f171194
-Node: GCPROing\7f172350
-Node: Garbage Collection - Step by Step\7f179354
-Node: Invocation\7f179746
-Node: garbage_collect_1\7f182759
-Node: mark_object\7f192239
-Node: gc_sweep\7f194051
-Node: sweep_lcrecords_1\7f199114
-Node: compact_string_chars\7f200109
-Node: sweep_strings\7f202289
-Node: sweep_bit_vectors_1\7f203254
-Node: Integers and Characters\7f203930
-Node: Allocation from Frob Blocks\7f204682
-Node: lrecords\7f206286
-Node: Low-level allocation\7f218512
-Node: Cons\7f222619
-Node: Vector\7f223345
-Node: Bit Vector\7f223922
-Node: Symbol\7f224415
-Node: Marker\7f224769
-Node: String\7f225324
-Node: Compiled Function\7f228937
-Node: Dumping\7f229106
-Node: Overview\7f231327
-Node: Data descriptions\7f231897
-Node: Dumping phase\7f233902
-Node: Object inventory\7f234305
-Node: Address allocation\7f237159
-Node: The header\7f238546
-Node: Data dumping\7f239054
-Node: Pointers dumping\7f239715
-Node: Reloading phase\7f240933
-Node: Remaining issues\7f242694
-Node: Events and the Event Loop\7f243655
-Node: Introduction to Events\7f244105
-Node: Main Loop\7f246054
-Node: Specifics of the Event Gathering Mechanism\7f249629
-Node: Specifics About the Emacs Event\7f262082
-Node: The Event Stream Callback Routines\7f262337
-Node: Other Event Loop Functions\7f262582
-Node: Converting Events\7f263722
-Node: Dispatching Events; The Command Builder\7f264331
-Node: Evaluation; Stack Frames; Bindings\7f264566
-Node: Evaluation\7f264908
-Node: Dynamic Binding; The specbinding Stack; Unwind-Protects\7f271463
-Node: Simple Special Forms\7f273847
-Node: Catch and Throw\7f274630
-Node: Symbols and Variables\7f277205
-Node: Introduction to Symbols\7f277469
-Node: Obarrays\7f278537
-Node: Symbol Values\7f282070
-Node: Buffers and Textual Representation\7f284358
-Node: Introduction to Buffers\7f285016
-Node: The Text in a Buffer\7f287722
-Node: Buffer Lists\7f294872
-Node: Markers and Extents\7f296823
-Node: Bufbytes and Emchars\7f299088
-Node: The Buffer Object\7f299303
-Node: MULE Character Sets and Encodings\7f302783
-Node: Character Sets\7f303845
-Node: Encodings\7f307330
-Node: Japanese EUC (Extended Unix Code)\7f308397
-Node: JIS7\7f309229
-Node: Internal Mule Encodings\7f310579
-Node: Internal String Encoding\7f312409
-Node: Internal Character Encoding\7f314554
-Node: CCL\7f316278
-Node: The Lisp Reader and Compiler\7f323031
-Node: Lstreams\7f323244
-Node: Creating an Lstream\7f324275
-Node: Lstream Types\7f325502
-Node: Lstream Functions\7f325754
-Node: Lstream Methods\7f329320
-Node: Consoles; Devices; Frames; Windows\7f332462
-Node: Introduction to Consoles; Devices; Frames; Windows\7f332777
-Node: Point\7f335310
-Node: Window Hierarchy\7f336589
-Node: The Window Object\7f341041
-Node: The Redisplay Mechanism\7f344478
-Node: Critical Redisplay Sections\7f345270
-Node: Line Start Cache\7f346257
-Node: Redisplay Piece by Piece\7f349493
-Node: Extents\7f351530
-Node: Introduction to Extents\7f352064
-Node: Extent Ordering\7f353206
-Node: Format of the Extent Info\7f354447
-Node: Zero-Length Extents\7f356334
-Node: Mathematics of Extent Ordering\7f357734
-Node: Extent Fragments\7f362491
-Node: Faces\7f363577
-Node: Glyphs\7f363693
-Node: Specifiers\7f366712
-Node: Menus\7f366841
-Node: Subprocesses\7f369099
-Node: Interface to X Windows\7f371075
-Node: Index\7f371246
+Node: Top\7f1777
+Node: A History of Emacs\7f7041
+Node: Through Version 18\7f8566
+Node: Lucid Emacs\7f12014
+Node: GNU Emacs 19\7f15032
+Node: GNU Emacs 20\7f17215
+Node: XEmacs\7f17642
+Node: XEmacs From the Outside\7f20821
+Node: The Lisp Language\7f22588
+Node: XEmacs From the Perspective of Building\7f32131
+Node: XEmacs From the Inside\7f38256
+Node: The XEmacs Object System (Abstractly Speaking)\7f46638
+Node: How Lisp Objects Are Represented in C\7f60724
+Node: Rules When Writing New C Code\7f65401
+Node: General Coding Rules\7f66205
+Node: Writing Lisp Primitives\7f72015
+Node: Adding Global Lisp Variables\7f83184
+Node: Coding for Mule\7f86822
+Node: Character-Related Data Types\7f87801
+Node: Working With Character and Byte Positions\7f90798
+Node: Conversion to and from External Data\7f94563
+Node: General Guidelines for Writing Mule-Aware Code\7f100704
+Node: An Example of Mule-Aware Code\7f103392
+Node: Techniques for XEmacs Developers\7f105373
+Node: A Summary of the Various XEmacs Modules\7f113320
+Node: Low-Level Modules\7f114140
+Node: Basic Lisp Modules\7f121601
+Node: Modules for Standard Editing Operations\7f128195
+Node: Editor-Level Control Flow Modules\7f134083
+Node: Modules for the Basic Displayable Lisp Objects\7f137594
+Node: Modules for other Display-Related Lisp Objects\7f140547
+Node: Modules for the Redisplay Mechanism\7f141888
+Node: Modules for Interfacing with the File System\7f144260
+Node: Modules for Other Aspects of the Lisp Interpreter and Object System\7f147958
+Node: Modules for Interfacing with the Operating System\7f153411
+Node: Modules for Interfacing with X Windows\7f160967
+Node: Modules for Internationalization\7f164450
+Node: Allocation of Objects in XEmacs Lisp\7f167087
+Node: Introduction to Allocation\7f167608
+Node: Garbage Collection\7f171294
+Node: GCPROing\7f172450
+Node: Garbage Collection - Step by Step\7f179454
+Node: Invocation\7f179846
+Node: garbage_collect_1\7f182859
+Node: mark_object\7f192339
+Node: gc_sweep\7f194151
+Node: sweep_lcrecords_1\7f199214
+Node: compact_string_chars\7f200209
+Node: sweep_strings\7f202389
+Node: sweep_bit_vectors_1\7f203354
+Node: Integers and Characters\7f204030
+Node: Allocation from Frob Blocks\7f204782
+Node: lrecords\7f206386
+Node: Low-level allocation\7f218612
+Node: Cons\7f222719
+Node: Vector\7f223445
+Node: Bit Vector\7f224022
+Node: Symbol\7f224515
+Node: Marker\7f224869
+Node: String\7f225424
+Node: Compiled Function\7f229037
+Node: Dumping\7f229206
+Node: Overview\7f231427
+Node: Data descriptions\7f231997
+Node: Dumping phase\7f234002
+Node: Object inventory\7f234405
+Node: Address allocation\7f237258
+Node: The header\7f238647
+Node: Data dumping\7f239154
+Node: Pointers dumping\7f239815
+Node: Reloading phase\7f241030
+Node: Remaining issues\7f242791
+Node: Events and the Event Loop\7f243752
+Node: Introduction to Events\7f244202
+Node: Main Loop\7f246151
+Node: Specifics of the Event Gathering Mechanism\7f249726
+Node: Specifics About the Emacs Event\7f262179
+Node: The Event Stream Callback Routines\7f262434
+Node: Other Event Loop Functions\7f262679
+Node: Converting Events\7f263819
+Node: Dispatching Events; The Command Builder\7f264428
+Node: Evaluation; Stack Frames; Bindings\7f264663
+Node: Evaluation\7f265005
+Node: Dynamic Binding; The specbinding Stack; Unwind-Protects\7f271560
+Node: Simple Special Forms\7f273944
+Node: Catch and Throw\7f274727
+Node: Symbols and Variables\7f277302
+Node: Introduction to Symbols\7f277566
+Node: Obarrays\7f278634
+Node: Symbol Values\7f282167
+Node: Buffers and Textual Representation\7f284455
+Node: Introduction to Buffers\7f285113
+Node: The Text in a Buffer\7f287819
+Node: Buffer Lists\7f294969
+Node: Markers and Extents\7f296920
+Node: Bufbytes and Emchars\7f299185
+Node: The Buffer Object\7f299400
+Node: MULE Character Sets and Encodings\7f302880
+Node: Character Sets\7f303942
+Node: Encodings\7f307427
+Node: Japanese EUC (Extended Unix Code)\7f308494
+Node: JIS7\7f309326
+Node: Internal Mule Encodings\7f310676
+Node: Internal String Encoding\7f312506
+Node: Internal Character Encoding\7f314651
+Node: CCL\7f316375
+Node: The Lisp Reader and Compiler\7f323128
+Node: Lstreams\7f323341
+Node: Creating an Lstream\7f324372
+Node: Lstream Types\7f325599
+Node: Lstream Functions\7f325851
+Node: Lstream Methods\7f329417
+Node: Consoles; Devices; Frames; Windows\7f332559
+Node: Introduction to Consoles; Devices; Frames; Windows\7f332874
+Node: Point\7f335407
+Node: Window Hierarchy\7f336686
+Node: The Window Object\7f341138
+Node: The Redisplay Mechanism\7f344575
+Node: Critical Redisplay Sections\7f345367
+Node: Line Start Cache\7f346354
+Node: Redisplay Piece by Piece\7f349590
+Node: Extents\7f351627
+Node: Introduction to Extents\7f352161
+Node: Extent Ordering\7f353303
+Node: Format of the Extent Info\7f354544
+Node: Zero-Length Extents\7f356431
+Node: Mathematics of Extent Ordering\7f357831
+Node: Extent Fragments\7f362588
+Node: Faces\7f363674
+Node: Glyphs\7f363790
+Node: Specifiers\7f365977
+Node: Menus\7f366106
+Node: Subprocesses\7f368364
+Node: Interface to the X Window System\7f370350
+Node: Lucid Widget Library\7f370631
+Node: Generic Widget Interface\7f371922
+Node: Scrollbars\7f375481
+Node: Menubars\7f375624
+Node: Checkboxes and Radio Buttons\7f375767
+Node: Progress Bars\7f375953
+Node: Tab Controls\7f376113
+Node: Index\7f376234
\1f
End Tag Table
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
* Specifiers::
* Menus::
* Subprocesses::
-* Interface to X Windows::
+* Interface to the X Window System::
* Index::
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
tools means that a greater variety of development tools are available to
the developer.
- Almost every module contains a `syms_of_*()' function and a
-`vars_of_*()' function. The former declares any Lisp primitives you
-have defined and defines any symbols you will be using. The latter
-declares any global Lisp variables you have added and initializes global
-C variables in the module. For each such function, declare it in
-`symsinit.h' and make sure it's called in the appropriate place in
-`emacs.c'. *Important*: There are stringent requirements on exactly
-what can go into these functions. See the comment in `emacs.c'. The
-reason for this is to avoid obscure unwanted interactions during
-initialization. If you don't follow these rules, you'll be sorry! If
-you want to do anything that isn't allowed, create a
-`complex_vars_of_*()' function for it. Doing this is tricky, though:
-You have to make sure your function is called at the right time so that
-all the initialization dependencies work out.
-
Every module includes `<config.h>' (angle brackets so that
`--srcdir' works correctly; `config.h' may or may not be in the same
directory as the C sources) and `lisp.h'. `config.h' must always be
using `../work/configure'. There will be two different `config.h'
files. Which one will be used if you `#include "config.h"'?
+ Almost every module contains a `syms_of_*()' function and a
+`vars_of_*()' function. The former declares any Lisp primitives you
+have defined and defines any symbols you will be using. The latter
+declares any global Lisp variables you have added and initializes global
+C variables in the module. *Important*: There are stringent
+requirements on exactly what can go into these functions. See the
+comment in `emacs.c'. The reason for this is to avoid obscure unwanted
+interactions during initialization. If you don't follow these rules,
+you'll be sorry! If you want to do anything that isn't allowed, create
+a `complex_vars_of_*()' function for it. Doing this is tricky, though:
+you have to make sure your function is called at the right time so that
+all the initialization dependencies work out.
+
+ Declare each function of these kinds in `symsinit.h'. Make sure
+it's called in the appropriate place in `emacs.c'. You never need to
+include `symsinit.h' directly, because it is included by `lisp.h'.
+
*All global and static variables that are to be modifiable must be
declared uninitialized.* This means that you may not use the "declare
with initializer" form for these variables, such as `int some_variable
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
differences though:
1. We do not use the mark bit (which does not exist for C structures
- anyway), we use a big hash table instead.
+ anyway); we use a big hash table instead.
2. We do not use the mark function of lrecords but instead rely on the
external descriptions. This happens essentially because we need to
allows us to look up a pdump_entry_list_elmt with the object it points
to). Entries are added with `pdump_add_entry()' and looked up with
`pdump_get_entry()'. There is no need for entry removal. The hash
-value is computed quite basically from the object pointer by
+value is computed quite simply from the object pointer by
`pdump_make_hash()'.
The roots for the marking are:
`staticpro_nodump()' call for protected variables we do not want
to dump).
- 2. the `pdump_wire''d variables (`staticpro' is equivalent to
+ 2. the `pdump_wire''d variables (`staticpro()' is equivalent to
`staticpro_nodump()' + `pdump_wire()').
3. the `dumpstruct''ed variables, which points to C structures.
2. the C compiler is required to adjust the size of a struct so that
you can have an array of them next to each other. This means you
- can have a upper bound of the alignment requirements of a given
+ can have an upper bound of the alignment requirements of a given
structure by looking at which power of two its size is a multiple.
3. the non-variant part of variable size lrecords has an alignment
The maximum alignment requirement we take into account is 2^8.
`pdump_allocate_offset()' only has to do a linear allocation,
-starting at offset 256 (this leaves room for the header and keep the
+starting at offset 256 (this leaves room for the header and keeps the
alignments happy).
\1f
----------
The next step creates the file and writes a header with a signature
-and some random informations in it (number of staticpro, number of
+and some random information in it (number of staticpro, number of
assigned lrecord types, etc...). The reloc_address field, which
indicates at which address the file should be loaded if we want to
avoid post-reload relocation, is set to 0. It then seeks to offset 256
4. a vector of all the offsets to the objects in the file that
include a description (for faster relocation at reload time)
- 5. the pdump_wired and pdump_wired_list arrays
+ 5. the pdump_wire and pdump_wire_list arrays
For each of the arrays we write both the pointer to the variables and
the relocated offset of the object they point to. Since these variables
are global, the pointers are still valid when restarting the program and
are used to regenerate the global pointers.
- The `pdump_wired_list' array is a special case. The variables it
+ The `pdump_wire_list' array is a special case. The variables it
points to are the head of weak linked lists of lisp objects of the same
type. Not all objects of this list are dumped so the relocated pointer
we associate with them points to the first dumped object of the list, or
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/internals.info, produced by makeinfo version 4.0 from
+This is ../info/internals.info, produced by makeinfo version 4.0b from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
Glyphs are graphical elements that can be displayed in XEmacs
buffers or gutters. We use the term graphical element here in the
-broadest possible sense since glyphs can be as mundane as text to as
+broadest possible sense since glyphs can be as mundane as text or as
arcane as a native tab widget.
In XEmacs, glyphs represent the uninstantiated state of graphical
elements, i.e. they hold all the information necessary to produce an
-image on-screen but the image does not exist at this stage.
+image on-screen but the image need not exist at this stage, and multiple
+screen images can be instantiated from a single glyph.
Glyphs are lazily instantiated by calling one of the glyph
functions. This usually occurs within redisplay when `Fglyph_height' is
Widget-glyphs (a.k.a native widgets) are not cached in this way.
This is because widget-glyph image-instances on screen are toolkit
windows, and thus cannot be reused in multiple XEmacs domains. Thus
-widget-glyphs are cached on a window basis.
+widget-glyphs are cached on an XEmacs window basis.
Any action on a glyph first consults the cache before actually
instantiating a widget.
Widget-Glyphs in the X Environment
==================================
- Widget-glyphs under X make heavy use of lwlib for manipulating the
-native toolkit objects. This is primarily so that different toolkits can
-be supported for widget-glyphs, just as they are supported for features
-such as menubars etc.
-
- Lwlib is extremely poorly documented and quite hairy so here is my
-understanding of what goes on.
-
- Lwlib maintains a set of widget_instances which mirror the
-hierarchical state of Xt widgets. I think this is so that widgets can
-be updated and manipulated generically by the lwlib library. For
-instance update_one_widget_instance can cope with multiple types of
-widget and multiple types of toolkit. Each element in the widget
-hierarchy is updated from its corresponding widget_instance by walking
-the widget_instance tree recursively.
-
- This has desirable properties such as lw_modify_all_widgets which is
-called from `glyphs-x.c' and updates all the properties of a widget
-without having to know what the widget is or what toolkit it is from.
-Unfortunately this also has hairy properties such as making the lwlib
-code quite complex. And of course lwlib has to know at some level what
-the widget is and how to set its properties.
+ Widget-glyphs under X make heavy use of lwlib (*note Lucid Widget
+Library::) for manipulating the native toolkit objects. This is
+primarily so that different toolkits can be supported for
+widget-glyphs, just as they are supported for features such as menubars
+etc.
\1f
File: internals.info, Node: Specifiers, Next: Menus, Prev: Glyphs, Up: Top
description.
\1f
-File: internals.info, Node: Subprocesses, Next: Interface to X Windows, Prev: Menus, Up: Top
+File: internals.info, Node: Subprocesses, Next: Interface to the X Window System, Prev: Menus, Up: Top
Subprocesses
************
it is using pipes.
\1f
-File: internals.info, Node: Interface to X Windows, Next: Index, Prev: Subprocesses, Up: Top
+File: internals.info, Node: Interface to the X Window System, Next: Index, Prev: Subprocesses, Up: Top
-Interface to X Windows
-**********************
+Interface to the X Window System
+********************************
- Not yet documented.
+ Mostly undocumented.
+
+* Menu:
+
+* Lucid Widget Library:: An interface to various widget sets.
+
+\1f
+File: internals.info, Node: Lucid Widget Library, Up: Interface to the X Window System
+
+Lucid Widget Library
+====================
+
+ Lwlib is extremely poorly documented and quite hairy. The author(s)
+blame that on X, Xt, and Motif, with some justice, but also sufficient
+hypocrisy to avoid drawing the obvious conclusion about their own work.
+
+ The Lucid Widget Library is composed of two more or less independent
+pieces. The first, as the name suggests, is a set of widgets. These
+widgets are intended to resemble and improve on widgets provided in the
+Motif toolkit but not in the Athena widgets, including menubars and
+scrollbars. Recent additions by Andy Piper integrate some "modern"
+widgets by Edward Falk, including checkboxes, radio buttons, progress
+gauges, and index tab controls (aka notebooks).
+
+ The second piece of the Lucid widget library is a generic interface
+to several toolkits for X (including Xt, the Athena widget set, and
+Motif, as well as the Lucid widgets themselves) so that core XEmacs
+code need not know which widget set has been used to build the
+graphical user interface.
+
+* Menu:
+
+* Generic Widget Interface:: The lwlib generic widget interface.
+* Scrollbars::
+* Menubars::
+* Checkboxes and Radio Buttons::
+* Progress Bars::
+* Tab Controls::
+
+\1f
+File: internals.info, Node: Generic Widget Interface, Next: Scrollbars, Up: Lucid Widget Library
+
+Generic Widget Interface
+------------------------
+
+ In general in any toolkit a widget may be a composite object. In Xt,
+all widgets have an X window that they manage, but typically a complex
+widget will have widget children, each of which manages a subwindow of
+the parent widget's X window. These children may themselves be
+composite widgets. Thus a widget is actually a tree or hierarchy of
+widgets.
+
+ For each toolkit widget, lwlib maintains a tree of `widget_values'
+which mirror the hierarchical state of Xt widgets (including Motif,
+Athena, 3D Athena, and Falk's widget sets). Each `widget_value' has
+`contents' member, which points to the head of a linked list of its
+children. The linked list of siblings is chained through the `next'
+member of `widget_value'.
+
+ +-----------+
+ | composite |
+ +-----------+
+ |
+ | contents
+ V
+ +-------+ next +-------+ next +-------+
+ | child |----->| child |----->| child |
+ +-------+ +-------+ +-------+
+ |
+ | contents
+ V
+ +-------------+ next +-------------+
+ | grand child |----->| grand child |
+ +-------------+ +-------------+
+
+ The `widget_value' hierarchy of a composite widget with two simple
+ children and one composite child.
+
+ The `widget_instance' structure maintains the inverse view of the
+tree. As for the `widget_value', siblings are chained through the
+`next' member. However, rather than naming children, the
+`widget_instance' tree links to parents.
+
+ +-----------+
+ | composite |
+ +-----------+
+ A
+ | parent
+ |
+ +-------+ next +-------+ next +-------+
+ | child |----->| child |----->| child |
+ +-------+ +-------+ +-------+
+ A
+ | parent
+ |
+ +-------------+ next +-------------+
+ | grand child |----->| grand child |
+ +-------------+ +-------------+
+
+ The `widget_value' hierarchy of a composite widget with two simple
+ children and one composite child.
+
+ This permits widgets derived from different toolkits to be updated
+and manipulated generically by the lwlib library. For instance
+`update_one_widget_instance' can cope with multiple types of widget and
+multiple types of toolkit. Each element in the widget hierarchy is
+updated from its corresponding `widget_value' by walking the
+`widget_value' tree. This has desirable properties. For example,
+`lw_modify_all_widgets' is called from `glyphs-x.c' and updates all the
+properties of a widget without having to know what the widget is or
+what toolkit it is from. Unfortunately this also has its hairy
+properties; the lwlib code quite complex. And of course lwlib has to
+know at some level what the widget is and how to set its properties.
+
+ The `widget_instance' structure also contains a pointer to the root
+of its tree. Widget instances are further confi
+
+\1f
+File: internals.info, Node: Scrollbars, Next: Menubars, Prev: Generic Widget Interface, Up: Lucid Widget Library
+
+Scrollbars
+----------
+
+\1f
+File: internals.info, Node: Menubars, Next: Checkboxes and Radio Buttons, Prev: Scrollbars, Up: Lucid Widget Library
+
+Menubars
+--------
+
+\1f
+File: internals.info, Node: Checkboxes and Radio Buttons, Next: Progress Bars, Prev: Menubars, Up: Lucid Widget Library
+
+Checkboxes and Radio Buttons
+----------------------------
+
+\1f
+File: internals.info, Node: Progress Bars, Next: Tab Controls, Prev: Checkboxes and Radio Buttons, Up: Lucid Widget Library
+
+Progress Bars
+-------------
+
+\1f
+File: internals.info, Node: Tab Controls, Prev: Progress Bars, Up: Lucid Widget Library
+
+Tab Controls
+------------
\1f
-File: internals.info, Node: Index, Prev: Interface to X Windows, Up: Top
+File: internals.info, Node: Index, Prev: Interface to the X Window System, Up: Top
Index
*****
\1f
Indirect:
lispref.info-1: 2366
-lispref.info-2: 48665
-lispref.info-3: 97152
-lispref.info-4: 146992
-lispref.info-5: 196731
-lispref.info-6: 245085
-lispref.info-7: 293492
-lispref.info-8: 342147
-lispref.info-9: 387229
-lispref.info-10: 436160
-lispref.info-11: 485017
-lispref.info-12: 533548
-lispref.info-13: 581024
-lispref.info-14: 630620
-lispref.info-15: 678992
-lispref.info-16: 724920
-lispref.info-17: 770257
-lispref.info-18: 817727
-lispref.info-19: 865285
-lispref.info-20: 912910
-lispref.info-21: 960937
-lispref.info-22: 1009857
-lispref.info-23: 1056119
-lispref.info-24: 1102583
-lispref.info-25: 1152243
-lispref.info-26: 1200932
-lispref.info-27: 1249787
-lispref.info-28: 1298454
-lispref.info-29: 1345033
-lispref.info-30: 1393850
-lispref.info-31: 1442263
-lispref.info-32: 1492252
-lispref.info-33: 1540816
-lispref.info-34: 1587991
-lispref.info-35: 1637817
-lispref.info-36: 1686493
-lispref.info-37: 1732226
-lispref.info-38: 1781365
-lispref.info-39: 1828801
-lispref.info-40: 1877354
-lispref.info-41: 1923907
-lispref.info-42: 1972602
-lispref.info-43: 2016977
-lispref.info-44: 2061346
-lispref.info-45: 2107840
-lispref.info-46: 2148682
-lispref.info-47: 2197899
-lispref.info-48: 2211766
+lispref.info-2: 49116
+lispref.info-3: 97603
+lispref.info-4: 147443
+lispref.info-5: 197182
+lispref.info-6: 245536
+lispref.info-7: 293943
+lispref.info-8: 342608
+lispref.info-9: 387690
+lispref.info-10: 436621
+lispref.info-11: 485478
+lispref.info-12: 534009
+lispref.info-13: 581561
+lispref.info-14: 629419
+lispref.info-15: 678834
+lispref.info-16: 726829
+lispref.info-17: 772166
+lispref.info-18: 819636
+lispref.info-19: 867194
+lispref.info-20: 914820
+lispref.info-21: 962847
+lispref.info-22: 1011769
+lispref.info-23: 1058032
+lispref.info-24: 1104496
+lispref.info-25: 1154156
+lispref.info-26: 1202847
+lispref.info-27: 1251702
+lispref.info-28: 1300369
+lispref.info-29: 1350320
+lispref.info-30: 1398469
+lispref.info-31: 1444124
+lispref.info-32: 1494113
+lispref.info-33: 1542683
+lispref.info-34: 1589888
+lispref.info-35: 1639714
+lispref.info-36: 1688390
+lispref.info-37: 1734123
+lispref.info-38: 1783262
+lispref.info-39: 1830704
+lispref.info-40: 1879257
+lispref.info-41: 1925810
+lispref.info-42: 1974505
+lispref.info-43: 2018880
+lispref.info-44: 2063249
+lispref.info-45: 2109743
+lispref.info-46: 2150585
+lispref.info-47: 2199803
+lispref.info-48: 2213672
\1f
Tag Table:
(Indirect)
Node: Top\7f2366
-Node: Copying\7f48665
-Node: Introduction\7f67823
-Node: Caveats\7f69414
-Node: Lisp History\7f71093
-Node: Conventions\7f72349
-Node: Some Terms\7f73164
-Node: nil and t\7f73885
-Node: Evaluation Notation\7f75562
-Node: Printing Notation\7f76475
-Node: Error Messages\7f77349
-Node: Buffer Text Notation\7f77790
-Node: Format of Descriptions\7f78665
-Node: A Sample Function Description\7f79519
-Node: A Sample Variable Description\7f83505
-Node: Acknowledgements\7f84413
-Node: Lisp Data Types\7f86391
-Node: Printed Representation\7f88946
-Node: Comments\7f90988
-Node: Primitive Types\7f91885
-Node: Programming Types\7f93544
-Node: Integer Type\7f95496
-Node: Floating Point Type\7f96533
-Node: Character Type\7f97152
-Node: Symbol Type\7f105056
-Node: Sequence Type\7f107751
-Node: Cons Cell Type\7f109270
-Node: Dotted Pair Notation\7f113754
-Node: Association List Type\7f115875
-Node: Array Type\7f116758
-Node: String Type\7f118224
-Node: Vector Type\7f120905
-Node: Bit Vector Type\7f121677
-Node: Function Type\7f122539
-Node: Macro Type\7f123652
-Node: Primitive Function Type\7f124349
-Node: Compiled-Function Type\7f125875
-Node: Autoload Type\7f126429
-Node: Char Table Type\7f127443
-Node: Hash Table Type\7f127617
-Node: Range Table Type\7f128772
-Node: Weak List Type\7f129625
-Node: Editing Types\7f129775
-Node: Buffer Type\7f131402
-Node: Marker Type\7f133429
-Node: Extent Type\7f134153
-Node: Window Type\7f135421
-Node: Frame Type\7f136832
-Node: Device Type\7f137627
-Node: Console Type\7f138453
-Node: Window Configuration Type\7f139654
-Node: Event Type\7f140352
-Node: Process Type\7f140516
-Node: Stream Type\7f141551
-Node: Keymap Type\7f142674
-Node: Syntax Table Type\7f143212
-Node: Display Table Type\7f144235
-Node: Database Type\7f144674
-Node: Charset Type\7f144840
-Node: Coding System Type\7f145004
-Node: ToolTalk Message Type\7f145188
-Node: ToolTalk Pattern Type\7f145387
-Node: Window-System Types\7f145559
-Node: Face Type\7f146705
-Node: Glyph Type\7f146836
-Node: Specifier Type\7f146992
-Node: Font Instance Type\7f147165
-Node: Color Instance Type\7f147355
-Node: Image Instance Type\7f147552
-Node: Toolbar Button Type\7f147750
-Node: Subwindow Type\7f147943
-Node: X Resource Type\7f148122
-Node: Type Predicates\7f148275
-Node: Equality Predicates\7f157404
-Node: Numbers\7f162215
-Node: Integer Basics\7f163670
-Node: Float Basics\7f166019
-Node: Predicates on Numbers\7f167761
-Node: Comparison of Numbers\7f169394
-Node: Numeric Conversions\7f173215
-Node: Arithmetic Operations\7f174681
-Node: Rounding Operations\7f180820
-Node: Bitwise Operations\7f181933
-Node: Math Functions\7f190979
-Node: Random Numbers\7f193512
-Node: Strings and Characters\7f195278
-Node: String Basics\7f196731
-Node: Predicates for Strings\7f199149
-Node: Creating Strings\7f199912
-Node: Predicates for Characters\7f205253
-Node: Character Codes\7f206324
-Node: Text Comparison\7f207744
-Node: String Conversion\7f211189
-Node: Modifying Strings\7f214859
-Node: String Properties\7f215500
-Node: Formatting Strings\7f216145
-Node: Character Case\7f225763
-Node: Case Tables\7f229317
-Node: Char Tables\7f233288
-Node: Char Table Types\7f234680
-Node: Working With Char Tables\7f236265
-Node: Lists\7f238282
-Node: Cons Cells\7f239405
-Node: Lists as Boxes\7f240741
-Node: List-related Predicates\7f243383
-Node: List Elements\7f245085
-Node: Building Lists\7f250114
-Node: Modifying Lists\7f256106
-Node: Setcar\7f256918
-Node: Setcdr\7f259349
-Node: Rearrangement\7f261870
-Node: Sets And Lists\7f267456
-Node: Association Lists\7f271684
-Ref: Association Lists-Footnote-1\7f280975
-Node: Property Lists\7f281180
-Node: Working With Normal Plists\7f282728
-Node: Working With Lax Plists\7f285065
-Node: Converting Plists To/From Alists\7f287345
-Node: Weak Lists\7f288693
-Node: Sequences Arrays Vectors\7f290856
-Node: Sequence Functions\7f293492
-Node: Arrays\7f297151
-Node: Array Functions\7f300215
-Node: Vectors\7f302748
-Node: Vector Functions\7f304246
-Node: Bit Vectors\7f306817
-Node: Bit Vector Functions\7f307662
-Node: Symbols\7f309961
-Node: Symbol Components\7f311010
-Node: Definitions\7f315183
-Node: Creating Symbols\7f317408
-Node: Symbol Properties\7f324442
-Node: Plists and Alists\7f325969
-Node: Object Plists\7f327718
-Node: Other Plists\7f330478
-Node: Evaluation\7f332277
-Node: Intro Eval\7f333082
-Ref: Intro Eval-Footnote-1\7f336435
-Node: Eval\7f336570
-Node: Forms\7f340988
-Node: Self-Evaluating Forms\7f342147
-Node: Symbol Forms\7f343660
-Node: Classifying Lists\7f344577
-Node: Function Indirection\7f345333
-Node: Function Forms\7f348432
-Node: Macro Forms\7f349429
-Node: Special Forms\7f351029
-Node: Autoloading\7f353338
-Node: Quoting\7f353836
-Node: Control Structures\7f355197
-Node: Sequencing\7f356817
-Node: Conditionals\7f359682
-Node: Combining Conditions\7f363105
-Node: Iteration\7f366375
-Node: Nonlocal Exits\7f368154
-Node: Catch and Throw\7f368856
-Node: Examples of Catch\7f372695
-Node: Errors\7f374714
-Node: Signaling Errors\7f376203
-Node: Processing of Errors\7f384950
-Node: Handling Errors\7f387229
-Node: Error Symbols\7f394470
-Node: Cleanups\7f398426
-Node: Variables\7f402204
-Node: Global Variables\7f403973
-Node: Constant Variables\7f405049
-Node: Local Variables\7f405675
-Node: Void Variables\7f410612
-Node: Defining Variables\7f414128
-Node: Accessing Variables\7f421292
-Node: Setting Variables\7f422717
-Node: Variable Scoping\7f427236
-Node: Scope\7f428835
-Node: Extent\7f430360
-Node: Impl of Scope\7f431839
-Node: Using Scoping\7f433802
-Node: Buffer-Local Variables\7f435324
-Node: Intro to Buffer-Local\7f436160
-Node: Creating Buffer-Local\7f438703
-Node: Default Value\7f444602
-Node: Variable Aliases\7f447745
-Node: Functions\7f449596
-Node: What Is a Function\7f450690
-Node: Lambda Expressions\7f454736
-Node: Lambda Components\7f455646
-Node: Simple Lambda\7f457478
-Node: Argument List\7f459135
-Node: Function Documentation\7f462863
-Node: Function Names\7f464805
-Node: Defining Functions\7f467378
-Node: Calling Functions\7f470418
-Node: Mapping Functions\7f474266
-Node: Anonymous Functions\7f476954
-Node: Function Cells\7f480199
-Node: Inline Functions\7f485017
-Node: Related Topics\7f486827
-Node: Macros\7f487880
-Node: Simple Macro\7f489164
-Node: Expansion\7f489899
-Node: Compiling Macros\7f492903
-Node: Defining Macros\7f494739
-Node: Backquote\7f496056
-Node: Problems with Macros\7f498453
-Node: Argument Evaluation\7f499148
-Node: Surprising Local Vars\7f502063
-Node: Eval During Expansion\7f504131
-Node: Repeated Expansion\7f505824
-Node: Customization\7f507740
-Node: Common Keywords\7f508209
-Node: Group Definitions\7f511054
-Node: Variable Definitions\7f513246
-Node: Customization Types\7f518236
-Node: Simple Types\7f519671
-Node: Composite Types\7f521828
-Node: Splicing into Lists\7f526518
-Node: Type Keywords\7f528353
-Node: Loading\7f531873
-Node: How Programs Do Loading\7f533548
-Node: Autoload\7f542674
-Node: Repeated Loading\7f548744
-Node: Named Features\7f550857
-Node: Unloading\7f557287
-Node: Hooks for Loading\7f559443
-Node: Byte Compilation\7f560160
-Node: Speed of Byte-Code\7f562077
-Node: Compilation Functions\7f563284
-Node: Docs and Compilation\7f569941
-Node: Dynamic Loading\7f572594
-Node: Eval During Compile\7f574958
-Node: Compiled-Function Objects\7f576223
-Node: Disassembly\7f581024
-Node: Debugging\7f588278
-Node: Debugger\7f589690
-Node: Error Debugging\7f590835
-Node: Infinite Loops\7f593588
-Node: Function Debugging\7f594832
-Node: Explicit Debug\7f597632
-Node: Using Debugger\7f598403
-Node: Debugger Commands\7f600265
-Node: Invoking the Debugger\7f604582
-Node: Internals of Debugger\7f608497
-Node: Syntax Errors\7f613384
-Node: Excess Open\7f614632
-Node: Excess Close\7f616507
-Node: Compilation Errors\7f617928
-Node: Edebug\7f619216
-Node: Using Edebug\7f621324
-Node: Instrumenting\7f624021
-Node: Edebug Execution Modes\7f627510
-Node: Jumping\7f630620
-Node: Edebug Misc\7f632963
-Node: Breakpoints\7f634352
-Node: Global Break Condition\7f637158
-Node: Embedded Breakpoints\7f638113
-Node: Trapping Errors\7f639068
-Node: Edebug Views\7f641144
-Node: Edebug Eval\7f643109
-Node: Eval List\7f644286
-Node: Reading in Edebug\7f647671
-Node: Printing in Edebug\7f648470
-Node: Tracing\7f650185
-Node: Coverage Testing\7f652073
-Node: The Outside Context\7f654114
-Node: Checking Whether to Stop\7f655063
-Node: Edebug Display Update\7f655710
-Node: Edebug Recursive Edit\7f657733
-Node: Instrumenting Macro Calls\7f659388
-Node: Specification List\7f661870
-Node: Backtracking\7f671281
-Node: Debugging Backquote\7f673219
-Node: Specification Examples\7f676925
-Node: Edebug Options\7f678992
-Node: Read and Print\7f684331
-Node: Streams Intro\7f685308
-Node: Input Streams\7f687326
-Node: Input Functions\7f692227
-Node: Output Streams\7f694287
-Node: Output Functions\7f698338
-Node: Output Variables\7f702638
-Node: Minibuffers\7f707439
-Node: Intro to Minibuffers\7f708591
-Node: Text from Minibuffer\7f710779
-Node: Object from Minibuffer\7f715873
-Node: Minibuffer History\7f719966
-Node: Completion\7f722945
-Node: Basic Completion\7f724920
-Node: Minibuffer Completion\7f729803
-Node: Completion Commands\7f733380
-Node: High-Level Completion\7f738037
-Node: Reading File Names\7f742786
-Node: Programmed Completion\7f746478
-Node: Yes-or-No Queries\7f748860
-Node: Multiple Queries\7f754597
-Node: Reading a Password\7f758664
-Node: Minibuffer Misc\7f760007
-Node: Command Loop\7f764887
-Node: Command Overview\7f766231
-Node: Defining Commands\7f769509
-Node: Using Interactive\7f770257
-Node: Interactive Codes\7f775030
-Node: Interactive Examples\7f780822
-Node: Interactive Call\7f782136
-Node: Command Loop Info\7f787551
-Node: Events\7f792530
-Node: Event Types\7f793991
-Node: Event Contents\7f795914
-Node: Event Predicates\7f800390
-Node: Accessing Mouse Event Positions\7f801708
-Node: Frame-Level Event Position Info\7f802407
-Node: Window-Level Event Position Info\7f803447
-Node: Event Text Position Info\7f805211
-Node: Event Glyph Position Info\7f807703
-Node: Event Toolbar Position Info\7f809026
-Node: Other Event Position Info\7f809697
-Node: Accessing Other Event Info\7f810106
-Node: Working With Events\7f811726
-Node: Converting Events\7f817727
-Node: Reading Input\7f821126
-Node: Key Sequence Input\7f822128
-Node: Reading One Event\7f824763
-Node: Dispatching an Event\7f827587
-Node: Quoted Character Input\7f828038
-Node: Peeking and Discarding\7f829386
-Node: Waiting\7f833290
-Node: Quitting\7f835604
-Node: Prefix Command Arguments\7f840012
-Node: Recursive Editing\7f845099
-Node: Disabling Commands\7f849894
-Node: Command History\7f851962
-Node: Keyboard Macros\7f853699
-Node: Keymaps\7f855916
-Node: Keymap Terminology\7f857493
-Node: Format of Keymaps\7f860422
-Node: Creating Keymaps\7f860833
-Node: Inheritance and Keymaps\7f862913
-Node: Key Sequences\7f865285
-Node: Prefix Keys\7f870081
-Node: Active Keymaps\7f873666
-Node: Key Lookup\7f883037
-Node: Functions for Key Lookup\7f888200
-Node: Changing Key Bindings\7f893901
-Node: Key Binding Commands\7f901063
-Node: Scanning Keymaps\7f903128
-Node: Other Keymap Functions\7f911696
-Node: Menus\7f912318
-Node: Menu Format\7f912910
-Node: Menubar Format\7f921556
-Node: Menubar\7f922181
-Node: Modifying Menus\7f925294
-Node: Menu Filters\7f930638
-Node: Pop-Up Menus\7f932534
-Node: Menu Accelerators\7f934862
-Node: Creating Menu Accelerators\7f935618
-Node: Keyboard Menu Traversal\7f936978
-Node: Menu Accelerator Functions\7f937705
-Node: Buffers Menu\7f940781
-Node: Dialog Boxes\7f942075
-Node: Dialog Box Format\7f942242
-Node: Dialog Box Functions\7f943667
-Node: Toolbar\7f944064
-Node: Toolbar Intro\7f944499
-Node: Creating Toolbar\7f946899
-Node: Toolbar Descriptor Format\7f947816
-Node: Specifying the Toolbar\7f952313
-Node: Other Toolbar Variables\7f955920
-Node: Gutter\7f960348
-Node: Gutter Intro\7f960937
-Node: Creating Gutter\7f962940
-Node: Gutter Descriptor Format\7f965827
-Node: Specifying a Gutter\7f970284
-Node: Other Gutter Variables\7f973819
-Node: Common Gutter Widgets\7f978206
-Node: Buffer Tabs\7f979198
-Node: Progress Bars\7f979339
-Node: Scrollbars\7f979484
-Node: Drag and Drop\7f979619
-Node: Supported Protocols\7f980695
-Node: OffiX DND\7f981198
-Node: CDE dt\7f982205
-Node: MSWindows OLE\7f982796
-Node: Loose ends\7f982967
-Node: Drop Interface\7f983359
-Node: Drag Interface\7f984381
-Node: Modes\7f984555
-Node: Major Modes\7f985506
-Node: Major Mode Conventions\7f988421
-Node: Example Major Modes\7f994376
-Node: Auto Major Mode\7f1002409
-Node: Mode Help\7f1009857
-Node: Derived Modes\7f1010958
-Node: Minor Modes\7f1013149
-Node: Minor Mode Conventions\7f1014451
-Node: Keymaps and Minor Modes\7f1017314
-Node: Modeline Format\7f1018149
-Node: Modeline Data\7f1019917
-Node: Modeline Variables\7f1025070
-Node: %-Constructs\7f1029786
-Node: Hooks\7f1032773
-Node: Documentation\7f1039533
-Node: Documentation Basics\7f1040956
-Node: Accessing Documentation\7f1044006
-Node: Keys in Documentation\7f1050287
-Node: Describing Characters\7f1053770
-Node: Help Functions\7f1056119
-Node: Obsoleteness\7f1062569
-Node: Files\7f1065561
-Node: Visiting Files\7f1067486
-Node: Visiting Functions\7f1068991
-Node: Subroutines of Visiting\7f1074149
-Node: Saving Buffers\7f1076222
-Node: Reading from Files\7f1082315
-Node: Writing to Files\7f1084476
-Node: File Locks\7f1087193
-Node: Information about Files\7f1090260
-Node: Testing Accessibility\7f1091021
-Node: Kinds of Files\7f1094761
-Node: Truenames\7f1096442
-Node: File Attributes\7f1097444
-Node: Changing File Attributes\7f1102583
-Node: File Names\7f1108005
-Node: File Name Components\7f1109578
-Node: Directory Names\7f1112023
-Node: Relative File Names\7f1115253
-Node: File Name Expansion\7f1116223
-Node: Unique File Names\7f1119977
-Node: File Name Completion\7f1121592
-Node: User Name Completion\7f1124860
-Node: Contents of Directories\7f1126267
-Node: Create/Delete Dirs\7f1129580
-Node: Magic File Names\7f1130686
-Node: Partial Files\7f1136334
-Node: Intro to Partial Files\7f1136562
-Node: Creating a Partial File\7f1137802
-Node: Detached Partial Files\7f1138738
-Node: Format Conversion\7f1139860
-Node: Files and MS-DOS\7f1145358
-Node: Backups and Auto-Saving\7f1147422
-Node: Backup Files\7f1148097
-Node: Making Backups\7f1149494
-Node: Rename or Copy\7f1152243
-Node: Numbered Backups\7f1154736
-Node: Backup Names\7f1156971
-Node: Auto-Saving\7f1160263
-Node: Reverting\7f1168424
-Node: Buffers\7f1171759
-Node: Buffer Basics\7f1173175
-Node: Current Buffer\7f1175228
-Node: Buffer Names\7f1179932
-Node: Buffer File Name\7f1183139
-Node: Buffer Modification\7f1187258
-Node: Modification Time\7f1189501
-Node: Read Only Buffers\7f1192876
-Node: The Buffer List\7f1196115
-Node: Creating Buffers\7f1200932
-Node: Killing Buffers\7f1203078
-Node: Indirect Buffers\7f1206910
-Node: Windows\7f1209484
-Node: Basic Windows\7f1210962
-Node: Splitting Windows\7f1214060
-Node: Deleting Windows\7f1219386
-Node: Selecting Windows\7f1223304
-Node: Cyclic Window Ordering\7f1227527
-Node: Buffers and Windows\7f1232682
-Node: Displaying Buffers\7f1234460
-Node: Choosing Window\7f1239799
-Node: Window Point\7f1247717
-Node: Window Start\7f1249787
-Node: Vertical Scrolling\7f1254586
-Node: Horizontal Scrolling\7f1260784
-Node: Size of Window\7f1264313
-Node: Position of Window\7f1269031
-Node: Resizing Windows\7f1271284
-Node: Window Configurations\7f1276722
-Node: Frames\7f1280219
-Node: Creating Frames\7f1282560
-Node: Frame Properties\7f1283900
-Node: Property Access\7f1284716
-Node: Initial Properties\7f1285623
-Node: X Frame Properties\7f1288109
-Node: Size and Position\7f1292743
-Node: Frame Name\7f1294741
-Node: Frame Titles\7f1295655
-Node: Deleting Frames\7f1297479
-Node: Finding All Frames\7f1298454
-Node: Frames and Windows\7f1301682
-Node: Minibuffers and Frames\7f1304464
-Node: Input Focus\7f1305382
-Node: Visibility of Frames\7f1308487
-Node: Raising and Lowering\7f1310477
-Node: Frame Configurations\7f1312853
-Node: Frame Hooks\7f1313910
-Node: Consoles and Devices\7f1315715
-Node: Basic Console Functions\7f1318458
-Node: Basic Device Functions\7f1318881
-Node: Console Types and Device Classes\7f1319727
-Node: Connecting to a Console or Device\7f1321994
-Node: The Selected Console and Device\7f1324178
-Node: Console and Device I/O\7f1325204
-Node: Positions\7f1325968
-Node: Point\7f1326937
-Node: Motion\7f1330027
-Node: Character Motion\7f1330794
-Node: Word Motion\7f1333031
-Node: Buffer End Motion\7f1334532
-Node: Text Lines\7f1336069
-Node: Screen Lines\7f1340970
-Node: List Motion\7f1345033
-Node: Skipping Characters\7f1348515
-Node: Excursions\7f1350734
-Node: Narrowing\7f1353774
-Node: Markers\7f1359105
-Node: Overview of Markers\7f1360011
-Node: Predicates on Markers\7f1364703
-Node: Creating Markers\7f1365949
-Node: Information from Markers\7f1370149
-Node: Changing Markers\7f1371247
-Node: The Mark\7f1372775
-Node: The Region\7f1381278
-Node: Text\7f1386964
-Node: Near Point\7f1389663
-Node: Buffer Contents\7f1393850
-Node: Comparing Text\7f1395256
-Node: Insertion\7f1396664
-Node: Commands for Insertion\7f1400574
-Node: Deletion\7f1403468
-Node: User-Level Deletion\7f1407062
-Node: The Kill Ring\7f1411222
-Node: Kill Ring Concepts\7f1413396
-Node: Kill Functions\7f1414450
-Node: Yank Commands\7f1416373
-Node: Low-Level Kill Ring\7f1418244
-Node: Internals of Kill Ring\7f1421330
-Node: Undo\7f1424110
-Node: Maintaining Undo\7f1428447
-Node: Filling\7f1431065
-Node: Margins\7f1437059
-Node: Auto Filling\7f1441082
-Node: Sorting\7f1442263
-Node: Columns\7f1451577
-Node: Indentation\7f1454658
-Node: Primitive Indent\7f1455437
-Node: Mode-Specific Indent\7f1456762
-Node: Region Indent\7f1459294
-Node: Relative Indent\7f1462241
-Node: Indent Tabs\7f1464623
-Node: Motion by Indent\7f1465944
-Node: Case Changes\7f1466723
-Node: Text Properties\7f1470076
-Node: Examining Properties\7f1471889
-Node: Changing Properties\7f1473772
-Node: Property Search\7f1477363
-Node: Special Properties\7f1482082
-Node: Saving Properties\7f1482363
-Node: Substitution\7f1485505
-Node: Registers\7f1488775
-Node: Transposition\7f1491358
-Node: Change Hooks\7f1492252
-Node: Transformations\7f1494292
-Node: Searching and Matching\7f1499396
-Node: String Search\7f1500527
-Node: Regular Expressions\7f1505508
-Node: Syntax of Regexps\7f1506875
-Node: Regexp Example\7f1521478
-Node: Regexp Search\7f1523648
-Node: POSIX Regexps\7f1529979
-Node: Search and Replace\7f1532056
-Node: Match Data\7f1535421
-Node: Simple Match Data\7f1536551
-Node: Replacing Match\7f1540816
-Node: Entire Match Data\7f1543497
-Node: Saving Match Data\7f1545735
-Node: Searching and Case\7f1547123
-Node: Standard Regexps\7f1549157
-Node: Syntax Tables\7f1551355
-Node: Syntax Basics\7f1552469
-Node: Syntax Descriptors\7f1555441
-Node: Syntax Class Table\7f1557291
-Node: Syntax Flags\7f1563329
-Node: Syntax Table Functions\7f1566546
-Node: Motion and Syntax\7f1570834
-Node: Parsing Expressions\7f1572286
-Node: Standard Syntax Tables\7f1578355
-Node: Syntax Table Internals\7f1579199
-Node: Abbrevs\7f1580225
-Node: Abbrev Mode\7f1582028
-Node: Abbrev Tables\7f1582748
-Node: Defining Abbrevs\7f1584287
-Node: Abbrev Files\7f1586208
-Node: Abbrev Expansion\7f1587991
-Node: Standard Abbrev Tables\7f1592622
-Node: Extents\7f1593781
-Node: Intro to Extents\7f1595024
-Node: Creating and Modifying Extents\7f1599016
-Node: Extent Endpoints\7f1600597
-Node: Finding Extents\7f1603860
-Node: Mapping Over Extents\7f1607982
-Node: Extent Properties\7f1614105
-Node: Detached Extents\7f1624266
-Node: Extent Parents\7f1626125
-Node: Duplicable Extents\7f1627819
-Node: Extents and Events\7f1631040
-Node: Atomic Extents\7f1632947
-Node: Specifiers\7f1633394
-Node: Introduction to Specifiers\7f1635507
-Node: Specifiers In-Depth\7f1637817
-Node: Specifier Instancing\7f1642729
-Node: Specifier Types\7f1645991
-Node: Adding Specifications\7f1651065
-Node: Retrieving Specifications\7f1660486
-Node: Specifier Tag Functions\7f1664231
-Node: Specifier Instancing Functions\7f1667465
-Node: Specifier Example\7f1670872
-Node: Creating Specifiers\7f1674028
-Node: Specifier Validation Functions\7f1678345
-Node: Other Specification Functions\7f1680731
-Node: Faces and Window-System Objects\7f1684552
-Node: Faces\7f1684876
-Node: Merging Faces\7f1686493
-Node: Basic Face Functions\7f1688454
-Node: Face Properties\7f1690602
-Node: Face Convenience Functions\7f1700875
-Node: Other Face Display Functions\7f1704095
-Node: Fonts\7f1704907
-Node: Font Specifiers\7f1705608
-Node: Font Instances\7f1706793
-Node: Font Instance Names\7f1707760
-Node: Font Instance Size\7f1708601
-Node: Font Instance Characteristics\7f1709887
-Node: Font Convenience Functions\7f1711065
-Node: Colors\7f1712355
-Node: Color Specifiers\7f1712795
-Node: Color Instances\7f1715155
-Node: Color Instance Properties\7f1715899
-Node: Color Convenience Functions\7f1716525
-Node: Glyphs\7f1717578
-Node: Glyph Functions\7f1719179
-Node: Creating Glyphs\7f1719586
-Node: Glyph Properties\7f1732226
-Node: Glyph Convenience Functions\7f1741393
-Node: Glyph Dimensions\7f1745340
-Node: Images\7f1746420
-Node: Image Specifiers\7f1746869
-Node: Image Instantiator Conversion\7f1762360
-Node: Image Instances\7f1763725
-Node: Image Instance Types\7f1764476
-Node: Image Instance Functions\7f1767241
-Node: Glyph Types\7f1774298
-Node: Mouse Pointer\7f1776070
-Node: Redisplay Glyphs\7f1779073
-Node: Subwindows\7f1780106
-Node: Annotations\7f1780349
-Node: Annotation Basics\7f1781365
-Node: Annotation Primitives\7f1785303
-Node: Annotation Properties\7f1786642
-Node: Locating Annotations\7f1789682
-Node: Margin Primitives\7f1790519
-Node: Annotation Hooks\7f1792413
-Node: Display\7f1793073
-Node: Refresh Screen\7f1794051
-Node: Truncation\7f1796245
-Node: The Echo Area\7f1798770
-Node: Warnings\7f1805207
-Node: Invisible Text\7f1809643
-Node: Selective Display\7f1812222
-Node: Overlay Arrow\7f1816348
-Node: Temporary Displays\7f1817701
-Node: Blinking\7f1821822
-Node: Usual Display\7f1824006
-Node: Display Tables\7f1826555
-Node: Display Table Format\7f1827359
-Node: Active Display Table\7f1828801
-Node: Character Descriptors\7f1832796
-Node: Beeping\7f1833553
-Node: Hash Tables\7f1838319
-Node: Introduction to Hash Tables\7f1838927
-Node: Working With Hash Tables\7f1845486
-Node: Weak Hash Tables\7f1846603
-Node: Range Tables\7f1848620
-Node: Introduction to Range Tables\7f1849309
-Node: Working With Range Tables\7f1849755
-Node: Databases\7f1850714
-Node: Connecting to a Database\7f1851013
-Node: Working With a Database\7f1852120
-Node: Other Database Functions\7f1852994
-Node: Processes\7f1853563
-Node: Subprocess Creation\7f1855787
-Node: Synchronous Processes\7f1859238
-Node: MS-DOS Subprocesses\7f1865960
-Node: Asynchronous Processes\7f1867034
-Node: Deleting Processes\7f1871391
-Node: Process Information\7f1873262
-Node: Input to Processes\7f1877354
-Node: Signals to Processes\7f1880049
-Node: Output from Processes\7f1884864
-Node: Process Buffers\7f1885676
-Node: Filter Functions\7f1888555
-Node: Accepting Output\7f1894146
-Node: Sentinels\7f1895673
-Node: Process Window Size\7f1899163
-Node: Transaction Queues\7f1899512
-Node: Network\7f1901210
-Node: System Interface\7f1903844
-Node: Starting Up\7f1905114
-Node: Start-up Summary\7f1905708
-Node: Init File\7f1909262
-Node: Terminal-Specific\7f1911643
-Node: Command Line Arguments\7f1914802
-Node: Getting Out\7f1918291
-Node: Killing XEmacs\7f1918860
-Node: Suspending XEmacs\7f1920528
-Node: System Environment\7f1923907
-Node: User Identification\7f1930088
-Node: Time of Day\7f1933617
-Node: Time Conversion\7f1936404
-Node: Timers\7f1941646
-Node: Terminal Input\7f1943819
-Node: Input Modes\7f1944322
-Node: Translating Input\7f1946781
-Node: Recording Input\7f1950946
-Node: Terminal Output\7f1953046
-Node: Flow Control\7f1956667
-Node: Batch Mode\7f1960629
-Node: X-Windows\7f1962011
-Node: X Selections\7f1962882
-Node: X Server\7f1965633
-Node: Resources\7f1966084
-Node: Server Data\7f1971395
-Node: Grabs\7f1972602
-Node: X Miscellaneous\7f1974182
-Node: ToolTalk Support\7f1976567
-Node: XEmacs ToolTalk API Summary\7f1976784
-Node: Sending Messages\7f1978084
-Node: Example of Sending Messages\7f1978335
-Node: Elisp Interface for Sending Messages\7f1979397
-Node: Receiving Messages\7f1985993
-Node: Example of Receiving Messages\7f1986216
-Node: Elisp Interface for Receiving Messages\7f1987052
-Node: LDAP Support\7f1990909
-Node: Building XEmacs with LDAP support\7f1991403
-Node: XEmacs LDAP API\7f1992380
-Node: LDAP Variables\7f1993432
-Node: The High-Level LDAP API\7f1996032
-Node: The Low-Level LDAP API\7f1999505
-Node: The LDAP Lisp Object\7f2000336
-Node: Opening and Closing a LDAP Connection\7f2000891
-Node: Low-level Operations on a LDAP Server\7f2002697
-Node: LDAP Internationalization\7f2005421
-Node: LDAP Internationalization Variables\7f2006326
-Node: Encoder/Decoder Functions\7f2008057
-Node: Syntax of Search Filters\7f2009094
-Node: PostgreSQL Support\7f2010392
-Node: Building XEmacs with PostgreSQL support\7f2010787
-Node: XEmacs PostgreSQL libpq API\7f2012134
-Node: libpq Lisp Variables\7f2014013
-Node: libpq Lisp Symbols and DataTypes\7f2016977
-Node: Synchronous Interface Functions\7f2030217
-Node: Asynchronous Interface Functions\7f2034708
-Node: Large Object Support\7f2038213
-Node: Other libpq Functions\7f2038840
-Node: Unimplemented libpq Functions\7f2041875
-Node: XEmacs PostgreSQL libpq Examples\7f2047194
-Node: Internationalization\7f2053285
-Node: I18N Levels 1 and 2\7f2053628
-Node: I18N Level 3\7f2054334
-Node: Level 3 Basics\7f2054615
-Node: Level 3 Primitives\7f2055448
-Node: Dynamic Messaging\7f2057054
-Node: Domain Specification\7f2057517
-Node: Documentation String Extraction\7f2059187
-Node: I18N Level 4\7f2060105
-Node: MULE\7f2060297
-Node: Internationalization Terminology\7f2061346
-Node: Charsets\7f2073545
-Node: Charset Properties\7f2074241
-Node: Basic Charset Functions\7f2078956
-Node: Charset Property Functions\7f2081137
-Node: Predefined Charsets\7f2083207
-Node: MULE Characters\7f2086127
-Node: Composite Characters\7f2087002
-Node: Coding Systems\7f2088269
-Node: Coding System Types\7f2090409
-Node: ISO 2022\7f2094393
-Node: EOL Conversion\7f2106668
-Node: Coding System Properties\7f2107840
-Node: Basic Coding System Functions\7f2112163
-Node: Coding System Property Functions\7f2114197
-Node: Encoding and Decoding Text\7f2114755
-Node: Detection of Textual Encoding\7f2115891
-Node: Big5 and Shift-JIS Functions\7f2117427
-Node: Predefined Coding Systems\7f2118579
-Node: CCL\7f2130673
-Node: CCL Syntax\7f2133777
-Node: CCL Statements\7f2135353
-Node: CCL Expressions\7f2140001
-Node: Calling CCL\7f2142540
-Node: CCL Examples\7f2145545
-Node: Category Tables\7f2145682
-Node: Tips\7f2148041
-Node: Style Tips\7f2148682
-Node: Compilation Tips\7f2158201
-Node: Documentation Tips\7f2160115
-Node: Comment Tips\7f2165624
-Node: Library Headers\7f2168626
-Node: Building XEmacs and Object Allocation\7f2172598
-Node: Building XEmacs\7f2173481
-Node: Pure Storage\7f2180059
-Node: Garbage Collection\7f2182847
-Node: Standard Errors\7f2193690
-Node: Standard Buffer-Local Variables\7f2197899
-Node: Standard Keymaps\7f2200532
-Node: Standard Hooks\7f2204266
-Node: Index\7f2211766
+Node: Copying\7f49116
+Node: Introduction\7f68274
+Node: Caveats\7f69865
+Node: Lisp History\7f71544
+Node: Conventions\7f72800
+Node: Some Terms\7f73615
+Node: nil and t\7f74336
+Node: Evaluation Notation\7f76013
+Node: Printing Notation\7f76926
+Node: Error Messages\7f77800
+Node: Buffer Text Notation\7f78241
+Node: Format of Descriptions\7f79116
+Node: A Sample Function Description\7f79970
+Node: A Sample Variable Description\7f83956
+Node: Acknowledgements\7f84864
+Node: Lisp Data Types\7f86842
+Node: Printed Representation\7f89397
+Node: Comments\7f91439
+Node: Primitive Types\7f92336
+Node: Programming Types\7f93995
+Node: Integer Type\7f95947
+Node: Floating Point Type\7f96984
+Node: Character Type\7f97603
+Node: Symbol Type\7f105507
+Node: Sequence Type\7f108202
+Node: Cons Cell Type\7f109721
+Node: Dotted Pair Notation\7f114205
+Node: Association List Type\7f116326
+Node: Array Type\7f117209
+Node: String Type\7f118675
+Node: Vector Type\7f121356
+Node: Bit Vector Type\7f122128
+Node: Function Type\7f122990
+Node: Macro Type\7f124103
+Node: Primitive Function Type\7f124800
+Node: Compiled-Function Type\7f126326
+Node: Autoload Type\7f126880
+Node: Char Table Type\7f127894
+Node: Hash Table Type\7f128068
+Node: Range Table Type\7f129223
+Node: Weak List Type\7f130076
+Node: Editing Types\7f130226
+Node: Buffer Type\7f131853
+Node: Marker Type\7f133880
+Node: Extent Type\7f134604
+Node: Window Type\7f135872
+Node: Frame Type\7f137283
+Node: Device Type\7f138078
+Node: Console Type\7f138904
+Node: Window Configuration Type\7f140105
+Node: Event Type\7f140803
+Node: Process Type\7f140967
+Node: Stream Type\7f142002
+Node: Keymap Type\7f143125
+Node: Syntax Table Type\7f143663
+Node: Display Table Type\7f144686
+Node: Database Type\7f145125
+Node: Charset Type\7f145291
+Node: Coding System Type\7f145455
+Node: ToolTalk Message Type\7f145639
+Node: ToolTalk Pattern Type\7f145838
+Node: Window-System Types\7f146010
+Node: Face Type\7f147156
+Node: Glyph Type\7f147287
+Node: Specifier Type\7f147443
+Node: Font Instance Type\7f147616
+Node: Color Instance Type\7f147806
+Node: Image Instance Type\7f148003
+Node: Toolbar Button Type\7f148201
+Node: Subwindow Type\7f148394
+Node: X Resource Type\7f148573
+Node: Type Predicates\7f148726
+Node: Equality Predicates\7f157855
+Node: Numbers\7f162666
+Node: Integer Basics\7f164121
+Node: Float Basics\7f166470
+Node: Predicates on Numbers\7f168212
+Node: Comparison of Numbers\7f169845
+Node: Numeric Conversions\7f173666
+Node: Arithmetic Operations\7f175132
+Node: Rounding Operations\7f181271
+Node: Bitwise Operations\7f182384
+Node: Math Functions\7f191430
+Node: Random Numbers\7f193963
+Node: Strings and Characters\7f195729
+Node: String Basics\7f197182
+Node: Predicates for Strings\7f199600
+Node: Creating Strings\7f200363
+Node: Predicates for Characters\7f205704
+Node: Character Codes\7f206775
+Node: Text Comparison\7f208195
+Node: String Conversion\7f211640
+Node: Modifying Strings\7f215310
+Node: String Properties\7f215951
+Node: Formatting Strings\7f216596
+Node: Character Case\7f226214
+Node: Case Tables\7f229768
+Node: Char Tables\7f233739
+Node: Char Table Types\7f235131
+Node: Working With Char Tables\7f236716
+Node: Lists\7f238733
+Node: Cons Cells\7f239856
+Node: Lists as Boxes\7f241192
+Node: List-related Predicates\7f243834
+Node: List Elements\7f245536
+Node: Building Lists\7f250565
+Node: Modifying Lists\7f256557
+Node: Setcar\7f257369
+Node: Setcdr\7f259800
+Node: Rearrangement\7f262321
+Node: Sets And Lists\7f267907
+Node: Association Lists\7f272135
+Ref: Association Lists-Footnote-1\7f281426
+Node: Property Lists\7f281631
+Node: Working With Normal Plists\7f283179
+Node: Working With Lax Plists\7f285516
+Node: Converting Plists To/From Alists\7f287796
+Node: Weak Lists\7f289144
+Node: Sequences Arrays Vectors\7f291307
+Node: Sequence Functions\7f293943
+Node: Arrays\7f297602
+Node: Array Functions\7f300666
+Node: Vectors\7f303199
+Node: Vector Functions\7f304697
+Node: Bit Vectors\7f307268
+Node: Bit Vector Functions\7f308113
+Node: Symbols\7f310412
+Node: Symbol Components\7f311461
+Node: Definitions\7f315644
+Node: Creating Symbols\7f317869
+Node: Symbol Properties\7f324903
+Node: Plists and Alists\7f326430
+Node: Object Plists\7f328179
+Node: Other Plists\7f330939
+Node: Evaluation\7f332738
+Node: Intro Eval\7f333543
+Ref: Intro Eval-Footnote-1\7f336896
+Node: Eval\7f337031
+Node: Forms\7f341449
+Node: Self-Evaluating Forms\7f342608
+Node: Symbol Forms\7f344121
+Node: Classifying Lists\7f345038
+Node: Function Indirection\7f345794
+Node: Function Forms\7f348893
+Node: Macro Forms\7f349890
+Node: Special Forms\7f351490
+Node: Autoloading\7f353799
+Node: Quoting\7f354297
+Node: Control Structures\7f355658
+Node: Sequencing\7f357278
+Node: Conditionals\7f360143
+Node: Combining Conditions\7f363566
+Node: Iteration\7f366836
+Node: Nonlocal Exits\7f368615
+Node: Catch and Throw\7f369317
+Node: Examples of Catch\7f373156
+Node: Errors\7f375175
+Node: Signaling Errors\7f376664
+Node: Processing of Errors\7f385411
+Node: Handling Errors\7f387690
+Node: Error Symbols\7f394931
+Node: Cleanups\7f398887
+Node: Variables\7f402665
+Node: Global Variables\7f404434
+Node: Constant Variables\7f405510
+Node: Local Variables\7f406136
+Node: Void Variables\7f411073
+Node: Defining Variables\7f414589
+Node: Accessing Variables\7f421753
+Node: Setting Variables\7f423178
+Node: Variable Scoping\7f427697
+Node: Scope\7f429296
+Node: Extent\7f430821
+Node: Impl of Scope\7f432300
+Node: Using Scoping\7f434263
+Node: Buffer-Local Variables\7f435785
+Node: Intro to Buffer-Local\7f436621
+Node: Creating Buffer-Local\7f439164
+Node: Default Value\7f445063
+Node: Variable Aliases\7f448206
+Node: Functions\7f450057
+Node: What Is a Function\7f451151
+Node: Lambda Expressions\7f455197
+Node: Lambda Components\7f456107
+Node: Simple Lambda\7f457939
+Node: Argument List\7f459596
+Node: Function Documentation\7f463324
+Node: Function Names\7f465266
+Node: Defining Functions\7f467839
+Node: Calling Functions\7f470879
+Node: Mapping Functions\7f474727
+Node: Anonymous Functions\7f477415
+Node: Function Cells\7f480660
+Node: Inline Functions\7f485478
+Node: Related Topics\7f487288
+Node: Macros\7f488341
+Node: Simple Macro\7f489625
+Node: Expansion\7f490360
+Node: Compiling Macros\7f493364
+Node: Defining Macros\7f495200
+Node: Backquote\7f496517
+Node: Problems with Macros\7f498914
+Node: Argument Evaluation\7f499609
+Node: Surprising Local Vars\7f502524
+Node: Eval During Expansion\7f504592
+Node: Repeated Expansion\7f506285
+Node: Customization\7f508201
+Node: Common Keywords\7f508670
+Node: Group Definitions\7f511515
+Node: Variable Definitions\7f513707
+Node: Customization Types\7f518697
+Node: Simple Types\7f520132
+Node: Composite Types\7f522289
+Node: Splicing into Lists\7f526979
+Node: Type Keywords\7f528814
+Node: Loading\7f532334
+Node: How Programs Do Loading\7f534009
+Node: Autoload\7f543135
+Node: Repeated Loading\7f549205
+Node: Named Features\7f551318
+Node: Unloading\7f557748
+Node: Hooks for Loading\7f559904
+Node: Byte Compilation\7f560621
+Node: Speed of Byte-Code\7f562614
+Node: Compilation Functions\7f563821
+Node: Docs and Compilation\7f570478
+Node: Dynamic Loading\7f573131
+Node: Eval During Compile\7f575495
+Node: Compiled-Function Objects\7f576760
+Node: Disassembly\7f581561
+Node: Different Behavior\7f588842
+Node: Debugging\7f590187
+Node: Debugger\7f591599
+Node: Error Debugging\7f592744
+Node: Infinite Loops\7f595497
+Node: Function Debugging\7f596741
+Node: Explicit Debug\7f599541
+Node: Using Debugger\7f600312
+Node: Debugger Commands\7f602174
+Node: Invoking the Debugger\7f606491
+Node: Internals of Debugger\7f610406
+Node: Syntax Errors\7f615293
+Node: Excess Open\7f616541
+Node: Excess Close\7f618416
+Node: Compilation Errors\7f619837
+Node: Edebug\7f621125
+Node: Using Edebug\7f623233
+Node: Instrumenting\7f625930
+Node: Edebug Execution Modes\7f629419
+Node: Jumping\7f632529
+Node: Edebug Misc\7f634872
+Node: Breakpoints\7f636261
+Node: Global Break Condition\7f639067
+Node: Embedded Breakpoints\7f640022
+Node: Trapping Errors\7f640977
+Node: Edebug Views\7f643053
+Node: Edebug Eval\7f645018
+Node: Eval List\7f646195
+Node: Reading in Edebug\7f649580
+Node: Printing in Edebug\7f650379
+Node: Tracing\7f652094
+Node: Coverage Testing\7f653982
+Node: The Outside Context\7f656023
+Node: Checking Whether to Stop\7f656972
+Node: Edebug Display Update\7f657619
+Node: Edebug Recursive Edit\7f659642
+Node: Instrumenting Macro Calls\7f661297
+Node: Specification List\7f663779
+Node: Backtracking\7f673190
+Node: Debugging Backquote\7f675128
+Node: Specification Examples\7f678834
+Node: Edebug Options\7f680901
+Node: Read and Print\7f686240
+Node: Streams Intro\7f687217
+Node: Input Streams\7f689235
+Node: Input Functions\7f694136
+Node: Output Streams\7f696196
+Node: Output Functions\7f700247
+Node: Output Variables\7f704547
+Node: Minibuffers\7f709348
+Node: Intro to Minibuffers\7f710500
+Node: Text from Minibuffer\7f712688
+Node: Object from Minibuffer\7f717782
+Node: Minibuffer History\7f721875
+Node: Completion\7f724854
+Node: Basic Completion\7f726829
+Node: Minibuffer Completion\7f731712
+Node: Completion Commands\7f735289
+Node: High-Level Completion\7f739946
+Node: Reading File Names\7f744695
+Node: Programmed Completion\7f748387
+Node: Yes-or-No Queries\7f750769
+Node: Multiple Queries\7f756506
+Node: Reading a Password\7f760573
+Node: Minibuffer Misc\7f761916
+Node: Command Loop\7f766796
+Node: Command Overview\7f768140
+Node: Defining Commands\7f771418
+Node: Using Interactive\7f772166
+Node: Interactive Codes\7f776939
+Node: Interactive Examples\7f782731
+Node: Interactive Call\7f784045
+Node: Command Loop Info\7f789460
+Node: Events\7f794439
+Node: Event Types\7f795900
+Node: Event Contents\7f797823
+Node: Event Predicates\7f802299
+Node: Accessing Mouse Event Positions\7f803617
+Node: Frame-Level Event Position Info\7f804316
+Node: Window-Level Event Position Info\7f805356
+Node: Event Text Position Info\7f807120
+Node: Event Glyph Position Info\7f809612
+Node: Event Toolbar Position Info\7f810935
+Node: Other Event Position Info\7f811606
+Node: Accessing Other Event Info\7f812015
+Node: Working With Events\7f813635
+Node: Converting Events\7f819636
+Node: Reading Input\7f823035
+Node: Key Sequence Input\7f824037
+Node: Reading One Event\7f826672
+Node: Dispatching an Event\7f829496
+Node: Quoted Character Input\7f829947
+Node: Peeking and Discarding\7f831295
+Node: Waiting\7f835199
+Node: Quitting\7f837513
+Node: Prefix Command Arguments\7f841921
+Node: Recursive Editing\7f847008
+Node: Disabling Commands\7f851803
+Node: Command History\7f853871
+Node: Keyboard Macros\7f855608
+Node: Keymaps\7f857825
+Node: Keymap Terminology\7f859402
+Node: Format of Keymaps\7f862331
+Node: Creating Keymaps\7f862742
+Node: Inheritance and Keymaps\7f864822
+Node: Key Sequences\7f867194
+Node: Prefix Keys\7f871990
+Node: Active Keymaps\7f875575
+Node: Key Lookup\7f884946
+Node: Functions for Key Lookup\7f890109
+Node: Changing Key Bindings\7f895810
+Node: Key Binding Commands\7f902972
+Node: Scanning Keymaps\7f905037
+Node: Other Keymap Functions\7f913606
+Node: Menus\7f914228
+Node: Menu Format\7f914820
+Node: Menubar Format\7f923466
+Node: Menubar\7f924091
+Node: Modifying Menus\7f927204
+Node: Menu Filters\7f932548
+Node: Pop-Up Menus\7f934444
+Node: Menu Accelerators\7f936772
+Node: Creating Menu Accelerators\7f937528
+Node: Keyboard Menu Traversal\7f938888
+Node: Menu Accelerator Functions\7f939615
+Node: Buffers Menu\7f942691
+Node: Dialog Boxes\7f943985
+Node: Dialog Box Format\7f944152
+Node: Dialog Box Functions\7f945577
+Node: Toolbar\7f945974
+Node: Toolbar Intro\7f946409
+Node: Creating Toolbar\7f948809
+Node: Toolbar Descriptor Format\7f949726
+Node: Specifying the Toolbar\7f954223
+Node: Other Toolbar Variables\7f957830
+Node: Gutter\7f962258
+Node: Gutter Intro\7f962847
+Node: Creating Gutter\7f964850
+Node: Gutter Descriptor Format\7f967737
+Node: Specifying a Gutter\7f972194
+Node: Other Gutter Variables\7f975729
+Node: Common Gutter Widgets\7f980116
+Node: Buffer Tabs\7f981108
+Node: Progress Bars\7f981249
+Node: Scrollbars\7f981394
+Node: Drag and Drop\7f981529
+Node: Supported Protocols\7f982605
+Node: OffiX DND\7f983108
+Node: CDE dt\7f984115
+Node: MSWindows OLE\7f984706
+Node: Loose ends\7f984877
+Node: Drop Interface\7f985269
+Node: Drag Interface\7f986291
+Node: Modes\7f986465
+Node: Major Modes\7f987416
+Node: Major Mode Conventions\7f990331
+Node: Example Major Modes\7f996286
+Node: Auto Major Mode\7f1004319
+Node: Mode Help\7f1011769
+Node: Derived Modes\7f1012870
+Node: Minor Modes\7f1015061
+Node: Minor Mode Conventions\7f1016363
+Node: Keymaps and Minor Modes\7f1019226
+Node: Modeline Format\7f1020061
+Node: Modeline Data\7f1021829
+Node: Modeline Variables\7f1026982
+Node: %-Constructs\7f1031698
+Node: Hooks\7f1034685
+Node: Documentation\7f1041445
+Node: Documentation Basics\7f1042868
+Node: Accessing Documentation\7f1045919
+Node: Keys in Documentation\7f1052200
+Node: Describing Characters\7f1055683
+Node: Help Functions\7f1058032
+Node: Obsoleteness\7f1064482
+Node: Files\7f1067474
+Node: Visiting Files\7f1069399
+Node: Visiting Functions\7f1070904
+Node: Subroutines of Visiting\7f1076062
+Node: Saving Buffers\7f1078135
+Node: Reading from Files\7f1084228
+Node: Writing to Files\7f1086389
+Node: File Locks\7f1089106
+Node: Information about Files\7f1092173
+Node: Testing Accessibility\7f1092934
+Node: Kinds of Files\7f1096674
+Node: Truenames\7f1098355
+Node: File Attributes\7f1099357
+Node: Changing File Attributes\7f1104496
+Node: File Names\7f1109918
+Node: File Name Components\7f1111491
+Node: Directory Names\7f1113936
+Node: Relative File Names\7f1117166
+Node: File Name Expansion\7f1118136
+Node: Unique File Names\7f1121890
+Node: File Name Completion\7f1123505
+Node: User Name Completion\7f1126773
+Node: Contents of Directories\7f1128180
+Node: Create/Delete Dirs\7f1131493
+Node: Magic File Names\7f1132599
+Node: Partial Files\7f1138247
+Node: Intro to Partial Files\7f1138475
+Node: Creating a Partial File\7f1139715
+Node: Detached Partial Files\7f1140651
+Node: Format Conversion\7f1141773
+Node: Files and MS-DOS\7f1147271
+Node: Backups and Auto-Saving\7f1149335
+Node: Backup Files\7f1150010
+Node: Making Backups\7f1151407
+Node: Rename or Copy\7f1154156
+Node: Numbered Backups\7f1156649
+Node: Backup Names\7f1158884
+Node: Auto-Saving\7f1162176
+Node: Reverting\7f1170338
+Node: Buffers\7f1173674
+Node: Buffer Basics\7f1175090
+Node: Current Buffer\7f1177143
+Node: Buffer Names\7f1181847
+Node: Buffer File Name\7f1185054
+Node: Buffer Modification\7f1189173
+Node: Modification Time\7f1191416
+Node: Read Only Buffers\7f1194791
+Node: The Buffer List\7f1198030
+Node: Creating Buffers\7f1202847
+Node: Killing Buffers\7f1204993
+Node: Indirect Buffers\7f1208825
+Node: Windows\7f1211399
+Node: Basic Windows\7f1212877
+Node: Splitting Windows\7f1215975
+Node: Deleting Windows\7f1221301
+Node: Selecting Windows\7f1225219
+Node: Cyclic Window Ordering\7f1229442
+Node: Buffers and Windows\7f1234597
+Node: Displaying Buffers\7f1236375
+Node: Choosing Window\7f1241714
+Node: Window Point\7f1249632
+Node: Window Start\7f1251702
+Node: Vertical Scrolling\7f1256501
+Node: Horizontal Scrolling\7f1262699
+Node: Size of Window\7f1266228
+Node: Position of Window\7f1270946
+Node: Resizing Windows\7f1273199
+Node: Window Configurations\7f1278637
+Node: Frames\7f1282134
+Node: Creating Frames\7f1284475
+Node: Frame Properties\7f1285815
+Node: Property Access\7f1286631
+Node: Initial Properties\7f1287538
+Node: X Frame Properties\7f1290024
+Node: Size and Position\7f1294658
+Node: Frame Name\7f1296656
+Node: Frame Titles\7f1297570
+Node: Deleting Frames\7f1299394
+Node: Finding All Frames\7f1300369
+Node: Frames and Windows\7f1303597
+Node: Minibuffers and Frames\7f1306379
+Node: Input Focus\7f1307297
+Node: Visibility of Frames\7f1310402
+Node: Raising and Lowering\7f1312392
+Node: Frame Configurations\7f1314768
+Node: Frame Hooks\7f1315825
+Node: Consoles and Devices\7f1317630
+Node: Basic Console Functions\7f1320373
+Node: Basic Device Functions\7f1320796
+Node: Console Types and Device Classes\7f1321642
+Node: Connecting to a Console or Device\7f1323909
+Node: The Selected Console and Device\7f1326093
+Node: Console and Device I/O\7f1327119
+Node: Positions\7f1327883
+Node: Point\7f1328852
+Node: Motion\7f1331942
+Node: Character Motion\7f1332709
+Node: Word Motion\7f1334946
+Node: Buffer End Motion\7f1336336
+Node: Text Lines\7f1337873
+Node: Screen Lines\7f1342774
+Node: List Motion\7f1346837
+Node: Skipping Characters\7f1350320
+Node: Excursions\7f1352539
+Node: Narrowing\7f1355579
+Node: Markers\7f1360910
+Node: Overview of Markers\7f1361816
+Node: Predicates on Markers\7f1366508
+Node: Creating Markers\7f1367754
+Node: Information from Markers\7f1371954
+Node: Changing Markers\7f1373052
+Node: The Mark\7f1374580
+Node: The Region\7f1383083
+Node: Text\7f1388769
+Node: Near Point\7f1391468
+Node: Buffer Contents\7f1395655
+Node: Comparing Text\7f1397061
+Node: Insertion\7f1398469
+Node: Commands for Insertion\7f1402379
+Node: Deletion\7f1405273
+Node: User-Level Deletion\7f1408923
+Node: The Kill Ring\7f1413083
+Node: Kill Ring Concepts\7f1415257
+Node: Kill Functions\7f1416311
+Node: Yank Commands\7f1418234
+Node: Low-Level Kill Ring\7f1420105
+Node: Internals of Kill Ring\7f1423191
+Node: Undo\7f1425971
+Node: Maintaining Undo\7f1430308
+Node: Filling\7f1432926
+Node: Margins\7f1438920
+Node: Auto Filling\7f1442943
+Node: Sorting\7f1444124
+Node: Columns\7f1453438
+Node: Indentation\7f1456519
+Node: Primitive Indent\7f1457298
+Node: Mode-Specific Indent\7f1458623
+Node: Region Indent\7f1461155
+Node: Relative Indent\7f1464102
+Node: Indent Tabs\7f1466484
+Node: Motion by Indent\7f1467805
+Node: Case Changes\7f1468584
+Node: Text Properties\7f1471937
+Node: Examining Properties\7f1473750
+Node: Changing Properties\7f1475633
+Node: Property Search\7f1479224
+Node: Special Properties\7f1483943
+Node: Saving Properties\7f1484224
+Node: Substitution\7f1487366
+Node: Registers\7f1490636
+Node: Transposition\7f1493219
+Node: Change Hooks\7f1494113
+Node: Transformations\7f1496153
+Node: Searching and Matching\7f1501257
+Node: String Search\7f1502388
+Node: Regular Expressions\7f1507369
+Node: Syntax of Regexps\7f1508736
+Node: Regexp Example\7f1523339
+Node: Regexp Search\7f1525509
+Node: POSIX Regexps\7f1531846
+Node: Search and Replace\7f1533923
+Node: Match Data\7f1537288
+Node: Simple Match Data\7f1538418
+Node: Replacing Match\7f1542683
+Node: Entire Match Data\7f1545364
+Node: Saving Match Data\7f1547602
+Node: Searching and Case\7f1548990
+Node: Standard Regexps\7f1551024
+Node: Syntax Tables\7f1553222
+Node: Syntax Basics\7f1554336
+Node: Syntax Descriptors\7f1557308
+Node: Syntax Class Table\7f1559158
+Node: Syntax Flags\7f1565196
+Node: Syntax Table Functions\7f1568413
+Node: Motion and Syntax\7f1572701
+Node: Parsing Expressions\7f1574153
+Node: Standard Syntax Tables\7f1580251
+Node: Syntax Table Internals\7f1581095
+Node: Abbrevs\7f1582121
+Node: Abbrev Mode\7f1583925
+Node: Abbrev Tables\7f1584645
+Node: Defining Abbrevs\7f1586184
+Node: Abbrev Files\7f1588105
+Node: Abbrev Expansion\7f1589888
+Node: Standard Abbrev Tables\7f1594519
+Node: Extents\7f1595678
+Node: Intro to Extents\7f1596921
+Node: Creating and Modifying Extents\7f1600913
+Node: Extent Endpoints\7f1602494
+Node: Finding Extents\7f1605757
+Node: Mapping Over Extents\7f1609879
+Node: Extent Properties\7f1616002
+Node: Detached Extents\7f1626163
+Node: Extent Parents\7f1628022
+Node: Duplicable Extents\7f1629716
+Node: Extents and Events\7f1632937
+Node: Atomic Extents\7f1634844
+Node: Specifiers\7f1635291
+Node: Introduction to Specifiers\7f1637404
+Node: Specifiers In-Depth\7f1639714
+Node: Specifier Instancing\7f1644626
+Node: Specifier Types\7f1647888
+Node: Adding Specifications\7f1652962
+Node: Retrieving Specifications\7f1662383
+Node: Specifier Tag Functions\7f1666128
+Node: Specifier Instancing Functions\7f1669362
+Node: Specifier Example\7f1672769
+Node: Creating Specifiers\7f1675925
+Node: Specifier Validation Functions\7f1680242
+Node: Other Specification Functions\7f1682628
+Node: Faces and Window-System Objects\7f1686449
+Node: Faces\7f1686773
+Node: Merging Faces\7f1688390
+Node: Basic Face Functions\7f1690351
+Node: Face Properties\7f1692499
+Node: Face Convenience Functions\7f1702772
+Node: Other Face Display Functions\7f1705992
+Node: Fonts\7f1706804
+Node: Font Specifiers\7f1707505
+Node: Font Instances\7f1708690
+Node: Font Instance Names\7f1709657
+Node: Font Instance Size\7f1710498
+Node: Font Instance Characteristics\7f1711784
+Node: Font Convenience Functions\7f1712962
+Node: Colors\7f1714252
+Node: Color Specifiers\7f1714692
+Node: Color Instances\7f1717052
+Node: Color Instance Properties\7f1717796
+Node: Color Convenience Functions\7f1718422
+Node: Glyphs\7f1719475
+Node: Glyph Functions\7f1721076
+Node: Creating Glyphs\7f1721483
+Node: Glyph Properties\7f1734123
+Node: Glyph Convenience Functions\7f1743290
+Node: Glyph Dimensions\7f1747237
+Node: Images\7f1748317
+Node: Image Specifiers\7f1748766
+Node: Image Instantiator Conversion\7f1764257
+Node: Image Instances\7f1765622
+Node: Image Instance Types\7f1766373
+Node: Image Instance Functions\7f1769138
+Node: Glyph Types\7f1776195
+Node: Mouse Pointer\7f1777967
+Node: Redisplay Glyphs\7f1780970
+Node: Subwindows\7f1782003
+Node: Annotations\7f1782246
+Node: Annotation Basics\7f1783262
+Node: Annotation Primitives\7f1787200
+Node: Annotation Properties\7f1788539
+Node: Locating Annotations\7f1791579
+Node: Margin Primitives\7f1792416
+Node: Annotation Hooks\7f1794310
+Node: Display\7f1794970
+Node: Refresh Screen\7f1795948
+Node: Truncation\7f1798142
+Node: The Echo Area\7f1800667
+Node: Warnings\7f1807110
+Node: Invisible Text\7f1811546
+Node: Selective Display\7f1814125
+Node: Overlay Arrow\7f1818251
+Node: Temporary Displays\7f1819604
+Node: Blinking\7f1823725
+Node: Usual Display\7f1825909
+Node: Display Tables\7f1828458
+Node: Display Table Format\7f1829262
+Node: Active Display Table\7f1830704
+Node: Character Descriptors\7f1834699
+Node: Beeping\7f1835456
+Node: Hash Tables\7f1840222
+Node: Introduction to Hash Tables\7f1840830
+Node: Working With Hash Tables\7f1847389
+Node: Weak Hash Tables\7f1848506
+Node: Range Tables\7f1850523
+Node: Introduction to Range Tables\7f1851212
+Node: Working With Range Tables\7f1851658
+Node: Databases\7f1852617
+Node: Connecting to a Database\7f1852916
+Node: Working With a Database\7f1854023
+Node: Other Database Functions\7f1854897
+Node: Processes\7f1855466
+Node: Subprocess Creation\7f1857690
+Node: Synchronous Processes\7f1861141
+Node: MS-DOS Subprocesses\7f1867863
+Node: Asynchronous Processes\7f1868937
+Node: Deleting Processes\7f1873294
+Node: Process Information\7f1875165
+Node: Input to Processes\7f1879257
+Node: Signals to Processes\7f1881952
+Node: Output from Processes\7f1886767
+Node: Process Buffers\7f1887579
+Node: Filter Functions\7f1890458
+Node: Accepting Output\7f1896049
+Node: Sentinels\7f1897576
+Node: Process Window Size\7f1901066
+Node: Transaction Queues\7f1901415
+Node: Network\7f1903113
+Node: System Interface\7f1905747
+Node: Starting Up\7f1907017
+Node: Start-up Summary\7f1907611
+Node: Init File\7f1911165
+Node: Terminal-Specific\7f1913546
+Node: Command Line Arguments\7f1916705
+Node: Getting Out\7f1920194
+Node: Killing XEmacs\7f1920763
+Node: Suspending XEmacs\7f1922431
+Node: System Environment\7f1925810
+Node: User Identification\7f1931991
+Node: Time of Day\7f1935520
+Node: Time Conversion\7f1938307
+Node: Timers\7f1943549
+Node: Terminal Input\7f1945722
+Node: Input Modes\7f1946225
+Node: Translating Input\7f1948684
+Node: Recording Input\7f1952849
+Node: Terminal Output\7f1954949
+Node: Flow Control\7f1958570
+Node: Batch Mode\7f1962532
+Node: X-Windows\7f1963914
+Node: X Selections\7f1964785
+Node: X Server\7f1967536
+Node: Resources\7f1967987
+Node: Server Data\7f1973298
+Node: Grabs\7f1974505
+Node: X Miscellaneous\7f1976085
+Node: ToolTalk Support\7f1978470
+Node: XEmacs ToolTalk API Summary\7f1978687
+Node: Sending Messages\7f1979987
+Node: Example of Sending Messages\7f1980238
+Node: Elisp Interface for Sending Messages\7f1981300
+Node: Receiving Messages\7f1987896
+Node: Example of Receiving Messages\7f1988119
+Node: Elisp Interface for Receiving Messages\7f1988955
+Node: LDAP Support\7f1992812
+Node: Building XEmacs with LDAP support\7f1993306
+Node: XEmacs LDAP API\7f1994283
+Node: LDAP Variables\7f1995335
+Node: The High-Level LDAP API\7f1997935
+Node: The Low-Level LDAP API\7f2001408
+Node: The LDAP Lisp Object\7f2002239
+Node: Opening and Closing a LDAP Connection\7f2002794
+Node: Low-level Operations on a LDAP Server\7f2004600
+Node: LDAP Internationalization\7f2007324
+Node: LDAP Internationalization Variables\7f2008229
+Node: Encoder/Decoder Functions\7f2009960
+Node: Syntax of Search Filters\7f2010997
+Node: PostgreSQL Support\7f2012295
+Node: Building XEmacs with PostgreSQL support\7f2012690
+Node: XEmacs PostgreSQL libpq API\7f2014037
+Node: libpq Lisp Variables\7f2015916
+Node: libpq Lisp Symbols and DataTypes\7f2018880
+Node: Synchronous Interface Functions\7f2032120
+Node: Asynchronous Interface Functions\7f2036611
+Node: Large Object Support\7f2040116
+Node: Other libpq Functions\7f2040743
+Node: Unimplemented libpq Functions\7f2043778
+Node: XEmacs PostgreSQL libpq Examples\7f2049097
+Node: Internationalization\7f2055188
+Node: I18N Levels 1 and 2\7f2055531
+Node: I18N Level 3\7f2056237
+Node: Level 3 Basics\7f2056518
+Node: Level 3 Primitives\7f2057351
+Node: Dynamic Messaging\7f2058957
+Node: Domain Specification\7f2059420
+Node: Documentation String Extraction\7f2061090
+Node: I18N Level 4\7f2062008
+Node: MULE\7f2062200
+Node: Internationalization Terminology\7f2063249
+Node: Charsets\7f2075448
+Node: Charset Properties\7f2076144
+Node: Basic Charset Functions\7f2080859
+Node: Charset Property Functions\7f2083040
+Node: Predefined Charsets\7f2085110
+Node: MULE Characters\7f2088030
+Node: Composite Characters\7f2088905
+Node: Coding Systems\7f2090172
+Node: Coding System Types\7f2092312
+Node: ISO 2022\7f2096296
+Node: EOL Conversion\7f2108571
+Node: Coding System Properties\7f2109743
+Node: Basic Coding System Functions\7f2114066
+Node: Coding System Property Functions\7f2116100
+Node: Encoding and Decoding Text\7f2116658
+Node: Detection of Textual Encoding\7f2117794
+Node: Big5 and Shift-JIS Functions\7f2119330
+Node: Predefined Coding Systems\7f2120482
+Node: CCL\7f2132576
+Node: CCL Syntax\7f2135680
+Node: CCL Statements\7f2137256
+Node: CCL Expressions\7f2141904
+Node: Calling CCL\7f2144443
+Node: CCL Examples\7f2147448
+Node: Category Tables\7f2147585
+Node: Tips\7f2149944
+Node: Style Tips\7f2150585
+Node: Compilation Tips\7f2160104
+Node: Documentation Tips\7f2162018
+Node: Comment Tips\7f2167527
+Node: Library Headers\7f2170530
+Node: Building XEmacs and Object Allocation\7f2174502
+Node: Building XEmacs\7f2175385
+Node: Pure Storage\7f2181963
+Node: Garbage Collection\7f2184751
+Node: Standard Errors\7f2195594
+Node: Standard Buffer-Local Variables\7f2199803
+Node: Standard Keymaps\7f2202438
+Node: Standard Hooks\7f2206172
+Node: Index\7f2213672
\1f
End Tag Table
Byte Compilation
-* Compilation Functions:: Byte compilation functions.
-* Disassembly:: Disassembling byte-code; how to read byte-code.
+* Speed of Byte-Code:: An example of speedup from byte compilation.
+* Compilation Functions:: Byte compilation functions.
+* Docs and Compilation:: Dynamic loading of documentation strings.
+* Dynamic Loading:: Dynamic loading of individual functions.
+* Eval During Compile:: Code to be evaluated when you compile.
+* Compiled-Function Objects:: The data type used for byte-compiled functions.
+* Disassembly:: Disassembling byte-code; how to read byte-code.
+* Different Behavior:: When compiled code gives different results.
Debugging Lisp Programs
* Eval During Compile:: Code to be evaluated when you compile.
* Compiled-Function Objects:: The data type used for byte-compiled functions.
* Disassembly:: Disassembling byte-code; how to read byte-code.
+* Different Behavior:: When compiled code gives different results.
\1f
File: lispref.info, Node: Speed of Byte-Code, Next: Compilation Functions, Up: Byte Compilation
Foundation instead of in the original English.
\1f
-File: lispref.info, Node: Disassembly, Prev: Compiled-Function Objects, Up: Byte Compilation
+File: lispref.info, Node: Disassembly, Next: Different Behavior, Prev: Compiled-Function Objects, Up: Byte Compilation
Disassembled Byte-Code
======================
=> nil
\1f
+File: lispref.info, Node: Different Behavior, Prev: Disassembly, Up: Byte Compilation
+
+Different Behavior
+==================
+
+ The intent is that compiled byte-code and the corresponding code
+executed by the Lisp interpreter produce identical results. However,
+there are some circumstances where the results will differ.
+
+ * Arithmetic operations may be rearranged for efficiency or
+ compile-time evaluation. When floating point numbers are
+ involved, this may produce different values or an overflow.
+
+ * Some arithmetic operations may be optimized away. For example, the
+ expression `(+ x)' may be optimized to simply `x'. If the value
+ of `x' is a marker, then the value will be a marker instead of an
+ integer. If the value of `x' is a cons cell, then the interpreter
+ will issue an error, while the bytecode will not.
+
+ If you're trying to use `(+ OBJECT 0)' to convert OBJECT to
+ integer, consider using an explicit conversion function, which is
+ clearer and guaranteed to work. Instead of `(+ MARKER 0)', use
+ `(marker-position MARKER)'. Instead of `(+ CHAR 0)', use
+ `(char-int CHAR)'.
+
+ For maximal equivalence between interpreted and compiled code, the
+variables `byte-compile-delete-errors' and `byte-compile-optimize' can
+be set to `nil', but this is not recommended.
+
+\1f
File: lispref.info, Node: Debugging, Next: Read and Print, Prev: Byte Compilation, Up: Top
Debugging Lisp Programs
See *Note Edebug Eval:: for other evaluation functions available
inside of Edebug.
-\1f
-File: lispref.info, Node: Edebug Execution Modes, Next: Jumping, Prev: Instrumenting, Up: Edebug
-
-Edebug Execution Modes
-----------------------
-
- Edebug supports several execution modes for running the program you
-are debugging. We call these alternatives "Edebug execution modes"; do
-not confuse them with major or minor modes. The current Edebug
-execution mode determines how Edebug displays the progress of the
-evaluation, whether it stops at each stop point, or continues to the
-next breakpoint, for example.
-
- Normally, you specify the Edebug execution mode by typing a command
-to continue the program in a certain mode. Here is a table of these
-commands. All except for `S' resume execution of the program, at least
-for a certain distance.
-
-`S'
- Stop: don't execute any more of the program for now, just wait for
- more Edebug commands (`edebug-stop').
-
-`<SPC>'
- Step: stop at the next stop point encountered (`edebug-step-mode').
-
-`n'
- Next: stop at the next stop point encountered after an expression
- (`edebug-next-mode'). Also see `edebug-forward-sexp' in *Note
- Edebug Misc::.
-
-`t'
- Trace: pause one second at each Edebug stop point
- (`edebug-trace-mode').
-
-`T'
- Rapid trace: update at each stop point, but don't actually pause
- (`edebug-Trace-fast-mode').
-
-`g'
- Go: run until the next breakpoint (`edebug-go-mode'). *Note
- Breakpoints::.
-
-`c'
- Continue: pause for one second at each breakpoint, but don't stop
- (`edebug-continue-mode').
-
-`C'
- Rapid continue: update at each breakpoint, but don't actually pause
- (`edebug-Continue-fast-mode').
-
-`G'
- Go non-stop: ignore breakpoints (`edebug-Go-nonstop-mode'). You
- can still stop the program by hitting any key.
-
- In general, the execution modes earlier in the above list run the
-program more slowly or stop sooner.
-
- When you enter a new Edebug level, the initial execution mode comes
-from the value of the variable `edebug-initial-mode'. By default, this
-specifies `step' mode. Note that you may reenter the same Edebug level
-several times if, for example, an instrumented function is called
-several times from one command.
-
- While executing or tracing, you can interrupt the execution by typing
-any Edebug command. Edebug stops the program at the next stop point and
-then executes the command that you typed. For example, typing `t'
-during execution switches to trace mode at the next stop point. You can
-use `S' to stop execution without doing anything else.
-
- If your function happens to read input, a character you hit
-intending to interrupt execution may be read by the function instead.
-You can avoid such unintended results by paying attention to when your
-program wants input.
-
- Keyboard macros containing Edebug commands do not work; when you exit
-from Edebug, to resume the program, whether you are defining or
-executing a keyboard macro is forgotten. Also, defining or executing a
-keyboard macro outside of Edebug does not affect the command loop inside
-Edebug. This is usually an advantage. But see
-`edebug-continue-kbd-macro'.
-
Foundation instead of in the original English.
\1f
+File: lispref.info, Node: Edebug Execution Modes, Next: Jumping, Prev: Instrumenting, Up: Edebug
+
+Edebug Execution Modes
+----------------------
+
+ Edebug supports several execution modes for running the program you
+are debugging. We call these alternatives "Edebug execution modes"; do
+not confuse them with major or minor modes. The current Edebug
+execution mode determines how Edebug displays the progress of the
+evaluation, whether it stops at each stop point, or continues to the
+next breakpoint, for example.
+
+ Normally, you specify the Edebug execution mode by typing a command
+to continue the program in a certain mode. Here is a table of these
+commands. All except for `S' resume execution of the program, at least
+for a certain distance.
+
+`S'
+ Stop: don't execute any more of the program for now, just wait for
+ more Edebug commands (`edebug-stop').
+
+`<SPC>'
+ Step: stop at the next stop point encountered (`edebug-step-mode').
+
+`n'
+ Next: stop at the next stop point encountered after an expression
+ (`edebug-next-mode'). Also see `edebug-forward-sexp' in *Note
+ Edebug Misc::.
+
+`t'
+ Trace: pause one second at each Edebug stop point
+ (`edebug-trace-mode').
+
+`T'
+ Rapid trace: update at each stop point, but don't actually pause
+ (`edebug-Trace-fast-mode').
+
+`g'
+ Go: run until the next breakpoint (`edebug-go-mode'). *Note
+ Breakpoints::.
+
+`c'
+ Continue: pause for one second at each breakpoint, but don't stop
+ (`edebug-continue-mode').
+
+`C'
+ Rapid continue: update at each breakpoint, but don't actually pause
+ (`edebug-Continue-fast-mode').
+
+`G'
+ Go non-stop: ignore breakpoints (`edebug-Go-nonstop-mode'). You
+ can still stop the program by hitting any key.
+
+ In general, the execution modes earlier in the above list run the
+program more slowly or stop sooner.
+
+ When you enter a new Edebug level, the initial execution mode comes
+from the value of the variable `edebug-initial-mode'. By default, this
+specifies `step' mode. Note that you may reenter the same Edebug level
+several times if, for example, an instrumented function is called
+several times from one command.
+
+ While executing or tracing, you can interrupt the execution by typing
+any Edebug command. Edebug stops the program at the next stop point and
+then executes the command that you typed. For example, typing `t'
+during execution switches to trace mode at the next stop point. You can
+use `S' to stop execution without doing anything else.
+
+ If your function happens to read input, a character you hit
+intending to interrupt execution may be read by the function instead.
+You can avoid such unintended results by paying attention to when your
+program wants input.
+
+ Keyboard macros containing Edebug commands do not work; when you exit
+from Edebug, to resume the program, whether you are defining or
+executing a keyboard macro is forgotten. Also, defining or executing a
+keyboard macro outside of Edebug does not affect the command loop inside
+Edebug. This is usually an advantage. But see
+`edebug-continue-kbd-macro'.
+
+\1f
File: lispref.info, Node: Jumping, Next: Edebug Misc, Prev: Edebug Execution Modes, Up: Edebug
Jumping
while debugging such expressions, but it would slow Edebug down to
always do this.
-\1f
-File: lispref.info, Node: Specification Examples, Prev: Debugging Backquote, Up: Instrumenting Macro Calls
-
-Specification Examples
-......................
-
- Here we provide several examples of Edebug specifications to show
-many of its capabilities.
-
- A `let' special form has a sequence of bindings and a body. Each of
-the bindings is either a symbol or a sublist with a symbol and optional
-value. In the specification below, notice the `gate' inside of the
-sublist to prevent backtracking.
-
- (def-edebug-spec let
- ((&rest
- &or symbolp (gate symbolp &optional form))
- body))
-
- Edebug uses the following specifications for `defun' and `defmacro'
-and the associated argument list and `interactive' specifications. It
-is necessary to handle the expression argument of an interactive form
-specially since it is actually evaluated outside of the function body.
-
- (def-edebug-spec defmacro defun) ; Indirect ref to `defun' spec
- (def-edebug-spec defun
- (&define name lambda-list
- [&optional stringp] ; Match the doc string, if present.
- [&optional ("interactive" interactive)]
- def-body))
-
- (def-edebug-spec lambda-list
- (([&rest arg]
- [&optional ["&optional" arg &rest arg]]
- &optional ["&rest" arg]
- )))
-
- (def-edebug-spec interactive
- (&optional &or stringp def-form)) ; Notice: `def-form'
-
- The specification for backquote below illustrates how to match
-dotted lists and use `nil' to terminate recursion. It also illustrates
-how components of a vector may be matched. (The actual specification
-provided by Edebug does not support dotted lists because doing so
-causes very deep recursion that could fail.)
-
- (def-edebug-spec ` (backquote-form)) ;; alias just for clarity
-
- (def-edebug-spec backquote-form
- (&or ([&or "," ",@"] &or ("quote" backquote-form) form)
- (backquote-form . [&or nil backquote-form])
- (vector &rest backquote-form)
- sexp))
-
Foundation instead of in the original English.
\1f
+File: lispref.info, Node: Specification Examples, Prev: Debugging Backquote, Up: Instrumenting Macro Calls
+
+Specification Examples
+......................
+
+ Here we provide several examples of Edebug specifications to show
+many of its capabilities.
+
+ A `let' special form has a sequence of bindings and a body. Each of
+the bindings is either a symbol or a sublist with a symbol and optional
+value. In the specification below, notice the `gate' inside of the
+sublist to prevent backtracking.
+
+ (def-edebug-spec let
+ ((&rest
+ &or symbolp (gate symbolp &optional form))
+ body))
+
+ Edebug uses the following specifications for `defun' and `defmacro'
+and the associated argument list and `interactive' specifications. It
+is necessary to handle the expression argument of an interactive form
+specially since it is actually evaluated outside of the function body.
+
+ (def-edebug-spec defmacro defun) ; Indirect ref to `defun' spec
+ (def-edebug-spec defun
+ (&define name lambda-list
+ [&optional stringp] ; Match the doc string, if present.
+ [&optional ("interactive" interactive)]
+ def-body))
+
+ (def-edebug-spec lambda-list
+ (([&rest arg]
+ [&optional ["&optional" arg &rest arg]]
+ &optional ["&rest" arg]
+ )))
+
+ (def-edebug-spec interactive
+ (&optional &or stringp def-form)) ; Notice: `def-form'
+
+ The specification for backquote below illustrates how to match
+dotted lists and use `nil' to terminate recursion. It also illustrates
+how components of a vector may be matched. (The actual specification
+provided by Edebug does not support dotted lists because doing so
+causes very deep recursion that could fail.)
+
+ (def-edebug-spec ` (backquote-form)) ;; alias just for clarity
+
+ (def-edebug-spec backquote-form
+ (&or ([&or "," ",@"] &or ("quote" backquote-form) form)
+ (backquote-form . [&or nil backquote-form])
+ (vector &rest backquote-form)
+ sexp))
+
+\1f
File: lispref.info, Node: Edebug Options, Prev: Instrumenting Macro Calls, Up: Edebug
Edebug Options
indirect keymap bindings. This makes it possible to search for an
indirect definition itself.
- This function is used by `where-is' (*note Help: (emacs)Help.).
+ This function is used by `where-is' (*note Help: (xemacs)Help.).
(where-is-internal 'describe-function)
=> ([(control h) d] [(control h) f] [f1 d] [f1 f])
If you run `normal-mode' interactively, the argument FIND-FILE is
normally `nil'. In this case, `normal-mode' unconditionally
processes any local variables list. *Note Local Variables in
- Files: (emacs)File variables, for the syntax of the local
+ Files: (xemacs)File variables, for the syntax of the local
variables section of a file.
`normal-mode' uses `condition-case' around the call to the major
value of a local variable. However, this function does not look
for the `mode:' local variable near the end of a file; the
`hack-local-variables' function does that. *Note How Major Modes
- are Chosen: (emacs)Choosing Modes.
+ are Chosen: (xemacs)Choosing Modes.
- User Option: default-major-mode
This variable holds the default major mode for new buffers. The
this is transparent to the user.
For information on the uses of documentation strings, see *Note
-Help: (emacs)Help.
+Help: (xemacs)Help.
The `emacs/lib-src' directory contains two utilities that you can
use to print nice-looking hardcopy for the file
called "auto-saving". Auto-saving prevents you from losing more than a
limited amount of work if the system crashes. By default, auto-saves
happen every 300 keystrokes, or after around 30 seconds of idle time.
-*Note Auto-Save: (emacs)Auto-Save, for information on auto-save for
+*Note Auto-Save: (xemacs)Auto-Save, for information on auto-save for
users. Here we describe the functions used to implement auto-saving
and the variables that control them.
If you have made extensive changes to a file and then change your
mind about them, you can get rid of them by reading in the previous
version of the file with the `revert-buffer' command. *Note Reverting
-a Buffer: (emacs)Reverting.
+a Buffer: (xemacs)Reverting.
- Command: revert-buffer &optional check-auto-save noconfirm
preserve-modes
These functions for parsing words use the syntax table to decide
whether a given character is part of a word. *Note Syntax Tables::.
- - Command: forward-word count &optional buffer
+ - Command: forward-word &optional count buffer
This function moves point forward COUNT words (or backward if
COUNT is negative). Normally it returns `t'. If this motion
encounters the beginning or end of the buffer, or the limits of the
accessible portion when narrowing is in effect, point stops there
- and the value is `nil'. BUFFER defaults to the current buffer if
- omitted.
+ and the value is `nil'.
+
+ COUNT defaults to `1' and BUFFER defaults to the current buffer.
In an interactive call, COUNT is set to the numeric prefix
argument.
- - Command: backward-word count &optional buffer
+ - Command: backward-word &optional count buffer
This function is just like `forward-word', except that it moves
backward until encountering the front of a word, rather than
forward. BUFFER defaults to the current buffer if omitted.
In an interactive call, COUNT is set to the numeric prefix
argument.
- This function is rarely used in programs, as it is more efficient
- to call `forward-word' with a negative argument.
-
- Variable: words-include-escapes
This variable affects the behavior of `forward-word' and everything
that uses it. If it is non-`nil', then characters in the "escape"
The value returned is the window line number point has moved to,
with the top line in the window numbered 0.
+\1f
+File: lispref.info, Node: List Motion, Next: Skipping Characters, Prev: Screen Lines, Up: Motion
+
+Moving over Balanced Expressions
+--------------------------------
+
+ Here are several functions concerned with balanced-parenthesis
+expressions (also called "sexps" in connection with moving across them
+in XEmacs). The syntax table controls how these functions interpret
+various characters; see *Note Syntax Tables::. *Note Parsing
+Expressions::, for lower-level primitives for scanning sexps or parts of
+sexps. For user-level commands, see *Note Lists and Sexps:
+(xemacs)Lists and Sexps.
+
+ - Command: forward-list &optional arg
+ This function moves forward across ARG balanced groups of
+ parentheses. (Other syntactic entities such as words or paired
+ string quotes are ignored.) ARG defaults to 1 if omitted. If ARG
+ is negative, move backward across that many groups of parentheses.
+
+ - Command: backward-list &optional count
+ This function moves backward across COUNT balanced groups of
+ parentheses. (Other syntactic entities such as words or paired
+ string quotes are ignored.) COUNT defaults to 1 if omitted. If
+ COUNT is negative, move forward across that many groups of
+ parentheses.
+
+ - Command: up-list &optional count
+ This function moves forward out of COUNT levels of parentheses. A
+ negative argument means move backward but still to a less deep
+ spot.
+
+ - Command: down-list &optional count
+ This function moves forward into COUNT levels of parentheses. A
+ negative argument means move backward but still go deeper in
+ parentheses (-COUNT levels).
+
+ - Command: forward-sexp &optional count
+ This function moves forward across COUNT balanced expressions.
+ Balanced expressions include both those delimited by parentheses
+ and other kinds, such as words and string constants. COUNT
+ defaults to 1 if omitted. If COUNT is negative, move backward
+ across that many balanced expressions. For example,
+
+ ---------- Buffer: foo ----------
+ (concat-!- "foo " (car x) y z)
+ ---------- Buffer: foo ----------
+
+ (forward-sexp 3)
+ => nil
+
+ ---------- Buffer: foo ----------
+ (concat "foo " (car x) y-!- z)
+ ---------- Buffer: foo ----------
+
+ - Command: backward-sexp &optional count
+ This function moves backward across COUNT balanced expressions.
+ COUNT defaults to 1 if omitted. If COUNT is negative, move
+ forward across that many balanced expressions.
+
+ - Command: beginning-of-defun &optional count
+ This function moves back to the COUNTth beginning of a defun. If
+ COUNT is negative, this actually moves forward, but it still moves
+ to the beginning of a defun, not to the end of one. COUNT
+ defaults to 1 if omitted.
+
+ - Command: end-of-defun &optional count
+ This function moves forward to the COUNTth end of a defun. If
+ COUNT is negative, this actually moves backward, but it still
+ moves to the end of a defun, not to the beginning of one. COUNT
+ defaults to 1 if omitted.
+
+ - User Option: defun-prompt-regexp
+ If non-`nil', this variable holds a regular expression that
+ specifies what text can appear before the open-parenthesis that
+ starts a defun. That is to say, a defun begins on a line that
+ starts with a match for this regular expression, followed by a
+ character with open-parenthesis syntax.
+
Foundation instead of in the original English.
\1f
-File: lispref.info, Node: List Motion, Next: Skipping Characters, Prev: Screen Lines, Up: Motion
-
-Moving over Balanced Expressions
---------------------------------
-
- Here are several functions concerned with balanced-parenthesis
-expressions (also called "sexps" in connection with moving across them
-in XEmacs). The syntax table controls how these functions interpret
-various characters; see *Note Syntax Tables::. *Note Parsing
-Expressions::, for lower-level primitives for scanning sexps or parts of
-sexps. For user-level commands, see *Note Lists and Sexps:
-(emacs)Lists and Sexps.
-
- - Command: forward-list &optional arg
- This function moves forward across ARG balanced groups of
- parentheses. (Other syntactic entities such as words or paired
- string quotes are ignored.) ARG defaults to 1 if omitted. If ARG
- is negative, move backward across that many groups of parentheses.
-
- - Command: backward-list &optional count
- This function moves backward across COUNT balanced groups of
- parentheses. (Other syntactic entities such as words or paired
- string quotes are ignored.) COUNT defaults to 1 if omitted. If
- COUNT is negative, move forward across that many groups of
- parentheses.
-
- - Command: up-list &optional count
- This function moves forward out of COUNT levels of parentheses. A
- negative argument means move backward but still to a less deep
- spot.
-
- - Command: down-list &optional count
- This function moves forward into COUNT levels of parentheses. A
- negative argument means move backward but still go deeper in
- parentheses (-COUNT levels).
-
- - Command: forward-sexp &optional count
- This function moves forward across COUNT balanced expressions.
- Balanced expressions include both those delimited by parentheses
- and other kinds, such as words and string constants. COUNT
- defaults to 1 if omitted. If COUNT is negative, move backward
- across that many balanced expressions. For example,
-
- ---------- Buffer: foo ----------
- (concat-!- "foo " (car x) y z)
- ---------- Buffer: foo ----------
-
- (forward-sexp 3)
- => nil
-
- ---------- Buffer: foo ----------
- (concat "foo " (car x) y-!- z)
- ---------- Buffer: foo ----------
-
- - Command: backward-sexp &optional count
- This function moves backward across COUNT balanced expressions.
- COUNT defaults to 1 if omitted. If COUNT is negative, move
- forward across that many balanced expressions.
-
- - Command: beginning-of-defun &optional count
- This function moves back to the COUNTth beginning of a defun. If
- COUNT is negative, this actually moves forward, but it still moves
- to the beginning of a defun, not to the end of one. COUNT
- defaults to 1 if omitted.
-
- - Command: end-of-defun &optional count
- This function moves forward to the COUNTth end of a defun. If
- COUNT is negative, this actually moves backward, but it still
- moves to the end of a defun, not to the beginning of one. COUNT
- defaults to 1 if omitted.
-
- - User Option: defun-prompt-regexp
- If non-`nil', this variable holds a regular expression that
- specifies what text can appear before the open-parenthesis that
- starts a defun. That is to say, a defun begins on a line that
- starts with a match for this regular expression, followed by a
- character with open-parenthesis syntax.
-
-\1f
File: lispref.info, Node: Skipping Characters, Prev: List Motion, Up: Motion
Skipping Characters
The end of the buffer (or of its accessible portion) is always
considered the end of a line.
+\1f
+File: lispref.info, Node: Buffer Contents, Next: Comparing Text, Prev: Near Point, Up: Text
+
+Examining Buffer Contents
+=========================
+
+ This section describes two functions that allow a Lisp program to
+convert any portion of the text in the buffer into a string.
+
+ - Function: buffer-substring start end &optional buffer
+ - Function: buffer-string start end &optional buffer
+ These functions are equivalent and return a string containing a
+ copy of the text of the region defined by positions START and END
+ in the buffer. If the arguments are not positions in the
+ accessible portion of the buffer, `buffer-substring' signals an
+ `args-out-of-range' error. If optional argument BUFFER is `nil',
+ the current buffer is assumed.
+
+ If the region delineated by START and END contains duplicable
+ extents, they will be remembered in the string. *Note Duplicable
+ Extents::.
+
+ It is not necessary for START to be less than END; the arguments
+ can be given in either order. But most often the smaller argument
+ is written first.
+
+ ---------- Buffer: foo ----------
+ This is the contents of buffer foo
+
+ ---------- Buffer: foo ----------
+
+ (buffer-substring 1 10)
+ => "This is t"
+ (buffer-substring (point-max) 10)
+ => "he contents of buffer foo
+ "
+
+\1f
+File: lispref.info, Node: Comparing Text, Next: Insertion, Prev: Buffer Contents, Up: Text
+
+Comparing Text
+==============
+
+ This function lets you compare portions of the text in a buffer,
+without copying them into strings first.
+
+ - Function: compare-buffer-substrings buffer1 start1 end1 buffer2
+ start2 end2
+ This function lets you compare two substrings of the same buffer
+ or two different buffers. The first three arguments specify one
+ substring, giving a buffer and two positions within the buffer.
+ The last three arguments specify the other substring in the same
+ way. You can use `nil' for BUFFER1, BUFFER2, or both to stand for
+ the current buffer.
+
+ The value is negative if the first substring is less, positive if
+ the first is greater, and zero if they are equal. The absolute
+ value of the result is one plus the index of the first differing
+ characters within the substrings.
+
+ This function ignores case when comparing characters if
+ `case-fold-search' is non-`nil'. It always ignores text
+ properties.
+
+ Suppose the current buffer contains the text `foobarbar
+ haha!rara!'; then in this example the two substrings are `rbar '
+ and `rara!'. The value is 2 because the first substring is greater
+ at the second character.
+
+ (compare-buffer-substring nil 6 11 nil 16 21)
+ => 2
+
Foundation instead of in the original English.
\1f
-File: lispref.info, Node: Buffer Contents, Next: Comparing Text, Prev: Near Point, Up: Text
-
-Examining Buffer Contents
-=========================
-
- This section describes two functions that allow a Lisp program to
-convert any portion of the text in the buffer into a string.
-
- - Function: buffer-substring start end &optional buffer
- - Function: buffer-string start end &optional buffer
- These functions are equivalent and return a string containing a
- copy of the text of the region defined by positions START and END
- in the buffer. If the arguments are not positions in the
- accessible portion of the buffer, `buffer-substring' signals an
- `args-out-of-range' error. If optional argument BUFFER is `nil',
- the current buffer is assumed.
-
- If the region delineated by START and END contains duplicable
- extents, they will be remembered in the string. *Note Duplicable
- Extents::.
-
- It is not necessary for START to be less than END; the arguments
- can be given in either order. But most often the smaller argument
- is written first.
-
- ---------- Buffer: foo ----------
- This is the contents of buffer foo
-
- ---------- Buffer: foo ----------
-
- (buffer-substring 1 10)
- => "This is t"
- (buffer-substring (point-max) 10)
- => "he contents of buffer foo
- "
-
-\1f
-File: lispref.info, Node: Comparing Text, Next: Insertion, Prev: Buffer Contents, Up: Text
-
-Comparing Text
-==============
-
- This function lets you compare portions of the text in a buffer,
-without copying them into strings first.
-
- - Function: compare-buffer-substrings buffer1 start1 end1 buffer2
- start2 end2
- This function lets you compare two substrings of the same buffer
- or two different buffers. The first three arguments specify one
- substring, giving a buffer and two positions within the buffer.
- The last three arguments specify the other substring in the same
- way. You can use `nil' for BUFFER1, BUFFER2, or both to stand for
- the current buffer.
-
- The value is negative if the first substring is less, positive if
- the first is greater, and zero if they are equal. The absolute
- value of the result is one plus the index of the first differing
- characters within the substrings.
-
- This function ignores case when comparing characters if
- `case-fold-search' is non-`nil'. It always ignores text
- properties.
-
- Suppose the current buffer contains the text `foobarbar
- haha!rara!'; then in this example the two substrings are `rbar '
- and `rara!'. The value is 2 because the first substring is greater
- at the second character.
-
- (compare-buffer-substring nil 6 11 nil 16 21)
- => 2
-
-\1f
File: lispref.info, Node: Insertion, Next: Commands for Insertion, Prev: Comparing Text, Up: Text
Inserting Text
START and END. The value is `nil'. If optional argument BUFFER
is `nil', the current buffer is assumed.
- - Command: delete-char count &optional killp
+ - Command: delete-char &optional count killp
This command deletes COUNT characters directly after point, or
- before point if COUNT is negative. If KILLP is non-`nil', then it
- saves the deleted characters in the kill ring.
+ before point if COUNT is negative. COUNT defaults to `1'. If
+ KILLP is non-`nil', then it saves the deleted characters in the
+ kill ring.
In an interactive call, COUNT is the numeric prefix argument, and
KILLP is the unprocessed prefix argument. Therefore, if a prefix
The value returned is always `nil'.
- - Command: delete-backward-char count &optional killp
+ - Command: delete-backward-char &optional count killp
This command deletes COUNT characters directly before point, or
- after point if COUNT is negative. If KILLP is non-`nil', then it
- saves the deleted characters in the kill ring.
+ after point if COUNT is negative. COUNT defaults to 1. If KILLP
+ is non-`nil', then it saves the deleted characters in the kill
+ ring.
In an interactive call, COUNT is the numeric prefix argument, and
KILLP is the unprocessed prefix argument. Therefore, if a prefix
In XEmacs, you can search for the next match for a regexp either
incrementally or not. Incremental search commands are described in the
-`The XEmacs Reference Manual'. *Note Regular Expression Search:
-(emacs)Regexp Search. Here we describe only the search functions
+`The XEmacs Lisp Reference Manual'. *Note Regular Expression Search:
+(xemacs)Regexp Search. Here we describe only the search functions
useful in programs. The principal one is `re-search-forward'.
- Command: re-search-forward regexp &optional limit noerror count
You can use `forward-comment' to move forward or backward over one
comment or several comments.
- - Function: forward-comment count &optional buffer
+ - Function: forward-comment &optional count buffer
This function moves point forward across COUNT comments (backward,
if COUNT is negative). If it finds anything other than a comment
or whitespace, it stops, leaving point at the place where it
- stopped. It also stops after satisfying COUNT.
+ stopped. It also stops after satisfying COUNT. COUNT defaults to
+ `1'.
Optional argument BUFFER defaults to the current buffer.
*Note Creating Symbols::.
For the user-level commands for abbrevs, see *Note Abbrev Mode:
-(emacs)Abbrevs.
+(xemacs)Abbrevs.
* Menu:
`message' primitive, and for echoing keystrokes. It is not the same as
the minibuffer, despite the fact that the minibuffer appears (when
active) in the same place on the screen as the echo area. The `XEmacs
-Reference Manual' specifies the rules for resolving conflicts between
-the echo area and the minibuffer for use of that screen space (*note
-The Minibuffer: (emacs)Minibuffer.). Error messages appear in the echo
-area; see *Note Errors::.
+Lisp Reference Manual' specifies the rules for resolving conflicts
+between the echo area and the minibuffer for use of that screen space
+(*note The Minibuffer: (xemacs)Minibuffer.). Error messages appear in
+the echo area; see *Note Errors::.
You can write output in the echo area by using the Lisp printing
functions with `t' as the stream (*note Output Functions::), or as
The indentation commands of the Lisp modes in XEmacs, such as `M-;'
(`indent-for-comment') and <TAB> (`lisp-indent-line') automatically
indent comments according to these conventions, depending on the number
-of semicolons. *Note Manipulating Comments: (emacs)Comments.
+of semicolons. *Note Manipulating Comments: (xemacs)Comments.
\1f
File: lispref.info, Node: Library Headers, Prev: Comment Tips, Up: Tips
*note Usual Display::
`comment-column'
- *note Comments: (emacs)Comments.
+ *note Comments: (xemacs)Comments.
`default-directory'
*note System Environment::
*note Auto Filling::
`goal-column'
- *note Moving Point: (emacs)Moving Point.
+ *note Moving Point: (xemacs)Moving Point.
`left-margin'
*note Indentation::
Because this symbol is the variable which holds the name of the file
being visited in the current buffer, the value cell contents we see are
-the name of the source file of this chapter of the XEmacs Lisp Manual.
-The property list cell contains the list `(variable-documentation
-29529)' which tells the documentation functions where to find the
-documentation string for the variable `buffer-file-name' in the `DOC'
-file. (29529 is the offset from the beginning of the `DOC' file to
-where that documentation string begins.) The function cell contains
-the function for returning the name of the file. `buffer-file-name'
-names a primitive function, which has no read syntax and prints in hash
-notation (*note Primitive Function Type::). A symbol naming a function
-written in Lisp would have a lambda expression (or a byte-code object)
-in this cell.
+the name of the source file of this chapter of the XEmacs Lisp Reference
+Manual. The property list cell contains the list
+`(variable-documentation 29529)' which tells the documentation
+functions where to find the documentation string for the variable
+`buffer-file-name' in the `DOC' file. (29529 is the offset from the
+beginning of the `DOC' file to where that documentation string begins.)
+The function cell contains the function for returning the name of the
+file. `buffer-file-name' names a primitive function, which has no read
+syntax and prints in hash notation (*note Primitive Function Type::). A
+symbol naming a function written in Lisp would have a lambda expression
+(or a byte-code object) in this cell.
\1f
File: lispref.info, Node: Definitions, Next: Creating Symbols, Prev: Symbol Components, Up: Symbols
texinfo.info-2: 48703
texinfo.info-3: 96677
texinfo.info-4: 146069
-texinfo.info-5: 196042
-texinfo.info-6: 245134
-texinfo.info-7: 293729
-texinfo.info-8: 343544
-texinfo.info-9: 392857
-texinfo.info-10: 435235
-texinfo.info-11: 481351
-texinfo.info-12: 519511
+texinfo.info-5: 196054
+texinfo.info-6: 245146
+texinfo.info-7: 293741
+texinfo.info-8: 343556
+texinfo.info-9: 392869
+texinfo.info-10: 435247
+texinfo.info-11: 481363
+texinfo.info-12: 519523
\1f
Tag Table:
(Indirect)
Node: Less Cluttered Menu Entry\7f168360
Node: Menu Example\7f168985
Node: Other Info Files\7f170506
-Node: Cross References\7f172362
-Node: References\7f173319
-Node: Cross Reference Commands\7f175066
-Node: Cross Reference Parts\7f176125
-Node: xref\7f178961
-Node: Reference Syntax\7f179760
-Node: One Argument\7f181414
-Node: Two Arguments\7f182426
-Node: Three Arguments\7f183541
-Node: Four and Five Arguments\7f185932
-Node: Top Node Naming\7f188344
-Node: ref\7f189354
-Node: pxref\7f190744
-Node: inforef\7f193126
-Node: uref\7f194419
-Node: Marking Text\7f195418
-Node: Indicating\7f196042
-Node: Useful Highlighting\7f197947
-Node: code\7f199336
-Node: kbd\7f202374
-Node: key\7f204244
-Node: samp\7f205577
-Node: var\7f207164
-Node: file\7f208957
-Node: dfn\7f209564
-Node: cite\7f210474
-Node: url\7f210928
-Node: email\7f211492
-Node: Emphasis\7f212304
-Node: emph & strong\7f213204
-Node: Smallcaps\7f214190
-Node: Fonts\7f215517
-Node: Customized Highlighting\7f216605
-Node: Customized Highlighting-Footnotes\7f219420
-Ref: Customized Highlighting-Footnote-1\7f219514
-Node: Quotations and Examples\7f219640
-Node: Block Enclosing Commands\7f221262
-Node: quotation\7f223287
-Node: example\7f224377
-Node: noindent\7f226432
-Node: Lisp Example\7f227896
-Node: Lisp Example-Footnotes\7f228598
-Ref: Lisp Example-Footnote-1\7f228670
-Node: smallexample & smalllisp\7f228788
-Node: display\7f230813
-Node: format\7f231445
-Node: exdent\7f231906
-Node: flushleft & flushright\7f232986
-Node: cartouche\7f234252
-Node: Lists and Tables\7f235019
-Node: Introducing Lists\7f235695
-Node: itemize\7f237360
-Node: enumerate\7f239507
-Node: Two-column Tables\7f242012
-Node: table\7f242701
-Node: ftable vtable\7f245134
-Node: itemx\7f246235
-Node: Multi-column Tables\7f247246
-Node: Multitable Column Widths\7f247917
-Node: Multitable Rows\7f249371
-Node: Indices\7f251148
-Node: Index Entries\7f252298
-Node: Predefined Indices\7f253431
-Node: Indexing Commands\7f254428
-Node: Combining Indices\7f258968
-Node: syncodeindex\7f260331
-Node: synindex\7f261993
-Node: New Indices\7f262518
-Node: Insertions\7f264343
-Node: Braces Atsigns\7f265527
-Node: Inserting An Atsign\7f266079
-Node: Inserting Braces\7f266353
-Node: Inserting Space\7f266716
-Node: Not Ending a Sentence\7f267220
-Node: Ending a Sentence\7f268574
-Node: Multiple Spaces\7f269703
-Node: dmn\7f270922
-Node: Inserting Accents\7f272129
-Node: Dots Bullets\7f273886
-Node: dots\7f274708
-Node: bullet\7f275232
-Node: TeX and copyright\7f275629
-Node: tex\7f276196
-Node: copyright symbol\7f276612
-Node: pounds\7f276872
-Node: minus\7f277236
-Node: math\7f278158
-Node: Glyphs\7f278886
-Node: Glyphs Summary\7f279999
-Node: result\7f280627
-Node: expansion\7f281112
-Node: Print Glyph\7f282068
-Node: Error Glyph\7f282945
-Node: Equivalence\7f283778
-Node: Point Glyph\7f284466
-Node: Images\7f286023
-Node: Breaks\7f287690
-Node: Break Commands\7f289121
-Node: Line Breaks\7f289962
-Node: - and hyphenation\7f290980
-Node: w\7f292230
-Node: sp\7f292943
-Node: page\7f293352
-Node: group\7f293729
-Node: need\7f295472
-Node: Definition Commands\7f296202
-Node: Def Cmd Template\7f297773
-Node: Optional Arguments\7f300770
-Node: deffnx\7f302358
-Node: Def Cmds in Detail\7f303313
-Node: Functions Commands\7f304423
-Node: Variables Commands\7f307428
-Node: Typed Functions\7f309514
-Node: Typed Variables\7f313056
-Node: Abstract Objects\7f315039
-Node: Data Types\7f320264
-Node: Def Cmd Conventions\7f321519
-Node: Sample Function Definition\7f322082
-Node: Footnotes\7f324966
-Node: Footnotes-Footnotes\7f325354
-Ref: Footnotes-Footnote-1\7f325420
-Node: Footnote Commands\7f325700
-Node: Footnote Commands-Footnotes\7f327197
-Ref: Footnote Commands-Footnote-1\7f327279
-Node: Footnote Styles\7f327315
-Node: Conditionals\7f329901
-Node: Conditional Commands\7f330712
-Node: Conditional Not Commands\7f332205
-Node: Raw Formatter Commands\7f332950
-Node: set clear value\7f334780
-Node: ifset ifclear\7f335581
-Node: value\7f338760
-Node: value Example\7f340172
-Node: Macros\7f341750
-Node: Defining Macros\7f342455
-Node: Invoking Macros\7f343544
-Node: Format/Print Hardcopy\7f344650
-Node: Use TeX\7f346487
-Node: Format with tex/texindex\7f347115
-Node: Format with texi2dvi\7f350756
-Node: Print with lpr\7f351347
-Node: Within Emacs\7f352201
-Node: Texinfo Mode Printing\7f353120
-Node: Compile-Command\7f356530
-Node: Requirements Summary\7f357418
-Node: Preparing for TeX\7f358731
-Node: Overfull hboxes\7f361518
-Node: smallbook\7f363077
-Node: A4 Paper\7f364595
-Node: Cropmarks and Magnification\7f365820
-Node: Create an Info File\7f367761
-Node: makeinfo advantages\7f369064
-Node: Invoking makeinfo\7f369980
-Node: makeinfo options\7f370668
-Node: Pointer Validation\7f376152
-Node: makeinfo in Emacs\7f377496
-Node: texinfo-format commands\7f380054
-Node: Batch Formatting\7f381325
-Node: Tag and Split Files\7f382541
-Node: Install an Info File\7f385895
-Node: Directory file\7f386713
-Node: New Info File\7f388581
-Node: Other Info Directories\7f389642
-Node: Installing Dir Entries\7f392857
-Node: Invoking install-info\7f394850
-Node: Command List\7f397265
-Node: Tips\7f435235
-Node: Sample Texinfo File\7f446645
-Node: Sample Permissions\7f448764
-Node: Inserting Permissions\7f449807
-Node: ifinfo Permissions\7f452113
-Node: Titlepage Permissions\7f453734
-Node: Include Files\7f454996
-Node: Using Include Files\7f456083
-Node: texinfo-multiple-files-update\7f458038
-Node: Include File Requirements\7f460399
-Node: Sample Include File\7f461644
-Node: Include Files Evolution\7f463163
-Node: Headings\7f465134
-Node: Headings Introduced\7f465771
-Node: Heading Format\7f467659
-Node: Heading Choice\7f470111
-Node: Custom Headings\7f471483
-Node: Catching Mistakes\7f475811
-Node: makeinfo Preferred\7f477100
-Node: Debugging with Info\7f478005
-Node: Debugging with TeX\7f481351
-Node: Using texinfo-show-structure\7f485631
-Node: Using occur\7f488730
-Node: Running Info-Validate\7f490267
-Node: Using Info-validate\7f491328
-Node: Unsplit\7f493170
-Node: Tagifying\7f494216
-Node: Splitting\7f495068
-Node: Refilling Paragraphs\7f496684
-Node: Refilling Paragraphs-Footnotes\7f498338
-Ref: Refilling Paragraphs-Footnote-1\7f498426
-Node: Command Syntax\7f498589
-Node: Obtaining TeX\7f501546
-Node: Command and Variable Index\7f503659
-Node: Concept Index\7f519511
+Node: Cross References\7f172374
+Node: References\7f173331
+Node: Cross Reference Commands\7f175078
+Node: Cross Reference Parts\7f176137
+Node: xref\7f178973
+Node: Reference Syntax\7f179772
+Node: One Argument\7f181426
+Node: Two Arguments\7f182438
+Node: Three Arguments\7f183553
+Node: Four and Five Arguments\7f185944
+Node: Top Node Naming\7f188356
+Node: ref\7f189366
+Node: pxref\7f190756
+Node: inforef\7f193138
+Node: uref\7f194431
+Node: Marking Text\7f195430
+Node: Indicating\7f196054
+Node: Useful Highlighting\7f197959
+Node: code\7f199348
+Node: kbd\7f202386
+Node: key\7f204256
+Node: samp\7f205589
+Node: var\7f207176
+Node: file\7f208969
+Node: dfn\7f209576
+Node: cite\7f210486
+Node: url\7f210940
+Node: email\7f211504
+Node: Emphasis\7f212316
+Node: emph & strong\7f213216
+Node: Smallcaps\7f214202
+Node: Fonts\7f215529
+Node: Customized Highlighting\7f216617
+Node: Customized Highlighting-Footnotes\7f219432
+Ref: Customized Highlighting-Footnote-1\7f219526
+Node: Quotations and Examples\7f219652
+Node: Block Enclosing Commands\7f221274
+Node: quotation\7f223299
+Node: example\7f224389
+Node: noindent\7f226444
+Node: Lisp Example\7f227908
+Node: Lisp Example-Footnotes\7f228610
+Ref: Lisp Example-Footnote-1\7f228682
+Node: smallexample & smalllisp\7f228800
+Node: display\7f230825
+Node: format\7f231457
+Node: exdent\7f231918
+Node: flushleft & flushright\7f232998
+Node: cartouche\7f234264
+Node: Lists and Tables\7f235031
+Node: Introducing Lists\7f235707
+Node: itemize\7f237372
+Node: enumerate\7f239519
+Node: Two-column Tables\7f242024
+Node: table\7f242713
+Node: ftable vtable\7f245146
+Node: itemx\7f246247
+Node: Multi-column Tables\7f247258
+Node: Multitable Column Widths\7f247929
+Node: Multitable Rows\7f249383
+Node: Indices\7f251160
+Node: Index Entries\7f252310
+Node: Predefined Indices\7f253443
+Node: Indexing Commands\7f254440
+Node: Combining Indices\7f258980
+Node: syncodeindex\7f260343
+Node: synindex\7f262005
+Node: New Indices\7f262530
+Node: Insertions\7f264355
+Node: Braces Atsigns\7f265539
+Node: Inserting An Atsign\7f266091
+Node: Inserting Braces\7f266365
+Node: Inserting Space\7f266728
+Node: Not Ending a Sentence\7f267232
+Node: Ending a Sentence\7f268586
+Node: Multiple Spaces\7f269715
+Node: dmn\7f270934
+Node: Inserting Accents\7f272141
+Node: Dots Bullets\7f273898
+Node: dots\7f274720
+Node: bullet\7f275244
+Node: TeX and copyright\7f275641
+Node: tex\7f276208
+Node: copyright symbol\7f276624
+Node: pounds\7f276884
+Node: minus\7f277248
+Node: math\7f278170
+Node: Glyphs\7f278898
+Node: Glyphs Summary\7f280011
+Node: result\7f280639
+Node: expansion\7f281124
+Node: Print Glyph\7f282080
+Node: Error Glyph\7f282957
+Node: Equivalence\7f283790
+Node: Point Glyph\7f284478
+Node: Images\7f286035
+Node: Breaks\7f287702
+Node: Break Commands\7f289133
+Node: Line Breaks\7f289974
+Node: - and hyphenation\7f290992
+Node: w\7f292242
+Node: sp\7f292955
+Node: page\7f293364
+Node: group\7f293741
+Node: need\7f295484
+Node: Definition Commands\7f296214
+Node: Def Cmd Template\7f297785
+Node: Optional Arguments\7f300782
+Node: deffnx\7f302370
+Node: Def Cmds in Detail\7f303325
+Node: Functions Commands\7f304435
+Node: Variables Commands\7f307440
+Node: Typed Functions\7f309526
+Node: Typed Variables\7f313068
+Node: Abstract Objects\7f315051
+Node: Data Types\7f320276
+Node: Def Cmd Conventions\7f321531
+Node: Sample Function Definition\7f322094
+Node: Footnotes\7f324978
+Node: Footnotes-Footnotes\7f325366
+Ref: Footnotes-Footnote-1\7f325432
+Node: Footnote Commands\7f325712
+Node: Footnote Commands-Footnotes\7f327209
+Ref: Footnote Commands-Footnote-1\7f327291
+Node: Footnote Styles\7f327327
+Node: Conditionals\7f329913
+Node: Conditional Commands\7f330724
+Node: Conditional Not Commands\7f332217
+Node: Raw Formatter Commands\7f332962
+Node: set clear value\7f334792
+Node: ifset ifclear\7f335593
+Node: value\7f338772
+Node: value Example\7f340184
+Node: Macros\7f341762
+Node: Defining Macros\7f342467
+Node: Invoking Macros\7f343556
+Node: Format/Print Hardcopy\7f344662
+Node: Use TeX\7f346499
+Node: Format with tex/texindex\7f347127
+Node: Format with texi2dvi\7f350768
+Node: Print with lpr\7f351359
+Node: Within Emacs\7f352213
+Node: Texinfo Mode Printing\7f353132
+Node: Compile-Command\7f356542
+Node: Requirements Summary\7f357430
+Node: Preparing for TeX\7f358743
+Node: Overfull hboxes\7f361530
+Node: smallbook\7f363089
+Node: A4 Paper\7f364607
+Node: Cropmarks and Magnification\7f365832
+Node: Create an Info File\7f367773
+Node: makeinfo advantages\7f369076
+Node: Invoking makeinfo\7f369992
+Node: makeinfo options\7f370680
+Node: Pointer Validation\7f376164
+Node: makeinfo in Emacs\7f377508
+Node: texinfo-format commands\7f380066
+Node: Batch Formatting\7f381337
+Node: Tag and Split Files\7f382553
+Node: Install an Info File\7f385907
+Node: Directory file\7f386725
+Node: New Info File\7f388593
+Node: Other Info Directories\7f389654
+Node: Installing Dir Entries\7f392869
+Node: Invoking install-info\7f394862
+Node: Command List\7f397277
+Node: Tips\7f435247
+Node: Sample Texinfo File\7f446657
+Node: Sample Permissions\7f448776
+Node: Inserting Permissions\7f449819
+Node: ifinfo Permissions\7f452125
+Node: Titlepage Permissions\7f453746
+Node: Include Files\7f455008
+Node: Using Include Files\7f456095
+Node: texinfo-multiple-files-update\7f458050
+Node: Include File Requirements\7f460411
+Node: Sample Include File\7f461656
+Node: Include Files Evolution\7f463175
+Node: Headings\7f465146
+Node: Headings Introduced\7f465783
+Node: Heading Format\7f467671
+Node: Heading Choice\7f470123
+Node: Custom Headings\7f471495
+Node: Catching Mistakes\7f475823
+Node: makeinfo Preferred\7f477112
+Node: Debugging with Info\7f478017
+Node: Debugging with TeX\7f481363
+Node: Using texinfo-show-structure\7f485643
+Node: Using occur\7f488742
+Node: Running Info-Validate\7f490279
+Node: Using Info-validate\7f491340
+Node: Unsplit\7f493182
+Node: Tagifying\7f494228
+Node: Splitting\7f495080
+Node: Refilling Paragraphs\7f496696
+Node: Refilling Paragraphs-Footnotes\7f498350
+Ref: Refilling Paragraphs-Footnote-1\7f498438
+Node: Command Syntax\7f498601
+Node: Obtaining TeX\7f501558
+Node: Command and Variable Index\7f503671
+Node: Concept Index\7f519523
\1f
End Tag Table
@end menu
For example, to refer directly to the `Outlining' and `Rebinding'
-nodes in the `Emacs Manual', you would write a menu like this:
+nodes in the `XEmacs User's Manual', you would write a menu like this:
@menu
- * Outlining: (emacs)Outline Mode. The major mode for
- editing outlines.
- * Rebinding: (emacs)Rebinding. How to redefine the
- meaning of a key.
+ * Outlining: (xemacs)Outline Mode. The major mode for
+ editing outlines.
+ * Rebinding: (xemacs)Rebinding. How to redefine the
+ meaning of a key.
@end menu
If you do not list the node name, but only name the file, then Info
\1f
Indirect:
xemacs-faq.info-1: 205
-xemacs-faq.info-2: 49999
-xemacs-faq.info-3: 99617
-xemacs-faq.info-4: 149492
-xemacs-faq.info-5: 199354
+xemacs-faq.info-2: 50001
+xemacs-faq.info-3: 99619
+xemacs-faq.info-4: 149494
+xemacs-faq.info-5: 199356
\1f
Tag Table:
(Indirect)
Node: Q1.0.12\7f26012
Node: Q1.0.13\7f26380
Node: Q1.0.14\7f26629
-Node: Q1.1.1\7f27139
-Node: Q1.1.2\7f28181
-Node: Q1.1.3\7f28574
-Node: Q1.2.1\7f29525
-Node: Q1.2.2\7f30581
-Node: Q1.2.3\7f31015
-Node: Q1.3.1\7f32099
-Node: Q1.3.2\7f32750
-Node: Q1.3.3\7f33214
-Node: Q1.3.4\7f33455
-Node: Q1.3.5\7f34228
-Node: Q1.3.6\7f36633
-Node: Q1.3.7\7f38164
-Node: Q1.4.1\7f39099
-Node: Q1.4.2\7f39961
-Node: Q1.4.3\7f40302
-Node: Q1.4.4\7f40721
-Node: Q1.4.5\7f42261
-Node: Q1.4.6\7f42565
-Node: Installation\7f43558
-Node: Q2.0.1\7f46133
-Node: Q2.0.2\7f46933
-Node: Q2.0.3\7f48701
-Node: Q2.0.4\7f49999
-Node: Q2.0.5\7f50591
-Node: Q2.0.6\7f50939
-Node: Q2.0.7\7f51320
-Node: Q2.0.8\7f51701
-Node: Q2.0.9\7f53278
-Node: Q2.0.10\7f54716
-Node: Q2.0.11\7f55560
-Node: Q2.0.12\7f56501
-Node: Q2.0.13\7f58024
-Node: Q2.0.14\7f58513
-Node: Q2.1.1\7f59571
-Node: Q2.1.2\7f62313
-Node: Q2.1.3\7f63490
-Node: Q2.1.4\7f64783
-Node: Q2.1.5\7f65582
-Node: Q2.1.6\7f65944
-Node: Q2.1.7\7f66421
-Node: Q2.1.8\7f66774
-Node: Q2.1.9\7f68308
-Node: Q2.1.10\7f68730
-Node: Q2.1.11\7f69487
-Node: Q2.1.12\7f70352
-Node: Q2.1.13\7f71307
-Node: Q2.1.14\7f72338
-Node: Q2.1.15\7f73449
-Node: Q2.1.16\7f80481
-Node: Q2.1.17\7f81175
-Node: Q2.1.18\7f81772
-Node: Q2.1.19\7f81899
-Node: Q2.1.20\7f82429
-Node: Q2.1.21\7f82811
-Node: Q2.1.22\7f83004
-Node: Q2.1.23\7f84301
-Node: Q2.1.24\7f84969
-Node: Q2.1.25\7f85441
-Node: Customization\7f86076
-Node: Q3.0.1\7f90914
-Node: Q3.0.2\7f91620
-Node: Q3.0.3\7f92184
-Node: Q3.0.4\7f92601
-Node: Q3.0.5\7f93434
-Node: Q3.0.6\7f94215
-Node: Q3.0.7\7f94795
-Node: Q3.0.8\7f95459
-Node: Q3.0.9\7f96417
-Node: Q3.1.1\7f96978
-Node: Q3.1.2\7f97715
-Node: Q3.1.3\7f98146
-Node: Q3.1.4\7f98335
-Node: Q3.1.5\7f98524
-Node: Q3.1.6\7f98908
-Node: Q3.1.7\7f99617
-Node: Q3.1.8\7f101841
-Node: Q3.2.1\7f102383
-Node: Q3.2.2\7f104036
-Node: Q3.2.3\7f104835
-Node: Q3.2.4\7f105437
-Node: Q3.2.5\7f106471
-Node: Q3.2.6\7f106938
-Node: Q3.3.1\7f107863
-Node: Q3.3.2\7f108293
-Node: Q3.3.3\7f108924
-Node: Q3.3.4\7f109305
-Node: Q3.3.5\7f110406
-Node: Q3.4.1\7f111900
-Node: Q3.4.2\7f112543
-Node: Q3.5.1\7f113055
-Node: Q3.5.2\7f114504
-Node: Q3.5.3\7f114922
-Node: Q3.5.4\7f115760
-Node: Q3.5.5\7f116592
-Node: Q3.5.6\7f117732
-Node: Q3.5.7\7f118722
-Node: Q3.5.8\7f120162
-Node: Q3.5.9\7f120909
-Node: Q3.5.10\7f121689
-Node: Q3.5.11\7f122325
-Node: Q3.6.1\7f122878
-Node: Q3.6.2\7f123623
-Node: Q3.6.3\7f124051
-Node: Q3.7.1\7f124551
-Node: Q3.7.2\7f125439
-Node: Q3.7.3\7f126098
-Node: Q3.7.4\7f126520
-Node: Q3.7.5\7f126863
-Node: Q3.7.6\7f127331
-Node: Q3.7.7\7f128046
-Node: Q3.7.8\7f129066
-Node: Q3.8.1\7f129485
-Node: Q3.8.2\7f129945
-Node: Q3.8.3\7f130408
-Node: Q3.8.4\7f131014
-Node: Q3.8.5\7f131733
-Node: Q3.9.1\7f132518
-Node: Q3.9.2\7f133458
-Node: Q3.9.3\7f134056
-Node: Q3.9.4\7f134718
-Node: Q3.10.1\7f135597
-Node: Q3.10.2\7f136415
-Node: Q3.10.3\7f137420
-Node: Q3.10.4\7f138148
-Node: Q3.10.5\7f138531
-Node: Subsystems\7f139583
-Node: Q4.0.1\7f142070
-Node: Q4.0.2\7f142595
-Node: Q4.0.3\7f143153
-Node: Q4.0.4\7f143474
-Node: Q4.0.5\7f143716
-Node: Q4.0.6\7f143947
-Node: Q4.0.7\7f144535
-Node: Q4.0.8\7f144860
-Node: Q4.0.9\7f146087
-Node: Q4.0.10\7f148125
-Node: Q4.0.11\7f148614
-Node: Q4.0.12\7f149492
-Node: Q4.1.1\7f150465
-Node: Q4.1.2\7f150868
-Node: Q4.1.3\7f151195
-Node: Q4.2.1\7f151504
-Node: Q4.2.2\7f152134
-Node: Q4.2.3\7f152374
-Node: Q4.2.4\7f152918
-Node: Q4.3.1\7f153571
-Node: Q4.3.2\7f154155
-Node: Q4.3.3\7f155636
-Node: Q4.3.4\7f155908
-Node: Q4.3.5\7f156585
-Node: Q4.4.1\7f157213
-Node: Q4.4.2\7f158699
-Node: Q4.5.1\7f159903
-Node: Q4.6.1\7f160672
-Node: Q4.7.1\7f165932
-Node: Q4.7.2\7f166887
-Node: Q4.7.3\7f167184
-Node: Q4.7.4\7f167370
-Node: Q4.7.5\7f168254
-Node: Q4.7.6\7f169895
-Node: Miscellaneous\7f170184
-Node: Q5.0.1\7f173597
-Node: Q5.0.2\7f174336
-Node: Q5.0.3\7f175190
-Node: Q5.0.4\7f175892
-Node: Q5.0.5\7f176831
-Node: Q5.0.6\7f178811
-Node: Q5.0.7\7f179468
-Node: Q5.0.8\7f180073
-Node: Q5.0.9\7f180592
-Node: Q5.0.10\7f181106
-Node: Q5.0.11\7f181354
-Node: Q5.0.12\7f181892
-Node: Q5.0.13\7f182809
-Node: Q5.0.14\7f183493
-Node: Q5.0.15\7f184258
-Node: Q5.0.16\7f184555
-Node: Q5.0.17\7f185067
-Node: Q5.0.18\7f185332
-Node: Q5.0.19\7f185526
-Node: Q5.0.20\7f185950
-Node: Q5.1.1\7f186865
-Node: Q5.1.2\7f188934
-Node: Q5.1.3\7f189670
-Node: Q5.1.4\7f193064
-Node: Q5.1.5\7f193599
-Node: Q5.1.6\7f195723
-Node: Q5.1.7\7f197209
-Node: Q5.1.8\7f198802
-Node: Q5.1.9\7f199354
-Node: Q5.1.10\7f200239
-Node: Q5.1.11\7f201370
-Node: Q5.2.1\7f201919
-Node: Q5.2.2\7f202489
-Node: Q5.2.3\7f202906
-Node: Q5.2.4\7f203141
-Node: Q5.3.1\7f204051
-Node: Q5.3.2\7f205272
-Node: Q5.3.3\7f206048
-Node: Q5.3.4\7f206532
-Node: Q5.3.5\7f207199
-Node: Q5.3.6\7f208068
-Node: Q5.3.7\7f208313
-Node: Q5.3.8\7f210503
-Node: Q5.3.9\7f210750
-Node: Q5.3.10\7f211703
-Node: Q5.3.11\7f213787
-Node: Q5.3.12\7f215378
-Node: MS Windows\7f216652
-Node: Q6.0.1\7f218129
-Node: Q6.0.2\7f218876
-Node: Q6.0.3\7f219341
-Node: Q6.0.4\7f219621
-Node: Q6.1.1\7f221900
-Node: Q6.1.2\7f222771
-Node: Q6.1.3\7f223226
-Node: Q6.1.4\7f223508
-Node: Q6.1.5\7f223886
-Node: Q6.1.6\7f224754
-Node: Q6.2.1\7f227060
-Node: Q6.2.2\7f227961
-Node: Q6.2.3\7f228373
-Node: Q6.3.1\7f228662
-Node: Q6.3.2\7f229756
-Node: Q6.3.3\7f232937
-Node: Q6.4.1\7f233206
-Node: Current Events\7f234541
-Node: Q7.0.1\7f235195
-Node: Q7.0.2\7f235834
-Node: Q7.0.3\7f236907
-Node: Q7.0.4\7f237135
+Node: Q1.1.1\7f27141
+Node: Q1.1.2\7f28183
+Node: Q1.1.3\7f28576
+Node: Q1.2.1\7f29527
+Node: Q1.2.2\7f30583
+Node: Q1.2.3\7f31017
+Node: Q1.3.1\7f32101
+Node: Q1.3.2\7f32752
+Node: Q1.3.3\7f33216
+Node: Q1.3.4\7f33457
+Node: Q1.3.5\7f34230
+Node: Q1.3.6\7f36635
+Node: Q1.3.7\7f38166
+Node: Q1.4.1\7f39101
+Node: Q1.4.2\7f39963
+Node: Q1.4.3\7f40304
+Node: Q1.4.4\7f40723
+Node: Q1.4.5\7f42263
+Node: Q1.4.6\7f42567
+Node: Installation\7f43560
+Node: Q2.0.1\7f46135
+Node: Q2.0.2\7f46935
+Node: Q2.0.3\7f48703
+Node: Q2.0.4\7f50001
+Node: Q2.0.5\7f50593
+Node: Q2.0.6\7f50941
+Node: Q2.0.7\7f51322
+Node: Q2.0.8\7f51703
+Node: Q2.0.9\7f53280
+Node: Q2.0.10\7f54718
+Node: Q2.0.11\7f55562
+Node: Q2.0.12\7f56503
+Node: Q2.0.13\7f58026
+Node: Q2.0.14\7f58515
+Node: Q2.1.1\7f59573
+Node: Q2.1.2\7f62315
+Node: Q2.1.3\7f63492
+Node: Q2.1.4\7f64785
+Node: Q2.1.5\7f65584
+Node: Q2.1.6\7f65946
+Node: Q2.1.7\7f66423
+Node: Q2.1.8\7f66776
+Node: Q2.1.9\7f68310
+Node: Q2.1.10\7f68732
+Node: Q2.1.11\7f69489
+Node: Q2.1.12\7f70354
+Node: Q2.1.13\7f71309
+Node: Q2.1.14\7f72340
+Node: Q2.1.15\7f73451
+Node: Q2.1.16\7f80483
+Node: Q2.1.17\7f81177
+Node: Q2.1.18\7f81774
+Node: Q2.1.19\7f81901
+Node: Q2.1.20\7f82431
+Node: Q2.1.21\7f82813
+Node: Q2.1.22\7f83006
+Node: Q2.1.23\7f84303
+Node: Q2.1.24\7f84971
+Node: Q2.1.25\7f85443
+Node: Customization\7f86078
+Node: Q3.0.1\7f90916
+Node: Q3.0.2\7f91622
+Node: Q3.0.3\7f92186
+Node: Q3.0.4\7f92603
+Node: Q3.0.5\7f93436
+Node: Q3.0.6\7f94217
+Node: Q3.0.7\7f94797
+Node: Q3.0.8\7f95461
+Node: Q3.0.9\7f96419
+Node: Q3.1.1\7f96980
+Node: Q3.1.2\7f97717
+Node: Q3.1.3\7f98148
+Node: Q3.1.4\7f98337
+Node: Q3.1.5\7f98526
+Node: Q3.1.6\7f98910
+Node: Q3.1.7\7f99619
+Node: Q3.1.8\7f101843
+Node: Q3.2.1\7f102385
+Node: Q3.2.2\7f104038
+Node: Q3.2.3\7f104837
+Node: Q3.2.4\7f105439
+Node: Q3.2.5\7f106473
+Node: Q3.2.6\7f106940
+Node: Q3.3.1\7f107865
+Node: Q3.3.2\7f108295
+Node: Q3.3.3\7f108926
+Node: Q3.3.4\7f109307
+Node: Q3.3.5\7f110408
+Node: Q3.4.1\7f111902
+Node: Q3.4.2\7f112545
+Node: Q3.5.1\7f113057
+Node: Q3.5.2\7f114506
+Node: Q3.5.3\7f114924
+Node: Q3.5.4\7f115762
+Node: Q3.5.5\7f116594
+Node: Q3.5.6\7f117734
+Node: Q3.5.7\7f118724
+Node: Q3.5.8\7f120164
+Node: Q3.5.9\7f120911
+Node: Q3.5.10\7f121691
+Node: Q3.5.11\7f122327
+Node: Q3.6.1\7f122880
+Node: Q3.6.2\7f123625
+Node: Q3.6.3\7f124053
+Node: Q3.7.1\7f124553
+Node: Q3.7.2\7f125441
+Node: Q3.7.3\7f126100
+Node: Q3.7.4\7f126522
+Node: Q3.7.5\7f126865
+Node: Q3.7.6\7f127333
+Node: Q3.7.7\7f128048
+Node: Q3.7.8\7f129068
+Node: Q3.8.1\7f129487
+Node: Q3.8.2\7f129947
+Node: Q3.8.3\7f130410
+Node: Q3.8.4\7f131016
+Node: Q3.8.5\7f131735
+Node: Q3.9.1\7f132520
+Node: Q3.9.2\7f133460
+Node: Q3.9.3\7f134058
+Node: Q3.9.4\7f134720
+Node: Q3.10.1\7f135599
+Node: Q3.10.2\7f136417
+Node: Q3.10.3\7f137422
+Node: Q3.10.4\7f138150
+Node: Q3.10.5\7f138533
+Node: Subsystems\7f139585
+Node: Q4.0.1\7f142072
+Node: Q4.0.2\7f142597
+Node: Q4.0.3\7f143155
+Node: Q4.0.4\7f143476
+Node: Q4.0.5\7f143718
+Node: Q4.0.6\7f143949
+Node: Q4.0.7\7f144537
+Node: Q4.0.8\7f144862
+Node: Q4.0.9\7f146089
+Node: Q4.0.10\7f148127
+Node: Q4.0.11\7f148616
+Node: Q4.0.12\7f149494
+Node: Q4.1.1\7f150467
+Node: Q4.1.2\7f150870
+Node: Q4.1.3\7f151197
+Node: Q4.2.1\7f151506
+Node: Q4.2.2\7f152136
+Node: Q4.2.3\7f152376
+Node: Q4.2.4\7f152920
+Node: Q4.3.1\7f153573
+Node: Q4.3.2\7f154157
+Node: Q4.3.3\7f155638
+Node: Q4.3.4\7f155910
+Node: Q4.3.5\7f156587
+Node: Q4.4.1\7f157215
+Node: Q4.4.2\7f158701
+Node: Q4.5.1\7f159905
+Node: Q4.6.1\7f160674
+Node: Q4.7.1\7f165934
+Node: Q4.7.2\7f166889
+Node: Q4.7.3\7f167186
+Node: Q4.7.4\7f167372
+Node: Q4.7.5\7f168256
+Node: Q4.7.6\7f169897
+Node: Miscellaneous\7f170186
+Node: Q5.0.1\7f173599
+Node: Q5.0.2\7f174338
+Node: Q5.0.3\7f175192
+Node: Q5.0.4\7f175894
+Node: Q5.0.5\7f176833
+Node: Q5.0.6\7f178813
+Node: Q5.0.7\7f179470
+Node: Q5.0.8\7f180075
+Node: Q5.0.9\7f180594
+Node: Q5.0.10\7f181108
+Node: Q5.0.11\7f181356
+Node: Q5.0.12\7f181894
+Node: Q5.0.13\7f182811
+Node: Q5.0.14\7f183495
+Node: Q5.0.15\7f184260
+Node: Q5.0.16\7f184557
+Node: Q5.0.17\7f185069
+Node: Q5.0.18\7f185334
+Node: Q5.0.19\7f185528
+Node: Q5.0.20\7f185952
+Node: Q5.1.1\7f186867
+Node: Q5.1.2\7f188936
+Node: Q5.1.3\7f189672
+Node: Q5.1.4\7f193066
+Node: Q5.1.5\7f193601
+Node: Q5.1.6\7f195725
+Node: Q5.1.7\7f197211
+Node: Q5.1.8\7f198804
+Node: Q5.1.9\7f199356
+Node: Q5.1.10\7f200241
+Node: Q5.1.11\7f201372
+Node: Q5.2.1\7f201921
+Node: Q5.2.2\7f202491
+Node: Q5.2.3\7f202908
+Node: Q5.2.4\7f203143
+Node: Q5.3.1\7f204053
+Node: Q5.3.2\7f205274
+Node: Q5.3.3\7f206050
+Node: Q5.3.4\7f206534
+Node: Q5.3.5\7f207201
+Node: Q5.3.6\7f208070
+Node: Q5.3.7\7f208315
+Node: Q5.3.8\7f210505
+Node: Q5.3.9\7f210752
+Node: Q5.3.10\7f211705
+Node: Q5.3.11\7f213789
+Node: Q5.3.12\7f215380
+Node: MS Windows\7f216654
+Node: Q6.0.1\7f218131
+Node: Q6.0.2\7f218878
+Node: Q6.0.3\7f219343
+Node: Q6.0.4\7f219623
+Node: Q6.1.1\7f221902
+Node: Q6.1.2\7f222773
+Node: Q6.1.3\7f223228
+Node: Q6.1.4\7f223510
+Node: Q6.1.5\7f223888
+Node: Q6.1.6\7f224756
+Node: Q6.2.1\7f227062
+Node: Q6.2.2\7f227963
+Node: Q6.2.3\7f228375
+Node: Q6.3.1\7f228664
+Node: Q6.3.2\7f229758
+Node: Q6.3.3\7f232939
+Node: Q6.4.1\7f233208
+Node: Current Events\7f234543
+Node: Q7.0.1\7f235197
+Node: Q7.0.2\7f235836
+Node: Q7.0.3\7f236909
+Node: Q7.0.4\7f237137
\1f
End Tag Table
\1f
File: xemacs-faq.info, Node: Q1.0.14, Next: Q1.1.1, Prev: Q1.0.13, Up: Introduction
-Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
-----------------------------------------------------------------------
+Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual?
+-----------------------------------------------------------------------
Pre-printed manuals are not available. If you are familiar with
TeX, you can generate your own manual from the XEmacs sources.
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
\1f
Indirect:
-xemacs.info-1: 1350
-xemacs.info-2: 48895
-xemacs.info-3: 98506
-xemacs.info-4: 147816
-xemacs.info-5: 197412
-xemacs.info-6: 246852
-xemacs.info-7: 296809
-xemacs.info-8: 345202
-xemacs.info-9: 392972
-xemacs.info-10: 442574
-xemacs.info-11: 491015
-xemacs.info-12: 538210
-xemacs.info-13: 586468
-xemacs.info-14: 634794
-xemacs.info-15: 684331
-xemacs.info-16: 731876
-xemacs.info-17: 780201
-xemacs.info-18: 826586
-xemacs.info-19: 867946
-xemacs.info-20: 899600
-xemacs.info-21: 949004
-xemacs.info-22: 991590
+xemacs.info-1: 1351
+xemacs.info-2: 48996
+xemacs.info-3: 96093
+xemacs.info-4: 145333
+xemacs.info-5: 194484
+xemacs.info-6: 242144
+xemacs.info-7: 282227
+xemacs.info-8: 332190
+xemacs.info-9: 379660
+xemacs.info-10: 428178
+xemacs.info-11: 476002
+xemacs.info-12: 525173
+xemacs.info-13: 574356
+xemacs.info-14: 623433
+xemacs.info-15: 672813
+xemacs.info-16: 722680
+xemacs.info-17: 771316
+xemacs.info-18: 820011
+xemacs.info-19: 868928
+xemacs.info-20: 915111
+xemacs.info-21: 964515
+xemacs.info-22: 1007101
\1f
Tag Table:
(Indirect)
-Node: Top\7f1350
-Node: License\7f22790
+Node: Top\7f1351
+Node: License\7f22791
Node: Distrib\7f36072
Node: Intro\7f37736
Node: Frame\7f40607
-Node: Point\7f44551
-Node: Echo Area\7f46518
-Node: Mode Line\7f48895
-Node: XEmacs under X\7f53326
-Node: Keystrokes\7f56503
-Node: Intro to Keystrokes\7f57347
-Node: Representing Keystrokes\7f59450
-Node: Key Sequences\7f60807
-Node: String Key Sequences\7f64148
-Node: Meta Key\7f64531
-Node: Super and Hyper Keys\7f66004
-Node: Character Representation\7f72249
-Node: Commands\7f73269
-Node: Pull-down Menus\7f76118
-Node: File Menu\7f79467
-Node: Edit Menu\7f83289
-Node: Apps Menu\7f85672
-Node: Options Menu\7f86162
-Node: Buffers Menu\7f90180
-Node: Tools Menu\7f90487
-Node: Help Menu\7f90978
-Node: Menu Customization\7f91379
-Node: Entering Emacs\7f95609
-Node: Exiting\7f98506
-Node: Command Switches\7f102979
-Node: Startup Paths\7f112343
-Node: Basic\7f119673
-Node: Inserting Text\7f121077
-Node: Moving Point\7f124073
-Node: Erasing\7f127679
-Node: Basic Files\7f128984
-Node: Basic Help\7f130906
-Node: Blank Lines\7f131501
-Node: Continuation Lines\7f133077
-Node: Position Info\7f134744
-Node: Arguments\7f138160
-Node: Undo\7f142259
-Node: Minibuffer\7f145206
-Node: Minibuffer File\7f147816
-Node: Minibuffer Edit\7f149621
-Node: Completion\7f152562
-Node: Completion Example\7f154493
-Node: Completion Commands\7f155588
-Node: Strict Completion\7f158564
-Node: Completion Options\7f160345
-Node: Minibuffer History\7f161853
-Node: Repetition\7f165037
-Node: M-x\7f167882
-Node: Help\7f172976
-Node: Help Summary\7f174386
-Node: Key Help\7f177172
-Node: Name Help\7f178131
-Node: Apropos\7f180776
-Node: Library Keywords\7f183895
-Node: Help Mode\7f186216
-Node: Misc Help\7f186713
-Node: Mark\7f189861
-Node: Setting Mark\7f191715
-Node: Using Region\7f194837
-Node: Marking Objects\7f195574
-Node: Mark Ring\7f197412
-Node: Mouse Selection\7f199128
-Node: Additional Mouse Operations\7f201135
-Node: Killing\7f205339
-Node: Yanking\7f210975
-Node: Kill Ring\7f211778
-Node: Appending Kills\7f213380
-Node: Earlier Kills\7f215417
-Node: Using X Selections\7f218030
-Node: X Clipboard Selection\7f219280
-Node: X Selection Commands\7f221457
-Node: X Cut Buffers\7f222543
-Node: Active Regions\7f223902
-Node: Accumulating Text\7f228482
-Node: Rectangles\7f231555
-Node: Registers\7f235074
-Node: RegPos\7f236528
-Node: RegText\7f237684
-Node: RegRect\7f238790
-Node: RegConfig\7f239669
-Node: RegNumbers\7f240609
-Node: RegFiles\7f241327
-Node: Bookmarks\7f241985
-Node: Display\7f245357
-Node: Scrolling\7f246852
-Node: Horizontal Scrolling\7f250995
-Node: Selective Display\7f252190
-Node: Display Vars\7f253409
-Node: Search\7f256087
-Node: Incremental Search\7f257280
-Node: Non-Incremental Search\7f266208
-Node: Word Search\7f267650
-Node: Regexp Search\7f269268
-Node: Regexps\7f271638
-Node: Search Case\7f285635
-Node: Replace\7f286416
-Node: Unconditional Replace\7f287364
-Node: Regexp Replace\7f288499
-Node: Replacement and Case\7f289434
-Node: Query Replace\7f290414
-Node: Other Repeating Search\7f293641
-Node: Fixit\7f294896
-Node: Kill Errors\7f295476
-Node: Transpose\7f296809
-Node: Fixing Case\7f299213
-Node: Spelling\7f299859
-Node: Files\7f301320
-Node: File Names\7f302630
-Node: Visiting\7f306967
-Node: Saving\7f313799
-Node: Backup\7f318722
-Node: Backup Names\7f320118
-Node: Backup Deletion\7f321601
-Node: Backup Copying\7f322751
-Node: Interlocking\7f324457
-Node: Reverting\7f328585
-Node: Auto Save\7f330497
-Node: Auto Save Files\7f331464
-Node: Auto Save Control\7f333305
-Node: Recover\7f335143
-Node: Version Control\7f336298
-Node: Concepts of VC\7f338336
-Node: Editing with VC\7f339946
-Node: Variables for Check-in/out\7f345202
-Node: Log Entries\7f347101
-Node: Change Logs and VC\7f348281
-Node: Old Versions\7f351548
-Node: VC Status\7f353551
-Node: Renaming and VC\7f355265
-Node: Snapshots\7f355944
-Node: Making Snapshots\7f356445
-Node: Snapshot Caveats\7f357738
-Node: Version Headers\7f359547
-Node: ListDir\7f362246
-Node: Comparing Files\7f364295
-Node: Dired\7f365828
-Node: Dired Enter\7f366499
-Node: Dired Edit\7f367324
-Node: Dired Deletion\7f369071
-Node: Dired Immed\7f372294
-Node: Misc File Ops\7f373570
-Node: Buffers\7f376058
-Node: Select Buffer\7f378216
-Node: List Buffers\7f380011
-Node: Misc Buffer\7f381769
-Node: Kill Buffer\7f383412
-Node: Several Buffers\7f384542
-Node: Windows\7f388409
-Node: Basic Window\7f389120
-Node: Split Window\7f390839
-Node: Other Window\7f392972
-Node: Pop Up Window\7f395403
-Node: Change Window\7f396908
-Node: Mule\7f399816
-Node: Mule Intro\7f401079
-Node: Language Environments\7f402095
-Node: Input Methods\7f404202
-Node: Select Input Method\7f407922
-Node: Coding Systems\7f410077
-Node: Recognize Coding\7f414263
-Node: Specify Coding\7f417589
-Node: Major Modes\7f422520
-Node: Choosing Modes\7f424739
-Node: Indentation\7f427129
-Node: Indentation Commands\7f429224
-Node: Tab Stops\7f431953
-Node: Just Spaces\7f433802
-Node: Text\7f434617
-Node: Text Mode\7f436600
-Node: Nroff Mode\7f438679
-Node: TeX Mode\7f440322
-Node: TeX Editing\7f442574
-Node: TeX Print\7f446008
-Node: Outline Mode\7f449227
-Node: Outline Format\7f450708
-Node: Outline Motion\7f453508
-Node: Outline Visibility\7f455061
-Node: Words\7f457982
-Node: Sentences\7f460929
-Node: Paragraphs\7f463125
-Node: Pages\7f465413
-Node: Filling\7f468013
-Node: Auto Fill\7f468584
-Node: Fill Commands\7f470731
-Node: Fill Prefix\7f472896
-Node: Case\7f475084
-Node: Programs\7f477112
-Node: Program Modes\7f479662
-Node: Lists\7f481894
-Node: Defuns\7f487734
-Node: Grinding\7f490387
-Node: Basic Indent\7f491015
-Node: Multi-line Indent\7f493036
-Node: Lisp Indent\7f494652
-Node: C Indent\7f498102
-Node: Matching\7f503342
-Node: Comments\7f504864
-Node: Balanced Editing\7f511316
-Node: Lisp Completion\7f512330
-Node: Documentation\7f513345
-Node: Change Log\7f514584
-Node: Tags\7f517162
-Node: Tag Syntax\7f518811
-Node: Create Tags Table\7f522755
-Node: Etags Regexps\7f526815
-Node: Select Tags Table\7f531473
-Node: Find Tag\7f535246
-Node: Tags Search\7f538210
-Node: List Tags\7f541666
-Node: Fortran\7f542695
-Node: Fortran Motion\7f543771
-Node: Fortran Indent\7f544591
-Node: ForIndent Commands\7f545276
-Node: ForIndent Num\7f546421
-Node: ForIndent Conv\7f547695
-Node: ForIndent Vars\7f548471
-Node: Fortran Comments\7f549639
-Node: Fortran Columns\7f553237
-Node: Fortran Abbrev\7f554660
-Node: Asm Mode\7f555569
-Node: Running\7f556121
-Node: Compilation\7f557090
-Node: Lisp Modes\7f561940
-Node: Lisp Libraries\7f563213
-Node: Loading\7f563767
-Node: Compiling Libraries\7f568227
-Node: Mocklisp\7f571118
-Node: Lisp Eval\7f571795
-Node: Lisp Debug\7f575435
-Node: Lisp Interaction\7f580862
-Node: External Lisp\7f582217
-Node: Packages\7f584291
-Node: Package Terminology\7f585110
-Node: Using Packages\7f586468
-Node: Building Packages\7f595346
-Node: Available Packages\7f597895
-Node: Abbrevs\7f603278
-Node: Defining Abbrevs\7f605477
-Node: Expanding Abbrevs\7f607924
-Node: Editing Abbrevs\7f610626
-Node: Saving Abbrevs\7f612499
-Node: Dynamic Abbrevs\7f614454
-Node: Picture\7f615756
-Node: Basic Picture\7f618189
-Node: Insert in Picture\7f620474
-Node: Tabs in Picture\7f621896
-Node: Rectangles in Picture\7f623417
-Node: Sending Mail\7f625325
-Node: Mail Format\7f627036
-Node: Mail Headers\7f628386
-Node: Mail Mode\7f634794
-Node: Reading Mail\7f638407
-Node: Calendar/Diary\7f639982
-Node: Calendar Motion\7f641654
-Node: Calendar Unit Motion\7f642537
-Node: Move to Beginning or End\7f644860
-Node: Specified Dates\7f645993
-Node: Scroll Calendar\7f646881
-Node: Mark and Region\7f648672
-Node: General Calendar\7f650578
-Node: LaTeX Calendar\7f652186
-Node: Holidays\7f654200
-Node: Sunrise/Sunset\7f657302
-Node: Lunar Phases\7f660341
-Node: Other Calendars\7f661726
-Node: Calendar Systems\7f663213
-Node: To Other Calendar\7f666324
-Node: From Other Calendar\7f668315
-Node: Mayan Calendar\7f670620
-Node: Diary\7f673815
-Node: Diary Commands\7f675564
-Node: Format of Diary File\7f678887
-Node: Date Formats\7f681757
-Node: Adding to Diary\7f684331
-Node: Special Diary Entries\7f685962
-Node: Calendar Customization\7f691301
-Node: Calendar Customizing\7f692163
-Node: Holiday Customizing\7f695398
-Node: Date Display Format\7f701885
-Node: Time Display Format\7f702843
-Node: Daylight Savings\7f703981
-Node: Diary Customizing\7f707169
-Node: Hebrew/Islamic Entries\7f711790
-Node: Fancy Diary Display\7f715130
-Node: Included Diary Files\7f717046
-Node: Sexp Diary Entries\7f718027
-Node: Appt Customizing\7f723117
-Node: Sorting\7f724163
-Node: Shell\7f728969
-Node: Single Shell\7f730262
-Node: Interactive Shell\7f731876
-Node: Shell Mode\7f735641
-Node: Terminal emulator\7f738132
-Node: Term Mode\7f740441
-Node: Paging in Term\7f741355
-Node: Narrowing\7f742153
-Node: Hardcopy\7f744103
-Node: Recursive Edit\7f745075
-Node: Dissociated Press\7f748062
-Node: CONX\7f750625
-Node: Amusements\7f751649
-Node: Emulation\7f752129
-Node: Customization\7f753989
-Node: Minor Modes\7f755805
-Node: Variables\7f757437
-Node: Examining\7f759393
-Node: Easy Customization\7f760854
-Node: Customization Groups\7f761868
-Node: Changing an Option\7f764797
-Node: Face Customization\7f771067
-Node: Specific Customization\7f772831
-Node: Edit Options\7f775438
-Node: Locals\7f777022
-Node: File Variables\7f780201
-Node: Keyboard Macros\7f784751
-Node: Basic Kbd Macro\7f786922
-Node: Save Kbd Macro\7f788854
-Node: Kbd Macro Query\7f790512
-Node: Key Bindings\7f792454
-Node: Keymaps\7f793328
-Node: Rebinding\7f797178
-Node: Interactive Rebinding\7f797877
-Node: Programmatic Rebinding\7f800066
-Node: Key Bindings Using Strings\7f802873
-Node: Disabling\7f804500
-Node: Syntax\7f806279
-Node: Syntax Entry\7f807160
-Node: Syntax Change\7f811244
-Node: Init File\7f813413
-Node: Init Syntax\7f814877
-Node: Init Examples\7f817228
-Node: Terminal Init\7f821418
-Node: Audible Bell\7f823155
-Node: Faces\7f826586
-Node: Frame Components\7f831428
-Node: X Resources\7f831873
-Node: Geometry Resources\7f833532
-Node: Iconic Resources\7f835980
-Node: Resource List\7f836452
-Node: Face Resources\7f842959
-Node: Widgets\7f846636
-Node: Menubar Resources\7f847575
-Node: Quitting\7f849089
-Node: Lossage\7f852067
-Node: Stuck Recursive\7f852711
-Node: Screen Garbled\7f853417
-Node: Text Garbled\7f854551
-Node: Unasked-for Search\7f855190
-Node: Emergency Escape\7f855975
-Node: Total Frustration\7f857754
-Node: Bugs\7f858385
-Node: Glossary\7f867946
-Node: Manifesto\7f899600
-Node: Key Index\7f923077
-Node: Command Index\7f949004
-Node: Variable Index\7f991590
-Node: Concept Index\7f1007676
+Node: Point\7f44652
+Node: Echo Area\7f46619
+Node: Mode Line\7f48996
+Node: GUI Components\7f53427
+Node: Menubar Basics\7f54657
+Node: Scrollbar Basics\7f56573
+Node: Toolbar Basics\7f57464
+Node: Gutter Basics\7f58131
+Node: Inhibiting\7f60185
+Node: Customizing\7f62556
+Node: XEmacs under X\7f62805
+Node: XEmacs under MS Windows\7f66019
+Node: Keystrokes\7f66434
+Node: Intro to Keystrokes\7f67278
+Node: Representing Keystrokes\7f69381
+Node: Key Sequences\7f70738
+Node: String Key Sequences\7f74079
+Node: Meta Key\7f74462
+Node: Super and Hyper Keys\7f75935
+Node: Character Representation\7f82180
+Node: Commands\7f83200
+Node: Pull-down Menus\7f86049
+Node: File Menu\7f89398
+Node: Edit Menu\7f93220
+Node: Apps Menu\7f95603
+Node: Options Menu\7f96093
+Node: Buffers Menu\7f100111
+Node: Tools Menu\7f100418
+Node: Help Menu\7f100909
+Node: Menu Customization\7f101310
+Node: Entering Emacs\7f105540
+Node: Exiting\7f108437
+Node: Command Switches\7f112910
+Node: Startup Paths\7f122932
+Node: Basic\7f130262
+Node: Inserting Text\7f131666
+Node: Moving Point\7f134662
+Node: Erasing\7f138268
+Node: Basic Files\7f139573
+Node: Basic Help\7f141495
+Node: Blank Lines\7f142090
+Node: Continuation Lines\7f143666
+Node: Position Info\7f145333
+Node: Arguments\7f148749
+Node: Undo\7f152848
+Node: Minibuffer\7f155795
+Node: Minibuffer File\7f158405
+Node: Minibuffer Edit\7f160210
+Node: Completion\7f163151
+Node: Completion Example\7f165082
+Node: Completion Commands\7f166177
+Node: Strict Completion\7f169153
+Node: Completion Options\7f170934
+Node: Minibuffer History\7f172442
+Node: Repetition\7f175626
+Node: M-x\7f178471
+Node: Help\7f183565
+Node: Help Summary\7f184975
+Node: Key Help\7f187761
+Node: Name Help\7f188720
+Node: Apropos\7f191365
+Node: Library Keywords\7f194484
+Node: Help Mode\7f196805
+Node: Misc Help\7f197302
+Node: Mark\7f200450
+Node: Setting Mark\7f202304
+Node: Using Region\7f205426
+Node: Marking Objects\7f206163
+Node: Mark Ring\7f208001
+Node: Mouse Selection\7f209717
+Node: Additional Mouse Operations\7f211724
+Node: Killing\7f215928
+Node: Yanking\7f221564
+Node: Kill Ring\7f222367
+Node: Appending Kills\7f223969
+Node: Earlier Kills\7f226006
+Node: Using X Selections\7f228619
+Node: X Clipboard Selection\7f229869
+Node: X Selection Commands\7f232046
+Node: X Cut Buffers\7f233132
+Node: Active Regions\7f234491
+Node: Accumulating Text\7f239071
+Node: Rectangles\7f242144
+Node: Registers\7f245663
+Node: RegPos\7f247117
+Node: RegText\7f248273
+Node: RegRect\7f249379
+Node: RegConfig\7f250258
+Node: RegNumbers\7f251198
+Node: RegFiles\7f251916
+Node: Bookmarks\7f252574
+Node: Display\7f255946
+Node: Scrolling\7f257441
+Node: Horizontal Scrolling\7f261584
+Node: Selective Display\7f262779
+Node: Display Vars\7f263998
+Node: Search\7f266676
+Node: Incremental Search\7f267869
+Node: Non-Incremental Search\7f276797
+Node: Word Search\7f278239
+Node: Regexp Search\7f279857
+Node: Regexps\7f282227
+Node: Search Case\7f296224
+Node: Replace\7f297005
+Node: Unconditional Replace\7f297953
+Node: Regexp Replace\7f299088
+Node: Replacement and Case\7f300023
+Node: Query Replace\7f301003
+Node: Other Repeating Search\7f304230
+Node: Fixit\7f305485
+Node: Kill Errors\7f306065
+Node: Transpose\7f307398
+Node: Fixing Case\7f309802
+Node: Spelling\7f310448
+Node: Files\7f311909
+Node: File Names\7f313219
+Node: Visiting\7f317556
+Node: Saving\7f324388
+Node: Backup\7f329311
+Node: Backup Names\7f330707
+Node: Backup Deletion\7f332190
+Node: Backup Copying\7f333340
+Node: Interlocking\7f335046
+Node: Reverting\7f339174
+Node: Auto Save\7f341086
+Node: Auto Save Files\7f342053
+Node: Auto Save Control\7f343894
+Node: Recover\7f345732
+Node: Version Control\7f346887
+Node: Concepts of VC\7f348925
+Node: Editing with VC\7f350535
+Node: Variables for Check-in/out\7f355791
+Node: Log Entries\7f357690
+Node: Change Logs and VC\7f358870
+Node: Old Versions\7f362137
+Node: VC Status\7f364140
+Node: Renaming and VC\7f365854
+Node: Snapshots\7f366533
+Node: Making Snapshots\7f367034
+Node: Snapshot Caveats\7f368327
+Node: Version Headers\7f370136
+Node: ListDir\7f372835
+Node: Comparing Files\7f374884
+Node: Dired\7f376417
+Node: Dired Enter\7f377088
+Node: Dired Edit\7f377913
+Node: Dired Deletion\7f379660
+Node: Dired Immed\7f382883
+Node: Misc File Ops\7f384159
+Node: Buffers\7f386647
+Node: Select Buffer\7f388805
+Node: List Buffers\7f390600
+Node: Misc Buffer\7f392358
+Node: Kill Buffer\7f394001
+Node: Several Buffers\7f395131
+Node: Windows\7f398998
+Node: Basic Window\7f399709
+Node: Split Window\7f401428
+Node: Other Window\7f403561
+Node: Pop Up Window\7f405992
+Node: Change Window\7f407497
+Node: Mule\7f410405
+Node: Mule Intro\7f411668
+Node: Language Environments\7f412684
+Node: Input Methods\7f414791
+Node: Select Input Method\7f418511
+Node: Coding Systems\7f420666
+Node: Recognize Coding\7f424852
+Node: Specify Coding\7f428178
+Node: Major Modes\7f433109
+Node: Choosing Modes\7f435328
+Node: Indentation\7f437718
+Node: Indentation Commands\7f439813
+Node: Tab Stops\7f442542
+Node: Just Spaces\7f444391
+Node: Text\7f445206
+Node: Text Mode\7f447189
+Node: Nroff Mode\7f449268
+Node: TeX Mode\7f450911
+Node: TeX Editing\7f453163
+Node: TeX Print\7f456597
+Node: Outline Mode\7f459816
+Node: Outline Format\7f461297
+Node: Outline Motion\7f464097
+Node: Outline Visibility\7f465650
+Node: Words\7f468571
+Node: Sentences\7f471518
+Node: Paragraphs\7f473714
+Node: Pages\7f476002
+Node: Filling\7f478602
+Node: Auto Fill\7f479173
+Node: Fill Commands\7f481320
+Node: Fill Prefix\7f483485
+Node: Case\7f485673
+Node: Programs\7f487701
+Node: Program Modes\7f490251
+Node: Lists\7f492483
+Node: Defuns\7f498323
+Node: Grinding\7f500976
+Node: Basic Indent\7f501604
+Node: Multi-line Indent\7f503625
+Node: Lisp Indent\7f505241
+Node: C Indent\7f508691
+Node: Matching\7f513931
+Node: Comments\7f515453
+Node: Balanced Editing\7f521905
+Node: Lisp Completion\7f522919
+Node: Documentation\7f523934
+Node: Change Log\7f525173
+Node: Tags\7f527751
+Node: Tag Syntax\7f529400
+Node: Create Tags Table\7f533344
+Node: Etags Regexps\7f537404
+Node: Select Tags Table\7f542062
+Node: Find Tag\7f545835
+Node: Tags Search\7f548799
+Node: List Tags\7f552255
+Node: Fortran\7f553284
+Node: Fortran Motion\7f554360
+Node: Fortran Indent\7f555180
+Node: ForIndent Commands\7f555865
+Node: ForIndent Num\7f557010
+Node: ForIndent Conv\7f558284
+Node: ForIndent Vars\7f559060
+Node: Fortran Comments\7f560228
+Node: Fortran Columns\7f563826
+Node: Fortran Abbrev\7f565249
+Node: Asm Mode\7f566158
+Node: Running\7f566710
+Node: Compilation\7f567679
+Node: Lisp Modes\7f572529
+Node: Lisp Libraries\7f573802
+Node: Loading\7f574356
+Node: Compiling Libraries\7f578816
+Node: Mocklisp\7f581707
+Node: Lisp Eval\7f582384
+Node: Lisp Debug\7f586024
+Node: Lisp Interaction\7f591451
+Node: External Lisp\7f592806
+Node: Packages\7f594880
+Node: Package Terminology\7f595735
+Node: Using Packages\7f597093
+Node: Building Packages\7f605971
+Node: Creating Packages\7f608514
+Node: Available Packages\7f613514
+Node: Abbrevs\7f618787
+Node: Defining Abbrevs\7f620986
+Node: Expanding Abbrevs\7f623433
+Node: Editing Abbrevs\7f626135
+Node: Saving Abbrevs\7f628008
+Node: Dynamic Abbrevs\7f629963
+Node: Picture\7f631265
+Node: Basic Picture\7f633698
+Node: Insert in Picture\7f635983
+Node: Tabs in Picture\7f637405
+Node: Rectangles in Picture\7f638926
+Node: Sending Mail\7f640834
+Node: Mail Format\7f642545
+Node: Mail Headers\7f643895
+Node: Mail Mode\7f650303
+Node: Reading Mail\7f653916
+Node: Calendar/Diary\7f655491
+Node: Calendar Motion\7f657165
+Node: Calendar Unit Motion\7f658048
+Node: Move to Beginning or End\7f660371
+Node: Specified Dates\7f661504
+Node: Scroll Calendar\7f662392
+Node: Mark and Region\7f664183
+Node: General Calendar\7f666089
+Node: LaTeX Calendar\7f667697
+Node: Holidays\7f669711
+Node: Sunrise/Sunset\7f672813
+Node: Lunar Phases\7f675852
+Node: Other Calendars\7f677237
+Node: Calendar Systems\7f678724
+Node: To Other Calendar\7f681835
+Node: From Other Calendar\7f683826
+Node: Mayan Calendar\7f686131
+Node: Diary\7f689326
+Node: Diary Commands\7f691075
+Node: Format of Diary File\7f694398
+Node: Date Formats\7f697268
+Node: Adding to Diary\7f699842
+Node: Special Diary Entries\7f701473
+Node: Calendar Customization\7f706812
+Node: Calendar Customizing\7f707674
+Node: Holiday Customizing\7f710909
+Node: Date Display Format\7f717396
+Node: Time Display Format\7f718354
+Node: Daylight Savings\7f719492
+Node: Diary Customizing\7f722680
+Node: Hebrew/Islamic Entries\7f727301
+Node: Fancy Diary Display\7f730641
+Node: Included Diary Files\7f732557
+Node: Sexp Diary Entries\7f733538
+Node: Appt Customizing\7f738628
+Node: Sorting\7f739674
+Node: Shell\7f744480
+Node: Single Shell\7f745773
+Node: Interactive Shell\7f747387
+Node: Shell Mode\7f751152
+Node: Terminal emulator\7f753643
+Node: Term Mode\7f755952
+Node: Paging in Term\7f756866
+Node: Narrowing\7f757664
+Node: Hardcopy\7f759614
+Node: Recursive Edit\7f760586
+Node: Dissociated Press\7f763573
+Node: CONX\7f766136
+Node: Amusements\7f767160
+Node: Emulation\7f767640
+Node: Customization\7f769500
+Node: Minor Modes\7f771316
+Node: Variables\7f772948
+Node: Examining\7f774904
+Node: Easy Customization\7f776365
+Node: Customization Groups\7f777379
+Node: Changing an Option\7f780308
+Node: Face Customization\7f786578
+Node: Specific Customization\7f788342
+Node: Edit Options\7f790949
+Node: Locals\7f792533
+Node: File Variables\7f795712
+Node: Keyboard Macros\7f800262
+Node: Basic Kbd Macro\7f802433
+Node: Save Kbd Macro\7f804365
+Node: Kbd Macro Query\7f806023
+Node: Key Bindings\7f807965
+Node: Keymaps\7f808839
+Node: Rebinding\7f812689
+Node: Interactive Rebinding\7f813388
+Node: Programmatic Rebinding\7f815577
+Node: Key Bindings Using Strings\7f818384
+Node: Disabling\7f820011
+Node: Syntax\7f821790
+Node: Syntax Entry\7f822671
+Node: Syntax Change\7f826755
+Node: Init File\7f828924
+Node: Init Syntax\7f830388
+Node: Init Examples\7f832739
+Node: Terminal Init\7f836929
+Node: Audible Bell\7f838666
+Node: Faces\7f842097
+Node: Frame Components\7f846939
+Node: X Resources\7f847384
+Node: Geometry Resources\7f849043
+Node: Iconic Resources\7f851491
+Node: Resource List\7f851963
+Node: Face Resources\7f858470
+Node: Widgets\7f862147
+Node: Menubar Resources\7f863086
+Node: Quitting\7f864600
+Node: Lossage\7f867578
+Node: Stuck Recursive\7f868222
+Node: Screen Garbled\7f868928
+Node: Text Garbled\7f870062
+Node: Unasked-for Search\7f870701
+Node: Emergency Escape\7f871486
+Node: Total Frustration\7f873265
+Node: Bugs\7f873896
+Node: Glossary\7f883457
+Node: Manifesto\7f915111
+Node: Key Index\7f938588
+Node: Command Index\7f964515
+Node: Variable Index\7f1007101
+Node: Concept Index\7f1023187
\1f
End Tag Table
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
modification follow.
TERMS AND CONDITIONS
-
1. This License Agreement applies to any program or other work which
contains a notice placed by the copyright holder saying it may be
distributed under the terms of this General Public License. The
menu bar at the top of the frame makes shortcuts to several of the
commands available (*note Pull-down Menus::).
- * If you are running XEmacs under a graphical windowing system, a
- toolbar at the top of the frame, just under the menu bar if it
- exists, provides "one-touch" shortcuts to several commands. (Not
- yet documented.)
+ * Under a graphical windowing system, a toolbar at the top of the
+ frame, just under the menu bar if it exists, provides "one-touch"
+ shortcuts to several commands. (Not yet documented.)
- * If you are running XEmacs under a graphical windowing system, a
- gutter at the top (under the toolbar) and/or bottom of the frame
- provides advanced GUI facilities like tab controls for rapid
- switching among related windows and progress bars for
- time-consuming operations like downloads across the Internet.
- Gutters are an experimental feature introduced in XEmacs version
- 21.2. (Not yet documented.)
+ * Under a graphical windowing system, a gutter at the top (under the
+ toolbar) and/or bottom of the frame provides advanced GUI
+ facilities like tab controls for rapid switching among related
+ windows and progress bars for time-consuming operations like
+ downloads across the Internet. Gutters are an experimental feature
+ introduced in XEmacs version 21.2. (Not yet documented.)
You can subdivide the XEmacs frame into multiple text windows, and
use each window for a different file (*note Windows::). Multiple XEmacs
* Point:: The place in the text where editing commands operate.
* Echo Area:: Short messages appear at the bottom of the frame.
* Mode Line:: Interpreting the mode line.
+* GUI Components:: Menubar, toolbars, gutters.
* XEmacs under X:: Some information on using XEmacs under the X
Window System.
+* XEmacs under MS Windows:: Some information on using XEmacs under
+ Microsoft Windows.
\1f
File: xemacs.info, Node: Point, Next: Echo Area, Prev: Frame, Up: Frame
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Specify Coding, Prev: Recognize Coding, Up: Mule
+
+Specifying a Coding System
+==========================
+
+ In cases where XEmacs does not automatically choose the right coding
+system, you can use these commands to specify one:
+
+`C-x <RET> f CODING <RET>'
+ Use coding system CODING for the visited file in the current
+ buffer.
+
+`C-x <RET> c CODING <RET>'
+ Specify coding system CODING for the immediately following command.
+
+`C-x <RET> k CODING <RET>'
+ Use coding system CODING for keyboard input.
+
+`C-x <RET> t CODING <RET>'
+ Use coding system CODING for terminal output.
+
+`C-x <RET> p CODING <RET>'
+ Use coding system CODING for subprocess input and output in the
+ current buffer.
+
+ The command `C-x RET f' (`set-buffer-file-coding-system') specifies
+the file coding system for the current buffer--in other words, which
+coding system to use when saving or rereading the visited file. You
+specify which coding system using the minibuffer. Since this command
+applies to a file you have already visited, it affects only the way the
+file is saved.
+
+ Another way to specify the coding system for a file is when you visit
+the file. First use the command `C-x <RET> c'
+(`universal-coding-system-argument'); this command uses the minibuffer
+to read a coding system name. After you exit the minibuffer, the
+specified coding system is used for _the immediately following command_.
+
+ So if the immediately following command is `C-x C-f', for example,
+it reads the file using that coding system (and records the coding
+system for when the file is saved). Or if the immediately following
+command is `C-x C-w', it writes the file using that coding system.
+Other file commands affected by a specified coding system include `C-x
+C-i' and `C-x C-v', as well as the other-window variants of `C-x C-f'.
+
+ In addition, if you run some file input commands with the precedent
+`C-u', you can specify coding system to read from minibuffer. So if
+the immediately following command is `C-x C-f', for example, it reads
+the file using that coding system (and records the coding system for
+when the file is saved). Other file commands affected by a specified
+coding system include `C-x C-i' and `C-x C-v', as well as the
+other-window variants of `C-x C-f'.
+
+ The variable `default-buffer-file-coding-system' specifies the
+choice of coding system to use when you create a new file. It applies
+when you find a new file, and when you create a buffer and then save it
+in a file. Selecting a language environment typically sets this
+variable to a good choice of default coding system for that language
+environment.
+
+ The command `C-x <RET> t' (`set-terminal-coding-system') specifies
+the coding system for terminal output. If you specify a character code
+for terminal output, all characters output to the terminal are
+translated into that coding system.
+
+ This feature is useful for certain character-only terminals built to
+support specific languages or character sets--for example, European
+terminals that support one of the ISO Latin character sets.
+
+ By default, output to the terminal is not translated at all.
+
+ The command `C-x <RET> k' (`set-keyboard-coding-system') specifies
+the coding system for keyboard input. Character-code translation of
+keyboard input is useful for terminals with keys that send non-ASCII
+graphic characters--for example, some terminals designed for ISO
+Latin-1 or subsets of it.
+
+ By default, keyboard input is not translated at all.
+
+ There is a similarity between using a coding system translation for
+keyboard input, and using an input method: both define sequences of
+keyboard input that translate into single characters. However, input
+methods are designed to be convenient for interactive use by humans, and
+the sequences that are translated are typically sequences of ASCII
+printing characters. Coding systems typically translate sequences of
+non-graphic characters.
+
+ The command `C-x <RET> p' (`set-buffer-process-coding-system')
+specifies the coding system for input and output to a subprocess. This
+command applies to the current buffer; normally, each subprocess has its
+own buffer, and thus you can use this command to specify translation to
+and from a particular subprocess by giving the command in the
+corresponding buffer.
+
+ By default, process input and output are not translated at all.
+
+ The variable `file-name-coding-system' specifies a coding system to
+use for encoding file names. If you set the variable to a coding
+system name (as a Lisp symbol or a string), XEmacs encodes file names
+using that coding system for all file operations. This makes it
+possible to use non-Latin-1 characters in file names--or, at least,
+those non-Latin-1 characters which the specified coding system can
+encode. By default, this variable is `nil', which implies that you
+cannot use non-Latin-1 characters in file names.
+
+\1f
+File: xemacs.info, Node: Major Modes, Next: Indentation, Prev: Mule, Up: Top
+
+Major Modes
+***********
+
+ Emacs has many different "major modes", each of which customizes
+Emacs for editing text of a particular sort. The major modes are
+mutually exclusive; at any time, each buffer has one major mode. The
+mode line normally contains the name of the current major mode in
+parentheses. *Note Mode Line::.
+
+ The least specialized major mode is called "Fundamental mode". This
+mode has no mode-specific redefinitions or variable settings. Each
+Emacs command behaves in its most general manner, and each option is in
+its default state. For editing any specific type of text, such as Lisp
+code or English text, you should switch to the appropriate major mode,
+such as Lisp mode or Text mode.
+
+ Selecting a major mode changes the meanings of a few keys to become
+more specifically adapted to the language being edited. <TAB>, <DEL>,
+and <LFD> are changed frequently. In addition, commands which handle
+comments use the mode to determine how to delimit comments. Many major
+modes redefine the syntactical properties of characters appearing in
+the buffer. *Note Syntax::.
+
+ The major modes fall into three major groups. Lisp mode (which has
+several variants), C mode, and Muddle mode are for specific programming
+languages. Text mode, Nroff mode, TeX mode, and Outline mode are for
+editing English text. The remaining major modes are not intended for
+use on users' files; they are used in buffers created by Emacs for
+specific purposes and include Dired mode for buffers made by Dired
+(*note Dired::), Mail mode for buffers made by `C-x m' (*note Sending
+Mail::), and Shell mode for buffers used for communicating with an
+inferior shell process (*note Interactive Shell::).
+
+ Most programming language major modes specify that only blank lines
+separate paragraphs. This is so that the paragraph commands remain
+useful. *Note Paragraphs::. They also cause Auto Fill mode to use the
+definition of <TAB> to indent the new lines it creates. This is
+because most lines in a program are usually indented. *Note
+Indentation::.
+
+* Menu:
+
+* Choosing Modes:: How major modes are specified or chosen.
+
+\1f
+File: xemacs.info, Node: Choosing Modes, Prev: Major Modes, Up: Major Modes
+
+Choosing Major Modes
+====================
+
+ You can select a major mode explicitly for the current buffer, but
+most of the time Emacs determines which mode to use based on the file
+name or some text in the file.
+
+ Use a `M-x' command to explicitly select a new major mode. Add
+`-mode' to the name of a major mode to get the name of a command to
+select that mode. For example, to enter Lisp mode, execute `M-x
+lisp-mode'.
+
+ When you visit a file, Emacs usually chooses the right major mode
+based on the file's name. For example, files whose names end in `.c'
+are edited in C mode. The variable `auto-mode-alist' controls the
+correspondence between file names and major mode. Its value is a list
+in which each element has the form:
+
+ (REGEXP . MODE-FUNCTION)
+
+For example, one element normally found in the list has the form
+`("\\.c$" . c-mode)'. It is responsible for selecting C mode for files
+whose names end in `.c'. (Note that `\\' is needed in Lisp syntax to
+include a `\' in the string, which is needed to suppress the special
+meaning of `.' in regexps.) The only practical way to change this
+variable is with Lisp code.
+
+ You can specify which major mode should be used for editing a certain
+file by a special sort of text in the first non-blank line of the file.
+The mode name should appear in this line both preceded and followed by
+`-*-'. Other text may appear on the line as well. For example,
+
+ ;-*-Lisp-*-
+
+tells Emacs to use Lisp mode. Note how the semicolon is used to make
+Lisp treat this line as a comment. Such an explicit specification
+overrides any default mode based on the file name.
+
+ Another format of mode specification is:
+
+ -*-Mode: MODENAME;-*-
+
+which allows other things besides the major mode name to be specified.
+However, Emacs does not look for anything except the mode name.
+
+ The major mode can also be specified in a local variables list.
+*Note File Variables::.
+
+ When you visit a file that does not specify a major mode to use, or
+when you create a new buffer with `C-x b', Emacs uses the major mode
+specified by the variable `default-major-mode'. Normally this value is
+the symbol `fundamental-mode', which specifies Fundamental mode. If
+`default-major-mode' is `nil', the major mode is taken from the
+previously selected buffer.
+
+\1f
+File: xemacs.info, Node: Indentation, Next: Text, Prev: Major Modes, Up: Top
+
+Indentation
+***********
+
+`<TAB>'
+ Indent current line "appropriately" in a mode-dependent fashion.
+
+`<LFD>'
+ Perform <RET> followed by <TAB> (`newline-and-indent').
+
+`M-^'
+ Merge two lines (`delete-indentation'). This would cancel out the
+ effect of <LFD>.
+
+`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
+ (`split-line').
+
+`M-m'
+ Move (forward or back) to the first non-blank character on the
+ current line (`back-to-indentation').
+
+`C-M-\'
+ Indent several lines to same column (`indent-region').
+
+`C-x <TAB>'
+ Shift block of lines rigidly right or left (`indent-rigidly').
+
+`M-i'
+ Indent from point to the next prespecified tab stop column
+ (`tab-to-tab-stop').
+
+`M-x indent-relative'
+ Indent from point to under an indentation point in the previous
+ line.
+
+ 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 <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, <TAB> aligns a line according
+to its depth in parentheses. No matter where in the line you are when
+you type <TAB>, it aligns the line as a whole. In C mode, <TAB>
+implements a subtle and sophisticated indentation style that knows
+about many aspects of C syntax.
+
+ In Text mode, <TAB> runs the command `tab-to-tab-stop', which
+indents to the next tab stop column. You can set the tab stops with
+`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.
+
+\1f
+File: xemacs.info, Node: Indentation Commands, Next: Tab Stops, Prev: Indentation, Up: Indentation
+
+Indentation Commands and Techniques
+===================================
+
+ If you just want to insert a tab character in the buffer, you can
+type `C-q <TAB>'.
+
+ To move over the indentation on a line, type `Meta-m'
+(`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 `C-a C-o
+<TAB>'. To make an indented line after the current line, use `C-e
+<LFD>'.
+
+ `C-M-o' (`split-line') moves the text from point to the end of the
+line vertically down, so that the current line becomes two lines.
+`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, `C-M-o' resembles `C-o'.
+
+ To join two lines cleanly, use the `Meta-^' (`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 `Meta-\'
+(`delete-horizontal-space'), which deletes all spaces and tabs around
+the cursor.
+
+ There are also commands for changing the indentation of several
+lines at once. `Control-Meta-\' (`indent-region') gives each line which
+begins in the region the "usual" indentation by invoking <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. `C-x <TAB>'
+(`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.
+
+ `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, `tab-to-tab-stop' is run
+(see next section).
+
+ `indent-relative' is the definition of <TAB> in Indented Text mode.
+*Note Text::.
+
+\1f
+File: xemacs.info, Node: Tab Stops, Next: Just Spaces, Prev: Indentation Commands, Up: Indentation
+
+Tab Stops
+=========
+
+ For typing in tables, you can use Text mode's definition of <TAB>,
+`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 `M-i' anyway.
+
+ You can arbitrarily set the tab stops used by `M-i'. They are
+stored as a list of column-numbers in increasing order in the variable
+`tab-stop-list'.
+
+ The convenient way to set the tab stops is using `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 `C-c C-c' to make those new
+tab stops take effect. In the tab stop buffer, `C-c C-c' runs the
+function `edit-tab-stops-note-changes' rather than the default
+`save-buffer'. `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 `tab-stop-list' local in one buffer
+`edit-tab-stops' in that buffer edits only the local settings.
+
+ Below is the text representing ordinary tab stops every eight
+columns:
+
+ : : : : : :
+ 0 1 2 3 4
+ 0123456789012345678901234567890123456789012345678
+ To install changes, type C-c C-c
+
+ 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 `tab-to-tab-stop' have nothing
+to do with displaying tab characters in the buffer. *Note Display
+Vars::, for more information on that.
+
+\1f
+File: xemacs.info, Node: Just Spaces, Prev: Tab Stops, Up: Indentation
+
+Tabs vs. Spaces
+===============
+
+ 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 `indent-tabs-mode' to `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. *Note Locals::.
+
+ There are also commands to convert tabs to spaces or vice versa,
+always preserving the columns of all non-blank text. `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. `M-x untabify' changes all tabs in the region to
+corresponding numbers of spaces.
+
+\1f
+File: xemacs.info, Node: Text, Next: Programs, Prev: Indentation, Up: Top
+
+Commands for Human Languages
+****************************
+
+ The term "text" has two widespread meanings in our area of the
+computer field. One is data that is a sequence of characters. In this
+sense of the word any file that you edit with Emacs is text. The other
+meaning is more restrictive: a sequence of characters in a human
+language for humans to read (possibly after processing by a text
+formatter), as opposed to a program or commands for a program.
+
+ Human languages have syntactic and stylistic conventions that editor
+commands should support or use to advantage: conventions involving
+words, sentences, paragraphs, and capital letters. This chapter
+describes Emacs commands for all these things. There are also commands
+for "filling", or rearranging paragraphs into lines of approximately
+equal length. The commands for moving over and killing words,
+sentences, and paragraphs, while intended primarily for editing text,
+are also often useful for editing programs.
+
+ Emacs has several major modes for editing human language text. If a
+file contains plain text, use Text mode, which customizes Emacs in
+small ways for the syntactic conventions of text. For text which
+contains embedded commands for text formatters, Emacs has other major
+modes, each for a particular text formatter. Thus, for input to TeX,
+you can use TeX mode; for input to nroff, Nroff mode.
+
+* Menu:
+
+* Text Mode:: The major modes for editing text files.
+* Nroff Mode:: The major mode for editing input to the formatter nroff.
+* TeX Mode:: The major modes for editing input to the formatter TeX.
+* Outline Mode:: The major mode for editing outlines.
+* Words:: Moving over and killing words.
+* Sentences:: Moving over and killing sentences.
+* Paragraphs:: Moving over paragraphs.
+* Pages:: Moving over pages.
+* Filling:: Filling or justifying text
+* Case:: Changing the case of text
+
+\1f
+File: xemacs.info, Node: Text Mode, Next: Words, Prev: Text, Up: Text
+
+Text Mode
+=========
+
+ You should use Text mode--rather than Fundamental or Lisp mode--to
+edit files of text in a human language. Invoke `M-x text-mode' to
+enter Text mode. In Text mode, <TAB> runs the function
+`tab-to-tab-stop', which allows you to use arbitrary tab stops set with
+`M-x edit-tab-stops' (*note Tab Stops::). Features concerned with
+comments in programs are turned off unless they are explicitly invoked.
+The syntax table is changed so that periods are not considered part of a
+word, while apostrophes, backspaces and underlines are.
+
+ A similar variant mode is Indented Text mode, intended for editing
+text in which most lines are indented. This mode defines <TAB> to run
+`indent-relative' (*note Indentation::), and makes Auto Fill indent the
+lines it creates. As a result, a line made by Auto Filling, or by
+<LFD>, is normally indented just like the previous line. Use `M-x
+indented-text-mode' to select this mode.
+
+ Entering Text mode or Indented Text mode calls the value of the
+variable `text-mode-hook' with no arguments, if that value exists and
+is not `nil'. This value is also called when modes related to Text
+mode are entered; this includes Nroff mode, TeX mode, Outline mode, and
+Mail mode. Your hook can look at the value of `major-mode' to see
+which of these modes is actually being entered.
+
+ Two modes similar to Text mode are of use for editing text that is to
+be passed through a text formatter before achieving its final readable
+form.
+
+* Menu:
+
+* Nroff Mode:: The major mode for editing input to the formatter nroff.
+* TeX Mode:: The major modes for editing input to the formatter TeX.
+
+
+ Another similar mode is used for editing outlines. It allows you
+to view the text at various levels of detail. You can view either
+the outline headings alone or both headings and text; you can also
+hide some of the headings at lower levels from view to make the high
+level structure more visible.
+
+
+* Outline Mode:: The major mode for editing outlines.
+
+\1f
+File: xemacs.info, Node: Nroff Mode, Next: TeX Mode, Prev: Text Mode, Up: Text Mode
+
+Nroff Mode
+----------
+
+ Nroff mode is a mode like Text mode but modified to handle nroff
+commands present in the text. Invoke `M-x nroff-mode' to enter this
+mode. Nroff mode differs from Text mode in only a few ways. All nroff
+command lines are considered paragraph separators, so that filling never
+garbles the nroff commands. Pages are separated by `.bp' commands.
+Comments start with backslash-doublequote. There are also three special
+commands that are not available in Text mode:
+
+`M-n'
+ Move to the beginning of the next line that isn't an nroff command
+ (`forward-text-line'). An argument is a repeat count.
+
+`M-p'
+ Like `M-n' but move up (`backward-text-line').
+
+`M-?'
+ Prints in the echo area the number of text lines (lines that are
+ not nroff commands) in the region (`count-text-lines').
+
+ The other feature of Nroff mode is Electric Nroff newline mode.
+This is a minor mode that you can turn on or off with `M-x
+electric-nroff-mode' (*note Minor Modes::). When the mode is on and
+you use <RET> to end a line containing an nroff command that opens a
+kind of grouping, Emacs automatically inserts the matching nroff
+command to close that grouping on the following line. For example, if
+you are at the beginning of a line and type `.(b <RET>', the matching
+command `.)b' will be inserted on a new line following point.
+
+ Entering Nroff mode calls the value of the variable `text-mode-hook'
+with no arguments, if that value exists and is not `nil'; then it does
+the same with the variable `nroff-mode-hook'.
+
+\1f
+File: xemacs.info, Node: TeX Mode, Next: Outline Mode, Prev: Nroff Mode, Up: Text Mode
+
+TeX Mode
+--------
+
+ TeX is a powerful text formatter written by Donald Knuth; like GNU
+Emacs, it is free. LaTeX is a simplified input format for TeX,
+implemented by TeX macros. It is part of TeX.
+
+ Emacs has a special TeX mode for editing TeX input files. It
+provides facilities for checking the balance of delimiters and for
+invoking TeX on all or part of the file.
+
+ TeX mode has two variants, Plain TeX mode and LaTeX mode, which are
+two distinct major modes that differ only slightly. These modes are
+designed for editing the two different input formats. The command `M-x
+tex-mode' looks at the contents of a buffer to determine whether it
+appears to be LaTeX input or not; it then selects the appropriate mode.
+If it can't tell which is right (e.g., the buffer is empty), the
+variable `tex-default-mode' controls which mode is used.
+
+ The commands `M-x plain-tex-mode' and `M-x latex-mode' explicitly
+select one of the variants of TeX mode. Use these commands when `M-x
+tex-mode' does not guess right.
+
+* Menu:
+
+* Editing: TeX Editing. Special commands for editing in TeX mode.
+* Printing: TeX Print. Commands for printing part of a file with TeX.
+
+ TeX for Unix systems can be obtained from the University of
+Washington for a distribution fee.
+
+ To order a full distribution, send $140.00 for a 1/2 inch 9-track
+tape, $165.00 for two 4-track 1/4 inch cartridge tapes (foreign sites
+$150.00, for 1/2 inch, $175.00 for 1/4 inch, to cover the extra
+postage) payable to the University of Washington to:
+
+ The Director
+ Northwest Computer Support Group, DW-10
+ University of Washington
+ Seattle, Washington 98195
+
+Purchase orders are acceptable, but there is an extra charge of $10.00
+to pay for processing charges. (The total cost comes to $150 for
+domestic sites, $175 for foreign sites).
+
+ The normal distribution is a tar tape, blocked 20, 1600 bpi, on an
+industry standard 2400 foot half-inch reel. The physical format for
+the 1/4 inch streamer cartridges uses QIC-11, 8000 bpi, 4-track
+serpentine recording for the SUN. Also, SystemV tapes can be written
+in cpio format, blocked 5120 bytes, ASCII headers.
+
+\1f
File: xemacs.info, Node: TeX Editing, Next: TeX Print, Prev: TeX Mode, Up: TeX Mode
TeX Editing Commands
The default values of these variables recognize the usual separator for
pages.
-\1f
-File: xemacs.info, Node: Pages, Next: Filling, Prev: Paragraphs, Up: Text
-
-Pages
-=====
-
- Files are often thought of as divided into "pages" by the "formfeed"
-character (ASCII Control-L, octal code 014). For example, if a file is
-printed on a line printer, each "page" of the file starts on a new page
-of paper. Emacs treats a page-separator character just like any other
-character. It can be inserted with `C-q C-l' or deleted with <DEL>.
-You are free to paginate your file or not. However, since pages are
-often meaningful divisions of the file, commands are provided to move
-over them and operate on them.
-
-`C-x ['
- Move point to previous page boundary (`backward-page').
-
-`C-x ]'
- Move point to next page boundary (`forward-page').
-
-`C-x C-p'
- Put point and mark around this page (or another page)
- (`mark-page').
-
-`C-x l'
- Count the lines in this page (`count-lines-page').
-
- The `C-x [' (`backward-page') command moves point to immediately
-after the previous page delimiter. If point is already right after a
-page delimiter, the command skips that one and stops at the previous
-one. A numeric argument serves as a repeat count. The `C-x ]'
-(`forward-page') command moves forward past the next page delimiter.
-
- The `C-x C-p' command (`mark-page') puts point at the beginning of
-the current page and the mark at the end. The page delimiter at the end
-is included (the mark follows it). The page delimiter at the front is
-excluded (point follows it). You can follow this command by `C-w' to
-kill a page you want to move elsewhere. If you insert the page after a
-page delimiter, at a place where `C-x ]' or `C-x [' would take you, the
-page will be properly delimited before and after once again.
-
- A numeric argument to `C-x C-p' is used to specify which page to go
-to, relative to the current one. Zero means the current page. One
-means the next page, and -1 means the previous one.
-
- The `C-x l' command (`count-lines-page') can help you decide where
-to break a page in two. It prints the total number of lines in the
-current page in the echo area, then divides the lines into those
-preceding the current line and those following it, for example
-
- Page has 96 (72+25) lines
-
-Notice that the sum is off by one; this is correct if point is not at
-the beginning of a line.
-
- The variable `page-delimiter' should have as its value a regexp that
-matches the beginning of a line that separates pages. This defines
-where pages begin. The normal value of this variable is `"^\f"', which
-matches a formfeed character at the beginning of a line.
-
-\1f
-File: xemacs.info, Node: Filling, Next: Case, Prev: Pages, Up: Text
-
-Filling Text
-============
-
- If you use Auto Fill mode, Emacs "fills" text (breaks it up into
-lines that fit in a specified width) as you insert it. When you alter
-existing text it is often no longer be properly filled afterwards and
-you can use explicit commands for filling.
-
-* Menu:
-
-* Auto Fill:: Auto Fill mode breaks long lines automatically.
-* Fill Commands:: Commands to refill paragraphs and center lines.
-* Fill Prefix:: Filling when every line is indented or in a comment, etc.
-
-\1f
-File: xemacs.info, Node: Auto Fill, Next: Fill Commands, Prev: Filling, Up: Filling
-
-Auto Fill Mode
---------------
-
- "Auto Fill" mode is a minor mode in which lines are broken
-automatically when they become too wide. Breaking happens only when
-you type a <SPC> or <RET>.
-
-`M-x auto-fill-mode'
- Enable or disable Auto Fill mode.
-
-`<SPC>'
-`<RET>'
- In Auto Fill mode, break lines when appropriate.
-
- `M-x auto-fill-mode' turns Auto Fill mode on if it was off, or off
-if it was on. With a positive numeric argument the command always turns
-Auto Fill mode on, and with a negative argument it always turns it off.
-The presence of the word `Fill' in the mode line, inside the
-parentheses, indicates that Auto Fill mode is in effect. Auto Fill mode
-is a minor mode; you can turn it on or off for each buffer individually.
-*Note Minor Modes::.
-
- In Auto Fill mode, lines are broken automatically at spaces when
-they get longer than desired. Line breaking and rearrangement takes
-place only when you type <SPC> or <RET>. To insert a space or newline
-without permitting line-breaking, type `C-q <SPC>' or `C-q <LFD>'
-(recall that a newline is really a linefeed). `C-o' inserts a newline
-without line breaking.
-
- Auto Fill mode works well with Lisp mode: when it makes a new line in
-Lisp mode, it indents that line with <TAB>. If a line ending in a Lisp
-comment gets too long, the text of the comment is split into two
-comment lines. Optionally, new comment delimiters are inserted at the
-end of the first line and the beginning of the second, so that each line
-is a separate comment. The variable `comment-multi-line' controls the
-choice (*note Comments::).
-
- Auto Fill mode does not refill entire paragraphs. It can break
-lines but cannot merge lines. Editing in the middle of a paragraph can
-result in a paragraph that is not correctly filled. The easiest way to
-make the paragraph properly filled again is using an explicit fill
-commands.
-
- Many users like Auto Fill mode and want to use it in all text files.
-The section on init files explains how you can arrange this permanently
-for yourself. *Note Init File::.
-
-\1f
-File: xemacs.info, Node: Fill Commands, Next: Fill Prefix, Prev: Auto Fill, Up: Filling
-
-Explicit Fill Commands
-----------------------
-
-`M-q'
- Fill current paragraph (`fill-paragraph').
-
-`M-g'
- Fill each paragraph in the region (`fill-region').
-
-`C-x f'
- Set the fill column (`set-fill-column').
-
-`M-x fill-region-as-paragraph'
- Fill the region, considering it as one paragraph.
-
-`M-s'
- Center a line.
-
- To refill a paragraph, use the command `Meta-q' (`fill-paragraph').
-It causes the paragraph containing point, or the one after point if
-point is between paragraphs, to be refilled. All line breaks are
-removed, and new ones are inserted where necessary. `M-q' can be
-undone with `C-_'. *Note Undo::.
-
- To refill many paragraphs, use `M-g' (`fill-region'), which divides
-the region into paragraphs and fills each of them.
-
- `Meta-q' and `Meta-g' use the same criteria as `Meta-h' for finding
-paragraph boundaries (*note Paragraphs::). For more control, you can
-use `M-x fill-region-as-paragraph', which refills everything between
-point and mark. This command recognizes only blank lines as paragraph
-separators.
-
- A numeric argument to `M-g' or `M-q' causes it to "justify" the text
-as well as filling it. Extra spaces are inserted to make the right
-margin line up exactly at the fill column. To remove the extra spaces,
-use `M-q' or `M-g' with no argument.
-
- The variable `auto-fill-inhibit-regexp' takes as a value a regexp to
-match lines that should not be auto-filled.
-
- The command `Meta-s' (`center-line') centers the current line within
-the current fill column. With an argument, it centers several lines
-individually and moves past them.
-
- The maximum line width for filling is in the variable `fill-column'.
-Altering the value of `fill-column' makes it local to the current
-buffer; until then, the default value--initially 70--is in effect.
-*Note Locals::.
-
- The easiest way to set `fill-column' is to use the command `C-x f'
-(`set-fill-column'). With no argument, it sets `fill-column' to the
-current horizontal position of point. With a numeric argument, it uses
-that number as the new fill column.
-
-\1f
-File: xemacs.info, Node: Fill Prefix, Prev: Fill Commands, Up: Filling
-
-The Fill Prefix
----------------
-
- To fill a paragraph in which each line starts with a special marker
-(which might be a few spaces, giving an indented paragraph), use the
-"fill prefix" feature. The fill prefix is a string which is not
-included in filling. Emacs expects every line to start with a fill
-prefix.
-
-`C-x .'
- Set the fill prefix (`set-fill-prefix').
-
-`M-q'
- Fill a paragraph using current fill prefix (`fill-paragraph').
-
-`M-x fill-individual-paragraphs'
- Fill the region, considering each change of indentation as
- starting a new paragraph.
-
- To specify a fill prefix, move to a line that starts with the desired
-prefix, put point at the end of the prefix, and give the command
-`C-x .' (`set-fill-prefix'). That's a period after the `C-x'. To turn
-off the fill prefix, specify an empty prefix: type `C-x .' with point
-at the beginning of a line.
-
- When a fill prefix is in effect, the fill commands remove the fill
-prefix from each line before filling and insert it on each line after
-filling. Auto Fill mode also inserts the fill prefix inserted on new
-lines it creates. Lines that do not start with the fill prefix are
-considered to start paragraphs, both in `M-q' and the paragraph
-commands; this is just right if you are using paragraphs with hanging
-indentation (every line indented except the first one). Lines which are
-blank or indented once the prefix is removed also separate or start
-paragraphs; this is what you want if you are writing multi-paragraph
-comments with a comment delimiter on each line.
-
- The fill prefix is stored in the variable `fill-prefix'. Its value
-is a string, or `nil' when there is no fill prefix. 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.
-*Note Locals::.
-
- Another way to use fill prefixes is through `M-x
-fill-individual-paragraphs'. This function divides the region into
-groups of consecutive lines with the same amount and kind of
-indentation and fills each group as a paragraph, using its indentation
-as a fill prefix.
-
-\1f
-File: xemacs.info, Node: Case, Prev: Filling, Up: Text
-
-Case Conversion Commands
-========================
-
- Emacs has commands for converting either a single word or any
-arbitrary range of text to upper case or to lower case.
-
-`M-l'
- Convert following word to lower case (`downcase-word').
-
-`M-u'
- Convert following word to upper case (`upcase-word').
-
-`M-c'
- Capitalize the following word (`capitalize-word').
-
-`C-x C-l'
- Convert region to lower case (`downcase-region').
-
-`C-x C-u'
- Convert region to upper case (`upcase-region').
-
- The word conversion commands are used most frequently. `Meta-l'
-(`downcase-word') converts the word after point to lower case, moving
-past it. Thus, repeating `Meta-l' converts successive words. `Meta-u'
-(`upcase-word') converts to all capitals instead, while `Meta-c'
-(`capitalize-word') puts the first letter of the word into upper case
-and the rest into lower case. The word conversion commands convert
-several words at once if given an argument. They are especially
-convenient for converting a large amount of text from all upper case to
-mixed case: you can move through the text using `M-l', `M-u', or `M-c'
-on each word as appropriate, occasionally using `M-f' instead to skip a
-word.
-
- When given a negative argument, the word case conversion commands
-apply to the appropriate number of words before point, but do not move
-point. This is convenient when you have just typed a word in the wrong
-case: you can give the case conversion command and continue typing.
-
- If a word case conversion command is given in the middle of a word,
-it applies only to the part of the word which follows point. This is
-just like what `Meta-d' (`kill-word') does. With a negative argument,
-case conversion applies only to the part of the word before point.
-
- The other case conversion commands are `C-x C-u' (`upcase-region')
-and `C-x C-l' (`downcase-region'), which convert everything between
-point and mark to the specified case. Point and mark do not move.
-
-\1f
-File: xemacs.info, Node: Programs, Next: Running, Prev: Text, Up: Top
-
-Editing Programs
-****************
-
- Emacs has many commands designed to understand the syntax of
-programming languages such as Lisp and C. These commands can:
-
- * Move over or kill balanced expressions or "sexps" (*note Lists::).
-
- * Move over or mark top-level balanced expressions ("defuns", in
- Lisp; functions, in C).
-
- * Show how parentheses balance (*note Matching::).
-
- * Insert, kill, or align comments (*note Comments::).
-
- * Follow the usual indentation conventions of the language (*note
- Grinding::).
-
- The commands available for words, sentences, and paragraphs are
-useful in editing code even though their canonical application is for
-editing human language text. Most symbols contain words (*note
-Words::); sentences can be found in strings and comments (*note
-Sentences::). Paragraphs per se are not present in code, but the
-paragraph commands are useful anyway, because Lisp mode and C mode
-define paragraphs to begin and end at blank lines (*note Paragraphs::).
-Judicious use of blank lines to make the program clearer also provides
-interesting chunks of text for the paragraph commands to work on.
-
- The selective display feature is useful for looking at the overall
-structure of a function (*note Selective Display::). This feature
-causes only the lines that are indented less than a specified amount to
-appear on the screen.
-
-* Menu:
-
-* Program Modes:: Major modes for editing programs.
-* Lists:: Expressions with balanced parentheses.
- There are editing commands to operate on them.
-* Defuns:: Each program is made up of separate functions.
- There are editing commands to operate on them.
-* Grinding:: Adjusting indentation to show the nesting.
-* Matching:: Insertion of a close-delimiter flashes matching open.
-* Comments:: Inserting, filling and aligning comments.
-* Balanced Editing:: Inserting two matching parentheses at once, etc.
-* Lisp Completion:: Completion on symbol names in Lisp code.
-* Documentation:: Getting documentation of functions you plan to call.
-* Change Log:: Maintaining a change history for your program.
-* Tags:: Go direct to any function in your program in one
- command. Tags remembers which file it is in.
-* Fortran:: Fortran mode and its special features.
-* Asm Mode:: Asm mode and its special features.
-
-\1f
-File: xemacs.info, Node: Program Modes, Next: Lists, Prev: Programs, Up: Programs
-
-Major Modes for Programming Languages
-=====================================
-
- Emacs has several major modes for the programming languages Lisp,
-Scheme (a variant of Lisp), C, Fortran, and Muddle. Ideally, a major
-mode should be implemented for each programming language you might want
-to edit with Emacs; but often the mode for one language can serve for
-other syntactically similar languages. The language modes that exist
-are those that someone decided to take the trouble to write.
-
- There are several variants of Lisp mode, which differ in the way they
-interface to Lisp execution. *Note Lisp Modes::.
-
- Each of the programming language modes defines the <TAB> key to run
-an indentation function that knows the indentation conventions of that
-language and updates the current line's indentation accordingly. For
-example, in C mode <TAB> is bound to `c-indent-line'. <LFD> is
-normally defined to do <RET> followed by <TAB>; thus it, too, indents
-in a mode-specific fashion.
-
- In most programming languages, indentation is likely to vary from
-line to line. So the major modes for those languages rebind <DEL> to
-treat a tab as if it were the equivalent number of spaces (using the
-command `backward-delete-char-untabify'). This makes it possible to
-rub out indentation one column at a time without worrying whether it is
-made up of spaces or tabs. In these modes, use `C-b C-d' to delete a
-tab character before point.
-
- Programming language modes define paragraphs to be separated only by
-blank lines, so that the paragraph commands remain useful. Auto Fill
-mode, if enabled in a programming language major mode, indents the new
-lines which it creates.
-
- Turning on a major mode calls a user-supplied function called the
-"mode hook", which is the value of a Lisp variable. For example,
-turning on C mode calls the value of the variable `c-mode-hook' if that
-value exists and is non-`nil'. Mode hook variables for other
-programming language modes include `lisp-mode-hook',
-`emacs-lisp-mode-hook', `lisp-interaction-mode-hook',
-`scheme-mode-hook', and `muddle-mode-hook'. The mode hook function
-receives no arguments.
-
-\1f
-File: xemacs.info, Node: Lists, Next: Defuns, Prev: Program Modes, Up: Programs
-
-Lists and Sexps
-===============
-
- By convention, Emacs keys for dealing with balanced expressions are
-usually `Control-Meta-' characters. They tend to be analogous in
-function to their `Control-' and `Meta-' equivalents. These commands
-are usually thought of as pertaining to expressions in programming
-languages, but can be useful with any language in which some sort of
-parentheses exist (including English).
-
- The commands fall into two classes. Some commands deal only with
-"lists" (parenthetical groupings). They see nothing except
-parentheses, brackets, braces (depending on what must balance in the
-language you are working with), and escape characters that might be used
-to quote those.
-
- The other commands deal with expressions or "sexps". The word `sexp'
-is derived from "s-expression", the term for a symbolic expression in
-Lisp. In Emacs, the notion of `sexp' is not limited to Lisp. It
-refers to an expression in the language your program is written in.
-Each programming language has its own major mode, which customizes the
-syntax tables so that expressions in that language count as sexps.
-
- Sexps typically include symbols, numbers, and string constants, as
-well as anything contained in parentheses, brackets, or braces.
-
- In languages that use prefix and infix operators, such as C, it is
-not possible for all expressions to be sexps. For example, C mode does
-not recognize `foo + bar' as an sexp, even though it is a C expression;
-it recognizes `foo' as one sexp and `bar' as another, with the `+' as
-punctuation between them. This is a fundamental ambiguity: both `foo +
-bar' and `foo' are legitimate choices for the sexp to move over if
-point is at the `f'. Note that `(foo + bar)' is a sexp in C mode.
-
- Some languages have obscure forms of syntax for expressions that
-nobody has bothered to make Emacs understand properly.
-
-`C-M-f'
- Move forward over an sexp (`forward-sexp').
-
-`C-M-b'
- Move backward over an sexp (`backward-sexp').
-
-`C-M-k'
- Kill sexp forward (`kill-sexp').
-
-`C-M-u'
- Move up and backward in list structure (`backward-up-list').
-
-`C-M-d'
- Move down and forward in list structure (`down-list').
-
-`C-M-n'
- Move forward over a list (`forward-list').
-
-`C-M-p'
- Move backward over a list (`backward-list').
-
-`C-M-t'
- Transpose expressions (`transpose-sexps').
-
-`C-M-@'
- Put mark after following expression (`mark-sexp').
-
- To move forward over an sexp, use `C-M-f' (`forward-sexp'). If the
-first significant character after point is an opening delimiter (`(' in
-Lisp; `(', `[', or `{' in C), `C-M-f' moves past the matching closing
-delimiter. If the character begins a symbol, string, or number,
-`C-M-f' moves over that. If the character after point is a closing
-delimiter, `C-M-f' just moves past it. (This last is not really moving
-across an sexp; it is an exception which is included in the definition
-of `C-M-f' because it is as useful a behavior as anyone can think of
-for that situation.)
-
- The command `C-M-b' (`backward-sexp') moves backward over a sexp.
-The detailed rules are like those above for `C-M-f', but with
-directions reversed. If there are any prefix characters (single quote,
-back quote, and comma, in Lisp) preceding the sexp, `C-M-b' moves back
-over them as well.
-
- `C-M-f' or `C-M-b' with an argument repeats that operation the
-specified number of times; with a negative argument, it moves in the
-opposite direction.
-
- In languages such as C where the comment-terminator can be
-recognized, the sexp commands move across comments as if they were
-whitespace. In Lisp and other languages where comments run until the
-end of a line, it is very difficult to ignore comments when parsing
-backwards; therefore, in such languages the sexp commands treat the
-text of comments as if it were code.
-
- Killing an sexp at a time can be done with `C-M-k' (`kill-sexp').
-`C-M-k' kills the characters that `C-M-f' would move over.
-
- The "list commands", `C-M-n' (`forward-list') and `C-M-p'
-(`backward-list'), move over lists like the sexp commands but skip over
-any number of other kinds of sexps (symbols, strings, etc). In some
-situations, these commands are useful because they usually ignore
-comments, since the comments usually do not contain any lists.
-
- `C-M-n' and `C-M-p' stay at the same level in parentheses, when that
-is possible. To move up one (or N) levels, use `C-M-u'
-(`backward-up-list'). `C-M-u' moves backward up past one unmatched
-opening delimiter. A positive argument serves as a repeat count; a
-negative argument reverses direction of motion and also requests
-repetition, so it moves forward and up one or more levels.
-
- To move down in list structure, use `C-M-d' (`down-list'). In Lisp
-mode, where `(' is the only opening delimiter, this is nearly the same
-as searching for a `('. An argument specifies the number of levels of
-parentheses to go down.
-
- `C-M-t' (`transpose-sexps') drags the previous sexp across the next
-one. An argument serves as a repeat count, and a negative argument
-drags backwards (thus canceling out the effect of `C-M-t' with a
-positive argument). An argument of zero, rather than doing nothing,
-transposes the sexps ending after point and the mark.
-
- To make the region be the next sexp in the buffer, use `C-M-@'
-(`mark-sexp') which sets the mark at the same place that `C-M-f' would
-move to. `C-M-@' takes arguments like `C-M-f'. In particular, a
-negative argument is useful for putting the mark at the beginning of
-the previous sexp.
-
- The list and sexp commands' understanding of syntax is completely
-controlled by the syntax table. Any character can, for example, be
-declared to be an opening delimiter and act like an open parenthesis.
-*Note Syntax::.
-
-\1f
-File: xemacs.info, Node: Defuns, Next: Grinding, Prev: Lists, Up: Programs
-
-Defuns
-======
-
- In Emacs, a parenthetical grouping at the top level in the buffer is
-called a "defun". The name derives from the fact that most top-level
-lists in Lisp are instances of the special form `defun', but Emacs
-calls any top-level parenthetical grouping counts a defun regardless of
-its contents or the programming language. For example, in C, the body
-of a function definition is a defun.
-
-`C-M-a'
- Move to beginning of current or preceding defun
- (`beginning-of-defun').
-
-`C-M-e'
- Move to end of current or following defun (`end-of-defun').
-
-`C-M-h'
- Put region around whole current or following defun (`mark-defun').
-
- The commands to move to the beginning and end of the current defun
-are `C-M-a' (`beginning-of-defun') and `C-M-e' (`end-of-defun').
-
- To operate on the current defun, use `C-M-h' (`mark-defun') which
-puts point at the beginning and the mark at the end of the current or
-next defun. This is the easiest way to prepare for moving the defun to
-a different place. In C mode, `C-M-h' runs the function
-`mark-c-function', which is almost the same as `mark-defun', but which
-backs up over the argument declarations, function name, and returned
-data type so that the entire C function is inside the region.
-
- To compile and evaluate the current defun, use `M-x compile-defun'.
-This function prints the results in the minibuffer. If you include an
-argument, it inserts the value in the current buffer after the defun.
-
- Emacs assumes that any open-parenthesis found in the leftmost column
-is the start of a defun. Therefore, never put an open-parenthesis at
-the left margin in a Lisp file unless it is the start of a top level
-list. Never put an open-brace or other opening delimiter at the
-beginning of a line of C code unless it starts the body of a function.
-The most likely problem case is when you want an opening delimiter at
-the start of a line inside a string. To avoid trouble, put an escape
-character (`\' in C and Emacs Lisp, `/' in some other Lisp dialects)
-before the opening delimiter. It will not affect the contents of the
-string.
-
- The original Emacs found defuns by moving upward a level of
-parentheses until there were no more levels to go up. This required
-scanning back to the beginning of the buffer for every function. To
-speed this up, Emacs was changed to assume that any `(' (or other
-character assigned the syntactic class of opening-delimiter) at the
-left margin is the start of a defun. This heuristic is nearly always
-right; however, it mandates the convention described above.
-
-\1f
-File: xemacs.info, Node: Grinding, Next: Matching, Prev: Defuns, Up: Programs
-
-Indentation for Programs
-========================
-
- The best way to keep a program properly indented ("ground") is to
-use Emacs to re-indent it as you change the program. Emacs has commands
-to indent properly either a single line, a specified number of lines, or
-all of the lines inside a single parenthetical grouping.
-
-* Menu:
-
-* Basic Indent::
-* Multi-line Indent:: Commands to reindent many lines at once.
-* Lisp Indent:: Specifying how each Lisp function should be indented.
-* C Indent:: Choosing an indentation style for C code.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Pages, Next: Filling, Prev: Paragraphs, Up: Text
+
+Pages
+=====
+
+ Files are often thought of as divided into "pages" by the "formfeed"
+character (ASCII Control-L, octal code 014). For example, if a file is
+printed on a line printer, each "page" of the file starts on a new page
+of paper. Emacs treats a page-separator character just like any other
+character. It can be inserted with `C-q C-l' or deleted with <DEL>.
+You are free to paginate your file or not. However, since pages are
+often meaningful divisions of the file, commands are provided to move
+over them and operate on them.
+
+`C-x ['
+ Move point to previous page boundary (`backward-page').
+
+`C-x ]'
+ Move point to next page boundary (`forward-page').
+
+`C-x C-p'
+ Put point and mark around this page (or another page)
+ (`mark-page').
+
+`C-x l'
+ Count the lines in this page (`count-lines-page').
+
+ The `C-x [' (`backward-page') command moves point to immediately
+after the previous page delimiter. If point is already right after a
+page delimiter, the command skips that one and stops at the previous
+one. A numeric argument serves as a repeat count. The `C-x ]'
+(`forward-page') command moves forward past the next page delimiter.
+
+ The `C-x C-p' command (`mark-page') puts point at the beginning of
+the current page and the mark at the end. The page delimiter at the end
+is included (the mark follows it). The page delimiter at the front is
+excluded (point follows it). You can follow this command by `C-w' to
+kill a page you want to move elsewhere. If you insert the page after a
+page delimiter, at a place where `C-x ]' or `C-x [' would take you, the
+page will be properly delimited before and after once again.
+
+ A numeric argument to `C-x C-p' is used to specify which page to go
+to, relative to the current one. Zero means the current page. One
+means the next page, and -1 means the previous one.
+
+ The `C-x l' command (`count-lines-page') can help you decide where
+to break a page in two. It prints the total number of lines in the
+current page in the echo area, then divides the lines into those
+preceding the current line and those following it, for example
+
+ Page has 96 (72+25) lines
+
+Notice that the sum is off by one; this is correct if point is not at
+the beginning of a line.
+
+ The variable `page-delimiter' should have as its value a regexp that
+matches the beginning of a line that separates pages. This defines
+where pages begin. The normal value of this variable is `"^\f"', which
+matches a formfeed character at the beginning of a line.
+
+\1f
+File: xemacs.info, Node: Filling, Next: Case, Prev: Pages, Up: Text
+
+Filling Text
+============
+
+ If you use Auto Fill mode, Emacs "fills" text (breaks it up into
+lines that fit in a specified width) as you insert it. When you alter
+existing text it is often no longer be properly filled afterwards and
+you can use explicit commands for filling.
+
+* Menu:
+
+* Auto Fill:: Auto Fill mode breaks long lines automatically.
+* Fill Commands:: Commands to refill paragraphs and center lines.
+* Fill Prefix:: Filling when every line is indented or in a comment, etc.
+
+\1f
+File: xemacs.info, Node: Auto Fill, Next: Fill Commands, Prev: Filling, Up: Filling
+
+Auto Fill Mode
+--------------
+
+ "Auto Fill" mode is a minor mode in which lines are broken
+automatically when they become too wide. Breaking happens only when
+you type a <SPC> or <RET>.
+
+`M-x auto-fill-mode'
+ Enable or disable Auto Fill mode.
+
+`<SPC>'
+`<RET>'
+ In Auto Fill mode, break lines when appropriate.
+
+ `M-x auto-fill-mode' turns Auto Fill mode on if it was off, or off
+if it was on. With a positive numeric argument the command always turns
+Auto Fill mode on, and with a negative argument it always turns it off.
+The presence of the word `Fill' in the mode line, inside the
+parentheses, indicates that Auto Fill mode is in effect. Auto Fill mode
+is a minor mode; you can turn it on or off for each buffer individually.
+*Note Minor Modes::.
+
+ In Auto Fill mode, lines are broken automatically at spaces when
+they get longer than desired. Line breaking and rearrangement takes
+place only when you type <SPC> or <RET>. To insert a space or newline
+without permitting line-breaking, type `C-q <SPC>' or `C-q <LFD>'
+(recall that a newline is really a linefeed). `C-o' inserts a newline
+without line breaking.
+
+ Auto Fill mode works well with Lisp mode: when it makes a new line in
+Lisp mode, it indents that line with <TAB>. If a line ending in a Lisp
+comment gets too long, the text of the comment is split into two
+comment lines. Optionally, new comment delimiters are inserted at the
+end of the first line and the beginning of the second, so that each line
+is a separate comment. The variable `comment-multi-line' controls the
+choice (*note Comments::).
+
+ Auto Fill mode does not refill entire paragraphs. It can break
+lines but cannot merge lines. Editing in the middle of a paragraph can
+result in a paragraph that is not correctly filled. The easiest way to
+make the paragraph properly filled again is using an explicit fill
+commands.
+
+ Many users like Auto Fill mode and want to use it in all text files.
+The section on init files explains how you can arrange this permanently
+for yourself. *Note Init File::.
+
+\1f
+File: xemacs.info, Node: Fill Commands, Next: Fill Prefix, Prev: Auto Fill, Up: Filling
+
+Explicit Fill Commands
+----------------------
+
+`M-q'
+ Fill current paragraph (`fill-paragraph').
+
+`M-g'
+ Fill each paragraph in the region (`fill-region').
+
+`C-x f'
+ Set the fill column (`set-fill-column').
+
+`M-x fill-region-as-paragraph'
+ Fill the region, considering it as one paragraph.
+
+`M-s'
+ Center a line.
+
+ To refill a paragraph, use the command `Meta-q' (`fill-paragraph').
+It causes the paragraph containing point, or the one after point if
+point is between paragraphs, to be refilled. All line breaks are
+removed, and new ones are inserted where necessary. `M-q' can be
+undone with `C-_'. *Note Undo::.
+
+ To refill many paragraphs, use `M-g' (`fill-region'), which divides
+the region into paragraphs and fills each of them.
+
+ `Meta-q' and `Meta-g' use the same criteria as `Meta-h' for finding
+paragraph boundaries (*note Paragraphs::). For more control, you can
+use `M-x fill-region-as-paragraph', which refills everything between
+point and mark. This command recognizes only blank lines as paragraph
+separators.
+
+ A numeric argument to `M-g' or `M-q' causes it to "justify" the text
+as well as filling it. Extra spaces are inserted to make the right
+margin line up exactly at the fill column. To remove the extra spaces,
+use `M-q' or `M-g' with no argument.
+
+ The variable `auto-fill-inhibit-regexp' takes as a value a regexp to
+match lines that should not be auto-filled.
+
+ The command `Meta-s' (`center-line') centers the current line within
+the current fill column. With an argument, it centers several lines
+individually and moves past them.
+
+ The maximum line width for filling is in the variable `fill-column'.
+Altering the value of `fill-column' makes it local to the current
+buffer; until then, the default value--initially 70--is in effect.
+*Note Locals::.
+
+ The easiest way to set `fill-column' is to use the command `C-x f'
+(`set-fill-column'). With no argument, it sets `fill-column' to the
+current horizontal position of point. With a numeric argument, it uses
+that number as the new fill column.
+
+\1f
+File: xemacs.info, Node: Fill Prefix, Prev: Fill Commands, Up: Filling
+
+The Fill Prefix
+---------------
+
+ To fill a paragraph in which each line starts with a special marker
+(which might be a few spaces, giving an indented paragraph), use the
+"fill prefix" feature. The fill prefix is a string which is not
+included in filling. Emacs expects every line to start with a fill
+prefix.
+
+`C-x .'
+ Set the fill prefix (`set-fill-prefix').
+
+`M-q'
+ Fill a paragraph using current fill prefix (`fill-paragraph').
+
+`M-x fill-individual-paragraphs'
+ Fill the region, considering each change of indentation as
+ starting a new paragraph.
+
+ To specify a fill prefix, move to a line that starts with the desired
+prefix, put point at the end of the prefix, and give the command
+`C-x .' (`set-fill-prefix'). That's a period after the `C-x'. To turn
+off the fill prefix, specify an empty prefix: type `C-x .' with point
+at the beginning of a line.
+
+ When a fill prefix is in effect, the fill commands remove the fill
+prefix from each line before filling and insert it on each line after
+filling. Auto Fill mode also inserts the fill prefix inserted on new
+lines it creates. Lines that do not start with the fill prefix are
+considered to start paragraphs, both in `M-q' and the paragraph
+commands; this is just right if you are using paragraphs with hanging
+indentation (every line indented except the first one). Lines which are
+blank or indented once the prefix is removed also separate or start
+paragraphs; this is what you want if you are writing multi-paragraph
+comments with a comment delimiter on each line.
+
+ The fill prefix is stored in the variable `fill-prefix'. Its value
+is a string, or `nil' when there is no fill prefix. 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.
+*Note Locals::.
+
+ Another way to use fill prefixes is through `M-x
+fill-individual-paragraphs'. This function divides the region into
+groups of consecutive lines with the same amount and kind of
+indentation and fills each group as a paragraph, using its indentation
+as a fill prefix.
+
+\1f
+File: xemacs.info, Node: Case, Prev: Filling, Up: Text
+
+Case Conversion Commands
+========================
+
+ Emacs has commands for converting either a single word or any
+arbitrary range of text to upper case or to lower case.
+
+`M-l'
+ Convert following word to lower case (`downcase-word').
+
+`M-u'
+ Convert following word to upper case (`upcase-word').
+
+`M-c'
+ Capitalize the following word (`capitalize-word').
+
+`C-x C-l'
+ Convert region to lower case (`downcase-region').
+
+`C-x C-u'
+ Convert region to upper case (`upcase-region').
+
+ The word conversion commands are used most frequently. `Meta-l'
+(`downcase-word') converts the word after point to lower case, moving
+past it. Thus, repeating `Meta-l' converts successive words. `Meta-u'
+(`upcase-word') converts to all capitals instead, while `Meta-c'
+(`capitalize-word') puts the first letter of the word into upper case
+and the rest into lower case. The word conversion commands convert
+several words at once if given an argument. They are especially
+convenient for converting a large amount of text from all upper case to
+mixed case: you can move through the text using `M-l', `M-u', or `M-c'
+on each word as appropriate, occasionally using `M-f' instead to skip a
+word.
+
+ When given a negative argument, the word case conversion commands
+apply to the appropriate number of words before point, but do not move
+point. This is convenient when you have just typed a word in the wrong
+case: you can give the case conversion command and continue typing.
+
+ If a word case conversion command is given in the middle of a word,
+it applies only to the part of the word which follows point. This is
+just like what `Meta-d' (`kill-word') does. With a negative argument,
+case conversion applies only to the part of the word before point.
+
+ The other case conversion commands are `C-x C-u' (`upcase-region')
+and `C-x C-l' (`downcase-region'), which convert everything between
+point and mark to the specified case. Point and mark do not move.
+
+\1f
+File: xemacs.info, Node: Programs, Next: Running, Prev: Text, Up: Top
+
+Editing Programs
+****************
+
+ Emacs has many commands designed to understand the syntax of
+programming languages such as Lisp and C. These commands can:
+
+ * Move over or kill balanced expressions or "sexps" (*note Lists::).
+
+ * Move over or mark top-level balanced expressions ("defuns", in
+ Lisp; functions, in C).
+
+ * Show how parentheses balance (*note Matching::).
+
+ * Insert, kill, or align comments (*note Comments::).
+
+ * Follow the usual indentation conventions of the language (*note
+ Grinding::).
+
+ The commands available for words, sentences, and paragraphs are
+useful in editing code even though their canonical application is for
+editing human language text. Most symbols contain words (*note
+Words::); sentences can be found in strings and comments (*note
+Sentences::). Paragraphs per se are not present in code, but the
+paragraph commands are useful anyway, because Lisp mode and C mode
+define paragraphs to begin and end at blank lines (*note Paragraphs::).
+Judicious use of blank lines to make the program clearer also provides
+interesting chunks of text for the paragraph commands to work on.
+
+ The selective display feature is useful for looking at the overall
+structure of a function (*note Selective Display::). This feature
+causes only the lines that are indented less than a specified amount to
+appear on the screen.
+
+* Menu:
+
+* Program Modes:: Major modes for editing programs.
+* Lists:: Expressions with balanced parentheses.
+ There are editing commands to operate on them.
+* Defuns:: Each program is made up of separate functions.
+ There are editing commands to operate on them.
+* Grinding:: Adjusting indentation to show the nesting.
+* Matching:: Insertion of a close-delimiter flashes matching open.
+* Comments:: Inserting, filling and aligning comments.
+* Balanced Editing:: Inserting two matching parentheses at once, etc.
+* Lisp Completion:: Completion on symbol names in Lisp code.
+* Documentation:: Getting documentation of functions you plan to call.
+* Change Log:: Maintaining a change history for your program.
+* Tags:: Go direct to any function in your program in one
+ command. Tags remembers which file it is in.
+* Fortran:: Fortran mode and its special features.
+* Asm Mode:: Asm mode and its special features.
+
+\1f
+File: xemacs.info, Node: Program Modes, Next: Lists, Prev: Programs, Up: Programs
+
+Major Modes for Programming Languages
+=====================================
+
+ Emacs has several major modes for the programming languages Lisp,
+Scheme (a variant of Lisp), C, Fortran, and Muddle. Ideally, a major
+mode should be implemented for each programming language you might want
+to edit with Emacs; but often the mode for one language can serve for
+other syntactically similar languages. The language modes that exist
+are those that someone decided to take the trouble to write.
+
+ There are several variants of Lisp mode, which differ in the way they
+interface to Lisp execution. *Note Lisp Modes::.
+
+ Each of the programming language modes defines the <TAB> key to run
+an indentation function that knows the indentation conventions of that
+language and updates the current line's indentation accordingly. For
+example, in C mode <TAB> is bound to `c-indent-line'. <LFD> is
+normally defined to do <RET> followed by <TAB>; thus it, too, indents
+in a mode-specific fashion.
+
+ In most programming languages, indentation is likely to vary from
+line to line. So the major modes for those languages rebind <DEL> to
+treat a tab as if it were the equivalent number of spaces (using the
+command `backward-delete-char-untabify'). This makes it possible to
+rub out indentation one column at a time without worrying whether it is
+made up of spaces or tabs. In these modes, use `C-b C-d' to delete a
+tab character before point.
+
+ Programming language modes define paragraphs to be separated only by
+blank lines, so that the paragraph commands remain useful. Auto Fill
+mode, if enabled in a programming language major mode, indents the new
+lines which it creates.
+
+ Turning on a major mode calls a user-supplied function called the
+"mode hook", which is the value of a Lisp variable. For example,
+turning on C mode calls the value of the variable `c-mode-hook' if that
+value exists and is non-`nil'. Mode hook variables for other
+programming language modes include `lisp-mode-hook',
+`emacs-lisp-mode-hook', `lisp-interaction-mode-hook',
+`scheme-mode-hook', and `muddle-mode-hook'. The mode hook function
+receives no arguments.
+
+\1f
+File: xemacs.info, Node: Lists, Next: Defuns, Prev: Program Modes, Up: Programs
+
+Lists and Sexps
+===============
+
+ By convention, Emacs keys for dealing with balanced expressions are
+usually `Control-Meta-' characters. They tend to be analogous in
+function to their `Control-' and `Meta-' equivalents. These commands
+are usually thought of as pertaining to expressions in programming
+languages, but can be useful with any language in which some sort of
+parentheses exist (including English).
+
+ The commands fall into two classes. Some commands deal only with
+"lists" (parenthetical groupings). They see nothing except
+parentheses, brackets, braces (depending on what must balance in the
+language you are working with), and escape characters that might be used
+to quote those.
+
+ The other commands deal with expressions or "sexps". The word `sexp'
+is derived from "s-expression", the term for a symbolic expression in
+Lisp. In Emacs, the notion of `sexp' is not limited to Lisp. It
+refers to an expression in the language your program is written in.
+Each programming language has its own major mode, which customizes the
+syntax tables so that expressions in that language count as sexps.
+
+ Sexps typically include symbols, numbers, and string constants, as
+well as anything contained in parentheses, brackets, or braces.
+
+ In languages that use prefix and infix operators, such as C, it is
+not possible for all expressions to be sexps. For example, C mode does
+not recognize `foo + bar' as an sexp, even though it is a C expression;
+it recognizes `foo' as one sexp and `bar' as another, with the `+' as
+punctuation between them. This is a fundamental ambiguity: both `foo +
+bar' and `foo' are legitimate choices for the sexp to move over if
+point is at the `f'. Note that `(foo + bar)' is a sexp in C mode.
+
+ Some languages have obscure forms of syntax for expressions that
+nobody has bothered to make Emacs understand properly.
+
+`C-M-f'
+ Move forward over an sexp (`forward-sexp').
+
+`C-M-b'
+ Move backward over an sexp (`backward-sexp').
+
+`C-M-k'
+ Kill sexp forward (`kill-sexp').
+
+`C-M-u'
+ Move up and backward in list structure (`backward-up-list').
+
+`C-M-d'
+ Move down and forward in list structure (`down-list').
+
+`C-M-n'
+ Move forward over a list (`forward-list').
+
+`C-M-p'
+ Move backward over a list (`backward-list').
+
+`C-M-t'
+ Transpose expressions (`transpose-sexps').
+
+`C-M-@'
+ Put mark after following expression (`mark-sexp').
+
+ To move forward over an sexp, use `C-M-f' (`forward-sexp'). If the
+first significant character after point is an opening delimiter (`(' in
+Lisp; `(', `[', or `{' in C), `C-M-f' moves past the matching closing
+delimiter. If the character begins a symbol, string, or number,
+`C-M-f' moves over that. If the character after point is a closing
+delimiter, `C-M-f' just moves past it. (This last is not really moving
+across an sexp; it is an exception which is included in the definition
+of `C-M-f' because it is as useful a behavior as anyone can think of
+for that situation.)
+
+ The command `C-M-b' (`backward-sexp') moves backward over a sexp.
+The detailed rules are like those above for `C-M-f', but with
+directions reversed. If there are any prefix characters (single quote,
+back quote, and comma, in Lisp) preceding the sexp, `C-M-b' moves back
+over them as well.
+
+ `C-M-f' or `C-M-b' with an argument repeats that operation the
+specified number of times; with a negative argument, it moves in the
+opposite direction.
+
+ In languages such as C where the comment-terminator can be
+recognized, the sexp commands move across comments as if they were
+whitespace. In Lisp and other languages where comments run until the
+end of a line, it is very difficult to ignore comments when parsing
+backwards; therefore, in such languages the sexp commands treat the
+text of comments as if it were code.
+
+ Killing an sexp at a time can be done with `C-M-k' (`kill-sexp').
+`C-M-k' kills the characters that `C-M-f' would move over.
+
+ The "list commands", `C-M-n' (`forward-list') and `C-M-p'
+(`backward-list'), move over lists like the sexp commands but skip over
+any number of other kinds of sexps (symbols, strings, etc). In some
+situations, these commands are useful because they usually ignore
+comments, since the comments usually do not contain any lists.
+
+ `C-M-n' and `C-M-p' stay at the same level in parentheses, when that
+is possible. To move up one (or N) levels, use `C-M-u'
+(`backward-up-list'). `C-M-u' moves backward up past one unmatched
+opening delimiter. A positive argument serves as a repeat count; a
+negative argument reverses direction of motion and also requests
+repetition, so it moves forward and up one or more levels.
+
+ To move down in list structure, use `C-M-d' (`down-list'). In Lisp
+mode, where `(' is the only opening delimiter, this is nearly the same
+as searching for a `('. An argument specifies the number of levels of
+parentheses to go down.
+
+ `C-M-t' (`transpose-sexps') drags the previous sexp across the next
+one. An argument serves as a repeat count, and a negative argument
+drags backwards (thus canceling out the effect of `C-M-t' with a
+positive argument). An argument of zero, rather than doing nothing,
+transposes the sexps ending after point and the mark.
+
+ To make the region be the next sexp in the buffer, use `C-M-@'
+(`mark-sexp') which sets the mark at the same place that `C-M-f' would
+move to. `C-M-@' takes arguments like `C-M-f'. In particular, a
+negative argument is useful for putting the mark at the beginning of
+the previous sexp.
+
+ The list and sexp commands' understanding of syntax is completely
+controlled by the syntax table. Any character can, for example, be
+declared to be an opening delimiter and act like an open parenthesis.
+*Note Syntax::.
+
+\1f
+File: xemacs.info, Node: Defuns, Next: Grinding, Prev: Lists, Up: Programs
+
+Defuns
+======
+
+ In Emacs, a parenthetical grouping at the top level in the buffer is
+called a "defun". The name derives from the fact that most top-level
+lists in Lisp are instances of the special form `defun', but Emacs
+calls any top-level parenthetical grouping counts a defun regardless of
+its contents or the programming language. For example, in C, the body
+of a function definition is a defun.
+
+`C-M-a'
+ Move to beginning of current or preceding defun
+ (`beginning-of-defun').
+
+`C-M-e'
+ Move to end of current or following defun (`end-of-defun').
+
+`C-M-h'
+ Put region around whole current or following defun (`mark-defun').
+
+ The commands to move to the beginning and end of the current defun
+are `C-M-a' (`beginning-of-defun') and `C-M-e' (`end-of-defun').
+
+ To operate on the current defun, use `C-M-h' (`mark-defun') which
+puts point at the beginning and the mark at the end of the current or
+next defun. This is the easiest way to prepare for moving the defun to
+a different place. In C mode, `C-M-h' runs the function
+`mark-c-function', which is almost the same as `mark-defun', but which
+backs up over the argument declarations, function name, and returned
+data type so that the entire C function is inside the region.
+
+ To compile and evaluate the current defun, use `M-x compile-defun'.
+This function prints the results in the minibuffer. If you include an
+argument, it inserts the value in the current buffer after the defun.
+
+ Emacs assumes that any open-parenthesis found in the leftmost column
+is the start of a defun. Therefore, never put an open-parenthesis at
+the left margin in a Lisp file unless it is the start of a top level
+list. Never put an open-brace or other opening delimiter at the
+beginning of a line of C code unless it starts the body of a function.
+The most likely problem case is when you want an opening delimiter at
+the start of a line inside a string. To avoid trouble, put an escape
+character (`\' in C and Emacs Lisp, `/' in some other Lisp dialects)
+before the opening delimiter. It will not affect the contents of the
+string.
+
+ The original Emacs found defuns by moving upward a level of
+parentheses until there were no more levels to go up. This required
+scanning back to the beginning of the buffer for every function. To
+speed this up, Emacs was changed to assume that any `(' (or other
+character assigned the syntactic class of opening-delimiter) at the
+left margin is the start of a defun. This heuristic is nearly always
+right; however, it mandates the convention described above.
+
+\1f
+File: xemacs.info, Node: Grinding, Next: Matching, Prev: Defuns, Up: Programs
+
+Indentation for Programs
+========================
+
+ The best way to keep a program properly indented ("ground") is to
+use Emacs to re-indent it as you change the program. Emacs has commands
+to indent properly either a single line, a specified number of lines, or
+all of the lines inside a single parenthetical grouping.
+
+* Menu:
+
+* Basic Indent::
+* Multi-line Indent:: Commands to reindent many lines at once.
+* Lisp Indent:: Specifying how each Lisp function should be indented.
+* C Indent:: Choosing an indentation style for C code.
+
+\1f
File: xemacs.info, Node: Basic Indent, Next: Multi-line Indent, Prev: Grinding, Up: Grinding
Basic Program Indentation Commands
`termcap' finds the description of the termcap library from section 3,
followed by the description of the termcap data base from section 5.
-\1f
-File: xemacs.info, Node: Change Log, Next: Tags, Prev: Documentation, Up: Programs
-
-Change Logs
-===========
-
- The Emacs command `M-x add-change-log-entry' helps you keep a record
-of when and why you have changed a program. It assumes that you have a
-file in which you write a chronological sequence of entries describing
-individual changes. The default is to store the change entries in a
-file called `ChangeLog' in the same directory as the file you are
-editing. The same `ChangeLog' file therefore records changes for all
-the files in a directory.
-
- A change log entry starts with a header line that contains your name
-and the current date. Except for these header lines, every line in the
-change log starts with a tab. One entry can describe several changes;
-each change starts with a line starting with a tab and a star. `M-x
-add-change-log-entry' visits the change log file and creates a new entry
-unless the most recent entry is for today's date and your name. In
-either case, it adds a new line to start the description of another
-change just after the header line of the entry. When `M-x
-add-change-log-entry' is finished, all is prepared for you to edit in
-the description of what you changed and how. You must then save the
-change log file yourself.
-
- The change log file is always visited in Indented Text mode, which
-means that <LFD> and auto-filling indent each new line like the previous
-line. This is convenient for entering the contents of an entry, which
-must be indented. *Note Text Mode::.
-
- Here is an example of the formatting conventions used in the change
-log for Emacs:
-
- Wed Jun 26 19:29:32 1985 Richard M. Stallman (rms at mit-prep)
-
- * xdisp.c (try_window_id):
- If C-k is done at end of next-to-last line,
- this fn updates window_end_vpos and cannot leave
- window_end_pos nonnegative (it is zero, in fact).
- If display is preempted before lines are output,
- this is inconsistent. Fix by setting
- blank_end_of_window to nonzero.
-
- Tue Jun 25 05:25:33 1985 Richard M. Stallman (rms at mit-prep)
-
- * cmds.c (Fnewline):
- Call the auto fill hook if appropriate.
-
- * xdisp.c (try_window_id):
- If point is found by compute_motion after xp, record that
- permanently. If display_text_line sets point position wrong
- (case where line is killed, point is at eob and that line is
- not displayed), set it again in final compute_motion.
-
-\1f
-File: xemacs.info, Node: Tags, Next: Fortran, Prev: Change Log, Up: Programs
-
-Tags Tables
-===========
-
- A "tags table" is a description of how a multi-file program is
-broken up into files. It lists the names of the component files and the
-names and positions of the functions (or other named subunits) in each
-file. Grouping the related files makes it possible to search or replace
-through all the files with one command. Recording the function names
-and positions makes possible the `M-.' command which finds the
-definition of a function by looking up which of the files it is in.
-
- Tags tables are stored in files called "tags table files". The
-conventional name for a tags table file is `TAGS'.
-
- Each entry in the tags table records the name of one tag, the name
-of the file that the tag is defined in (implicitly), and the position
-in that file of the tag's definition.
-
- Just what names from the described files are recorded in the tags
-table depends on the programming language of the described file. They
-normally include all functions and subroutines, and may also include
-global variables, data types, and anything else convenient. Each name
-recorded is called a "tag".
-
-* Menu:
-
-* Tag Syntax:: Tag syntax for various types of code and text files.
-* Create Tags Table:: Creating a tags table with `etags'.
-* Etags Regexps:: Create arbitrary tags using regular expressions.
-* Select Tags Table:: How to visit a tags table.
-* Find Tag:: Commands to find the definition of a specific tag.
-* Tags Search:: Using a tags table for searching and replacing.
-* List Tags:: Listing and finding tags defined in a file.
-
-\1f
-File: xemacs.info, Node: Tag Syntax, Next: Create Tags Table, Prev: Tags, Up: Tags
-
-Source File Tag Syntax
-----------------------
-
- Here is how tag syntax is defined for the most popular languages:
-
- * In C code, any C function or typedef is a tag, and so are
- definitions of `struct', `union' and `enum'. You can tag function
- declarations and external variables in addition to function
- definitions by giving the `--declarations' option to `etags'.
- `#define' macro definitions and `enum' constants are also tags,
- unless you specify `--no-defines' when making the tags table.
- Similarly, global variables are tags, unless you specify
- `--no-globals'. Use of `--no-globals' and `--no-defines' can make
- the tags table file much smaller.
-
- * In C++ code, in addition to all the tag constructs of C code,
- member functions are also recognized, and optionally member
- variables if you use the `--members' option. Tags for variables
- and functions in classes are named `CLASS::VARIABLE' and
- `CLASS::FUNCTION'. `operator' functions tags are named, for
- example `operator+'.
-
- * In Java code, tags include all the constructs recognized in C++,
- plus the `interface', `extends' and `implements' constructs. Tags
- for variables and functions in classes are named `CLASS.VARIABLE'
- and `CLASS.FUNCTION'.
-
- * In LaTeX text, the argument of any of the commands `\chapter',
- `\section', `\subsection', `\subsubsection', `\eqno', `\label',
- `\ref', `\cite', `\bibitem', `\part', `\appendix', `\entry', or
- `\index', is a tag.
-
- Other commands can make tags as well, if you specify them in the
- environment variable `TEXTAGS' before invoking `etags'. The value
- of this environment variable should be a colon-separated list of
- command names. For example,
-
- TEXTAGS="def:newcommand:newenvironment"
- export TEXTAGS
-
- specifies (using Bourne shell syntax) that the commands `\def',
- `\newcommand' and `\newenvironment' also define tags.
-
- * In Lisp code, any function defined with `defun', any variable
- defined with `defvar' or `defconst', and in general the first
- argument of any expression that starts with `(def' in column zero,
- is a tag.
-
- * In Scheme code, tags include anything defined with `def' or with a
- construct whose name starts with `def'. They also include
- variables set with `set!' at top level in the file.
-
- Several other languages are also supported:
-
- * In Ada code, functions, procedures, packages, tasks, and types are
- tags. Use the `--packages-only' option to create tags for packages
- only.
-
- * In assembler code, labels appearing at the beginning of a line,
- followed by a colon, are tags.
-
- * In Bison or Yacc input files, each rule defines as a tag the
- nonterminal it constructs. The portions of the file that contain
- C code are parsed as C code.
-
- * In Cobol code, tags are paragraph names; that is, any word
- starting in column 8 and followed by a period.
-
- * In Erlang code, the tags are the functions, records, and macros
- defined in the file.
-
- * In Fortran code, functions, subroutines and blockdata are tags.
-
- * In Objective C code, tags include Objective C definitions for
- classes, class categories, methods, and protocols.
-
- * In Pascal code, the tags are the functions and procedures defined
- in the file.
-
- * In Perl code, the tags are the procedures defined by the `sub',
- `my' and `local' keywords. Use `--globals' if you want to tag
- global variables.
-
- * In Postscript code, the tags are the functions.
-
- * In Prolog code, a tag name appears at the left margin.
-
- * In Python code, `def' or `class' at the beginning of a line
- generate a tag.
-
- You can also generate tags based on regexp matching (*note Etags
-Regexps::) to handle other formats and languages.
-
-\1f
-File: xemacs.info, Node: Create Tags Table, Next: Etags Regexps, Prev: Tag Syntax, Up: Tags
-
-Creating Tags Tables
---------------------
-
- The `etags' program is used to create a tags table file. It knows
-the syntax of several languages, as described in *Note Tag Syntax::.
-Here is how to run `etags':
-
- etags INPUTFILES...
-
-The `etags' program reads the specified files, and writes a tags table
-named `TAGS' in the current working directory. You can intermix
-compressed and plain text source file names. `etags' knows about the
-most common compression formats, and does the right thing. So you can
-compress all your source files and have `etags' look for compressed
-versions of its file name arguments, if it does not find uncompressed
-versions. Under MS-DOS, `etags' also looks for file names like
-`mycode.cgz' if it is given `mycode.c' on the command line and
-`mycode.c' does not exist.
-
- `etags' recognizes the language used in an input file based on its
-file name and contents. You can specify the language with the
-`--language=NAME' option, described below.
-
- If the tags table data become outdated due to changes in the files
-described in the table, the way to update the tags table is the same
-way it was made in the first place. It is not necessary to do this
-often.
-
- If the tags table fails to record a tag, or records it for the wrong
-file, then Emacs cannot possibly find its definition. However, if the
-position recorded in the tags table becomes a little bit wrong (due to
-some editing in the file that the tag definition is in), the only
-consequence is a slight delay in finding the tag. Even if the stored
-position is very wrong, Emacs will still find the tag, but it must
-search the entire file for it.
-
- So you should update a tags table when you define new tags that you
-want to have listed, or when you move tag definitions from one file to
-another, or when changes become substantial. Normally there is no need
-to update the tags table after each edit, or even every day.
-
- One tags table can effectively include another. Specify the included
-tags file name with the `--include=FILE' option when creating the file
-that is to include it. The latter file then acts as if it contained
-all the files specified in the included file, as well as the files it
-directly contains.
-
- If you specify the source files with relative file names when you run
-`etags', the tags file will contain file names relative to the
-directory where the tags file was initially written. This way, you can
-move an entire directory tree containing both the tags file and the
-source files, and the tags file will still refer correctly to the source
-files.
-
- If you specify absolute file names as arguments to `etags', then the
-tags file will contain absolute file names. This way, the tags file
-will still refer to the same files even if you move it, as long as the
-source files remain in the same place. Absolute file names start with
-`/', or with `DEVICE:/' on MS-DOS and MS-Windows.
-
- When you want to make a tags table from a great number of files, you
-may have problems listing them on the command line, because some systems
-have a limit on its length. The simplest way to circumvent this limit
-is to tell `etags' to read the file names from its standard input, by
-typing a dash in place of the file names, like this:
-
- find . -name "*.[chCH]" -print | etags -
-
- Use the option `--language=NAME' to specify the language explicitly.
-You can intermix these options with file names; each one applies to
-the file names that follow it. Specify `--language=auto' to tell
-`etags' to resume guessing the language from the file names and file
-contents. Specify `--language=none' to turn off language-specific
-processing entirely; then `etags' recognizes tags by regexp matching
-alone (*note Etags Regexps::).
-
- `etags --help' prints the list of the languages `etags' knows, and
-the file name rules for guessing the language. It also prints a list of
-all the available `etags' options, together with a short explanation.
-
-\1f
-File: xemacs.info, Node: Etags Regexps, Next: Select Tags Table, Prev: Create Tags Table, Up: Tags
-
-Etags Regexps
--------------
-
- The `--regex' option provides a general way of recognizing tags
-based on regexp matching. You can freely intermix it with file names.
-Each `--regex' option adds to the preceding ones, and applies only to
-the following files. The syntax is:
-
- --regex=/TAGREGEXP[/NAMEREGEXP]/
-
-where TAGREGEXP is used to match the lines to tag. It is always
-anchored, that is, it behaves as if preceded by `^'. If you want to
-account for indentation, just match any initial number of blanks by
-beginning your regular expression with `[ \t]*'. In the regular
-expressions, `\' quotes the next character, and `\t' stands for the tab
-character. Note that `etags' does not handle the other C escape
-sequences for special characters.
-
- The syntax of regular expressions in `etags' is the same as in
-Emacs, augmented with the "interval operator", which works as in `grep'
-and `ed'. The syntax of an interval operator is `\{M,N\}', and its
-meaning is to match the preceding expression at least M times and up to
-N times.
-
- You should not match more characters with TAGREGEXP than that needed
-to recognize what you want to tag. If the match is such that more
-characters than needed are unavoidably matched by TAGREGEXP (as will
-usually be the case), you should add a NAMEREGEXP, to pick out just the
-tag. This will enable Emacs to find tags more accurately and to do
-completion on tag names more reliably. You can find some examples
-below.
-
- The option `--ignore-case-regex' (or `-c') is like `--regex', except
-that the regular expression provided will be matched without regard to
-case, which is appropriate for various programming languages.
-
- The `-R' option deletes all the regexps defined with `--regex'
-options. It applies to the file names following it, as you can see
-from the following example:
-
- etags --regex=/REG1/ voo.doo --regex=/REG2/ \
- bar.ber -R --lang=lisp los.er
-
-Here `etags' chooses the parsing language for `voo.doo' and `bar.ber'
-according to their contents. `etags' also uses REG1 to recognize
-additional tags in `voo.doo', and both REG1 and REG2 to recognize
-additional tags in `bar.ber'. `etags' uses the Lisp tags rules, and no
-regexp matching, to recognize tags in `los.er'.
-
- A regular expression can be bound to a given language, by prepending
-it with `{lang}'. When you do this, `etags' will use the regular
-expression only for files of that language. `etags --help' prints the
-list of languages recognised by `etags'. The following example tags
-the `DEFVAR' macros in the Emacs source files. `etags' applies this
-regular expression to C files only:
-
- --regex='{c}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/'
-
-This feature is particularly useful when storing a list of regular
-expressions in a file. The following option syntax instructs `etags'
-to read two files of regular expressions. The regular expressions
-contained in the second file are matched without regard to case.
-
- --regex=@first-file --ignore-case-regex=@second-file
-
-A regex file contains one regular expressions per line. Empty lines,
-and lines beginning with space or tab are ignored. When the first
-character in a line is `@', `etags' assumes that the rest of the line
-is the name of a file of regular expressions. This means that such
-files can be nested. All the other lines are taken to be regular
-expressions. For example, one can create a file called `emacs.tags'
-with the following contents (the first line in the file is a comment):
-
- -- This is for GNU Emacs source files
- {c}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/\1/
-
-and then use it like this:
-
- etags --regex=@emacs.tags *.[ch] */*.[ch]
-
- Here are some more examples. The regexps are quoted to protect them
-from shell interpretation.
-
- * Tag Octave files:
-
- etags --language=none \
- --regex='/[ \t]*function.*=[ \t]*\([^ \t]*\)[ \t]*(/\1/' \
- --regex='/###key \(.*\)/\1/' \
- --regex='/[ \t]*global[ \t].*/' \
- *.m
-
- Note that tags are not generated for scripts so that you have to
- add a line by yourself of the form `###key <script-name>' if you
- want to jump to it.
-
- * Tag Tcl files:
-
- etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' *.tcl
-
- * Tag VHDL files:
-
- --language=none \
- --regex='/[ \t]*\(ARCHITECTURE\|CONFIGURATION\) +[^ ]* +OF/' \
- --regex='/[ \t]*\(ATTRIBUTE\|ENTITY\|FUNCTION\|PACKAGE\
- \( BODY\)?\|PROCEDURE\|PROCESS\|TYPE\)[ \t]+\([^ \t(]+\)/\3/'
-
-\1f
-File: xemacs.info, Node: Select Tags Table, Next: Find Tag, Prev: Etags Regexps, Up: Tags
-
-Selecting a Tags Table
-----------------------
-
- At any time Emacs has one "selected" tags table, and all the commands
-for working with tags tables use the selected one. To select a tags
-table, use the variable `tag-table-alist'.
-
- The value of `tag-table-alist' is a list that determines which
-`TAGS' files should be active for a given buffer. This is not really
-an association list, in that all elements are checked. The car of each
-element of this list is a pattern against which the buffers file name
-is compared; if it matches, then the cdr of the list should be the name
-of the tags table to use. If more than one element of this list
-matches the buffers file name, all of the associated tags tables are
-used. Earlier ones are searched first.
-
- If the car of elements of this list are strings, they are treated as
-regular-expressions against which the file is compared (like the
-`auto-mode-alist'). If they are not strings, they are evaluated. If
-they evaluate to non-`nil', the current buffer is considered to match.
-
- If the cdr of the elements of this list are strings, they are
-assumed to name a tags file. If they name a directory, the string
-`tags' is appended to them to get the file name. If they are not
-strings, they are evaluated and must return an appropriate string.
-
- For example:
-
- (setq tag-table-alist
- '(("/usr/src/public/perl/" . "/usr/src/public/perl/perl-3.0/")
- ("\\.el$" . "/usr/local/emacs/src/")
- ("/jbw/gnu/" . "/usr15/degree/stud/jbw/gnu/")
- ("" . "/usr/local/emacs/src/")
- ))
-
- The example defines the tags table alist in the following way:
-
- * Anything in the directory `/usr/src/public/perl/' should use the
- `TAGS' file `/usr/src/public/perl/perl-3.0/TAGS'.
-
- * Files ending in `.el' should use the `TAGS' file
- `/usr/local/emacs/src/TAGS'.
-
- * Anything in or below the directory `/jbw/gnu/' should use the
- `TAGS' file `/usr15/degree/stud/jbw/gnu/TAGS'.
-
- If you had a file called `/usr/jbw/foo.el', it would use both `TAGS'
-files,
-`/usr/local/emacs/src/TAGS' and `/usr15/degree/stud/jbw/gnu/TAGS' (in
-that order), because it matches both patterns.
-
- If the buffer-local variable `buffer-tag-table' is set, it names a
-tags table that is searched before all others when `find-tag' is
-executed from this buffer.
-
- If there is a file called `TAGS' in the same directory as the file
-in question, then that tags file will always be used as well (after the
-`buffer-tag-table' but before the tables specified by this list).
-
- If the variable `tags-file-name' is set, the `TAGS' file it names
-will apply to all buffers (for backwards compatibility.) It is searched
-first.
-
- If the value of the variable `tags-always-build-completion-table' is
-`t', the tags file will always be added to the completion table without
-asking first, regardless of the size of the tags file.
-
- The function `M-x visit-tags-table', is largely made obsolete by the
-variable `tag-table-alist', tells tags commands to use the tags table
-file FILE first. The FILE should be the name of a file created with
-the `etags' program. A directory name is also acceptable; it means the
-file `TAGS' in that directory. The function only stores the file name
-you provide in the variable `tags-file-name'. Emacs does not actually
-read in the tags table contents until you try to use them. You can set
-the variable explicitly instead of using `visit-tags-table'. The value
-of the variable `tags-file-name' is the name of the tags table used by
-all buffers. This is for backward compatibility, and is largely
-supplanted by the variable `tag-table-alist'.
-
-\1f
-File: xemacs.info, Node: Find Tag, Next: Tags Search, Prev: Select Tags Table, Up: Tags
-
-Finding a Tag
--------------
-
- The most important thing that a tags table enables you to do is to
-find the definition of a specific tag.
-
-`M-. TAG &OPTIONAL OTHER-WINDOW'
- Find first definition of TAG (`find-tag').
-
-`C-u M-.'
- Find next alternate definition of last tag specified.
-
-`C-x 4 . TAG'
- Find first definition of TAG, but display it in another window
- (`find-tag-other-window').
-
- `M-.' (`find-tag') is the command to find the definition of a
-specified tag. It searches through the tags table for that tag, as a
-string, then uses the tags table information to determine the file in
-which the definition is used and the approximate character position of
-the definition in the file. Then `find-tag' visits the file, moves
-point to the approximate character position, and starts searching
-ever-increasing distances away for the text that should appear at the
-beginning of the definition.
-
- If an empty argument is given (by typing <RET>), the sexp in the
-buffer before or around point is used as the name of the tag to find.
-*Note Lists::, for information on sexps.
-
- The argument to `find-tag' need not be the whole tag name; it can be
-a substring of a tag name. However, there can be many tag names
-containing the substring you specify. Since `find-tag' works by
-searching the text of the tags table, it finds the first tag in the
-table that the specified substring appears in. To find other tags that
-match the substring, give `find-tag' a numeric argument, as in `C-u
-M-.'. This does not read a tag name, but continues searching the tag
-table's text for another tag containing the same substring last used.
-If your keyboard has a real <META> key, `M-0 M-.' is an easier
-alternative to `C-u M-.'.
-
- If the optional second argument OTHER-WINDOW is non-`nil', it uses
-another window to display the tag. Multiple active tags tables and
-completion are supported.
-
- Variables of note include the following:
-
-`tag-table-alist'
- Controls which tables apply to which buffers.
-
-`tags-file-name'
- Stores a default tags table.
-
-`tags-build-completion-table'
- Controls completion behavior.
-
-`buffer-tag-table'
- Specifies a buffer-local table.
-
-`make-tags-files-invisible'
- Sets whether tags tables should be very hidden.
-
-`tag-mark-stack-max'
- Specifies how many tags-based hops to remember.
-
- Like most commands that can switch buffers, `find-tag' has another
-similar command that displays the new buffer in another window. `C-x 4
-.' invokes the function `find-tag-other-window'. (This key sequence
-ends with a period.)
-
- Emacs comes with a tags table file `TAGS' (in the directory
-containing Lisp libraries) that includes all the Lisp libraries and all
-the C sources of Emacs. By specifying this file with `visit-tags-table'
-and then using `M-.' you can quickly look at the source of any Emacs
-function.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Change Log, Next: Tags, Prev: Documentation, Up: Programs
+
+Change Logs
+===========
+
+ The Emacs command `M-x add-change-log-entry' helps you keep a record
+of when and why you have changed a program. It assumes that you have a
+file in which you write a chronological sequence of entries describing
+individual changes. The default is to store the change entries in a
+file called `ChangeLog' in the same directory as the file you are
+editing. The same `ChangeLog' file therefore records changes for all
+the files in a directory.
+
+ A change log entry starts with a header line that contains your name
+and the current date. Except for these header lines, every line in the
+change log starts with a tab. One entry can describe several changes;
+each change starts with a line starting with a tab and a star. `M-x
+add-change-log-entry' visits the change log file and creates a new entry
+unless the most recent entry is for today's date and your name. In
+either case, it adds a new line to start the description of another
+change just after the header line of the entry. When `M-x
+add-change-log-entry' is finished, all is prepared for you to edit in
+the description of what you changed and how. You must then save the
+change log file yourself.
+
+ The change log file is always visited in Indented Text mode, which
+means that <LFD> and auto-filling indent each new line like the previous
+line. This is convenient for entering the contents of an entry, which
+must be indented. *Note Text Mode::.
+
+ Here is an example of the formatting conventions used in the change
+log for Emacs:
+
+ Wed Jun 26 19:29:32 1985 Richard M. Stallman (rms at mit-prep)
+
+ * xdisp.c (try_window_id):
+ If C-k is done at end of next-to-last line,
+ this fn updates window_end_vpos and cannot leave
+ window_end_pos nonnegative (it is zero, in fact).
+ If display is preempted before lines are output,
+ this is inconsistent. Fix by setting
+ blank_end_of_window to nonzero.
+
+ Tue Jun 25 05:25:33 1985 Richard M. Stallman (rms at mit-prep)
+
+ * cmds.c (Fnewline):
+ Call the auto fill hook if appropriate.
+
+ * xdisp.c (try_window_id):
+ If point is found by compute_motion after xp, record that
+ permanently. If display_text_line sets point position wrong
+ (case where line is killed, point is at eob and that line is
+ not displayed), set it again in final compute_motion.
+
+\1f
+File: xemacs.info, Node: Tags, Next: Fortran, Prev: Change Log, Up: Programs
+
+Tags Tables
+===========
+
+ A "tags table" is a description of how a multi-file program is
+broken up into files. It lists the names of the component files and the
+names and positions of the functions (or other named subunits) in each
+file. Grouping the related files makes it possible to search or replace
+through all the files with one command. Recording the function names
+and positions makes possible the `M-.' command which finds the
+definition of a function by looking up which of the files it is in.
+
+ Tags tables are stored in files called "tags table files". The
+conventional name for a tags table file is `TAGS'.
+
+ Each entry in the tags table records the name of one tag, the name
+of the file that the tag is defined in (implicitly), and the position
+in that file of the tag's definition.
+
+ Just what names from the described files are recorded in the tags
+table depends on the programming language of the described file. They
+normally include all functions and subroutines, and may also include
+global variables, data types, and anything else convenient. Each name
+recorded is called a "tag".
+
+* Menu:
+
+* Tag Syntax:: Tag syntax for various types of code and text files.
+* Create Tags Table:: Creating a tags table with `etags'.
+* Etags Regexps:: Create arbitrary tags using regular expressions.
+* Select Tags Table:: How to visit a tags table.
+* Find Tag:: Commands to find the definition of a specific tag.
+* Tags Search:: Using a tags table for searching and replacing.
+* List Tags:: Listing and finding tags defined in a file.
+
+\1f
+File: xemacs.info, Node: Tag Syntax, Next: Create Tags Table, Prev: Tags, Up: Tags
+
+Source File Tag Syntax
+----------------------
+
+ Here is how tag syntax is defined for the most popular languages:
+
+ * In C code, any C function or typedef is a tag, and so are
+ definitions of `struct', `union' and `enum'. You can tag function
+ declarations and external variables in addition to function
+ definitions by giving the `--declarations' option to `etags'.
+ `#define' macro definitions and `enum' constants are also tags,
+ unless you specify `--no-defines' when making the tags table.
+ Similarly, global variables are tags, unless you specify
+ `--no-globals'. Use of `--no-globals' and `--no-defines' can make
+ the tags table file much smaller.
+
+ * In C++ code, in addition to all the tag constructs of C code,
+ member functions are also recognized, and optionally member
+ variables if you use the `--members' option. Tags for variables
+ and functions in classes are named `CLASS::VARIABLE' and
+ `CLASS::FUNCTION'. `operator' functions tags are named, for
+ example `operator+'.
+
+ * In Java code, tags include all the constructs recognized in C++,
+ plus the `interface', `extends' and `implements' constructs. Tags
+ for variables and functions in classes are named `CLASS.VARIABLE'
+ and `CLASS.FUNCTION'.
+
+ * In LaTeX text, the argument of any of the commands `\chapter',
+ `\section', `\subsection', `\subsubsection', `\eqno', `\label',
+ `\ref', `\cite', `\bibitem', `\part', `\appendix', `\entry', or
+ `\index', is a tag.
+
+ Other commands can make tags as well, if you specify them in the
+ environment variable `TEXTAGS' before invoking `etags'. The value
+ of this environment variable should be a colon-separated list of
+ command names. For example,
+
+ TEXTAGS="def:newcommand:newenvironment"
+ export TEXTAGS
+
+ specifies (using Bourne shell syntax) that the commands `\def',
+ `\newcommand' and `\newenvironment' also define tags.
+
+ * In Lisp code, any function defined with `defun', any variable
+ defined with `defvar' or `defconst', and in general the first
+ argument of any expression that starts with `(def' in column zero,
+ is a tag.
+
+ * In Scheme code, tags include anything defined with `def' or with a
+ construct whose name starts with `def'. They also include
+ variables set with `set!' at top level in the file.
+
+ Several other languages are also supported:
+
+ * In Ada code, functions, procedures, packages, tasks, and types are
+ tags. Use the `--packages-only' option to create tags for packages
+ only.
+
+ * In assembler code, labels appearing at the beginning of a line,
+ followed by a colon, are tags.
+
+ * In Bison or Yacc input files, each rule defines as a tag the
+ nonterminal it constructs. The portions of the file that contain
+ C code are parsed as C code.
+
+ * In Cobol code, tags are paragraph names; that is, any word
+ starting in column 8 and followed by a period.
+
+ * In Erlang code, the tags are the functions, records, and macros
+ defined in the file.
+
+ * In Fortran code, functions, subroutines and blockdata are tags.
+
+ * In Objective C code, tags include Objective C definitions for
+ classes, class categories, methods, and protocols.
+
+ * In Pascal code, the tags are the functions and procedures defined
+ in the file.
+
+ * In Perl code, the tags are the procedures defined by the `sub',
+ `my' and `local' keywords. Use `--globals' if you want to tag
+ global variables.
+
+ * In Postscript code, the tags are the functions.
+
+ * In Prolog code, a tag name appears at the left margin.
+
+ * In Python code, `def' or `class' at the beginning of a line
+ generate a tag.
+
+ You can also generate tags based on regexp matching (*note Etags
+Regexps::) to handle other formats and languages.
+
+\1f
+File: xemacs.info, Node: Create Tags Table, Next: Etags Regexps, Prev: Tag Syntax, Up: Tags
+
+Creating Tags Tables
+--------------------
+
+ The `etags' program is used to create a tags table file. It knows
+the syntax of several languages, as described in *Note Tag Syntax::.
+Here is how to run `etags':
+
+ etags INPUTFILES...
+
+The `etags' program reads the specified files, and writes a tags table
+named `TAGS' in the current working directory. You can intermix
+compressed and plain text source file names. `etags' knows about the
+most common compression formats, and does the right thing. So you can
+compress all your source files and have `etags' look for compressed
+versions of its file name arguments, if it does not find uncompressed
+versions. Under MS-DOS, `etags' also looks for file names like
+`mycode.cgz' if it is given `mycode.c' on the command line and
+`mycode.c' does not exist.
+
+ `etags' recognizes the language used in an input file based on its
+file name and contents. You can specify the language with the
+`--language=NAME' option, described below.
+
+ If the tags table data become outdated due to changes in the files
+described in the table, the way to update the tags table is the same
+way it was made in the first place. It is not necessary to do this
+often.
+
+ If the tags table fails to record a tag, or records it for the wrong
+file, then Emacs cannot possibly find its definition. However, if the
+position recorded in the tags table becomes a little bit wrong (due to
+some editing in the file that the tag definition is in), the only
+consequence is a slight delay in finding the tag. Even if the stored
+position is very wrong, Emacs will still find the tag, but it must
+search the entire file for it.
+
+ So you should update a tags table when you define new tags that you
+want to have listed, or when you move tag definitions from one file to
+another, or when changes become substantial. Normally there is no need
+to update the tags table after each edit, or even every day.
+
+ One tags table can effectively include another. Specify the included
+tags file name with the `--include=FILE' option when creating the file
+that is to include it. The latter file then acts as if it contained
+all the files specified in the included file, as well as the files it
+directly contains.
+
+ If you specify the source files with relative file names when you run
+`etags', the tags file will contain file names relative to the
+directory where the tags file was initially written. This way, you can
+move an entire directory tree containing both the tags file and the
+source files, and the tags file will still refer correctly to the source
+files.
+
+ If you specify absolute file names as arguments to `etags', then the
+tags file will contain absolute file names. This way, the tags file
+will still refer to the same files even if you move it, as long as the
+source files remain in the same place. Absolute file names start with
+`/', or with `DEVICE:/' on MS-DOS and MS-Windows.
+
+ When you want to make a tags table from a great number of files, you
+may have problems listing them on the command line, because some systems
+have a limit on its length. The simplest way to circumvent this limit
+is to tell `etags' to read the file names from its standard input, by
+typing a dash in place of the file names, like this:
+
+ find . -name "*.[chCH]" -print | etags -
+
+ Use the option `--language=NAME' to specify the language explicitly.
+You can intermix these options with file names; each one applies to
+the file names that follow it. Specify `--language=auto' to tell
+`etags' to resume guessing the language from the file names and file
+contents. Specify `--language=none' to turn off language-specific
+processing entirely; then `etags' recognizes tags by regexp matching
+alone (*note Etags Regexps::).
+
+ `etags --help' prints the list of the languages `etags' knows, and
+the file name rules for guessing the language. It also prints a list of
+all the available `etags' options, together with a short explanation.
+
+\1f
+File: xemacs.info, Node: Etags Regexps, Next: Select Tags Table, Prev: Create Tags Table, Up: Tags
+
+Etags Regexps
+-------------
+
+ The `--regex' option provides a general way of recognizing tags
+based on regexp matching. You can freely intermix it with file names.
+Each `--regex' option adds to the preceding ones, and applies only to
+the following files. The syntax is:
+
+ --regex=/TAGREGEXP[/NAMEREGEXP]/
+
+where TAGREGEXP is used to match the lines to tag. It is always
+anchored, that is, it behaves as if preceded by `^'. If you want to
+account for indentation, just match any initial number of blanks by
+beginning your regular expression with `[ \t]*'. In the regular
+expressions, `\' quotes the next character, and `\t' stands for the tab
+character. Note that `etags' does not handle the other C escape
+sequences for special characters.
+
+ The syntax of regular expressions in `etags' is the same as in
+Emacs, augmented with the "interval operator", which works as in `grep'
+and `ed'. The syntax of an interval operator is `\{M,N\}', and its
+meaning is to match the preceding expression at least M times and up to
+N times.
+
+ You should not match more characters with TAGREGEXP than that needed
+to recognize what you want to tag. If the match is such that more
+characters than needed are unavoidably matched by TAGREGEXP (as will
+usually be the case), you should add a NAMEREGEXP, to pick out just the
+tag. This will enable Emacs to find tags more accurately and to do
+completion on tag names more reliably. You can find some examples
+below.
+
+ The option `--ignore-case-regex' (or `-c') is like `--regex', except
+that the regular expression provided will be matched without regard to
+case, which is appropriate for various programming languages.
+
+ The `-R' option deletes all the regexps defined with `--regex'
+options. It applies to the file names following it, as you can see
+from the following example:
+
+ etags --regex=/REG1/ voo.doo --regex=/REG2/ \
+ bar.ber -R --lang=lisp los.er
+
+Here `etags' chooses the parsing language for `voo.doo' and `bar.ber'
+according to their contents. `etags' also uses REG1 to recognize
+additional tags in `voo.doo', and both REG1 and REG2 to recognize
+additional tags in `bar.ber'. `etags' uses the Lisp tags rules, and no
+regexp matching, to recognize tags in `los.er'.
+
+ A regular expression can be bound to a given language, by prepending
+it with `{lang}'. When you do this, `etags' will use the regular
+expression only for files of that language. `etags --help' prints the
+list of languages recognised by `etags'. The following example tags
+the `DEFVAR' macros in the Emacs source files. `etags' applies this
+regular expression to C files only:
+
+ --regex='{c}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/'
+
+This feature is particularly useful when storing a list of regular
+expressions in a file. The following option syntax instructs `etags'
+to read two files of regular expressions. The regular expressions
+contained in the second file are matched without regard to case.
+
+ --regex=@first-file --ignore-case-regex=@second-file
+
+A regex file contains one regular expressions per line. Empty lines,
+and lines beginning with space or tab are ignored. When the first
+character in a line is `@', `etags' assumes that the rest of the line
+is the name of a file of regular expressions. This means that such
+files can be nested. All the other lines are taken to be regular
+expressions. For example, one can create a file called `emacs.tags'
+with the following contents (the first line in the file is a comment):
+
+ -- This is for GNU Emacs source files
+ {c}/[ \t]*DEFVAR_[A-Z_ \t(]+"\([^"]+\)"/\1/
+
+and then use it like this:
+
+ etags --regex=@emacs.tags *.[ch] */*.[ch]
+
+ Here are some more examples. The regexps are quoted to protect them
+from shell interpretation.
+
+ * Tag Octave files:
+
+ etags --language=none \
+ --regex='/[ \t]*function.*=[ \t]*\([^ \t]*\)[ \t]*(/\1/' \
+ --regex='/###key \(.*\)/\1/' \
+ --regex='/[ \t]*global[ \t].*/' \
+ *.m
+
+ Note that tags are not generated for scripts so that you have to
+ add a line by yourself of the form `###key <script-name>' if you
+ want to jump to it.
+
+ * Tag Tcl files:
+
+ etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' *.tcl
+
+ * Tag VHDL files:
+
+ --language=none \
+ --regex='/[ \t]*\(ARCHITECTURE\|CONFIGURATION\) +[^ ]* +OF/' \
+ --regex='/[ \t]*\(ATTRIBUTE\|ENTITY\|FUNCTION\|PACKAGE\
+ \( BODY\)?\|PROCEDURE\|PROCESS\|TYPE\)[ \t]+\([^ \t(]+\)/\3/'
+
+\1f
+File: xemacs.info, Node: Select Tags Table, Next: Find Tag, Prev: Etags Regexps, Up: Tags
+
+Selecting a Tags Table
+----------------------
+
+ At any time Emacs has one "selected" tags table, and all the commands
+for working with tags tables use the selected one. To select a tags
+table, use the variable `tag-table-alist'.
+
+ The value of `tag-table-alist' is a list that determines which
+`TAGS' files should be active for a given buffer. This is not really
+an association list, in that all elements are checked. The car of each
+element of this list is a pattern against which the buffers file name
+is compared; if it matches, then the cdr of the list should be the name
+of the tags table to use. If more than one element of this list
+matches the buffers file name, all of the associated tags tables are
+used. Earlier ones are searched first.
+
+ If the car of elements of this list are strings, they are treated as
+regular-expressions against which the file is compared (like the
+`auto-mode-alist'). If they are not strings, they are evaluated. If
+they evaluate to non-`nil', the current buffer is considered to match.
+
+ If the cdr of the elements of this list are strings, they are
+assumed to name a tags file. If they name a directory, the string
+`tags' is appended to them to get the file name. If they are not
+strings, they are evaluated and must return an appropriate string.
+
+ For example:
+
+ (setq tag-table-alist
+ '(("/usr/src/public/perl/" . "/usr/src/public/perl/perl-3.0/")
+ ("\\.el$" . "/usr/local/emacs/src/")
+ ("/jbw/gnu/" . "/usr15/degree/stud/jbw/gnu/")
+ ("" . "/usr/local/emacs/src/")
+ ))
+
+ The example defines the tags table alist in the following way:
+
+ * Anything in the directory `/usr/src/public/perl/' should use the
+ `TAGS' file `/usr/src/public/perl/perl-3.0/TAGS'.
+
+ * Files ending in `.el' should use the `TAGS' file
+ `/usr/local/emacs/src/TAGS'.
+
+ * Anything in or below the directory `/jbw/gnu/' should use the
+ `TAGS' file `/usr15/degree/stud/jbw/gnu/TAGS'.
+
+ If you had a file called `/usr/jbw/foo.el', it would use both `TAGS'
+files,
+`/usr/local/emacs/src/TAGS' and `/usr15/degree/stud/jbw/gnu/TAGS' (in
+that order), because it matches both patterns.
+
+ If the buffer-local variable `buffer-tag-table' is set, it names a
+tags table that is searched before all others when `find-tag' is
+executed from this buffer.
+
+ If there is a file called `TAGS' in the same directory as the file
+in question, then that tags file will always be used as well (after the
+`buffer-tag-table' but before the tables specified by this list).
+
+ If the variable `tags-file-name' is set, the `TAGS' file it names
+will apply to all buffers (for backwards compatibility.) It is searched
+first.
+
+ If the value of the variable `tags-always-build-completion-table' is
+`t', the tags file will always be added to the completion table without
+asking first, regardless of the size of the tags file.
+
+ The function `M-x visit-tags-table', is largely made obsolete by the
+variable `tag-table-alist', tells tags commands to use the tags table
+file FILE first. The FILE should be the name of a file created with
+the `etags' program. A directory name is also acceptable; it means the
+file `TAGS' in that directory. The function only stores the file name
+you provide in the variable `tags-file-name'. Emacs does not actually
+read in the tags table contents until you try to use them. You can set
+the variable explicitly instead of using `visit-tags-table'. The value
+of the variable `tags-file-name' is the name of the tags table used by
+all buffers. This is for backward compatibility, and is largely
+supplanted by the variable `tag-table-alist'.
+
+\1f
+File: xemacs.info, Node: Find Tag, Next: Tags Search, Prev: Select Tags Table, Up: Tags
+
+Finding a Tag
+-------------
+
+ The most important thing that a tags table enables you to do is to
+find the definition of a specific tag.
+
+`M-. TAG &OPTIONAL OTHER-WINDOW'
+ Find first definition of TAG (`find-tag').
+
+`C-u M-.'
+ Find next alternate definition of last tag specified.
+
+`C-x 4 . TAG'
+ Find first definition of TAG, but display it in another window
+ (`find-tag-other-window').
+
+ `M-.' (`find-tag') is the command to find the definition of a
+specified tag. It searches through the tags table for that tag, as a
+string, then uses the tags table information to determine the file in
+which the definition is used and the approximate character position of
+the definition in the file. Then `find-tag' visits the file, moves
+point to the approximate character position, and starts searching
+ever-increasing distances away for the text that should appear at the
+beginning of the definition.
+
+ If an empty argument is given (by typing <RET>), the sexp in the
+buffer before or around point is used as the name of the tag to find.
+*Note Lists::, for information on sexps.
+
+ The argument to `find-tag' need not be the whole tag name; it can be
+a substring of a tag name. However, there can be many tag names
+containing the substring you specify. Since `find-tag' works by
+searching the text of the tags table, it finds the first tag in the
+table that the specified substring appears in. To find other tags that
+match the substring, give `find-tag' a numeric argument, as in `C-u
+M-.'. This does not read a tag name, but continues searching the tag
+table's text for another tag containing the same substring last used.
+If your keyboard has a real <META> key, `M-0 M-.' is an easier
+alternative to `C-u M-.'.
+
+ If the optional second argument OTHER-WINDOW is non-`nil', it uses
+another window to display the tag. Multiple active tags tables and
+completion are supported.
+
+ Variables of note include the following:
+
+`tag-table-alist'
+ Controls which tables apply to which buffers.
+
+`tags-file-name'
+ Stores a default tags table.
+
+`tags-build-completion-table'
+ Controls completion behavior.
+
+`buffer-tag-table'
+ Specifies a buffer-local table.
+
+`make-tags-files-invisible'
+ Sets whether tags tables should be very hidden.
+
+`tag-mark-stack-max'
+ Specifies how many tags-based hops to remember.
+
+ Like most commands that can switch buffers, `find-tag' has another
+similar command that displays the new buffer in another window. `C-x 4
+.' invokes the function `find-tag-other-window'. (This key sequence
+ends with a period.)
+
+ Emacs comes with a tags table file `TAGS' (in the directory
+containing Lisp libraries) that includes all the Lisp libraries and all
+the C sources of Emacs. By specifying this file with `visit-tags-table'
+and then using `M-.' you can quickly look at the source of any Emacs
+function.
+
+\1f
File: xemacs.info, Node: Tags Search, Next: List Tags, Prev: Find Tag, Up: Tags
Searching and Replacing with Tags Tables
* Compiling Libraries:: Compiling a library makes it load and run faster.
* Mocklisp:: Converting Mocklisp to Lisp so XEmacs can run it.
-\1f
-File: xemacs.info, Node: Loading, Next: Compiling Libraries, Prev: Lisp Libraries, Up: Lisp Libraries
-
-Loading Libraries
------------------
-
-`M-x load-file FILE'
- Load the file FILE of Lisp code.
-
-`M-x load-library LIBRARY'
- Load the library named LIBRARY.
-
-`M-x locate-library LIBRARY &optional NOSUFFIX'
- Show the full path name of Emacs library LIBRARY.
-
- To execute a file of Emacs Lisp, use `M-x load-file'. This command
-reads the file name you provide in the minibuffer, then executes the
-contents of that file as Lisp code. It is not necessary to visit the
-file first; in fact, this command reads the file as found on disk, not
-the text in an Emacs buffer.
-
- Once a file of Lisp code is installed in the Emacs Lisp library
-directories, users can load it using `M-x load-library'. Programs can
-load it by calling `load-library', or with `load', a more primitive
-function that is similar but accepts some additional arguments.
-
- `M-x load-library' differs from `M-x load-file' in that it searches
-a sequence of directories and tries three file names in each directory.
-The three names are: first, the specified name with `.elc' appended;
-second, the name with `.el' appended; third, the specified name alone.
-A `.elc' file would be the result of compiling the Lisp file into byte
-code; if possible, it is loaded in preference to the Lisp file itself
-because the compiled file loads and runs faster.
-
- Because the argument to `load-library' is usually not in itself a
-valid file name, file name completion is not available. In fact, when
-using this command, you usually do not know exactly what file name will
-be used.
-
- The sequence of directories searched by `M-x load-library' is
-specified by the variable `load-path', a list of strings that are
-directory names. The elements of this list may not begin with "`~'",
-so you must call `expand-file-name' on them before adding them to the
-list. The default value of the list contains the directory where the
-Lisp code for Emacs itself is stored. If you have libraries of your
-own, put them in a single directory and add that directory to
-`load-path'. `nil' in this list stands for the current default
-directory, but it is probably not a good idea to put `nil' in the list.
-If you start wishing that `nil' were in the list, you should probably
-use `M-x load-file' for this case.
-
- The variable is initialized by the EMACSLOADPATH environment
-variable. If no value is specified, the variable takes the default value
-specified in the file `paths.h' when Emacs was built. If a path isn't
-specified in `paths.h', a default value is obtained from the file
-system, near the directory in which the Emacs executable resides.
-
- Like `M-x load-library', `M-x locate-library' searches the
-directories in `load-path' to find the file that `M-x load-library'
-would load. If the optional second argument NOSUFFIX is non-`nil', the
-suffixes `.elc' or `.el' are not added to the specified name LIBRARY
-(like calling `load' instead of `load-library').
-
- You often do not have to give any command to load a library, because
-the commands defined in the library are set up to "autoload" that
-library. Running any of those commands causes `load' to be called to
-load the library; this replaces the autoload definitions with the real
-ones from the library.
-
- If autoloading a file does not finish, either because of an error or
-because of a `C-g' quit, all function definitions made by the file are
-undone automatically. So are any calls to `provide'. As a
-consequence, the entire file is loaded a second time if you use one of
-the autoloadable commands again. This prevents problems when the
-command is no longer autoloading but is working incorrectly because the
-file was only partially loaded. Function definitions are undone only
-for autoloading; explicit calls to `load' do not undo anything if
-loading is not completed.
-
- The variable `after-load-alist' takes an alist of expressions to be
-evaluated when particular files are loaded. Each element has the form
-`(FILENAME forms...)'. When `load' is run and the filename argument is
-FILENAME, the forms in the corresponding element are executed at the
-end of loading.
-
- FILENAME must match exactly. Normally FILENAME is the name of a
-library, with no directory specified, since that is how load is
-normally called. An error in `forms' does not undo the load, but it
-does prevent execution of the rest of the `forms'.
-
-\1f
-File: xemacs.info, Node: Compiling Libraries, Next: Mocklisp, Prev: Loading, Up: Lisp Libraries
-
-Compiling Libraries
--------------------
-
- Emacs Lisp code can be compiled into byte-code which loads faster,
-takes up less space when loaded, and executes faster.
-
-`M-x batch-byte-compile'
- Run byte-compile-file on the files remaining on the command line.
-
-`M-x byte-compile-buffer &optional BUFFER'
- Byte-compile and evaluate contents of BUFFER (default is current
- buffer).
-
-`M-x byte-compile-file'
- Compile a file of Lisp code named FILENAME into a file of byte
- code.
-
-`M-x byte-compile-and-load-file FILENAME'
- Compile a file of Lisp code named FILENAME into a file of byte
- code and load it.
-
-`M-x byte-recompile-directory DIRECTORY'
- Recompile every `.el' file in DIRECTORY that needs recompilation.
-
-`M-x disassemble'
- Print disassembled code for OBJECT on (optional) STREAM.
-
-`M-x make-obsolete FUNCTION NEW'
- Make the byte-compiler warn that FUNCTION is obsolete and NEW
- should be used instead.
-
- `byte-compile-file' creates a byte-code compiled file from an
-Emacs-Lisp source file. The default argument for this function is the
-file visited in the current buffer. The function reads the specified
-file, compiles it into byte code, and writes an output file whose name
-is made by appending `c' to the input file name. Thus, the file
-`rmail.el' would be compiled into `rmail.elc'. To compile a file of
-Lisp code named FILENAME into a file of byte code and then load it, use
-`byte-compile-and-load-file'. To compile and evaluate Lisp code in a
-given buffer, use `byte-compile-buffer'.
-
- To recompile all changed Lisp files in a directory, use `M-x
-byte-recompile-directory'. Specify just the directory name as an
-argument. Each `.el' file that has been byte-compiled before is
-byte-compiled again if it has changed since the previous compilation.
-A numeric argument to this command tells it to offer to compile each
-`.el' file that has not been compiled yet. You must answer `y' or `n'
-to each offer.
-
- You can use the function `batch-byte-compile' to invoke Emacs
-non-interactively from the shell to do byte compilation. When you use
-this function, the files to be compiled are specified with command-line
-arguments. Use a shell command of the form:
-
- emacs -batch -f batch-byte-compile FILES...
-
- Directory names may also be given as arguments; in that case,
-`byte-recompile-directory' is invoked on each such directory.
-`batch-byte-compile' uses all remaining command-line arguments as file
-or directory names, then kills the Emacs process.
-
- `M-x disassemble' explains the result of byte compilation. Its
-argument is a function name. It displays the byte-compiled code in a
-help window in symbolic form, one instruction per line. If the
-instruction refers to a variable or constant, that is shown, too.
-
-\1f
-File: xemacs.info, Node: Mocklisp, Prev: Compiling Libraries, Up: Lisp Libraries
-
-Converting Mocklisp to Lisp
----------------------------
-
- XEmacs can run Mocklisp files by converting them to Emacs Lisp first.
-To convert a Mocklisp file, visit it and then type `M-x
-convert-mocklisp-buffer'. Then save the resulting buffer of Lisp file
-in a file whose name ends in `.el' and use the new file as a Lisp
-library.
-
- You cannot currently byte-compile converted Mocklisp code. The
-reason is that converted Mocklisp code uses some special Lisp features
-to deal with Mocklisp's incompatible ideas of how arguments are
-evaluated and which values signify "true" or "false".
-
-\1f
-File: xemacs.info, Node: Lisp Eval, Next: Lisp Debug, Prev: Lisp Libraries, Up: Running
-
-Evaluating Emacs-Lisp Expressions
-=================================
-
- Lisp programs intended to be run in Emacs should be edited in
-Emacs-Lisp mode; this will happen automatically for file names ending in
-`.el'. By contrast, Lisp mode itself should be used for editing Lisp
-programs intended for other Lisp systems. Emacs-Lisp mode can be
-selected with the command `M-x emacs-lisp-mode'.
-
- For testing of Lisp programs to run in Emacs, it is useful to be able
-to evaluate part of the program as it is found in the Emacs buffer. For
-example, if you change the text of a Lisp function definition and then
-evaluate the definition, Emacs installs the change for future calls to
-the function. Evaluation of Lisp expressions is also useful in any
-kind of editing task for invoking non-interactive functions (functions
-that are not commands).
-
-`M-<ESC>'
- Read a Lisp expression in the minibuffer, evaluate it, and print
- the value in the minibuffer (`eval-expression').
-
-`C-x C-e'
- Evaluate the Lisp expression before point, and print the value in
- the minibuffer (`eval-last-sexp').
-
-`C-M-x'
- Evaluate the defun containing point or after point, and print the
- value in the minibuffer (`eval-defun').
-
-`M-x eval-region'
- Evaluate all the Lisp expressions in the region.
-
-`M-x eval-current-buffer'
- Evaluate all the Lisp expressions in the buffer.
-
- `M-<ESC>' (`eval-expression') is the most basic command for
-evaluating a Lisp expression interactively. It reads the expression
-using the minibuffer, so you can execute any expression on a buffer
-regardless of what the buffer contains. When evaluation is complete,
-the current buffer is once again the buffer that was current when
-`M-<ESC>' was typed.
-
- `M-<ESC>' can easily confuse users, especially on keyboards with
-autorepeat, where it can result from holding down the <ESC> key for too
-long. Therefore, `eval-expression' is normally a disabled command.
-Attempting to use this command asks for confirmation and gives you the
-option of enabling it; once you enable the command, you are no longer
-required to confirm. *Note Disabling::.
-
- In Emacs-Lisp mode, the key `C-M-x' is bound to the function
-`eval-defun', which parses the defun containing point or following point
-as a Lisp expression and evaluates it. The value is printed in the echo
-area. This command is convenient for installing in the Lisp environment
-changes that you have just made in the text of a function definition.
-
- The command `C-x C-e' (`eval-last-sexp') performs a similar job but
-is available in all major modes, not just Emacs-Lisp mode. It finds
-the sexp before point, reads it as a Lisp expression, evaluates it, and
-prints the value in the echo area. It is sometimes useful to type in an
-expression and then, with point still after it, type `C-x C-e'.
-
- If `C-M-x' or `C-x C-e' are given a numeric argument, they print the
-value by inserting it into the current buffer at point, rather than in
-the echo area. The argument value does not matter.
-
- The most general command for evaluating Lisp expressions from a
-buffer is `eval-region'. `M-x eval-region' parses the text of the
-region as one or more Lisp expressions, evaluating them one by one.
-`M-x eval-current-buffer' is similar, but it evaluates the entire
-buffer. This is a reasonable way to install the contents of a file of
-Lisp code that you are just ready to test. After finding and fixing a
-bug, use `C-M-x' on each function that you change, to keep the Lisp
-world in step with the source file.
-
-\1f
-File: xemacs.info, Node: Lisp Debug, Next: Lisp Interaction, Prev: Lisp Eval, Up: Running
-
-The Emacs-Lisp Debugger
-=======================
-
- XEmacs contains a debugger for Lisp programs executing inside it.
-This debugger is normally not used; many commands frequently get Lisp
-errors when invoked in inappropriate contexts (such as `C-f' at the end
-of the buffer) and it would be unpleasant to enter a special debugging
-mode in this case. When you want to make Lisp errors invoke the
-debugger, you must set the variable `debug-on-error' to non-`nil'.
-Quitting with `C-g' is not considered an error, and `debug-on-error'
-has no effect on the handling of `C-g'. However, if you set
-`debug-on-quit' to be non-`nil', `C-g' will invoke the debugger. This
-can be useful for debugging an infinite loop; type `C-g' once the loop
-has had time to reach its steady state. `debug-on-quit' has no effect
-on errors.
-
- You can make Emacs enter the debugger when a specified function is
-called or at a particular place in Lisp code. Use `M-x debug-on-entry'
-with argument FUN-NAME to have Emacs enter the debugger as soon as
-FUN-NAME is called. Use `M-x cancel-debug-on-entry' to make the
-function stop entering the debugger when called. (Redefining the
-function also does this.) To enter the debugger from some other place
-in Lisp code, you must insert the expression `(debug)' there and
-install the changed code with `C-M-x'. *Note Lisp Eval::.
-
- When the debugger is entered, it displays the previously selected
-buffer in one window and a buffer named `*Backtrace*' in another
-window. The backtrace buffer contains one line for each level of Lisp
-function execution currently going on. At the beginning of the buffer
-is a message describing the reason that the debugger was invoked, for
-example, an error message if it was invoked due to an error.
-
- The backtrace buffer is read-only and is in Backtrace mode, a special
-major mode in which letters are defined as debugger commands. The
-usual Emacs editing commands are available; you can switch windows to
-examine the buffer that was being edited at the time of the error, and
-you can switch buffers, visit files, and perform any other editing
-operations. However, the debugger is a recursive editing level (*note
-Recursive Edit::); it is a good idea to return to the backtrace buffer
-and explicitly exit the debugger when you don't want to use it any
-more. Exiting the debugger kills the backtrace buffer.
-
- The contents of the backtrace buffer show you the functions that are
-executing and the arguments that were given to them. It also allows you
-to specify a stack frame by moving point to the line describing that
-frame. The frame whose line point is on is considered the "current
-frame". Some of the debugger commands operate on the current frame.
-Debugger commands are mainly used for stepping through code one
-expression at a time. Here is a list of them:
-
-`c'
- Exit the debugger and continue execution. In most cases,
- execution of the program continues as if the debugger had never
- been entered (aside from the effect of any variables or data
- structures you may have changed while inside the debugger). This
- includes entry to the debugger due to function entry or exit,
- explicit invocation, and quitting or certain errors. Most errors
- cannot be continued; trying to continue an error usually causes
- the same error to occur again.
-
-`d'
- Continue execution, but enter the debugger the next time a Lisp
- function is called. This allows you to step through the
- subexpressions of an expression, and see what the subexpressions
- do and what values they compute.
-
- When you enter the debugger this way, Emacs flags the stack frame
- for the function call from which you entered. The same function
- is then called when you exit the frame. To cancel this flag, use
- `u'.
-
-`b'
- Set up to enter the debugger when the current frame is exited.
- Frames that invoke the debugger on exit are flagged with stars.
-
-`u'
- Don't enter the debugger when the current frame is exited. This
- cancels a `b' command on a frame.
-
-`e'
- Read a Lisp expression in the minibuffer, evaluate it, and print
- the value in the echo area. This is equivalent to the command
- `M-<ESC>', except that `e' is not normally disabled like `M-<ESC>'.
-
-`q'
- Terminate the program being debugged; return to top-level Emacs
- command execution.
-
- If the debugger was entered due to a `C-g' but you really want to
- quit, not to debug, use the `q' command.
-
-`r'
- Return a value from the debugger. The value is computed by
- reading an expression with the minibuffer and evaluating it.
-
- The value returned by the debugger makes a difference when the
- debugger was invoked due to exit from a Lisp call frame (as
- requested with `b'); then the value specified in the `r' command
- is used as the value of that frame.
-
- The debugger's return value also matters with many errors. For
- example, `wrong-type-argument' errors will use the debugger's
- return value instead of the invalid argument; `no-catch' errors
- will use the debugger value as a throw tag instead of the tag that
- was not found. If an error was signaled by calling the Lisp
- function `signal', the debugger's return value is returned as the
- value of `signal'.
-
-\1f
-File: xemacs.info, Node: Lisp Interaction, Next: External Lisp, Prev: Lisp Debug, Up: Running
-
-Lisp Interaction Buffers
-========================
-
- The buffer `*scratch*', which is selected when Emacs starts up, is
-provided for evaluating Lisp expressions interactively inside Emacs.
-Both the expressions you evaluate and their output goes in the buffer.
-
- The `*scratch*' buffer's major mode is Lisp Interaction mode, which
-is the same as Emacs-Lisp mode except for one command, <LFD>. In
-Emacs-Lisp mode, <LFD> is an indentation command. In Lisp Interaction
-mode, <LFD> is bound to `eval-print-last-sexp'. This function reads
-the Lisp expression before point, evaluates it, and inserts the value
-in printed representation before point.
-
- The way to use the `*scratch*' buffer is to insert Lisp expressions
-at the end, ending each one with <LFD> so that it will be evaluated.
-The result is a complete typescript of the expressions you have
-evaluated and their values.
-
- The rationale for this feature is that Emacs must have a buffer when
-it starts up, but that buffer is not useful for editing files since a
-new buffer is made for every file that you visit. The Lisp interpreter
-typescript is the most useful thing I can think of for the initial
-buffer to do. `M-x lisp-interaction-mode' will put any buffer in Lisp
-Interaction mode.
-
-\1f
-File: xemacs.info, Node: External Lisp, Prev: Lisp Interaction, Up: Running
-
-Running an External Lisp
-========================
-
- Emacs has facilities for running programs in other Lisp systems.
-You can run a Lisp process as an inferior of Emacs, and pass
-expressions to it to be evaluated. You can also pass changed function
-definitions directly from the Emacs buffers in which you edit the Lisp
-programs to the inferior Lisp process.
-
- To run an inferior Lisp process, type `M-x run-lisp'. This runs the
-program named `lisp', the same program you would run by typing `lisp'
-as a shell command, with both input and output going through an Emacs
-buffer named `*lisp*'. In other words, any "terminal output" from Lisp
-will go into the buffer, advancing point, and any "terminal input" for
-Lisp comes from text in the buffer. To give input to Lisp, go to the
-end of the buffer and type the input, terminated by <RET>. The
-`*lisp*' buffer is in Inferior Lisp mode, which has all the special
-characteristics of Lisp mode and Shell mode (*note Shell Mode::).
-
- Use Lisp mode to run the source files of programs in external Lisps.
-You can select this mode with `M-x lisp-mode'. It is used automatically
-for files whose names end in `.l' or `.lisp', as most Lisp systems
-usually expect.
-
- When you edit a function in a Lisp program you are running, the
-easiest way to send the changed definition to the inferior Lisp process
-is the key `C-M-x'. In Lisp mode, this key runs the function
-`lisp-send-defun', which finds the defun around or following point and
-sends it as input to the Lisp process. (Emacs can send input to any
-inferior process regardless of what buffer is current.)
-
- Contrast the meanings of `C-M-x' in Lisp mode (for editing programs
-to be run in another Lisp system) and Emacs-Lisp mode (for editing Lisp
-programs to be run in Emacs): in both modes it has the effect of
-installing the function definition that point is in, but the way of
-doing so is different according to where the relevant Lisp environment
-is found. *Note Lisp Modes::.
-
-\1f
-File: xemacs.info, Node: Packages, Next: Basic, Prev: Startup Paths, Up: Top
-
-Packages
-========
-
- The XEmacs 21 distribution comes only with a very basic set of
-built-in modes and packages. Most of the packages that were part of
-the distribution of earlier versions of XEmacs are now available
-separately. The installer as well as the user can choose which
-packages to install; the actual installation process is easy. This
-gives an installer the ability to tailor an XEmacs installation for
-local needs with safe removal of unnecessary code.
-
-* Menu:
-
-* Package Terminology:: Understanding different kinds of packages.
-* Using Packages:: How to install and use packages.
-* Building Packages:: Building packages from sources.
-* Available Packages:: A brief, out-of-date, directory of packaged LISP.
-
-\1f
-File: xemacs.info, Node: Package Terminology, Next: Using Packages, Up: Packages
-
-Package Flavors
----------------
-
- There are two main flavors of packages.
-
- * Regular Packages A regular package is one in which multiple files
- are involved and one may not in general safely remove any of them.
-
- * Single-File Packages A single-file package is an aggregate
- collection of thematically related but otherwise independent lisp
- files. These files are bundled together for download convenience
- and individual files may be deleted at will without any loss of
- functionality.
-
-Package Distributions
----------------------
-
- XEmacs Lisp packages are distributed in two ways, depending on the
-intended use. Binary Packages are for installers and end-users and may
-be installed directly into an XEmacs package directory. Source Packages
-are for developers and include all files necessary for rebuilding
-bytecompiled lisp and creating tarballs for distribution.
-
-Binary Packages
----------------
-
- Binary packages may be installed directly into an XEmacs package
-hierarchy.
-
-Source Packages
----------------
-
- Source packages contain all of the Package author's (where
-appropriate in regular packages) source code plus all of the files
-necessary to build distribution tarballs (Unix Tar format files,
-gzipped for space savings).
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Loading, Next: Compiling Libraries, Prev: Lisp Libraries, Up: Lisp Libraries
+
+Loading Libraries
+-----------------
+
+`M-x load-file FILE'
+ Load the file FILE of Lisp code.
+
+`M-x load-library LIBRARY'
+ Load the library named LIBRARY.
+
+`M-x locate-library LIBRARY &optional NOSUFFIX'
+ Show the full path name of Emacs library LIBRARY.
+
+ To execute a file of Emacs Lisp, use `M-x load-file'. This command
+reads the file name you provide in the minibuffer, then executes the
+contents of that file as Lisp code. It is not necessary to visit the
+file first; in fact, this command reads the file as found on disk, not
+the text in an Emacs buffer.
+
+ Once a file of Lisp code is installed in the Emacs Lisp library
+directories, users can load it using `M-x load-library'. Programs can
+load it by calling `load-library', or with `load', a more primitive
+function that is similar but accepts some additional arguments.
+
+ `M-x load-library' differs from `M-x load-file' in that it searches
+a sequence of directories and tries three file names in each directory.
+The three names are: first, the specified name with `.elc' appended;
+second, the name with `.el' appended; third, the specified name alone.
+A `.elc' file would be the result of compiling the Lisp file into byte
+code; if possible, it is loaded in preference to the Lisp file itself
+because the compiled file loads and runs faster.
+
+ Because the argument to `load-library' is usually not in itself a
+valid file name, file name completion is not available. In fact, when
+using this command, you usually do not know exactly what file name will
+be used.
+
+ The sequence of directories searched by `M-x load-library' is
+specified by the variable `load-path', a list of strings that are
+directory names. The elements of this list may not begin with "`~'",
+so you must call `expand-file-name' on them before adding them to the
+list. The default value of the list contains the directory where the
+Lisp code for Emacs itself is stored. If you have libraries of your
+own, put them in a single directory and add that directory to
+`load-path'. `nil' in this list stands for the current default
+directory, but it is probably not a good idea to put `nil' in the list.
+If you start wishing that `nil' were in the list, you should probably
+use `M-x load-file' for this case.
+
+ The variable is initialized by the EMACSLOADPATH environment
+variable. If no value is specified, the variable takes the default value
+specified in the file `paths.h' when Emacs was built. If a path isn't
+specified in `paths.h', a default value is obtained from the file
+system, near the directory in which the Emacs executable resides.
+
+ Like `M-x load-library', `M-x locate-library' searches the
+directories in `load-path' to find the file that `M-x load-library'
+would load. If the optional second argument NOSUFFIX is non-`nil', the
+suffixes `.elc' or `.el' are not added to the specified name LIBRARY
+(like calling `load' instead of `load-library').
+
+ You often do not have to give any command to load a library, because
+the commands defined in the library are set up to "autoload" that
+library. Running any of those commands causes `load' to be called to
+load the library; this replaces the autoload definitions with the real
+ones from the library.
+
+ If autoloading a file does not finish, either because of an error or
+because of a `C-g' quit, all function definitions made by the file are
+undone automatically. So are any calls to `provide'. As a
+consequence, the entire file is loaded a second time if you use one of
+the autoloadable commands again. This prevents problems when the
+command is no longer autoloading but is working incorrectly because the
+file was only partially loaded. Function definitions are undone only
+for autoloading; explicit calls to `load' do not undo anything if
+loading is not completed.
+
+ The variable `after-load-alist' takes an alist of expressions to be
+evaluated when particular files are loaded. Each element has the form
+`(FILENAME forms...)'. When `load' is run and the filename argument is
+FILENAME, the forms in the corresponding element are executed at the
+end of loading.
+
+ FILENAME must match exactly. Normally FILENAME is the name of a
+library, with no directory specified, since that is how load is
+normally called. An error in `forms' does not undo the load, but it
+does prevent execution of the rest of the `forms'.
+
+\1f
+File: xemacs.info, Node: Compiling Libraries, Next: Mocklisp, Prev: Loading, Up: Lisp Libraries
+
+Compiling Libraries
+-------------------
+
+ Emacs Lisp code can be compiled into byte-code which loads faster,
+takes up less space when loaded, and executes faster.
+
+`M-x batch-byte-compile'
+ Run byte-compile-file on the files remaining on the command line.
+
+`M-x byte-compile-buffer &optional BUFFER'
+ Byte-compile and evaluate contents of BUFFER (default is current
+ buffer).
+
+`M-x byte-compile-file'
+ Compile a file of Lisp code named FILENAME into a file of byte
+ code.
+
+`M-x byte-compile-and-load-file FILENAME'
+ Compile a file of Lisp code named FILENAME into a file of byte
+ code and load it.
+
+`M-x byte-recompile-directory DIRECTORY'
+ Recompile every `.el' file in DIRECTORY that needs recompilation.
+
+`M-x disassemble'
+ Print disassembled code for OBJECT on (optional) STREAM.
+
+`M-x make-obsolete FUNCTION NEW'
+ Make the byte-compiler warn that FUNCTION is obsolete and NEW
+ should be used instead.
+
+ `byte-compile-file' creates a byte-code compiled file from an
+Emacs-Lisp source file. The default argument for this function is the
+file visited in the current buffer. The function reads the specified
+file, compiles it into byte code, and writes an output file whose name
+is made by appending `c' to the input file name. Thus, the file
+`rmail.el' would be compiled into `rmail.elc'. To compile a file of
+Lisp code named FILENAME into a file of byte code and then load it, use
+`byte-compile-and-load-file'. To compile and evaluate Lisp code in a
+given buffer, use `byte-compile-buffer'.
+
+ To recompile all changed Lisp files in a directory, use `M-x
+byte-recompile-directory'. Specify just the directory name as an
+argument. Each `.el' file that has been byte-compiled before is
+byte-compiled again if it has changed since the previous compilation.
+A numeric argument to this command tells it to offer to compile each
+`.el' file that has not been compiled yet. You must answer `y' or `n'
+to each offer.
+
+ You can use the function `batch-byte-compile' to invoke Emacs
+non-interactively from the shell to do byte compilation. When you use
+this function, the files to be compiled are specified with command-line
+arguments. Use a shell command of the form:
+
+ emacs -batch -f batch-byte-compile FILES...
+
+ Directory names may also be given as arguments; in that case,
+`byte-recompile-directory' is invoked on each such directory.
+`batch-byte-compile' uses all remaining command-line arguments as file
+or directory names, then kills the Emacs process.
+
+ `M-x disassemble' explains the result of byte compilation. Its
+argument is a function name. It displays the byte-compiled code in a
+help window in symbolic form, one instruction per line. If the
+instruction refers to a variable or constant, that is shown, too.
+
+\1f
+File: xemacs.info, Node: Mocklisp, Prev: Compiling Libraries, Up: Lisp Libraries
+
+Converting Mocklisp to Lisp
+---------------------------
+
+ XEmacs can run Mocklisp files by converting them to Emacs Lisp first.
+To convert a Mocklisp file, visit it and then type `M-x
+convert-mocklisp-buffer'. Then save the resulting buffer of Lisp file
+in a file whose name ends in `.el' and use the new file as a Lisp
+library.
+
+ You cannot currently byte-compile converted Mocklisp code. The
+reason is that converted Mocklisp code uses some special Lisp features
+to deal with Mocklisp's incompatible ideas of how arguments are
+evaluated and which values signify "true" or "false".
+
+\1f
+File: xemacs.info, Node: Lisp Eval, Next: Lisp Debug, Prev: Lisp Libraries, Up: Running
+
+Evaluating Emacs-Lisp Expressions
+=================================
+
+ Lisp programs intended to be run in Emacs should be edited in
+Emacs-Lisp mode; this will happen automatically for file names ending in
+`.el'. By contrast, Lisp mode itself should be used for editing Lisp
+programs intended for other Lisp systems. Emacs-Lisp mode can be
+selected with the command `M-x emacs-lisp-mode'.
+
+ For testing of Lisp programs to run in Emacs, it is useful to be able
+to evaluate part of the program as it is found in the Emacs buffer. For
+example, if you change the text of a Lisp function definition and then
+evaluate the definition, Emacs installs the change for future calls to
+the function. Evaluation of Lisp expressions is also useful in any
+kind of editing task for invoking non-interactive functions (functions
+that are not commands).
+
+`M-<ESC>'
+ Read a Lisp expression in the minibuffer, evaluate it, and print
+ the value in the minibuffer (`eval-expression').
+
+`C-x C-e'
+ Evaluate the Lisp expression before point, and print the value in
+ the minibuffer (`eval-last-sexp').
+
+`C-M-x'
+ Evaluate the defun containing point or after point, and print the
+ value in the minibuffer (`eval-defun').
+
+`M-x eval-region'
+ Evaluate all the Lisp expressions in the region.
+
+`M-x eval-current-buffer'
+ Evaluate all the Lisp expressions in the buffer.
+
+ `M-<ESC>' (`eval-expression') is the most basic command for
+evaluating a Lisp expression interactively. It reads the expression
+using the minibuffer, so you can execute any expression on a buffer
+regardless of what the buffer contains. When evaluation is complete,
+the current buffer is once again the buffer that was current when
+`M-<ESC>' was typed.
+
+ `M-<ESC>' can easily confuse users, especially on keyboards with
+autorepeat, where it can result from holding down the <ESC> key for too
+long. Therefore, `eval-expression' is normally a disabled command.
+Attempting to use this command asks for confirmation and gives you the
+option of enabling it; once you enable the command, you are no longer
+required to confirm. *Note Disabling::.
+
+ In Emacs-Lisp mode, the key `C-M-x' is bound to the function
+`eval-defun', which parses the defun containing point or following point
+as a Lisp expression and evaluates it. The value is printed in the echo
+area. This command is convenient for installing in the Lisp environment
+changes that you have just made in the text of a function definition.
+
+ The command `C-x C-e' (`eval-last-sexp') performs a similar job but
+is available in all major modes, not just Emacs-Lisp mode. It finds
+the sexp before point, reads it as a Lisp expression, evaluates it, and
+prints the value in the echo area. It is sometimes useful to type in an
+expression and then, with point still after it, type `C-x C-e'.
+
+ If `C-M-x' or `C-x C-e' are given a numeric argument, they print the
+value by inserting it into the current buffer at point, rather than in
+the echo area. The argument value does not matter.
+
+ The most general command for evaluating Lisp expressions from a
+buffer is `eval-region'. `M-x eval-region' parses the text of the
+region as one or more Lisp expressions, evaluating them one by one.
+`M-x eval-current-buffer' is similar, but it evaluates the entire
+buffer. This is a reasonable way to install the contents of a file of
+Lisp code that you are just ready to test. After finding and fixing a
+bug, use `C-M-x' on each function that you change, to keep the Lisp
+world in step with the source file.
+
+\1f
+File: xemacs.info, Node: Lisp Debug, Next: Lisp Interaction, Prev: Lisp Eval, Up: Running
+
+The Emacs-Lisp Debugger
+=======================
+
+ XEmacs contains a debugger for Lisp programs executing inside it.
+This debugger is normally not used; many commands frequently get Lisp
+errors when invoked in inappropriate contexts (such as `C-f' at the end
+of the buffer) and it would be unpleasant to enter a special debugging
+mode in this case. When you want to make Lisp errors invoke the
+debugger, you must set the variable `debug-on-error' to non-`nil'.
+Quitting with `C-g' is not considered an error, and `debug-on-error'
+has no effect on the handling of `C-g'. However, if you set
+`debug-on-quit' to be non-`nil', `C-g' will invoke the debugger. This
+can be useful for debugging an infinite loop; type `C-g' once the loop
+has had time to reach its steady state. `debug-on-quit' has no effect
+on errors.
+
+ You can make Emacs enter the debugger when a specified function is
+called or at a particular place in Lisp code. Use `M-x debug-on-entry'
+with argument FUN-NAME to have Emacs enter the debugger as soon as
+FUN-NAME is called. Use `M-x cancel-debug-on-entry' to make the
+function stop entering the debugger when called. (Redefining the
+function also does this.) To enter the debugger from some other place
+in Lisp code, you must insert the expression `(debug)' there and
+install the changed code with `C-M-x'. *Note Lisp Eval::.
+
+ When the debugger is entered, it displays the previously selected
+buffer in one window and a buffer named `*Backtrace*' in another
+window. The backtrace buffer contains one line for each level of Lisp
+function execution currently going on. At the beginning of the buffer
+is a message describing the reason that the debugger was invoked, for
+example, an error message if it was invoked due to an error.
+
+ The backtrace buffer is read-only and is in Backtrace mode, a special
+major mode in which letters are defined as debugger commands. The
+usual Emacs editing commands are available; you can switch windows to
+examine the buffer that was being edited at the time of the error, and
+you can switch buffers, visit files, and perform any other editing
+operations. However, the debugger is a recursive editing level (*note
+Recursive Edit::); it is a good idea to return to the backtrace buffer
+and explicitly exit the debugger when you don't want to use it any
+more. Exiting the debugger kills the backtrace buffer.
+
+ The contents of the backtrace buffer show you the functions that are
+executing and the arguments that were given to them. It also allows you
+to specify a stack frame by moving point to the line describing that
+frame. The frame whose line point is on is considered the "current
+frame". Some of the debugger commands operate on the current frame.
+Debugger commands are mainly used for stepping through code one
+expression at a time. Here is a list of them:
+
+`c'
+ Exit the debugger and continue execution. In most cases,
+ execution of the program continues as if the debugger had never
+ been entered (aside from the effect of any variables or data
+ structures you may have changed while inside the debugger). This
+ includes entry to the debugger due to function entry or exit,
+ explicit invocation, and quitting or certain errors. Most errors
+ cannot be continued; trying to continue an error usually causes
+ the same error to occur again.
+
+`d'
+ Continue execution, but enter the debugger the next time a Lisp
+ function is called. This allows you to step through the
+ subexpressions of an expression, and see what the subexpressions
+ do and what values they compute.
+
+ When you enter the debugger this way, Emacs flags the stack frame
+ for the function call from which you entered. The same function
+ is then called when you exit the frame. To cancel this flag, use
+ `u'.
+
+`b'
+ Set up to enter the debugger when the current frame is exited.
+ Frames that invoke the debugger on exit are flagged with stars.
+
+`u'
+ Don't enter the debugger when the current frame is exited. This
+ cancels a `b' command on a frame.
+
+`e'
+ Read a Lisp expression in the minibuffer, evaluate it, and print
+ the value in the echo area. This is equivalent to the command
+ `M-<ESC>', except that `e' is not normally disabled like `M-<ESC>'.
+
+`q'
+ Terminate the program being debugged; return to top-level Emacs
+ command execution.
+
+ If the debugger was entered due to a `C-g' but you really want to
+ quit, not to debug, use the `q' command.
+
+`r'
+ Return a value from the debugger. The value is computed by
+ reading an expression with the minibuffer and evaluating it.
+
+ The value returned by the debugger makes a difference when the
+ debugger was invoked due to exit from a Lisp call frame (as
+ requested with `b'); then the value specified in the `r' command
+ is used as the value of that frame.
+
+ The debugger's return value also matters with many errors. For
+ example, `wrong-type-argument' errors will use the debugger's
+ return value instead of the invalid argument; `no-catch' errors
+ will use the debugger value as a throw tag instead of the tag that
+ was not found. If an error was signaled by calling the Lisp
+ function `signal', the debugger's return value is returned as the
+ value of `signal'.
+
+\1f
+File: xemacs.info, Node: Lisp Interaction, Next: External Lisp, Prev: Lisp Debug, Up: Running
+
+Lisp Interaction Buffers
+========================
+
+ The buffer `*scratch*', which is selected when Emacs starts up, is
+provided for evaluating Lisp expressions interactively inside Emacs.
+Both the expressions you evaluate and their output goes in the buffer.
+
+ The `*scratch*' buffer's major mode is Lisp Interaction mode, which
+is the same as Emacs-Lisp mode except for one command, <LFD>. In
+Emacs-Lisp mode, <LFD> is an indentation command. In Lisp Interaction
+mode, <LFD> is bound to `eval-print-last-sexp'. This function reads
+the Lisp expression before point, evaluates it, and inserts the value
+in printed representation before point.
+
+ The way to use the `*scratch*' buffer is to insert Lisp expressions
+at the end, ending each one with <LFD> so that it will be evaluated.
+The result is a complete typescript of the expressions you have
+evaluated and their values.
+
+ The rationale for this feature is that Emacs must have a buffer when
+it starts up, but that buffer is not useful for editing files since a
+new buffer is made for every file that you visit. The Lisp interpreter
+typescript is the most useful thing I can think of for the initial
+buffer to do. `M-x lisp-interaction-mode' will put any buffer in Lisp
+Interaction mode.
+
+\1f
+File: xemacs.info, Node: External Lisp, Prev: Lisp Interaction, Up: Running
+
+Running an External Lisp
+========================
+
+ Emacs has facilities for running programs in other Lisp systems.
+You can run a Lisp process as an inferior of Emacs, and pass
+expressions to it to be evaluated. You can also pass changed function
+definitions directly from the Emacs buffers in which you edit the Lisp
+programs to the inferior Lisp process.
+
+ To run an inferior Lisp process, type `M-x run-lisp'. This runs the
+program named `lisp', the same program you would run by typing `lisp'
+as a shell command, with both input and output going through an Emacs
+buffer named `*lisp*'. In other words, any "terminal output" from Lisp
+will go into the buffer, advancing point, and any "terminal input" for
+Lisp comes from text in the buffer. To give input to Lisp, go to the
+end of the buffer and type the input, terminated by <RET>. The
+`*lisp*' buffer is in Inferior Lisp mode, which has all the special
+characteristics of Lisp mode and Shell mode (*note Shell Mode::).
+
+ Use Lisp mode to run the source files of programs in external Lisps.
+You can select this mode with `M-x lisp-mode'. It is used automatically
+for files whose names end in `.l' or `.lisp', as most Lisp systems
+usually expect.
+
+ When you edit a function in a Lisp program you are running, the
+easiest way to send the changed definition to the inferior Lisp process
+is the key `C-M-x'. In Lisp mode, this key runs the function
+`lisp-send-defun', which finds the defun around or following point and
+sends it as input to the Lisp process. (Emacs can send input to any
+inferior process regardless of what buffer is current.)
+
+ Contrast the meanings of `C-M-x' in Lisp mode (for editing programs
+to be run in another Lisp system) and Emacs-Lisp mode (for editing Lisp
+programs to be run in Emacs): in both modes it has the effect of
+installing the function definition that point is in, but the way of
+doing so is different according to where the relevant Lisp environment
+is found. *Note Lisp Modes::.
+
+\1f
+File: xemacs.info, Node: Packages, Next: Basic, Prev: Startup Paths, Up: Top
+
+Packages
+========
+
+ The XEmacs 21 distribution comes only with a very basic set of
+built-in modes and packages. Most of the packages that were part of
+the distribution of earlier versions of XEmacs are now available
+separately. The installer as well as the user can choose which
+packages to install; the actual installation process is easy. This
+gives an installer the ability to tailor an XEmacs installation for
+local needs with safe removal of unnecessary code.
+
+* Menu:
+
+* Package Terminology:: Understanding different kinds of packages.
+* Using Packages:: How to install and use packages.
+* Building Packages:: Building packages from sources.
+* Creating Packages:: The basics.
+* Available Packages:: A brief, out-of-date, directory of packaged LISP.
+
+\1f
+File: xemacs.info, Node: Package Terminology, Next: Using Packages, Up: Packages
+
+Package Flavors
+---------------
+
+ There are two main flavors of packages.
+
+ * Regular Packages A regular package is one in which multiple files
+ are involved and one may not in general safely remove any of them.
+
+ * Single-File Packages A single-file package is an aggregate
+ collection of thematically related but otherwise independent lisp
+ files. These files are bundled together for download convenience
+ and individual files may be deleted at will without any loss of
+ functionality.
+
+Package Distributions
+---------------------
+
+ XEmacs Lisp packages are distributed in two ways, depending on the
+intended use. Binary Packages are for installers and end-users and may
+be installed directly into an XEmacs package directory. Source Packages
+are for developers and include all files necessary for rebuilding
+bytecompiled lisp and creating tarballs for distribution.
+
+Binary Packages
+---------------
+
+ Binary packages may be installed directly into an XEmacs package
+hierarchy.
+
+Source Packages
+---------------
+
+ Source packages contain all of the Package author's (where
+appropriate in regular packages) source code plus all of the files
+necessary to build distribution tarballs (Unix Tar format files,
+gzipped for space savings).
+
+\1f
File: xemacs.info, Node: Using Packages, Next: Building Packages, Prev: Package Terminology, Up: Packages
Getting Started
\1f
-File: xemacs.info, Node: Building Packages, Next: Available Packages, Prev: Using Packages, Up: Packages
+File: xemacs.info, Node: Building Packages, Next: Creating Packages, Prev: Using Packages, Up: Packages
Source packages are available from the `packages/source-packages'
subdirectory of your favorite XEmacs distribution site. Alternatively,
TeXinfo documentation if present.
`srckit'
- Usually aliased to `make srckit-std'. This does a `make
- distclean' and creates a package source tarball in the staging
- directory. This is generally only of use for package maintainers.
+ Usually aliased to `srckit-std'. This does a `make distclean' and
+ creates a package source tarball in the staging directory. This
+ is generally only of use for package maintainers.
`binkit'
May be aliased to `binkit-sourceonly', `binkit-sourceinfo',
of use by XEmacs maintainers producing files for distribution.
\1f
-File: xemacs.info, Node: Available Packages, Prev: Building Packages, Up: Packages
+File: xemacs.info, Node: Creating Packages, Next: Available Packages, Prev: Building Packages, Up: Packages
+
+ Creating a package from an existing Lisp library is not very
+difficult.
+
+ In addition to the Lisp libraries themselves, you need a
+`package-info.in' file and a simple `Makefile'. The rest is done by
+`XEmacs.rules', part of the packaging system infrastructure.
+
+ `package-info.in' contains a single Lisp form like this:
+
+ (name ; your package's name
+ (standards-version 1.1
+ version VERSION
+ author-version AUTHOR_VERSION
+ date DATE
+ build-date BUILD_DATE
+ maintainer MAINTAINER
+ distribution xemacs ; change to "mule" if MULE is needed
+ priority high
+ category CATEGORY
+ dump nil
+ description "description" ; a one-line description string
+ filename FILENAME
+ md5sum MD5SUM
+ size SIZE
+ provides (feature1 feature2) ; one for every `provides' form
+ requires (REQUIRES)
+ type regular
+ ))
+
+ You must fill in the four commented lines. The value of `name' is
+the name of your package as an unquoted symbol. Normally it is the name
+of the main Lisp file or principal feature provided. The allowed values
+for distribution are `xemacs' and `mule'. Write them as unquoted
+symbols. The `description' is a quoted Lisp string; use the usual
+conventions. The value for `provides' is a list of feature symbols
+(written unquoted). All of the features provided by libraries in your
+package should be elements of this list. Implementing an automatic
+method for generating the `provides' line is desirable, but as yet
+undone.
+
+ The variables in upper-case are references to variables set in the
+`Makefile' or automatically generated. Do not change them; they are
+automatically filled in by the build process.
+
+ The remaining lines refer to implementation constants
+(`standards-version'), or features that are unimplemented or have been
+removed (`priority' and `dump'). The `type' line is not normally
+relevant to external maintainers; the alternate value is `single-file',
+which refers to packages consed up out of a number of single-file
+libraries that are more or less thematically related. An example is
+`prog-modes'. Single-file packages are basically for administrative
+convenience, and new packages should generally be created as regular
+packages.
+
+ The `Makefile' is quite stylized. The idea is similar to an
+`Imakefile' or an `automake' file: the complexity is hidden in generic
+rules files, in this case the `XEmacs.rules' include file in the top
+directory of the packages hierarchy. Although a number of facilities
+are available for complex libraries, most simple packages' `Makefile's
+contain a copyright notice, a few variable definitions, an include for
+`XEmacs.rules', and a couple of standard targets.
+
+ The first few `make' variables defined are `VERSION',
+`AUTHOR_VERSION', `MAINTAINER', `PACKAGE', `PKG_TYPE', `REQUIRES', and
+`CATEGORY'. All but one were described in the description of
+`package-info.in'. The last is an admistrative grouping. Current
+categories include `comm', `games', `libs', `mule', `oa', `os', `prog',
+and `wp'. *Note Available Packages::, for a list of categories.
+
+ Next, define the variable `ELCS'. This contains the list of the
+byte-compiled Lisp files used by the package. These files and their
+`.el' versions will be included in the binary package. If there are
+other files (such as extra Lisp sources or an upstream `Makefile') that
+are normally placed in the installed Lisp directory, but not
+byte-compiled, they can be listed as the value of `EXTRA_SOURCES'.
+
+ The include is simply
+ include ../../XEmacs.rules
+
+ The standard targets follow. These are
+
+ all:: $(ELCS) auto-autoloads.elc
+
+ srckit: srckit-alias
+
+ binkit: binkit-alias
+
+ Other targets (such as Texinfo sources) may need to be added as
+dependencies for the `all' target. Dependencies for `srckit' and
+`binkit' (that is, values for SRCKIT-ALIAS and BINKIT-ALIAS) are
+defined in `XEmacs.rules'. The most useful of these values are given
+in the following table.
+
+SRCKIT-ALIAS
+ Usually set to `srckit-std'.
+
+BINKIT-ALIAS
+ May be set to `binkit-sourceonly', `binkit-sourceinfo',
+ `binkit-sourcedata', or `binkit-sourcedatainfo'. `sourceonly'
+ indicates there is nothing to install in a data directory or info
+ directory. `sourceinfo' indicates that source and info files are
+ to be installed. `sourcedata' indicates that source and etc
+ (data) files are to be installed. `sourcedatainfo' indicates
+ source, etc (data), and info files are to be installed.
+
+ Data files include things like pixmaps for a package-specific
+toolbar, and are normally installed in `etc/PACKAGE_NAME'. A few
+packages have needs beyond the basic templates. See `XEmacs.rules' or
+a future revision of this manual for details.
+
+\1f
+File: xemacs.info, Node: Available Packages, Prev: Creating Packages, Up: Packages
This section is surely out-of-date. If you're sure that XEmacs is
able to do something, but your installed XEmacs won't do it for you,
CVS frontend.
`prog-modes'
- Miscellaneous single-file lisp files for various programming
- languages.
+ Miscellaneous Lisp libraries for various programming languages.
`scheme'
Front-end support for Inferior Scheme.
Support for editing shell scripts.
`vc'
- Version Control for Free systems.
+ Version control for free systems.
`vc-cc'
- Version Control for ClearCase. This package must be installed
- prior to building XEmacs [broken as of XEmacs 20.5-beta19].
+ Version control for ClearCase.
`vhdl'
Support for VHDL.
`M-x kill-all-abbrevs' removes all existing abbrev definitions.
-\1f
-File: xemacs.info, Node: Expanding Abbrevs, Next: Editing Abbrevs, Prev: Defining Abbrevs, Up: Abbrevs
-
-Controlling Abbrev Expansion
-============================
-
- An abbrev expands whenever it is in a buffer just before point and
-you type a self-inserting punctuation character (<SPC>, comma, etc.).
-Most often an abbrev is used by inserting the abbrev followed by
-punctuation.
-
- Abbrev expansion preserves case; thus, `foo' expands into `find
-outer otter', `Foo' into `Find outer otter', and `FOO' into `FIND OUTER
-OTTER' or `Find Outer Otter' according to the variable
-`abbrev-all-caps' (a non-`nil' value chooses the first of the two
-expansions).
-
- Two commands are available to control abbrev expansion:
-
-`M-''
- Separate a prefix from a following abbrev to be expanded
- (`abbrev-prefix-mark').
-
-`C-x a e'
- Expand the abbrev before point (`expand-abbrev'). This is
- effective even when Abbrev mode is not enabled.
-
-`M-x unexpand-abbrev'
- Undo last abbrev expansion.
-
-`M-x expand-region-abbrevs'
- Expand some or all abbrevs found in the region.
-
- You may wish to expand an abbrev with a prefix attached. For
-example, if `cnst' expands into `construction', you may want to use it
-to enter `reconstruction'. It does not work to type `recnst', because
-that is not necessarily a defined abbrev. Instead, you can use the
-command `M-'' (`abbrev-prefix-mark') between the prefix `re' and the
-abbrev `cnst'. First, insert `re'. Then type `M-''; this inserts a
-minus sign in the buffer to indicate that it has done its work. Then
-insert the abbrev `cnst'. The buffer now contains `re-cnst'. Now
-insert a punctuation character to expand the abbrev `cnst' into
-`construction'. The minus sign is deleted at this point by `M-''. The
-resulting text is the desired `reconstruction'.
-
- If you actually want the text of the abbrev in the buffer, rather
-than its expansion, insert the following punctuation with `C-q'. Thus,
-`foo C-q -' leaves `foo-' in the buffer.
-
- If you expand an abbrev by mistake, you can undo the expansion
-(replace the expansion by the original abbrev text) with `M-x
-unexpand-abbrev'. You can also use `C-_' (`undo') to undo the
-expansion; but that will first undo the insertion of the punctuation
-character.
-
- `M-x expand-region-abbrevs' searches through the region for defined
-abbrevs, and offers to replace each one it finds with its expansion.
-This command is useful if you have typed text using abbrevs but forgot
-to turn on Abbrev mode first. It may also be useful together with a
-special set of abbrev definitions for making several global
-replacements at once. The command is effective even if Abbrev mode is
-not enabled.
-
-\1f
-File: xemacs.info, Node: Editing Abbrevs, Next: Saving Abbrevs, Prev: Expanding Abbrevs, Up: Abbrevs
-
-Examining and Editing Abbrevs
-=============================
-
-`M-x list-abbrevs'
- Print a list of all abbrev definitions.
-
-`M-x edit-abbrevs'
- Edit a list of abbrevs; you can add, alter, or remove definitions.
-
- The output from `M-x list-abbrevs' looks like this:
-
- (lisp-mode-abbrev-table)
- "dk" 0 "define-key"
- (global-abbrev-table)
- "dfn" 0 "definition"
-
-(Some blank lines of no semantic significance, and some other abbrev
-tables, have been omitted.)
-
- A line containing a name in parentheses is the header for abbrevs in
-a particular abbrev table; `global-abbrev-table' contains all the global
-abbrevs, and the other abbrev tables that are named after major modes
-contain the mode-specific abbrevs.
-
- Within each abbrev table, each non-blank line defines one abbrev.
-The word at the beginning is the abbrev. The number that appears is
-the number of times the abbrev has been expanded. Emacs keeps track of
-this to help you see which abbrevs you actually use, in case you want
-to eliminate those that you don't use often. The string at the end of
-the line is the expansion.
-
- `M-x edit-abbrevs' allows you to add, change or kill abbrev
-definitions by editing a list of them in an Emacs buffer. The list has
-the format described above. The buffer of abbrevs is called
-`*Abbrevs*', and is in Edit-Abbrevs mode. This mode redefines the key
-`C-c C-c' to install the abbrev definitions as specified in the buffer.
-The `edit-abbrevs-redefine' command does this. Any abbrevs not
-described in the buffer are eliminated when this is done.
-
- `edit-abbrevs' is actually the same as `list-abbrevs', except that
-it selects the buffer `*Abbrevs*' whereas `list-abbrevs' merely
-displays it in another window.
-
-\1f
-File: xemacs.info, Node: Saving Abbrevs, Next: Dynamic Abbrevs, Prev: Editing Abbrevs, Up: Abbrevs
-
-Saving Abbrevs
-==============
-
- These commands allow you to keep abbrev definitions between editing
-sessions.
-
-`M-x write-abbrev-file'
- Write a file describing all defined abbrevs.
-
-`M-x read-abbrev-file'
- Read such an abbrev file and define abbrevs as specified there.
-
-`M-x quietly-read-abbrev-file'
- Similar, but do not display a message about what is going on.
-
-`M-x define-abbrevs'
- Define abbrevs from buffer.
-
-`M-x insert-abbrevs'
- Insert all abbrevs and their expansions into the buffer.
-
- Use `M-x write-abbrev-file' to save abbrev definitions for use in a
-later session. The command reads a file name using the minibuffer and
-writes a description of all current abbrev definitions into the
-specified file. The text stored in the file looks like the output of
-`M-x list-abbrevs'.
-
- `M-x read-abbrev-file' prompts for a file name using the minibuffer
-and reads the specified file, defining abbrevs according to its
-contents. `M-x quietly-read-abbrev-file' is the same but does not
-display a message in the echo area; it is actually useful primarily in
-the init file. *Note Init File::. If you give an empty argument to
-either of these functions, the file name Emacs uses is the value of the
-variable `abbrev-file-name', which is by default `"~/.abbrev_defs"'.
-
- Emacs offers to save abbrevs automatically if you have changed any of
-them, whenever it offers to save all files (for `C-x s' or `C-x C-c').
-Set the variable `save-abbrevs' to `nil' to inhibit this feature.
-
- The commands `M-x insert-abbrevs' and `M-x define-abbrevs' are
-similar to the previous commands but work on text in an Emacs buffer.
-`M-x insert-abbrevs' inserts text into the current buffer before point,
-describing all current abbrev definitions; `M-x define-abbrevs' parses
-the entire current buffer and defines abbrevs accordingly.
-
-\1f
-File: xemacs.info, Node: Dynamic Abbrevs, Prev: Saving Abbrevs, Up: Abbrevs
-
-Dynamic Abbrev Expansion
-========================
-
- The abbrev facility described above operates automatically as you
-insert text, but all abbrevs must be defined explicitly. By contrast,
-"dynamic abbrevs" allow the meanings of abbrevs to be determined
-automatically from the contents of the buffer, but dynamic abbrev
-expansion happens only when you request it explicitly.
-
-`M-/'
- Expand the word in the buffer before point as a "dynamic abbrev",
- by searching in the buffer for words starting with that
- abbreviation (`dabbrev-expand').
-
- For example, if the buffer contains `does this follow ' and you type
-`f o M-/', the effect is to insert `follow' because that is the last
-word in the buffer that starts with `fo'. A numeric argument to `M-/'
-says to take the second, third, etc. distinct expansion found looking
-backward from point. Repeating `M-/' searches for an alternative
-expansion by looking farther back. After the entire buffer before
-point has been considered, the buffer after point is searched.
-
- Dynamic abbrev expansion is completely independent of Abbrev mode;
-the expansion of a word with `M-/' is completely independent of whether
-it has a definition as an ordinary abbrev.
-
-\1f
-File: xemacs.info, Node: Picture, Next: Sending Mail, Prev: Abbrevs, Up: Top
-
-Editing Pictures
-****************
-
- If you want to create a picture made out of text characters (for
-example, a picture of the division of a register into fields, as a
-comment in a program), use the command `edit-picture' to enter Picture
-mode.
-
- In Picture mode, editing is based on the "quarter-plane" model of
-text. In this model, the text characters lie studded on an area that
-stretches infinitely far to the right and downward. The concept of the
-end of a line does not exist in this model; the most you can say is
-where the last non-blank character on the line is found.
-
- Of course, Emacs really always considers text as a sequence of
-characters, and lines really do have ends. But in Picture mode most
-frequently-used keys are rebound to commands that simulate the
-quarter-plane model of text. They do this by inserting spaces or by
-converting tabs to spaces.
-
- Most of the basic editing commands of Emacs are redefined by Picture
-mode to do essentially the same thing but in a quarter-plane way. In
-addition, Picture mode defines various keys starting with the `C-c'
-prefix to run special picture editing commands.
-
- One of these keys, `C-c C-c', is pretty important. Often a picture
-is part of a larger file that is usually edited in some other major
-mode. `M-x edit-picture' records the name of the previous major mode.
-You can then use the `C-c C-c' command (`picture-mode-exit') to restore
-that mode. `C-c C-c' also deletes spaces from the ends of lines,
-unless you give it a numeric argument.
-
- The commands used in Picture mode all work in other modes (provided
-the `picture' library is loaded), but are only bound to keys in
-Picture mode. Note that the descriptions below talk of moving "one
-column" and so on, but all the picture mode commands handle numeric
-arguments as their normal equivalents do.
-
- Turning on Picture mode calls the value of the variable
-`picture-mode-hook' as a function, with no arguments, if that value
-exists and is non-`nil'.
-
-* Menu:
-
-* Basic Picture:: Basic concepts and simple commands of Picture Mode.
-* Insert in Picture:: Controlling direction of cursor motion
- after "self-inserting" characters.
-* Tabs in Picture:: Various features for tab stops and indentation.
-* Rectangles in Picture:: Clearing and superimposing rectangles.
-
-\1f
-File: xemacs.info, Node: Basic Picture, Next: Insert in Picture, Prev: Picture, Up: Picture
-
-Basic Editing in Picture Mode
-=============================
-
- Most keys do the same thing in Picture mode that they usually do,
-but do it in a quarter-plane style. For example, `C-f' is rebound to
-run `picture-forward-column', which moves point one column to the
-right, by inserting a space if necessary, so that the actual end of the
-line makes no difference. `C-b' is rebound to run
-`picture-backward-column', which always moves point left one column,
-converting a tab to multiple spaces if necessary. `C-n' and `C-p' are
-rebound to run `picture-move-down' and `picture-move-up', which can
-either insert spaces or convert tabs as necessary to make sure that
-point stays in exactly the same column. `C-e' runs
-`picture-end-of-line', which moves to after the last non-blank
-character on the line. There was no need to change `C-a', as the choice
-of screen model does not affect beginnings of lines.
-
- Insertion of text is adapted to the quarter-plane screen model
-through the use of Overwrite mode (*note Minor Modes::).
-Self-inserting characters replace existing text, column by column,
-rather than pushing existing text to the right. <RET> runs
-`picture-newline', which just moves to the beginning of the following
-line so that new text will replace that line.
-
- Text is erased instead of deleted and killed. <DEL>
-(`picture-backward-clear-column') replaces the preceding character with
-a space rather than removing it. `C-d' (`picture-clear-column') does
-the same in a forward direction. `C-k' (`picture-clear-line') really
-kills the contents of lines, but never removes the newlines from a
-buffer.
-
- To do actual insertion, you must use special commands. `C-o'
-(`picture-open-line') creates a blank line, but does so after the
-current line; it never splits a line. `C-M-o', `split-line', makes
-sense in Picture mode, so it remains unchanged. <LFD>
-(`picture-duplicate-line') inserts another line with the same contents
-below the current line.
-
- To actually delete parts of the picture, use `C-w', or with `C-c
-C-d' (which is defined as `delete-char', as `C-d' is in other modes),
-or with one of the picture rectangle commands (*note Rectangles in
-Picture::).
-
-\1f
-File: xemacs.info, Node: Insert in Picture, Next: Tabs in Picture, Prev: Basic Picture, Up: Picture
-
-Controlling Motion After Insert
-===============================
-
- Since "self-inserting" characters just overwrite and move point in
-Picture mode, there is no essential restriction on how point should be
-moved. Normally point moves right, but you can specify any of the eight
-orthogonal or diagonal directions for motion after a "self-inserting"
-character. This is useful for drawing lines in the buffer.
-
-`C-c <'
- Move left after insertion (`picture-movement-left').
-
-`C-c >'
- Move right after insertion (`picture-movement-right').
-
-`C-c ^'
- Move up after insertion (`picture-movement-up').
-
-`C-c .'
- Move down after insertion (`picture-movement-down').
-
-`C-c `'
- Move up and left ("northwest") after insertion
- (`picture-movement-nw').
-
-`C-c ''
- Move up and right ("northeast") after insertion
- (`picture-movement-ne').
-
-`C-c /'
- Move down and left ("southwest") after insertion
- (`picture-movement-sw').
-
-`C-c \'
- Move down and right ("southeast") after insertion
- (`picture-movement-se').
-
- Two motion commands move based on the current Picture insertion
-direction. The command `C-c C-f' (`picture-motion') moves in the same
-direction as motion after "insertion" currently does, while `C-c C-b'
-(`picture-motion-reverse') moves in the opposite direction.
-
-\1f
-File: xemacs.info, Node: Tabs in Picture, Next: Rectangles in Picture, Prev: Insert in Picture, Up: Picture
-
-Picture Mode Tabs
-=================
-
- Two kinds of tab-like action are provided in Picture mode.
-Context-based tabbing is done with `M-<TAB>' (`picture-tab-search').
-With no argument, it moves to a point underneath the next "interesting"
-character that follows whitespace in the previous non-blank line.
-"Next" here means "appearing at a horizontal position greater than the
-one point starts out at". With an argument, as in `C-u M-<TAB>', the
-command moves to the next such interesting character in the current
-line. `M-<TAB>' does not change the text; it only moves point.
-"Interesting" characters are defined by the variable
-`picture-tab-chars', which contains a string of characters considered
-interesting. Its default value is `"!-~"'.
-
- <TAB> itself runs `picture-tab', which operates based on the current
-tab stop settings; it is the Picture mode equivalent of
-`tab-to-tab-stop'. Without arguments it just moves point, but with a
-numeric argument it clears the text that it moves over.
-
- The context-based and tab-stop-based forms of tabbing are brought
-together by the command `C-c <TAB>' (`picture-set-tab-stops'.) This
-command sets the tab stops to the positions which `M-<TAB>' would
-consider significant in the current line. If you use this command with
-<TAB>, you can get the effect of context-based tabbing. But `M-<TAB>'
-is more convenient in the cases where it is sufficient.
-
-\1f
-File: xemacs.info, Node: Rectangles in Picture, Prev: Tabs in Picture, Up: Picture
-
-Picture Mode Rectangle Commands
-===============================
-
- Picture mode defines commands for working on rectangular pieces of
-the text in ways that fit with the quarter-plane model. The standard
-rectangle commands may also be useful (*note Rectangles::).
-
-`C-c C-k'
- Clear out the region-rectangle (`picture-clear-rectangle'). With
- argument, kill it.
-
-`C-c C-w R'
- Similar but save rectangle contents in register R first
- (`picture-clear-rectangle-to-register').
-
-`C-c C-y'
- Copy last killed rectangle into the buffer by overwriting, with
- upper left corner at point (`picture-yank-rectangle'). With
- argument, insert instead.
-
-`C-c C-x R'
- Similar, but use the rectangle in register R
- (`picture-yank-rectangle-from-register').
-
- The picture rectangle commands `C-c C-k' (`picture-clear-rectangle')
-and `C-c C-w' (`picture-clear-rectangle-to-register') differ from the
-standard rectangle commands in that they normally clear the rectangle
-instead of deleting it; this is analogous with the way `C-d' is changed
-in Picture mode.
-
- However, deletion of rectangles can be useful in Picture mode, so
-these commands delete the rectangle if given a numeric argument.
-
- The Picture mode commands for yanking rectangles differ from the
-standard ones in overwriting instead of inserting. This is the same
-way that Picture mode insertion of other text is different from other
-modes. `C-c C-y' (`picture-yank-rectangle') inserts (by overwriting)
-the rectangle that was most recently killed, while `C-c C-x'
-(`picture-yank-rectangle-from-register') does for the rectangle found
-in a specified register.
-
- Since most region commands in Picture mode operate on rectangles,
-when you select a region of text with the mouse in Picture mode, it is
-highlighted as a rectangle.
-
-\1f
-File: xemacs.info, Node: Sending Mail, Next: Reading Mail, Prev: Picture, Up: Top
-
-Sending Mail
-************
-
- To send a message in Emacs, start by typing the command (`C-x m') to
-select and initialize the `*mail*' buffer. You can then edit the text
-and headers of the message in the mail buffer, and type the command
-(`C-c C-c') to send the message.
-
-`C-x m'
- Begin composing a message to send (`mail').
-
-`C-x 4 m'
- Likewise, but display the message in another window
- (`mail-other-window').
-
-`C-c C-c'
- In Mail mode, send the message and switch to another buffer
- (`mail-send-and-exit').
-
- The command `C-x m' (`mail') selects a buffer named `*mail*' and
-initializes it with the skeleton of an outgoing message. `C-x 4 m'
-(`mail-other-window') selects the `*mail*' buffer in a different
-window, leaving the previous current buffer visible.
-
- Because the buffer for mail composition is an ordinary Emacs buffer,
-you can switch to other buffers while in the middle of composing mail,
-and switch back later (or never). If you use the `C-x m' command again
-when you have been composing another message but have not sent it, a
-new mail buffer will be created; in this way, you can compose multiple
-messages at once. You can switch back to and complete an unsent
-message by using the normal buffer selection mechanisms.
-
- `C-u C-x m' is another way to switch back to a message in progress:
-it will search for an existing, unsent mail message buffer and select
-it.
-
-* Menu:
-
-* Format: Mail Format. Format of the mail being composed.
-* Headers: Mail Headers. Details of allowed mail header fields.
-* Mode: Mail Mode. Special commands for editing mail being composed.
-
-\1f
-File: xemacs.info, Node: Mail Format, Next: Mail Headers, Prev: Sending Mail, Up: Sending Mail
-
-The Format of the Mail Buffer
-=============================
-
- In addition to the "text" or contents, a message has "header
-fields", which say who sent it, when, to whom, why, and so on. Some
-header fields, such as the date and sender, are created automatically
-after the message is sent. Others, such as the recipient names, must
-be specified by you in order to send the message properly.
-
- Mail mode provides a few commands to help you edit some header
-fields, and some are preinitialized in the buffer automatically at
-times. You can insert or edit any header fields using ordinary editing
-commands.
-
- The line in the buffer that says:
-
- --text follows this line--
-
-is a special delimiter that separates the headers you have specified
-from the text. Whatever follows this line is the text of the message;
-the headers precede it. The delimiter line itself does not appear in
-the message actually sent. The text used for the delimiter line is
-controlled by the variable `mail-header-separator'.
-
- Here is an example of what the headers and text in the `*mail*'
-buffer might look like.
-
- To: rms@mc
- CC: mly@mc, rg@oz
- Subject: The XEmacs User's Manual
- --Text follows this line--
- Please ignore this message.
-
-\1f
-File: xemacs.info, Node: Mail Headers, Next: Mail Mode, Prev: Mail Format, Up: Sending Mail
-
-Mail Header Fields
-==================
-
- There are several header fields you can use in the `*mail*' buffer.
-Each header field starts with a field name at the beginning of a line,
-terminated by a colon. It does not matter whether you use upper or
-lower case in the field name. After the colon and optional whitespace
-comes the contents of the field.
-
-`To'
- This field contains the mailing addresses of the message.
-
-`Subject'
- The contents of the `Subject' field should be a piece of text that
- says what the message is about. Subject fields are useful because
- most mail-reading programs can provide a summary of messages,
- listing the subject of each message but not its text.
-
-`CC'
- This field contains additional mailing addresses to send the
- message to, but whose readers should not regard the message as
- addressed to them.
-
-`BCC'
- This field contains additional mailing addresses to send the
- message to, but which should not appear in the header of the
- message actually sent.
-
-`FCC'
- This field contains the name of one file (in Unix mail file
- format) to which a copy of the message should be appended when the
- message is sent.
-
-`From'
- Use the `From' field to say who you are, when the account you are
- using to send the mail is not your own. The contents of the
- `From' field should be a valid mailing address, since replies will
- normally go there.
-
-`Reply-To'
- Use the `Reply-To' field to direct replies to a different address,
- not your own. `From' and `Reply-To' have the same effect on where
- replies go, but they convey a different meaning to the person who
- reads the message.
-
-`In-Reply-To'
- This field contains a piece of text describing a message you are
- replying to. Some mail systems can use the information to
- correlate related pieces of mail. This field is normally filled
- in by your mail handling package when you are replying to a
- message and you never need to think about it.
-
-The `To', `CC', `BCC' and `FCC' fields can appear any number of times,
-to specify many places to send the message.
-
-The `To', `CC', and `BCC', fields can have continuation lines. All the
-lines starting with whitespace, following the line on which the field
-starts, are considered part of the field. For example,
-
- To: foo@here, this@there,
- me@gnu.cambridge.mass.usa.earth.spiral3281
-
-If you have a `~/.mailrc' file, Emacs scans it for mail aliases the
-first time you try to send mail in an Emacs session. Emacs expands
-aliases found in the `To', `CC', and `BCC' fields where appropriate.
-You can set the variable `mail-abbrev-mailrc-file' to the name of the
-file with mail aliases. If `nil', `~/.mailrc' is used.
-
- Your `.mailrc' file ensures that word-abbrevs are defined for each
-of your mail aliases when point is in a `To', `CC', `BCC', or `From'
-field. The aliases are defined in your `.mailrc' file or in a file
-specified by the MAILRC environment variable if it exists. Your mail
-aliases expand any time you type a word-delimiter at the end of an
-abbreviation.
-
- In this version of Emacs, what you see is what you get: in contrast
-to some other versions, no abbreviations are expanded after you have
-sent the mail. This means you don't suffer the annoyance of having the
-system do things behind your back--if the system rewrites an address
-you typed, you know it immediately, instead of after the mail has been
-sent and it's too late to do anything about it. For example, you will
-never again be in trouble because you forgot to delete an old alias
-from your `.mailrc' and a new local user is given a userid which
-conflicts with one of your aliases.
-
- Your mail alias abbrevs are in effect only when point is in an
-appropriate header field. The mail aliases will not expand in the body
-of the message, or in other header fields. The default mode-specific
-abbrev table `mail-mode-abbrev-table' is used instead if defined. That
-means if you have been using mail-mode specific abbrevs, this code will
-not adversely affect you. You can control which header fields the
-abbrevs are used in by changing the variable `mail-abbrev-mode-regexp'.
-
- If auto-fill mode is on, abbrevs wrap at commas instead of at word
-boundaries, and header continuation lines will be properly indented.
-
- You can also insert a mail alias with
-`mail-interactive-insert-alias'. This function, which is bound to `C-c
-C-a', prompts you for an alias (with completion) and inserts its
-expansion at point.
-
- In this version of Emacs, it is possible to have lines like the
-following in your `.mailrc' file:
-
- alias someone "John Doe <doe@quux.com>"
-
- That is, if you want an address to have embedded spaces, simply
-surround it with double-quotes. The quotes are necessary because the
-format of the `.mailrc' file uses spaces as address delimiters.
-
- Aliases in the `.mailrc' file may be nested. For example, assume you
-define aliases like:
- alias group1 fred ethel
- alias group2 larry curly moe
- alias everybody group1 group2
-
- When you now type `everybody' on the `To' line, it will expand to:
- fred, ethyl, larry, curly, moe
-
- Aliases may contain forward references; the alias of `everybody' in
-the example above can precede the aliases of `group1' and `group2'.
-
- In this version of Emacs, you can use the `source' `.mailrc' command
-for reading aliases from some other file as well.
-
- Aliases may contain hyphens, as in `"alias foo-bar foo@bar"', even
-though word-abbrevs normally cannot contain hyphens.
-
- To read in the contents of another `.mailrc'-type file from Emacs,
-use the command `M-x merge-mail-aliases'. The `rebuild-mail-aliases'
-command is similar, but deletes existing aliases first.
-
- If you want multiple addresses separated by a string other than `,'
-(a comma), then set the variable `mail-alias-separator-string' to it.
-This has to be a comma bracketed by whitespace if you want any kind of
-reasonable behavior.
-
- If the variable `mail-archive-file-name' is non-`nil', it should be
-a string naming a file. Each time you start to edit a message to send,
-an `FCC' field is entered for that file. Unless you remove the `FCC'
-field, every message is written into that file when it is sent.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Expanding Abbrevs, Next: Editing Abbrevs, Prev: Defining Abbrevs, Up: Abbrevs
+
+Controlling Abbrev Expansion
+============================
+
+ An abbrev expands whenever it is in a buffer just before point and
+you type a self-inserting punctuation character (<SPC>, comma, etc.).
+Most often an abbrev is used by inserting the abbrev followed by
+punctuation.
+
+ Abbrev expansion preserves case; thus, `foo' expands into `find
+outer otter', `Foo' into `Find outer otter', and `FOO' into `FIND OUTER
+OTTER' or `Find Outer Otter' according to the variable
+`abbrev-all-caps' (a non-`nil' value chooses the first of the two
+expansions).
+
+ Two commands are available to control abbrev expansion:
+
+`M-''
+ Separate a prefix from a following abbrev to be expanded
+ (`abbrev-prefix-mark').
+
+`C-x a e'
+ Expand the abbrev before point (`expand-abbrev'). This is
+ effective even when Abbrev mode is not enabled.
+
+`M-x unexpand-abbrev'
+ Undo last abbrev expansion.
+
+`M-x expand-region-abbrevs'
+ Expand some or all abbrevs found in the region.
+
+ You may wish to expand an abbrev with a prefix attached. For
+example, if `cnst' expands into `construction', you may want to use it
+to enter `reconstruction'. It does not work to type `recnst', because
+that is not necessarily a defined abbrev. Instead, you can use the
+command `M-'' (`abbrev-prefix-mark') between the prefix `re' and the
+abbrev `cnst'. First, insert `re'. Then type `M-''; this inserts a
+minus sign in the buffer to indicate that it has done its work. Then
+insert the abbrev `cnst'. The buffer now contains `re-cnst'. Now
+insert a punctuation character to expand the abbrev `cnst' into
+`construction'. The minus sign is deleted at this point by `M-''. The
+resulting text is the desired `reconstruction'.
+
+ If you actually want the text of the abbrev in the buffer, rather
+than its expansion, insert the following punctuation with `C-q'. Thus,
+`foo C-q -' leaves `foo-' in the buffer.
+
+ If you expand an abbrev by mistake, you can undo the expansion
+(replace the expansion by the original abbrev text) with `M-x
+unexpand-abbrev'. You can also use `C-_' (`undo') to undo the
+expansion; but that will first undo the insertion of the punctuation
+character.
+
+ `M-x expand-region-abbrevs' searches through the region for defined
+abbrevs, and offers to replace each one it finds with its expansion.
+This command is useful if you have typed text using abbrevs but forgot
+to turn on Abbrev mode first. It may also be useful together with a
+special set of abbrev definitions for making several global
+replacements at once. The command is effective even if Abbrev mode is
+not enabled.
+
+\1f
+File: xemacs.info, Node: Editing Abbrevs, Next: Saving Abbrevs, Prev: Expanding Abbrevs, Up: Abbrevs
+
+Examining and Editing Abbrevs
+=============================
+
+`M-x list-abbrevs'
+ Print a list of all abbrev definitions.
+
+`M-x edit-abbrevs'
+ Edit a list of abbrevs; you can add, alter, or remove definitions.
+
+ The output from `M-x list-abbrevs' looks like this:
+
+ (lisp-mode-abbrev-table)
+ "dk" 0 "define-key"
+ (global-abbrev-table)
+ "dfn" 0 "definition"
+
+(Some blank lines of no semantic significance, and some other abbrev
+tables, have been omitted.)
+
+ A line containing a name in parentheses is the header for abbrevs in
+a particular abbrev table; `global-abbrev-table' contains all the global
+abbrevs, and the other abbrev tables that are named after major modes
+contain the mode-specific abbrevs.
+
+ Within each abbrev table, each non-blank line defines one abbrev.
+The word at the beginning is the abbrev. The number that appears is
+the number of times the abbrev has been expanded. Emacs keeps track of
+this to help you see which abbrevs you actually use, in case you want
+to eliminate those that you don't use often. The string at the end of
+the line is the expansion.
+
+ `M-x edit-abbrevs' allows you to add, change or kill abbrev
+definitions by editing a list of them in an Emacs buffer. The list has
+the format described above. The buffer of abbrevs is called
+`*Abbrevs*', and is in Edit-Abbrevs mode. This mode redefines the key
+`C-c C-c' to install the abbrev definitions as specified in the buffer.
+The `edit-abbrevs-redefine' command does this. Any abbrevs not
+described in the buffer are eliminated when this is done.
+
+ `edit-abbrevs' is actually the same as `list-abbrevs', except that
+it selects the buffer `*Abbrevs*' whereas `list-abbrevs' merely
+displays it in another window.
+
+\1f
+File: xemacs.info, Node: Saving Abbrevs, Next: Dynamic Abbrevs, Prev: Editing Abbrevs, Up: Abbrevs
+
+Saving Abbrevs
+==============
+
+ These commands allow you to keep abbrev definitions between editing
+sessions.
+
+`M-x write-abbrev-file'
+ Write a file describing all defined abbrevs.
+
+`M-x read-abbrev-file'
+ Read such an abbrev file and define abbrevs as specified there.
+
+`M-x quietly-read-abbrev-file'
+ Similar, but do not display a message about what is going on.
+
+`M-x define-abbrevs'
+ Define abbrevs from buffer.
+
+`M-x insert-abbrevs'
+ Insert all abbrevs and their expansions into the buffer.
+
+ Use `M-x write-abbrev-file' to save abbrev definitions for use in a
+later session. The command reads a file name using the minibuffer and
+writes a description of all current abbrev definitions into the
+specified file. The text stored in the file looks like the output of
+`M-x list-abbrevs'.
+
+ `M-x read-abbrev-file' prompts for a file name using the minibuffer
+and reads the specified file, defining abbrevs according to its
+contents. `M-x quietly-read-abbrev-file' is the same but does not
+display a message in the echo area; it is actually useful primarily in
+the init file. *Note Init File::. If you give an empty argument to
+either of these functions, the file name Emacs uses is the value of the
+variable `abbrev-file-name', which is by default `"~/.abbrev_defs"'.
+
+ Emacs offers to save abbrevs automatically if you have changed any of
+them, whenever it offers to save all files (for `C-x s' or `C-x C-c').
+Set the variable `save-abbrevs' to `nil' to inhibit this feature.
+
+ The commands `M-x insert-abbrevs' and `M-x define-abbrevs' are
+similar to the previous commands but work on text in an Emacs buffer.
+`M-x insert-abbrevs' inserts text into the current buffer before point,
+describing all current abbrev definitions; `M-x define-abbrevs' parses
+the entire current buffer and defines abbrevs accordingly.
+
+\1f
+File: xemacs.info, Node: Dynamic Abbrevs, Prev: Saving Abbrevs, Up: Abbrevs
+
+Dynamic Abbrev Expansion
+========================
+
+ The abbrev facility described above operates automatically as you
+insert text, but all abbrevs must be defined explicitly. By contrast,
+"dynamic abbrevs" allow the meanings of abbrevs to be determined
+automatically from the contents of the buffer, but dynamic abbrev
+expansion happens only when you request it explicitly.
+
+`M-/'
+ Expand the word in the buffer before point as a "dynamic abbrev",
+ by searching in the buffer for words starting with that
+ abbreviation (`dabbrev-expand').
+
+ For example, if the buffer contains `does this follow ' and you type
+`f o M-/', the effect is to insert `follow' because that is the last
+word in the buffer that starts with `fo'. A numeric argument to `M-/'
+says to take the second, third, etc. distinct expansion found looking
+backward from point. Repeating `M-/' searches for an alternative
+expansion by looking farther back. After the entire buffer before
+point has been considered, the buffer after point is searched.
+
+ Dynamic abbrev expansion is completely independent of Abbrev mode;
+the expansion of a word with `M-/' is completely independent of whether
+it has a definition as an ordinary abbrev.
+
+\1f
+File: xemacs.info, Node: Picture, Next: Sending Mail, Prev: Abbrevs, Up: Top
+
+Editing Pictures
+****************
+
+ If you want to create a picture made out of text characters (for
+example, a picture of the division of a register into fields, as a
+comment in a program), use the command `edit-picture' to enter Picture
+mode.
+
+ In Picture mode, editing is based on the "quarter-plane" model of
+text. In this model, the text characters lie studded on an area that
+stretches infinitely far to the right and downward. The concept of the
+end of a line does not exist in this model; the most you can say is
+where the last non-blank character on the line is found.
+
+ Of course, Emacs really always considers text as a sequence of
+characters, and lines really do have ends. But in Picture mode most
+frequently-used keys are rebound to commands that simulate the
+quarter-plane model of text. They do this by inserting spaces or by
+converting tabs to spaces.
+
+ Most of the basic editing commands of Emacs are redefined by Picture
+mode to do essentially the same thing but in a quarter-plane way. In
+addition, Picture mode defines various keys starting with the `C-c'
+prefix to run special picture editing commands.
+
+ One of these keys, `C-c C-c', is pretty important. Often a picture
+is part of a larger file that is usually edited in some other major
+mode. `M-x edit-picture' records the name of the previous major mode.
+You can then use the `C-c C-c' command (`picture-mode-exit') to restore
+that mode. `C-c C-c' also deletes spaces from the ends of lines,
+unless you give it a numeric argument.
+
+ The commands used in Picture mode all work in other modes (provided
+the `picture' library is loaded), but are only bound to keys in
+Picture mode. Note that the descriptions below talk of moving "one
+column" and so on, but all the picture mode commands handle numeric
+arguments as their normal equivalents do.
+
+ Turning on Picture mode calls the value of the variable
+`picture-mode-hook' as a function, with no arguments, if that value
+exists and is non-`nil'.
+
+* Menu:
+
+* Basic Picture:: Basic concepts and simple commands of Picture Mode.
+* Insert in Picture:: Controlling direction of cursor motion
+ after "self-inserting" characters.
+* Tabs in Picture:: Various features for tab stops and indentation.
+* Rectangles in Picture:: Clearing and superimposing rectangles.
+
+\1f
+File: xemacs.info, Node: Basic Picture, Next: Insert in Picture, Prev: Picture, Up: Picture
+
+Basic Editing in Picture Mode
+=============================
+
+ Most keys do the same thing in Picture mode that they usually do,
+but do it in a quarter-plane style. For example, `C-f' is rebound to
+run `picture-forward-column', which moves point one column to the
+right, by inserting a space if necessary, so that the actual end of the
+line makes no difference. `C-b' is rebound to run
+`picture-backward-column', which always moves point left one column,
+converting a tab to multiple spaces if necessary. `C-n' and `C-p' are
+rebound to run `picture-move-down' and `picture-move-up', which can
+either insert spaces or convert tabs as necessary to make sure that
+point stays in exactly the same column. `C-e' runs
+`picture-end-of-line', which moves to after the last non-blank
+character on the line. There was no need to change `C-a', as the choice
+of screen model does not affect beginnings of lines.
+
+ Insertion of text is adapted to the quarter-plane screen model
+through the use of Overwrite mode (*note Minor Modes::).
+Self-inserting characters replace existing text, column by column,
+rather than pushing existing text to the right. <RET> runs
+`picture-newline', which just moves to the beginning of the following
+line so that new text will replace that line.
+
+ Text is erased instead of deleted and killed. <DEL>
+(`picture-backward-clear-column') replaces the preceding character with
+a space rather than removing it. `C-d' (`picture-clear-column') does
+the same in a forward direction. `C-k' (`picture-clear-line') really
+kills the contents of lines, but never removes the newlines from a
+buffer.
+
+ To do actual insertion, you must use special commands. `C-o'
+(`picture-open-line') creates a blank line, but does so after the
+current line; it never splits a line. `C-M-o', `split-line', makes
+sense in Picture mode, so it remains unchanged. <LFD>
+(`picture-duplicate-line') inserts another line with the same contents
+below the current line.
+
+ To actually delete parts of the picture, use `C-w', or with `C-c
+C-d' (which is defined as `delete-char', as `C-d' is in other modes),
+or with one of the picture rectangle commands (*note Rectangles in
+Picture::).
+
+\1f
+File: xemacs.info, Node: Insert in Picture, Next: Tabs in Picture, Prev: Basic Picture, Up: Picture
+
+Controlling Motion After Insert
+===============================
+
+ Since "self-inserting" characters just overwrite and move point in
+Picture mode, there is no essential restriction on how point should be
+moved. Normally point moves right, but you can specify any of the eight
+orthogonal or diagonal directions for motion after a "self-inserting"
+character. This is useful for drawing lines in the buffer.
+
+`C-c <'
+ Move left after insertion (`picture-movement-left').
+
+`C-c >'
+ Move right after insertion (`picture-movement-right').
+
+`C-c ^'
+ Move up after insertion (`picture-movement-up').
+
+`C-c .'
+ Move down after insertion (`picture-movement-down').
+
+`C-c `'
+ Move up and left ("northwest") after insertion
+ (`picture-movement-nw').
+
+`C-c ''
+ Move up and right ("northeast") after insertion
+ (`picture-movement-ne').
+
+`C-c /'
+ Move down and left ("southwest") after insertion
+ (`picture-movement-sw').
+
+`C-c \'
+ Move down and right ("southeast") after insertion
+ (`picture-movement-se').
+
+ Two motion commands move based on the current Picture insertion
+direction. The command `C-c C-f' (`picture-motion') moves in the same
+direction as motion after "insertion" currently does, while `C-c C-b'
+(`picture-motion-reverse') moves in the opposite direction.
+
+\1f
+File: xemacs.info, Node: Tabs in Picture, Next: Rectangles in Picture, Prev: Insert in Picture, Up: Picture
+
+Picture Mode Tabs
+=================
+
+ Two kinds of tab-like action are provided in Picture mode.
+Context-based tabbing is done with `M-<TAB>' (`picture-tab-search').
+With no argument, it moves to a point underneath the next "interesting"
+character that follows whitespace in the previous non-blank line.
+"Next" here means "appearing at a horizontal position greater than the
+one point starts out at". With an argument, as in `C-u M-<TAB>', the
+command moves to the next such interesting character in the current
+line. `M-<TAB>' does not change the text; it only moves point.
+"Interesting" characters are defined by the variable
+`picture-tab-chars', which contains a string of characters considered
+interesting. Its default value is `"!-~"'.
+
+ <TAB> itself runs `picture-tab', which operates based on the current
+tab stop settings; it is the Picture mode equivalent of
+`tab-to-tab-stop'. Without arguments it just moves point, but with a
+numeric argument it clears the text that it moves over.
+
+ The context-based and tab-stop-based forms of tabbing are brought
+together by the command `C-c <TAB>' (`picture-set-tab-stops'.) This
+command sets the tab stops to the positions which `M-<TAB>' would
+consider significant in the current line. If you use this command with
+<TAB>, you can get the effect of context-based tabbing. But `M-<TAB>'
+is more convenient in the cases where it is sufficient.
+
+\1f
+File: xemacs.info, Node: Rectangles in Picture, Prev: Tabs in Picture, Up: Picture
+
+Picture Mode Rectangle Commands
+===============================
+
+ Picture mode defines commands for working on rectangular pieces of
+the text in ways that fit with the quarter-plane model. The standard
+rectangle commands may also be useful (*note Rectangles::).
+
+`C-c C-k'
+ Clear out the region-rectangle (`picture-clear-rectangle'). With
+ argument, kill it.
+
+`C-c C-w R'
+ Similar but save rectangle contents in register R first
+ (`picture-clear-rectangle-to-register').
+
+`C-c C-y'
+ Copy last killed rectangle into the buffer by overwriting, with
+ upper left corner at point (`picture-yank-rectangle'). With
+ argument, insert instead.
+
+`C-c C-x R'
+ Similar, but use the rectangle in register R
+ (`picture-yank-rectangle-from-register').
+
+ The picture rectangle commands `C-c C-k' (`picture-clear-rectangle')
+and `C-c C-w' (`picture-clear-rectangle-to-register') differ from the
+standard rectangle commands in that they normally clear the rectangle
+instead of deleting it; this is analogous with the way `C-d' is changed
+in Picture mode.
+
+ However, deletion of rectangles can be useful in Picture mode, so
+these commands delete the rectangle if given a numeric argument.
+
+ The Picture mode commands for yanking rectangles differ from the
+standard ones in overwriting instead of inserting. This is the same
+way that Picture mode insertion of other text is different from other
+modes. `C-c C-y' (`picture-yank-rectangle') inserts (by overwriting)
+the rectangle that was most recently killed, while `C-c C-x'
+(`picture-yank-rectangle-from-register') does for the rectangle found
+in a specified register.
+
+ Since most region commands in Picture mode operate on rectangles,
+when you select a region of text with the mouse in Picture mode, it is
+highlighted as a rectangle.
+
+\1f
+File: xemacs.info, Node: Sending Mail, Next: Reading Mail, Prev: Picture, Up: Top
+
+Sending Mail
+************
+
+ To send a message in Emacs, start by typing the command (`C-x m') to
+select and initialize the `*mail*' buffer. You can then edit the text
+and headers of the message in the mail buffer, and type the command
+(`C-c C-c') to send the message.
+
+`C-x m'
+ Begin composing a message to send (`mail').
+
+`C-x 4 m'
+ Likewise, but display the message in another window
+ (`mail-other-window').
+
+`C-c C-c'
+ In Mail mode, send the message and switch to another buffer
+ (`mail-send-and-exit').
+
+ The command `C-x m' (`mail') selects a buffer named `*mail*' and
+initializes it with the skeleton of an outgoing message. `C-x 4 m'
+(`mail-other-window') selects the `*mail*' buffer in a different
+window, leaving the previous current buffer visible.
+
+ Because the buffer for mail composition is an ordinary Emacs buffer,
+you can switch to other buffers while in the middle of composing mail,
+and switch back later (or never). If you use the `C-x m' command again
+when you have been composing another message but have not sent it, a
+new mail buffer will be created; in this way, you can compose multiple
+messages at once. You can switch back to and complete an unsent
+message by using the normal buffer selection mechanisms.
+
+ `C-u C-x m' is another way to switch back to a message in progress:
+it will search for an existing, unsent mail message buffer and select
+it.
+
+* Menu:
+
+* Format: Mail Format. Format of the mail being composed.
+* Headers: Mail Headers. Details of allowed mail header fields.
+* Mode: Mail Mode. Special commands for editing mail being composed.
+
+\1f
+File: xemacs.info, Node: Mail Format, Next: Mail Headers, Prev: Sending Mail, Up: Sending Mail
+
+The Format of the Mail Buffer
+=============================
+
+ In addition to the "text" or contents, a message has "header
+fields", which say who sent it, when, to whom, why, and so on. Some
+header fields, such as the date and sender, are created automatically
+after the message is sent. Others, such as the recipient names, must
+be specified by you in order to send the message properly.
+
+ Mail mode provides a few commands to help you edit some header
+fields, and some are preinitialized in the buffer automatically at
+times. You can insert or edit any header fields using ordinary editing
+commands.
+
+ The line in the buffer that says:
+
+ --text follows this line--
+
+is a special delimiter that separates the headers you have specified
+from the text. Whatever follows this line is the text of the message;
+the headers precede it. The delimiter line itself does not appear in
+the message actually sent. The text used for the delimiter line is
+controlled by the variable `mail-header-separator'.
+
+ Here is an example of what the headers and text in the `*mail*'
+buffer might look like.
+
+ To: rms@mc
+ CC: mly@mc, rg@oz
+ Subject: The XEmacs User's Manual
+ --Text follows this line--
+ Please ignore this message.
+
+\1f
+File: xemacs.info, Node: Mail Headers, Next: Mail Mode, Prev: Mail Format, Up: Sending Mail
+
+Mail Header Fields
+==================
+
+ There are several header fields you can use in the `*mail*' buffer.
+Each header field starts with a field name at the beginning of a line,
+terminated by a colon. It does not matter whether you use upper or
+lower case in the field name. After the colon and optional whitespace
+comes the contents of the field.
+
+`To'
+ This field contains the mailing addresses of the message.
+
+`Subject'
+ The contents of the `Subject' field should be a piece of text that
+ says what the message is about. Subject fields are useful because
+ most mail-reading programs can provide a summary of messages,
+ listing the subject of each message but not its text.
+
+`CC'
+ This field contains additional mailing addresses to send the
+ message to, but whose readers should not regard the message as
+ addressed to them.
+
+`BCC'
+ This field contains additional mailing addresses to send the
+ message to, but which should not appear in the header of the
+ message actually sent.
+
+`FCC'
+ This field contains the name of one file (in Unix mail file
+ format) to which a copy of the message should be appended when the
+ message is sent.
+
+`From'
+ Use the `From' field to say who you are, when the account you are
+ using to send the mail is not your own. The contents of the
+ `From' field should be a valid mailing address, since replies will
+ normally go there.
+
+`Reply-To'
+ Use the `Reply-To' field to direct replies to a different address,
+ not your own. `From' and `Reply-To' have the same effect on where
+ replies go, but they convey a different meaning to the person who
+ reads the message.
+
+`In-Reply-To'
+ This field contains a piece of text describing a message you are
+ replying to. Some mail systems can use the information to
+ correlate related pieces of mail. This field is normally filled
+ in by your mail handling package when you are replying to a
+ message and you never need to think about it.
+
+The `To', `CC', `BCC' and `FCC' fields can appear any number of times,
+to specify many places to send the message.
+
+The `To', `CC', and `BCC', fields can have continuation lines. All the
+lines starting with whitespace, following the line on which the field
+starts, are considered part of the field. For example,
+
+ To: foo@here, this@there,
+ me@gnu.cambridge.mass.usa.earth.spiral3281
+
+If you have a `~/.mailrc' file, Emacs scans it for mail aliases the
+first time you try to send mail in an Emacs session. Emacs expands
+aliases found in the `To', `CC', and `BCC' fields where appropriate.
+You can set the variable `mail-abbrev-mailrc-file' to the name of the
+file with mail aliases. If `nil', `~/.mailrc' is used.
+
+ Your `.mailrc' file ensures that word-abbrevs are defined for each
+of your mail aliases when point is in a `To', `CC', `BCC', or `From'
+field. The aliases are defined in your `.mailrc' file or in a file
+specified by the MAILRC environment variable if it exists. Your mail
+aliases expand any time you type a word-delimiter at the end of an
+abbreviation.
+
+ In this version of Emacs, what you see is what you get: in contrast
+to some other versions, no abbreviations are expanded after you have
+sent the mail. This means you don't suffer the annoyance of having the
+system do things behind your back--if the system rewrites an address
+you typed, you know it immediately, instead of after the mail has been
+sent and it's too late to do anything about it. For example, you will
+never again be in trouble because you forgot to delete an old alias
+from your `.mailrc' and a new local user is given a userid which
+conflicts with one of your aliases.
+
+ Your mail alias abbrevs are in effect only when point is in an
+appropriate header field. The mail aliases will not expand in the body
+of the message, or in other header fields. The default mode-specific
+abbrev table `mail-mode-abbrev-table' is used instead if defined. That
+means if you have been using mail-mode specific abbrevs, this code will
+not adversely affect you. You can control which header fields the
+abbrevs are used in by changing the variable `mail-abbrev-mode-regexp'.
+
+ If auto-fill mode is on, abbrevs wrap at commas instead of at word
+boundaries, and header continuation lines will be properly indented.
+
+ You can also insert a mail alias with
+`mail-interactive-insert-alias'. This function, which is bound to `C-c
+C-a', prompts you for an alias (with completion) and inserts its
+expansion at point.
+
+ In this version of Emacs, it is possible to have lines like the
+following in your `.mailrc' file:
+
+ alias someone "John Doe <doe@quux.com>"
+
+ That is, if you want an address to have embedded spaces, simply
+surround it with double-quotes. The quotes are necessary because the
+format of the `.mailrc' file uses spaces as address delimiters.
+
+ Aliases in the `.mailrc' file may be nested. For example, assume you
+define aliases like:
+ alias group1 fred ethel
+ alias group2 larry curly moe
+ alias everybody group1 group2
+
+ When you now type `everybody' on the `To' line, it will expand to:
+ fred, ethyl, larry, curly, moe
+
+ Aliases may contain forward references; the alias of `everybody' in
+the example above can precede the aliases of `group1' and `group2'.
+
+ In this version of Emacs, you can use the `source' `.mailrc' command
+for reading aliases from some other file as well.
+
+ Aliases may contain hyphens, as in `"alias foo-bar foo@bar"', even
+though word-abbrevs normally cannot contain hyphens.
+
+ To read in the contents of another `.mailrc'-type file from Emacs,
+use the command `M-x merge-mail-aliases'. The `rebuild-mail-aliases'
+command is similar, but deletes existing aliases first.
+
+ If you want multiple addresses separated by a string other than `,'
+(a comma), then set the variable `mail-alias-separator-string' to it.
+This has to be a comma bracketed by whitespace if you want any kind of
+reasonable behavior.
+
+ If the variable `mail-archive-file-name' is non-`nil', it should be
+a string naming a file. Each time you start to edit a message to send,
+an `FCC' field is entered for that file. Unless you remove the `FCC'
+field, every message is written into that file when it is sent.
+
+\1f
File: xemacs.info, Node: Mail Mode, Prev: Mail Headers, Up: Sending Mail
Mail Mode
particular date; `Buttons3' brings up a menu of commonly used calendar
features that are independent of any particular date. To exit the
calendar, type `q'. *Note Customizing the Calendar and Diary:
-(elisp)Calendar, for customization information about the calendar and
+(lispref)Calendar, for customization information about the calendar and
diary.
* Menu:
are set up for the United States, Emacs always uses the present
definition, even though it is wrong for some prior years.
-\1f
-File: xemacs.info, Node: Sunrise/Sunset, Next: Lunar Phases, Prev: Holidays, Up: Calendar/Diary
-
-Times of Sunrise and Sunset
----------------------------
-
- Special calendar commands can tell you, to within a minute or two,
-the times of sunrise and sunset for any date.
-
-`S'
- Display times of sunrise and sunset for the selected date
- (`calendar-sunrise-sunset').
-
-`Button2 Sunrise/Sunset'
- Display times of sunrise and sunset for the date you click on.
-
-`M-x sunrise-sunset'
- Display times of sunrise and sunset for today's date.
-
-`C-u M-x sunrise-sunset'
- Display times of sunrise and sunset for a specified date.
-
- Within the calendar, to display the _local times_ of sunrise and
-sunset in the echo area, move point to the date you want, and type `S'.
-Alternatively, click `Button2' on the date, then choose
-`Sunrise/Sunset' from the menu that appears. The command `M-x
-sunrise-sunset' is available outside the calendar to display this
-information for today's date or a specified date. To specify a date
-other than today, use `C-u M-x sunrise-sunset', which prompts for the
-year, month, and day.
-
- You can display the times of sunrise and sunset for any location and
-any date with `C-u C-u M-x sunrise-sunset'. This asks you for a
-longitude, latitude, number of minutes difference from Coordinated
-Universal Time, and date, and then tells you the times of sunrise and
-sunset for that location on that date.
-
- Because the times of sunrise and sunset depend on the location on
-earth, you need to tell Emacs your latitude, longitude, and location
-name before using these commands. Here is an example of what to set:
-
- (setq calendar-latitude 40.1)
- (setq calendar-longitude -88.2)
- (setq calendar-location-name "Urbana, IL")
-
-Use one decimal place in the values of `calendar-latitude' and
-`calendar-longitude'.
-
- Your time zone also affects the local time of sunrise and sunset.
-Emacs usually gets time zone information from the operating system, but
-if these values are not what you want (or if the operating system does
-not supply them), you must set them yourself. Here is an example:
-
- (setq calendar-time-zone -360)
- (setq calendar-standard-time-zone-name "CST")
- (setq calendar-daylight-time-zone-name "CDT")
-
-The value of `calendar-time-zone' is the number of minutes difference
-between your local standard time and Coordinated Universal Time
-(Greenwich time). The values of `calendar-standard-time-zone-name' and
-`calendar-daylight-time-zone-name' are the abbreviations used in your
-time zone. Emacs displays the times of sunrise and sunset _corrected
-for daylight savings time_. *Note Daylight Savings::, for how daylight
-savings time is determined.
-
- As a user, you might find it convenient to set the calendar location
-variables for your usual physical location in your init file. And when
-you install Emacs on a machine, you can create a `default.el' file
-which sets them properly for the typical location of most users of that
-machine. *Note Init File::.
-
-\1f
-File: xemacs.info, Node: Lunar Phases, Next: Other Calendars, Prev: Sunrise/Sunset, Up: Calendar/Diary
-
-Phases of the Moon
-------------------
-
- These calendar commands display the dates and times of the phases of
-the moon (new moon, first quarter, full moon, last quarter). This
-feature is useful for debugging problems that "depend on the phase of
-the moon."
-
-`M'
- Display the dates and times for all the quarters of the moon for
- the three-month period shown (`calendar-phases-of-moon').
-
-`M-x phases-of-moon'
- Display dates and times of the quarters of the moon for three
- months around today's date.
-
- Within the calendar, use the `M' command to display a separate
-buffer of the phases of the moon for the current three-month range. The
-dates and times listed are accurate to within a few minutes.
-
- Outside the calendar, use the command `M-x phases-of-moon' to
-display the list of the phases of the moon for the current month and the
-preceding and succeeding months. For information about a different
-month, use `C-u M-x phases-of-moon', which prompts for the month and
-year.
-
- The dates and times given for the phases of the moon are given in
-local time (corrected for daylight savings, when appropriate); but if
-the variable `calendar-time-zone' is void, Coordinated Universal Time
-(the Greenwich time zone) is used. *Note Daylight Savings::.
-
-\1f
-File: xemacs.info, Node: Other Calendars, Next: Calendar Systems, Prev: Lunar Phases, Up: Calendar/Diary
-
-Conversion To and From Other Calendars
---------------------------------------
-
- The Emacs calendar displayed is _always_ the Gregorian calendar,
-sometimes called the "new style" calendar, which is used in most of the
-world today. However, this calendar did not exist before the sixteenth
-century and was not widely used before the eighteenth century; it did
-not fully displace the Julian calendar and gain universal acceptance
-until the early twentieth century. The Emacs calendar can display any
-month since January, year 1 of the current era, but the calendar
-displayed is the Gregorian, even for a date at which the Gregorian
-calendar did not exist.
-
- While Emacs cannot display other calendars, it can convert dates to
-and from several other calendars.
-
-* Menu:
-
-* Calendar Systems:: The calendars Emacs understands
- (aside from Gregorian).
-* To Other Calendar:: Converting the selected date to various calendars.
-* From Other Calendar:: Moving to a date specified in another calendar.
-* Mayan Calendar:: Moving to a date specified in a Mayan calendar.
-
- If you are interested in these calendars, you can convert dates one
-at a time. Put point on the desired date of the Gregorian calendar and
-press the appropriate keys. The `p' is a mnemonic for "print" since
-Emacs "prints' the equivalent date in the echo area.
-
-\1f
-File: xemacs.info, Node: Calendar Systems, Next: To Other Calendar, Prev: Other Calendars, Up: Other Calendars
-
-Supported Calendar Systems
-==========================
-
- The ISO commercial calendar is used largely in Europe.
-
- The Julian calendar, named after Julius Caesar, was the one used in
-Europe throughout medieval times, and in many countries up until the
-nineteenth century.
-
- Astronomers use a simple counting of days elapsed since noon, Monday,
-January 1, 4713 B.C. on the Julian calendar. The number of days elapsed
-is called the _Julian day number_ or the _Astronomical day number_.
-
- The Hebrew calendar is used by tradition in the Jewish religion. The
-Emacs calendar program uses the Hebrew calendar to determine the dates
-of Jewish holidays. Hebrew calendar dates begin and end at sunset.
-
- The Islamic calendar is used in many predominantly Islamic countries.
-Emacs uses it to determine the dates of Islamic holidays. There is no
-universal agreement in the Islamic world about the calendar; Emacs uses
-a widely accepted version, but the precise dates of Islamic holidays
-often depend on proclamation by religious authorities, not on
-calculations. As a consequence, the actual dates of observance can vary
-slightly from the dates computed by Emacs. Islamic calendar dates begin
-and end at sunset.
-
- The French Revolutionary calendar was created by the Jacobins after
-the 1789 revolution, to represent a more secular and nature-based view
-of the annual cycle, and to install a 10-day week in a rationalization
-measure similar to the metric system. The French government officially
-abandoned this calendar at the end of 1805.
-
- The Maya of Central America used three separate, overlapping calendar
-systems, the _long count_, the _tzolkin_, and the _haab_. Emacs knows
-about all three of these calendars. Experts dispute the exact
-correlation between the Mayan calendar and our calendar; Emacs uses the
-Goodman-Martinez-Thompson correlation in its calculations.
-
- The Copts use a calendar based on the ancient Egyptian solar
-calendar. Their calendar consists of twelve 30-day months followed by
-an extra five-day period. Once every fourth year they add a leap day
-to this extra period to make it six days. The Ethiopic calendar is
-identical in structure, but has different year numbers and month names.
-
- The Persians use a solar calendar based on a design of Omar Khayyam.
-Their calendar consists of twelve months of which the first six have 31
-days, the next five have 30 days, and the last has 29 in ordinary years
-and 30 in leap years. Leap years occur in a complicated pattern every
-four or five years.
-
- The Chinese calendar is a complicated system of lunar months arranged
-into solar years. The years go in cycles of sixty, each year containing
-either twelve months in an ordinary year or thirteen months in a leap
-year; each month has either 29 or 30 days. Years, ordinary months, and
-days are named by combining one of ten "celestial stems" with one of
-twelve "terrestrial branches" for a total of sixty names that are
-repeated in a cycle of sixty.
-
-\1f
-File: xemacs.info, Node: To Other Calendar, Next: From Other Calendar, Prev: Calendar Systems, Up: Other Calendars
-
-Converting To Other Calendars
-=============================
-
- The following commands describe the selected date (the date at point)
-in various other calendar systems:
-
-`Button2 Other Calendars'
- Display the date that you click on, expressed in various other
- calendars.
-
-`p c'
- Display ISO commercial calendar equivalent for selected day
- (`calendar-print-iso-date').
-
-`p j'
- Display Julian date for selected day
- (`calendar-print-julian-date').
-
-`p a'
- Display astronomical (Julian) day number for selected day
- (`calendar-print-astro-day-number').
-
-`p h'
- Display Hebrew date for selected day
- (`calendar-print-hebrew-date').
-
-`p i'
- Display Islamic date for selected day
- (`calendar-print-islamic-date').
-
-`p f'
- Display French Revolutionary date for selected day
- (`calendar-print-french-date').
-
-`p C'
- Display Chinese date for selected day
- (`calendar-print-chinese-date').
-
-`p k'
- Display Coptic date for selected day
- (`calendar-print-coptic-date').
-
-`p e'
- Display Ethiopic date for selected day
- (`calendar-print-ethiopic-date').
-
-`p p'
- Display Persian date for selected day
- (`calendar-print-persian-date').
-
-`p m'
- Display Mayan date for selected day (`calendar-print-mayan-date').
-
- If you are using X, the easiest way to translate a date into other
-calendars is to click on it with `Button2', then choose `Other
-Calendars' from the menu that appears. This displays the equivalent
-forms of the date in all the calendars Emacs understands, in the form of
-a menu. (Choosing an alternative from this menu doesn't actually do
-anything--the menu is used only for display.)
-
- Put point on the desired date of the Gregorian calendar, then type
-the appropriate keys. The `p' is a mnemonic for "print" since Emacs
-"prints" the equivalent date in the echo area.
-
-\1f
-File: xemacs.info, Node: From Other Calendar, Next: Mayan Calendar, Prev: To Other Calendar, Up: Other Calendars
-
-Converting From Other Calendars
-===============================
-
- You can use the other supported calendars to specify a date to move
-to. This section describes the commands for doing this using calendars
-other than Mayan; for the Mayan calendar, see the following section.
-
-`g c'
- Move to a date specified in the ISO commercial calendar
- (`calendar-goto-iso-date').
-
-`g j'
- Move to a date specified in the Julian calendar
- (`calendar-goto-julian-date').
-
-`g a'
- Move to a date specified in astronomical (Julian) day number
- (`calendar-goto-astro-day-number').
-
-`g h'
- Move to a date specified in the Hebrew calendar
- (`calendar-goto-hebrew-date').
-
-`g i'
- Move to a date specified in the Islamic calendar
- (`calendar-goto-islamic-date').
-
-`g f'
- Move to a date specified in the French Revolutionary calendar
- (`calendar-goto-french-date').
-
-`g C'
- Move to a date specified in the Chinese calendar
- (`calendar-goto-chinese-date').
-
-`g p'
- Move to a date specified in the Persian calendar
- (`calendar-goto-persian-date').
-
-`g k'
- Move to a date specified in the Coptic calendar
- (`calendar-goto-coptic-date').
-
-`g e'
- Move to a date specified in the Ethiopic calendar
- (`calendar-goto-ethiopic-date').
-
- These commands ask you for a date on the other calendar, move point
-to the Gregorian calendar date equivalent to that date, and display the
-other calendar's date in the echo area. Emacs uses strict completion
-(*note Completion::) whenever it asks you to type a month name, so you
-don't have to worry about the spelling of Hebrew, Islamic, or French
-names.
-
- One common question concerning the Hebrew calendar is the computation
-of the anniversary of a date of death, called a "yahrzeit." The Emacs
-calendar includes a facility for such calculations. If you are in the
-calendar, the command `M-x list-yahrzeit-dates' asks you for a range of
-years and then displays a list of the yahrzeit dates for those years
-for the date given by point. If you are not in the calendar, this
-command first asks you for the date of death and the range of years,
-and then displays the list of yahrzeit dates.
-
-\1f
-File: xemacs.info, Node: Mayan Calendar, Next: Diary, Prev: From Other Calendar, Up: Other Calendars
-
-Converting from the Mayan Calendar
-----------------------------------
-
- Here are the commands to select dates based on the Mayan calendar:
-
-`g m l'
- Move to a date specified by the long count calendar
- (`calendar-goto-mayan-long-count-date').
-
-`g m n t'
- Move to the next occurrence of a place in the tzolkin calendar
- (`calendar-next-tzolkin-date').
-
-`g m p t'
- Move to the previous occurrence of a place in the tzolkin calendar
- (`calendar-previous-tzolkin-date').
-
-`g m n h'
- Move to the next occurrence of a place in the haab calendar
- (`calendar-next-haab-date').
-
-`g m p h'
- Move to the previous occurrence of a place in the haab calendar
- (`calendar-previous-haab-date').
-
-`g m n c'
- Move to the next occurrence of a place in the calendar round
- (`calendar-next-calendar-round-date').
-
-`g m p c'
- Move to the previous occurrence of a place in the calendar round
- (`calendar-previous-calendar-round-date').
-
- To understand these commands, you need to understand the Mayan
-calendars. The "long count" is a counting of days with these units:
-
- 1 kin = 1 day 1 uinal = 20 kin 1 tun = 18 uinal
- 1 katun = 20 tun 1 baktun = 20 katun
-
-Thus, the long count date 12.16.11.16.6 means 12 baktun, 16 katun, 11
-tun, 16 uinal, and 6 kin. The Emacs calendar can handle Mayan long
-count dates as early as 7.17.18.13.1, but no earlier. When you use the
-`g m l' command, type the Mayan long count date with the baktun, katun,
-tun, uinal, and kin separated by periods.
-
- The Mayan tzolkin calendar is a cycle of 260 days formed by a pair of
-independent cycles of 13 and 20 days. Since this cycle repeats
-endlessly, Emacs provides commands to move backward and forward to the
-previous or next point in the cycle. Type `g m p t' to go to the
-previous tzolkin date; Emacs asks you for a tzolkin date and moves point
-to the previous occurrence of that date. Similarly, type `g m n t' to
-go to the next occurrence of a tzolkin date.
-
- The Mayan haab calendar is a cycle of 365 days arranged as 18 months
-of 20 days each, followed a 5-day monthless period. Like the tzolkin
-cycle, this cycle repeats endlessly, and there are commands to move
-backward and forward to the previous or next point in the cycle. Type
-`g m p h' to go to the previous haab date; Emacs asks you for a haab
-date and moves point to the previous occurrence of that date.
-Similarly, type `g m n h' to go to the next occurrence of a haab date.
-
- The Maya also used the combination of the tzolkin date and the haab
-date. This combination is a cycle of about 52 years called a _calendar
-round_. If you type `g m p c', Emacs asks you for both a haab and a
-tzolkin date and then moves point to the previous occurrence of that
-combination. Use `g m n c' to move point to the next occurrence of a
-combination. These commands signal an error if the haab/tzolkin date
-combination you have typed is impossible.
-
- Emacs uses strict completion (*note Completion::) whenever it asks
-you to type a Mayan name, so you don't have to worry about spelling.
-
-\1f
-File: xemacs.info, Node: Diary, Next: Calendar Customization, Prev: Mayan Calendar, Up: Calendar/Diary
-
-The Diary
----------
-
- The Emacs diary keeps track of appointments or other events on a
-daily basis, in conjunction with the calendar. To use the diary
-feature, you must first create a "diary file" containing a list of
-events and their dates. Then Emacs can automatically pick out and
-display the events for today, for the immediate future, or for any
-specified date.
-
- By default, Emacs uses `~/diary' as the diary file. This is the
-same file that the `calendar' utility uses. A sample `~/diary' file is:
-
- 12/22/1988 Twentieth wedding anniversary!!
- &1/1. Happy New Year!
- 10/22 Ruth's birthday.
- * 21, *: Payday
- Tuesday--weekly meeting with grad students at 10am
- Supowit, Shen, Bitner, and Kapoor to attend.
- 1/13/89 Friday the thirteenth!!
- &thu 4pm squash game with Lloyd.
- mar 16 Dad's birthday
- April 15, 1989 Income tax due.
- &* 15 time cards due.
-
-This example uses extra spaces to align the event descriptions of most
-of the entries. Such formatting is purely a matter of taste.
-
- Although you probably will start by creating a diary manually, Emacs
-provides a number of commands to let you view, add, and change diary
-entries. You can also share diary entries with other users (*note
-Included Diary Files::).
-
-* Menu:
-
-* Diary Commands:: Viewing diary entries and associated calendar dates.
-* Format of Diary File:: Entering events in your diary.
-* Date Formats:: Various ways you can specify dates.
-* Adding to Diary:: Commands to create diary entries.
-* Special Diary Entries:: Anniversaries, blocks of dates, cyclic entries, etc.
-
-\1f
-File: xemacs.info, Node: Diary Commands, Next: Format of Diary File, Prev: Diary, Up: Diary
-
-Commands Displaying Diary Entries
----------------------------------
-
- Once you have created a `~/diary' file, you can use the calendar to
-view it. You can also view today's events outside of Calendar mode.
-
-`d'
- Display all diary entries for the selected date
- (`view-diary-entries').
-
-`Button2 Diary'
- Display all diary entries for the date you click on.
-
-`s'
- Display the entire diary file (`show-all-diary-entries').
-
-`m'
- Mark all visible dates that have diary entries
- (`mark-diary-entries').
-
-`u'
- Unmark the calendar window (`calendar-unmark').
-
-`M-x print-diary-entries'
- Print hard copy of the diary display as it appears.
-
-`M-x diary'
- Display all diary entries for today's date.
-
-`M-x diary-mail-entries'
- Mail yourself email reminders about upcoming diary entries.
-
- Displaying the diary entries with `d' shows in a separate window the
-diary entries for the selected date in the calendar. The mode line of
-the new window shows the date of the diary entries and any holidays
-that fall on that date. If you specify a numeric argument with `d', it
-shows all the diary entries for that many successive days. Thus, `2 d'
-displays all the entries for the selected date and for the following
-day.
-
- Another way to display the diary entries for a date is to click
-`Button2' on the date, and then choose `Diary' from the menu that
-appears.
-
- To get a broader view of which days are mentioned in the diary, use
-the `m' command. This displays the dates that have diary entries in a
-different face (or places a `+' after these dates, if display with
-multiple faces is not available). The command applies both to the
-currently visible months and to other months that subsequently become
-visible by scrolling. To turn marking off and erase the current marks,
-type `u', which also turns off holiday marks (*note Holidays::).
-
- To see the full diary file, rather than just some of the entries, use
-the `s' command.
-
- Display of selected diary entries uses the selective display feature
-to hide entries that don't apply.
-
- The diary buffer as you see it is an illusion, so simply printing the
-buffer does not print what you see on your screen. There is a special
-command to print hard copy of the diary buffer _as it appears_; this
-command is `M-x print-diary-entries'. It sends the data directly to
-the printer. You can customize it like `lpr-region' (*note Hardcopy::).
-
- The command `M-x diary' displays the diary entries for the current
-date, independently of the calendar display, and optionally for the next
-few days as well; the variable `number-of-diary-entries' specifies how
-many days to include (*note Customization::).
-
- If you put `(diary)' in your init file, this automatically displays
-a window with the day's diary entries, when you enter Emacs. *Note
-Init File::. The mode line of the displayed window shows the date and
-any holidays that fall on that date.
-
- Many users like to receive notice of events in their diary as email.
-To send such mail to yourself, use the command `M-x
-diary-mail-entries'. A prefix argument specifies how many days
-(starting with today) to check; otherwise, the variable
-`diary-mail-days' says how many days.
-
-\1f
-File: xemacs.info, Node: Format of Diary File, Next: Date Formats, Prev: Diary Commands, Up: Diary
-
-The Diary File
---------------
-
- Your "diary file" is a file that records events associated with
-particular dates. The name of the diary file is specified by the
-variable `diary-file'; `~/diary' is the default. The `calendar'
-utility program supports a subset of the format allowed by the Emacs
-diary facilities, so you can use that utility to view the diary file,
-with reasonable results aside from the entries it cannot understand.
-
- Each entry in the diary file describes one event and consists of one
-or more lines. An entry always begins with a date specification at the
-left margin. The rest of the entry is simply text to describe the
-event. If the entry has more than one line, then the lines after the
-first must begin with whitespace to indicate they continue a previous
-entry. Lines that do not begin with valid dates and do not continue a
-preceding entry are ignored.
-
- You can inhibit the marking of certain diary entries in the calendar
-window; to do this, insert an ampersand (`&') at the beginning of the
-entry, before the date. This has no effect on display of the entry in
-the diary window; it affects only marks on dates in the calendar
-window. Nonmarking entries are especially useful for generic entries
-that would otherwise mark many different dates.
-
- If the first line of a diary entry consists only of the date or day
-name with no following blanks or punctuation, then the diary window
-display doesn't include that line; only the continuation lines appear.
-For example, this entry:
-
- 02/11/1989
- Bill B. visits Princeton today
- 2pm Cognitive Studies Committee meeting
- 2:30-5:30 Liz at Lawrenceville
- 4:00pm Dentist appt
- 7:30pm Dinner at George's
- 8:00-10:00pm concert
-
-appears in the diary window without the date line at the beginning.
-This style of entry looks neater when you display just a single day's
-entries, but can cause confusion if you ask for more than one day's
-entries.
-
- You can edit the diary entries as they appear in the window, but it
-is important to remember that the buffer displayed contains the _entire_
-diary file, with portions of it concealed from view. This means, for
-instance, that the `C-f' (`forward-char') command can put point at what
-appears to be the end of the line, but what is in reality the middle of
-some concealed line.
-
- _Be careful when editing the diary entries!_ Inserting additional
-lines or adding/deleting characters in the middle of a visible line
-cannot cause problems, but editing at the end of a line may not do what
-you expect. Deleting a line may delete other invisible entries that
-follow it. Before editing the diary, it is best to display the entire
-file with `s' (`show-all-diary-entries').
-
-\1f
-File: xemacs.info, Node: Date Formats, Next: Adding to Diary, Prev: Format of Diary File, Up: Diary
-
-Date Formats
-------------
-
- Here are some sample diary entries, illustrating different ways of
-formatting a date. The examples all show dates in American order
-(month, day, year), but Calendar mode supports European order (day,
-month, year) as an option.
-
- 4/20/93 Switch-over to new tabulation system
- apr. 25 Start tabulating annual results
- 4/30 Results for April are due
- */25 Monthly cycle finishes
- Friday Don't leave without backing up files
-
- The first entry appears only once, on April 20, 1993. The second and
-third appear every year on the specified dates, and the fourth uses a
-wildcard (asterisk) for the month, so it appears on the 25th of every
-month. The final entry appears every week on Friday.
-
- You can use just numbers to express a date, as in `MONTH/DAY' or
-`MONTH/DAY/YEAR'. This must be followed by a nondigit. In the date
-itself, MONTH and DAY are numbers of one or two digits. The optional
-YEAR is also a number, and may be abbreviated to the last two digits;
-that is, you can use `11/12/1989' or `11/12/89'.
-
- Dates can also have the form `MONTHNAME DAY' or `MONTHNAME DAY,
-YEAR', where the month's name can be spelled in full or abbreviated to
-three characters (with or without a period). Case is not significant.
-
- A date may be "generic"; that is, partially unspecified. Then the
-entry applies to all dates that match the specification. If the date
-does not contain a year, it is generic and applies to any year.
-Alternatively, MONTH, DAY, or YEAR can be a `*'; this matches any
-month, day, or year, respectively. Thus, a diary entry `3/*/*' matches
-any day in March of any year; so does `march *'.
-
- If you prefer the European style of writing dates--in which the day
-comes before the month--type `M-x european-calendar' while in the
-calendar, or set the variable `european-calendar-style' to `t' _before_
-using any calendar or diary command. This mode interprets all dates in
-the diary in the European manner, and also uses European style for
-displaying diary dates. (Note that there is no comma after the
-MONTHNAME in the European style.) To go back to the (default) American
-style of writing dates, type `M-x american-calendar'.
-
- You can use the name of a day of the week as a generic date which
-applies to any date falling on that day of the week. You can abbreviate
-the day of the week to three letters (with or without a period) or spell
-it in full; case is not significant.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Sunrise/Sunset, Next: Lunar Phases, Prev: Holidays, Up: Calendar/Diary
+
+Times of Sunrise and Sunset
+---------------------------
+
+ Special calendar commands can tell you, to within a minute or two,
+the times of sunrise and sunset for any date.
+
+`S'
+ Display times of sunrise and sunset for the selected date
+ (`calendar-sunrise-sunset').
+
+`Button2 Sunrise/Sunset'
+ Display times of sunrise and sunset for the date you click on.
+
+`M-x sunrise-sunset'
+ Display times of sunrise and sunset for today's date.
+
+`C-u M-x sunrise-sunset'
+ Display times of sunrise and sunset for a specified date.
+
+ Within the calendar, to display the _local times_ of sunrise and
+sunset in the echo area, move point to the date you want, and type `S'.
+Alternatively, click `Button2' on the date, then choose
+`Sunrise/Sunset' from the menu that appears. The command `M-x
+sunrise-sunset' is available outside the calendar to display this
+information for today's date or a specified date. To specify a date
+other than today, use `C-u M-x sunrise-sunset', which prompts for the
+year, month, and day.
+
+ You can display the times of sunrise and sunset for any location and
+any date with `C-u C-u M-x sunrise-sunset'. This asks you for a
+longitude, latitude, number of minutes difference from Coordinated
+Universal Time, and date, and then tells you the times of sunrise and
+sunset for that location on that date.
+
+ Because the times of sunrise and sunset depend on the location on
+earth, you need to tell Emacs your latitude, longitude, and location
+name before using these commands. Here is an example of what to set:
+
+ (setq calendar-latitude 40.1)
+ (setq calendar-longitude -88.2)
+ (setq calendar-location-name "Urbana, IL")
+
+Use one decimal place in the values of `calendar-latitude' and
+`calendar-longitude'.
+
+ Your time zone also affects the local time of sunrise and sunset.
+Emacs usually gets time zone information from the operating system, but
+if these values are not what you want (or if the operating system does
+not supply them), you must set them yourself. Here is an example:
+
+ (setq calendar-time-zone -360)
+ (setq calendar-standard-time-zone-name "CST")
+ (setq calendar-daylight-time-zone-name "CDT")
+
+The value of `calendar-time-zone' is the number of minutes difference
+between your local standard time and Coordinated Universal Time
+(Greenwich time). The values of `calendar-standard-time-zone-name' and
+`calendar-daylight-time-zone-name' are the abbreviations used in your
+time zone. Emacs displays the times of sunrise and sunset _corrected
+for daylight savings time_. *Note Daylight Savings::, for how daylight
+savings time is determined.
+
+ As a user, you might find it convenient to set the calendar location
+variables for your usual physical location in your init file. And when
+you install Emacs on a machine, you can create a `default.el' file
+which sets them properly for the typical location of most users of that
+machine. *Note Init File::.
+
+\1f
+File: xemacs.info, Node: Lunar Phases, Next: Other Calendars, Prev: Sunrise/Sunset, Up: Calendar/Diary
+
+Phases of the Moon
+------------------
+
+ These calendar commands display the dates and times of the phases of
+the moon (new moon, first quarter, full moon, last quarter). This
+feature is useful for debugging problems that "depend on the phase of
+the moon."
+
+`M'
+ Display the dates and times for all the quarters of the moon for
+ the three-month period shown (`calendar-phases-of-moon').
+
+`M-x phases-of-moon'
+ Display dates and times of the quarters of the moon for three
+ months around today's date.
+
+ Within the calendar, use the `M' command to display a separate
+buffer of the phases of the moon for the current three-month range. The
+dates and times listed are accurate to within a few minutes.
+
+ Outside the calendar, use the command `M-x phases-of-moon' to
+display the list of the phases of the moon for the current month and the
+preceding and succeeding months. For information about a different
+month, use `C-u M-x phases-of-moon', which prompts for the month and
+year.
+
+ The dates and times given for the phases of the moon are given in
+local time (corrected for daylight savings, when appropriate); but if
+the variable `calendar-time-zone' is void, Coordinated Universal Time
+(the Greenwich time zone) is used. *Note Daylight Savings::.
+
+\1f
+File: xemacs.info, Node: Other Calendars, Next: Calendar Systems, Prev: Lunar Phases, Up: Calendar/Diary
+
+Conversion To and From Other Calendars
+--------------------------------------
+
+ The Emacs calendar displayed is _always_ the Gregorian calendar,
+sometimes called the "new style" calendar, which is used in most of the
+world today. However, this calendar did not exist before the sixteenth
+century and was not widely used before the eighteenth century; it did
+not fully displace the Julian calendar and gain universal acceptance
+until the early twentieth century. The Emacs calendar can display any
+month since January, year 1 of the current era, but the calendar
+displayed is the Gregorian, even for a date at which the Gregorian
+calendar did not exist.
+
+ While Emacs cannot display other calendars, it can convert dates to
+and from several other calendars.
+
+* Menu:
+
+* Calendar Systems:: The calendars Emacs understands
+ (aside from Gregorian).
+* To Other Calendar:: Converting the selected date to various calendars.
+* From Other Calendar:: Moving to a date specified in another calendar.
+* Mayan Calendar:: Moving to a date specified in a Mayan calendar.
+
+ If you are interested in these calendars, you can convert dates one
+at a time. Put point on the desired date of the Gregorian calendar and
+press the appropriate keys. The `p' is a mnemonic for "print" since
+Emacs "prints' the equivalent date in the echo area.
+
+\1f
+File: xemacs.info, Node: Calendar Systems, Next: To Other Calendar, Prev: Other Calendars, Up: Other Calendars
+
+Supported Calendar Systems
+==========================
+
+ The ISO commercial calendar is used largely in Europe.
+
+ The Julian calendar, named after Julius Caesar, was the one used in
+Europe throughout medieval times, and in many countries up until the
+nineteenth century.
+
+ Astronomers use a simple counting of days elapsed since noon, Monday,
+January 1, 4713 B.C. on the Julian calendar. The number of days elapsed
+is called the _Julian day number_ or the _Astronomical day number_.
+
+ The Hebrew calendar is used by tradition in the Jewish religion. The
+Emacs calendar program uses the Hebrew calendar to determine the dates
+of Jewish holidays. Hebrew calendar dates begin and end at sunset.
+
+ The Islamic calendar is used in many predominantly Islamic countries.
+Emacs uses it to determine the dates of Islamic holidays. There is no
+universal agreement in the Islamic world about the calendar; Emacs uses
+a widely accepted version, but the precise dates of Islamic holidays
+often depend on proclamation by religious authorities, not on
+calculations. As a consequence, the actual dates of observance can vary
+slightly from the dates computed by Emacs. Islamic calendar dates begin
+and end at sunset.
+
+ The French Revolutionary calendar was created by the Jacobins after
+the 1789 revolution, to represent a more secular and nature-based view
+of the annual cycle, and to install a 10-day week in a rationalization
+measure similar to the metric system. The French government officially
+abandoned this calendar at the end of 1805.
+
+ The Maya of Central America used three separate, overlapping calendar
+systems, the _long count_, the _tzolkin_, and the _haab_. Emacs knows
+about all three of these calendars. Experts dispute the exact
+correlation between the Mayan calendar and our calendar; Emacs uses the
+Goodman-Martinez-Thompson correlation in its calculations.
+
+ The Copts use a calendar based on the ancient Egyptian solar
+calendar. Their calendar consists of twelve 30-day months followed by
+an extra five-day period. Once every fourth year they add a leap day
+to this extra period to make it six days. The Ethiopic calendar is
+identical in structure, but has different year numbers and month names.
+
+ The Persians use a solar calendar based on a design of Omar Khayyam.
+Their calendar consists of twelve months of which the first six have 31
+days, the next five have 30 days, and the last has 29 in ordinary years
+and 30 in leap years. Leap years occur in a complicated pattern every
+four or five years.
+
+ The Chinese calendar is a complicated system of lunar months arranged
+into solar years. The years go in cycles of sixty, each year containing
+either twelve months in an ordinary year or thirteen months in a leap
+year; each month has either 29 or 30 days. Years, ordinary months, and
+days are named by combining one of ten "celestial stems" with one of
+twelve "terrestrial branches" for a total of sixty names that are
+repeated in a cycle of sixty.
+
+\1f
+File: xemacs.info, Node: To Other Calendar, Next: From Other Calendar, Prev: Calendar Systems, Up: Other Calendars
+
+Converting To Other Calendars
+=============================
+
+ The following commands describe the selected date (the date at point)
+in various other calendar systems:
+
+`Button2 Other Calendars'
+ Display the date that you click on, expressed in various other
+ calendars.
+
+`p c'
+ Display ISO commercial calendar equivalent for selected day
+ (`calendar-print-iso-date').
+
+`p j'
+ Display Julian date for selected day
+ (`calendar-print-julian-date').
+
+`p a'
+ Display astronomical (Julian) day number for selected day
+ (`calendar-print-astro-day-number').
+
+`p h'
+ Display Hebrew date for selected day
+ (`calendar-print-hebrew-date').
+
+`p i'
+ Display Islamic date for selected day
+ (`calendar-print-islamic-date').
+
+`p f'
+ Display French Revolutionary date for selected day
+ (`calendar-print-french-date').
+
+`p C'
+ Display Chinese date for selected day
+ (`calendar-print-chinese-date').
+
+`p k'
+ Display Coptic date for selected day
+ (`calendar-print-coptic-date').
+
+`p e'
+ Display Ethiopic date for selected day
+ (`calendar-print-ethiopic-date').
+
+`p p'
+ Display Persian date for selected day
+ (`calendar-print-persian-date').
+
+`p m'
+ Display Mayan date for selected day (`calendar-print-mayan-date').
+
+ If you are using X, the easiest way to translate a date into other
+calendars is to click on it with `Button2', then choose `Other
+Calendars' from the menu that appears. This displays the equivalent
+forms of the date in all the calendars Emacs understands, in the form of
+a menu. (Choosing an alternative from this menu doesn't actually do
+anything--the menu is used only for display.)
+
+ Put point on the desired date of the Gregorian calendar, then type
+the appropriate keys. The `p' is a mnemonic for "print" since Emacs
+"prints" the equivalent date in the echo area.
+
+\1f
+File: xemacs.info, Node: From Other Calendar, Next: Mayan Calendar, Prev: To Other Calendar, Up: Other Calendars
+
+Converting From Other Calendars
+===============================
+
+ You can use the other supported calendars to specify a date to move
+to. This section describes the commands for doing this using calendars
+other than Mayan; for the Mayan calendar, see the following section.
+
+`g c'
+ Move to a date specified in the ISO commercial calendar
+ (`calendar-goto-iso-date').
+
+`g j'
+ Move to a date specified in the Julian calendar
+ (`calendar-goto-julian-date').
+
+`g a'
+ Move to a date specified in astronomical (Julian) day number
+ (`calendar-goto-astro-day-number').
+
+`g h'
+ Move to a date specified in the Hebrew calendar
+ (`calendar-goto-hebrew-date').
+
+`g i'
+ Move to a date specified in the Islamic calendar
+ (`calendar-goto-islamic-date').
+
+`g f'
+ Move to a date specified in the French Revolutionary calendar
+ (`calendar-goto-french-date').
+
+`g C'
+ Move to a date specified in the Chinese calendar
+ (`calendar-goto-chinese-date').
+
+`g p'
+ Move to a date specified in the Persian calendar
+ (`calendar-goto-persian-date').
+
+`g k'
+ Move to a date specified in the Coptic calendar
+ (`calendar-goto-coptic-date').
+
+`g e'
+ Move to a date specified in the Ethiopic calendar
+ (`calendar-goto-ethiopic-date').
+
+ These commands ask you for a date on the other calendar, move point
+to the Gregorian calendar date equivalent to that date, and display the
+other calendar's date in the echo area. Emacs uses strict completion
+(*note Completion::) whenever it asks you to type a month name, so you
+don't have to worry about the spelling of Hebrew, Islamic, or French
+names.
+
+ One common question concerning the Hebrew calendar is the computation
+of the anniversary of a date of death, called a "yahrzeit." The Emacs
+calendar includes a facility for such calculations. If you are in the
+calendar, the command `M-x list-yahrzeit-dates' asks you for a range of
+years and then displays a list of the yahrzeit dates for those years
+for the date given by point. If you are not in the calendar, this
+command first asks you for the date of death and the range of years,
+and then displays the list of yahrzeit dates.
+
+\1f
+File: xemacs.info, Node: Mayan Calendar, Next: Diary, Prev: From Other Calendar, Up: Other Calendars
+
+Converting from the Mayan Calendar
+----------------------------------
+
+ Here are the commands to select dates based on the Mayan calendar:
+
+`g m l'
+ Move to a date specified by the long count calendar
+ (`calendar-goto-mayan-long-count-date').
+
+`g m n t'
+ Move to the next occurrence of a place in the tzolkin calendar
+ (`calendar-next-tzolkin-date').
+
+`g m p t'
+ Move to the previous occurrence of a place in the tzolkin calendar
+ (`calendar-previous-tzolkin-date').
+
+`g m n h'
+ Move to the next occurrence of a place in the haab calendar
+ (`calendar-next-haab-date').
+
+`g m p h'
+ Move to the previous occurrence of a place in the haab calendar
+ (`calendar-previous-haab-date').
+
+`g m n c'
+ Move to the next occurrence of a place in the calendar round
+ (`calendar-next-calendar-round-date').
+
+`g m p c'
+ Move to the previous occurrence of a place in the calendar round
+ (`calendar-previous-calendar-round-date').
+
+ To understand these commands, you need to understand the Mayan
+calendars. The "long count" is a counting of days with these units:
+
+ 1 kin = 1 day 1 uinal = 20 kin 1 tun = 18 uinal
+ 1 katun = 20 tun 1 baktun = 20 katun
+
+Thus, the long count date 12.16.11.16.6 means 12 baktun, 16 katun, 11
+tun, 16 uinal, and 6 kin. The Emacs calendar can handle Mayan long
+count dates as early as 7.17.18.13.1, but no earlier. When you use the
+`g m l' command, type the Mayan long count date with the baktun, katun,
+tun, uinal, and kin separated by periods.
+
+ The Mayan tzolkin calendar is a cycle of 260 days formed by a pair of
+independent cycles of 13 and 20 days. Since this cycle repeats
+endlessly, Emacs provides commands to move backward and forward to the
+previous or next point in the cycle. Type `g m p t' to go to the
+previous tzolkin date; Emacs asks you for a tzolkin date and moves point
+to the previous occurrence of that date. Similarly, type `g m n t' to
+go to the next occurrence of a tzolkin date.
+
+ The Mayan haab calendar is a cycle of 365 days arranged as 18 months
+of 20 days each, followed a 5-day monthless period. Like the tzolkin
+cycle, this cycle repeats endlessly, and there are commands to move
+backward and forward to the previous or next point in the cycle. Type
+`g m p h' to go to the previous haab date; Emacs asks you for a haab
+date and moves point to the previous occurrence of that date.
+Similarly, type `g m n h' to go to the next occurrence of a haab date.
+
+ The Maya also used the combination of the tzolkin date and the haab
+date. This combination is a cycle of about 52 years called a _calendar
+round_. If you type `g m p c', Emacs asks you for both a haab and a
+tzolkin date and then moves point to the previous occurrence of that
+combination. Use `g m n c' to move point to the next occurrence of a
+combination. These commands signal an error if the haab/tzolkin date
+combination you have typed is impossible.
+
+ Emacs uses strict completion (*note Completion::) whenever it asks
+you to type a Mayan name, so you don't have to worry about spelling.
+
+\1f
+File: xemacs.info, Node: Diary, Next: Calendar Customization, Prev: Mayan Calendar, Up: Calendar/Diary
+
+The Diary
+---------
+
+ The Emacs diary keeps track of appointments or other events on a
+daily basis, in conjunction with the calendar. To use the diary
+feature, you must first create a "diary file" containing a list of
+events and their dates. Then Emacs can automatically pick out and
+display the events for today, for the immediate future, or for any
+specified date.
+
+ By default, Emacs uses `~/diary' as the diary file. This is the
+same file that the `calendar' utility uses. A sample `~/diary' file is:
+
+ 12/22/1988 Twentieth wedding anniversary!!
+ &1/1. Happy New Year!
+ 10/22 Ruth's birthday.
+ * 21, *: Payday
+ Tuesday--weekly meeting with grad students at 10am
+ Supowit, Shen, Bitner, and Kapoor to attend.
+ 1/13/89 Friday the thirteenth!!
+ &thu 4pm squash game with Lloyd.
+ mar 16 Dad's birthday
+ April 15, 1989 Income tax due.
+ &* 15 time cards due.
+
+This example uses extra spaces to align the event descriptions of most
+of the entries. Such formatting is purely a matter of taste.
+
+ Although you probably will start by creating a diary manually, Emacs
+provides a number of commands to let you view, add, and change diary
+entries. You can also share diary entries with other users (*note
+Included Diary Files::).
+
+* Menu:
+
+* Diary Commands:: Viewing diary entries and associated calendar dates.
+* Format of Diary File:: Entering events in your diary.
+* Date Formats:: Various ways you can specify dates.
+* Adding to Diary:: Commands to create diary entries.
+* Special Diary Entries:: Anniversaries, blocks of dates, cyclic entries, etc.
+
+\1f
+File: xemacs.info, Node: Diary Commands, Next: Format of Diary File, Prev: Diary, Up: Diary
+
+Commands Displaying Diary Entries
+---------------------------------
+
+ Once you have created a `~/diary' file, you can use the calendar to
+view it. You can also view today's events outside of Calendar mode.
+
+`d'
+ Display all diary entries for the selected date
+ (`view-diary-entries').
+
+`Button2 Diary'
+ Display all diary entries for the date you click on.
+
+`s'
+ Display the entire diary file (`show-all-diary-entries').
+
+`m'
+ Mark all visible dates that have diary entries
+ (`mark-diary-entries').
+
+`u'
+ Unmark the calendar window (`calendar-unmark').
+
+`M-x print-diary-entries'
+ Print hard copy of the diary display as it appears.
+
+`M-x diary'
+ Display all diary entries for today's date.
+
+`M-x diary-mail-entries'
+ Mail yourself email reminders about upcoming diary entries.
+
+ Displaying the diary entries with `d' shows in a separate window the
+diary entries for the selected date in the calendar. The mode line of
+the new window shows the date of the diary entries and any holidays
+that fall on that date. If you specify a numeric argument with `d', it
+shows all the diary entries for that many successive days. Thus, `2 d'
+displays all the entries for the selected date and for the following
+day.
+
+ Another way to display the diary entries for a date is to click
+`Button2' on the date, and then choose `Diary' from the menu that
+appears.
+
+ To get a broader view of which days are mentioned in the diary, use
+the `m' command. This displays the dates that have diary entries in a
+different face (or places a `+' after these dates, if display with
+multiple faces is not available). The command applies both to the
+currently visible months and to other months that subsequently become
+visible by scrolling. To turn marking off and erase the current marks,
+type `u', which also turns off holiday marks (*note Holidays::).
+
+ To see the full diary file, rather than just some of the entries, use
+the `s' command.
+
+ Display of selected diary entries uses the selective display feature
+to hide entries that don't apply.
+
+ The diary buffer as you see it is an illusion, so simply printing the
+buffer does not print what you see on your screen. There is a special
+command to print hard copy of the diary buffer _as it appears_; this
+command is `M-x print-diary-entries'. It sends the data directly to
+the printer. You can customize it like `lpr-region' (*note Hardcopy::).
+
+ The command `M-x diary' displays the diary entries for the current
+date, independently of the calendar display, and optionally for the next
+few days as well; the variable `number-of-diary-entries' specifies how
+many days to include (*note Customization::).
+
+ If you put `(diary)' in your init file, this automatically displays
+a window with the day's diary entries, when you enter Emacs. *Note
+Init File::. The mode line of the displayed window shows the date and
+any holidays that fall on that date.
+
+ Many users like to receive notice of events in their diary as email.
+To send such mail to yourself, use the command `M-x
+diary-mail-entries'. A prefix argument specifies how many days
+(starting with today) to check; otherwise, the variable
+`diary-mail-days' says how many days.
+
+\1f
+File: xemacs.info, Node: Format of Diary File, Next: Date Formats, Prev: Diary Commands, Up: Diary
+
+The Diary File
+--------------
+
+ Your "diary file" is a file that records events associated with
+particular dates. The name of the diary file is specified by the
+variable `diary-file'; `~/diary' is the default. The `calendar'
+utility program supports a subset of the format allowed by the Emacs
+diary facilities, so you can use that utility to view the diary file,
+with reasonable results aside from the entries it cannot understand.
+
+ Each entry in the diary file describes one event and consists of one
+or more lines. An entry always begins with a date specification at the
+left margin. The rest of the entry is simply text to describe the
+event. If the entry has more than one line, then the lines after the
+first must begin with whitespace to indicate they continue a previous
+entry. Lines that do not begin with valid dates and do not continue a
+preceding entry are ignored.
+
+ You can inhibit the marking of certain diary entries in the calendar
+window; to do this, insert an ampersand (`&') at the beginning of the
+entry, before the date. This has no effect on display of the entry in
+the diary window; it affects only marks on dates in the calendar
+window. Nonmarking entries are especially useful for generic entries
+that would otherwise mark many different dates.
+
+ If the first line of a diary entry consists only of the date or day
+name with no following blanks or punctuation, then the diary window
+display doesn't include that line; only the continuation lines appear.
+For example, this entry:
+
+ 02/11/1989
+ Bill B. visits Princeton today
+ 2pm Cognitive Studies Committee meeting
+ 2:30-5:30 Liz at Lawrenceville
+ 4:00pm Dentist appt
+ 7:30pm Dinner at George's
+ 8:00-10:00pm concert
+
+appears in the diary window without the date line at the beginning.
+This style of entry looks neater when you display just a single day's
+entries, but can cause confusion if you ask for more than one day's
+entries.
+
+ You can edit the diary entries as they appear in the window, but it
+is important to remember that the buffer displayed contains the _entire_
+diary file, with portions of it concealed from view. This means, for
+instance, that the `C-f' (`forward-char') command can put point at what
+appears to be the end of the line, but what is in reality the middle of
+some concealed line.
+
+ _Be careful when editing the diary entries!_ Inserting additional
+lines or adding/deleting characters in the middle of a visible line
+cannot cause problems, but editing at the end of a line may not do what
+you expect. Deleting a line may delete other invisible entries that
+follow it. Before editing the diary, it is best to display the entire
+file with `s' (`show-all-diary-entries').
+
+\1f
+File: xemacs.info, Node: Date Formats, Next: Adding to Diary, Prev: Format of Diary File, Up: Diary
+
+Date Formats
+------------
+
+ Here are some sample diary entries, illustrating different ways of
+formatting a date. The examples all show dates in American order
+(month, day, year), but Calendar mode supports European order (day,
+month, year) as an option.
+
+ 4/20/93 Switch-over to new tabulation system
+ apr. 25 Start tabulating annual results
+ 4/30 Results for April are due
+ */25 Monthly cycle finishes
+ Friday Don't leave without backing up files
+
+ The first entry appears only once, on April 20, 1993. The second and
+third appear every year on the specified dates, and the fourth uses a
+wildcard (asterisk) for the month, so it appears on the 25th of every
+month. The final entry appears every week on Friday.
+
+ You can use just numbers to express a date, as in `MONTH/DAY' or
+`MONTH/DAY/YEAR'. This must be followed by a nondigit. In the date
+itself, MONTH and DAY are numbers of one or two digits. The optional
+YEAR is also a number, and may be abbreviated to the last two digits;
+that is, you can use `11/12/1989' or `11/12/89'.
+
+ Dates can also have the form `MONTHNAME DAY' or `MONTHNAME DAY,
+YEAR', where the month's name can be spelled in full or abbreviated to
+three characters (with or without a period). Case is not significant.
+
+ A date may be "generic"; that is, partially unspecified. Then the
+entry applies to all dates that match the specification. If the date
+does not contain a year, it is generic and applies to any year.
+Alternatively, MONTH, DAY, or YEAR can be a `*'; this matches any
+month, day, or year, respectively. Thus, a diary entry `3/*/*' matches
+any day in March of any year; so does `march *'.
+
+ If you prefer the European style of writing dates--in which the day
+comes before the month--type `M-x european-calendar' while in the
+calendar, or set the variable `european-calendar-style' to `t' _before_
+using any calendar or diary command. This mode interprets all dates in
+the diary in the European manner, and also uses European style for
+displaying diary dates. (Note that there is no comma after the
+MONTHNAME in the European style.) To go back to the (default) American
+style of writing dates, type `M-x american-calendar'.
+
+ You can use the name of a day of the week as a generic date which
+applies to any date falling on that day of the week. You can abbreviate
+the day of the week to three letters (with or without a period) or spell
+it in full; case is not significant.
+
+\1f
File: xemacs.info, Node: Adding to Diary, Next: Special Diary Entries, Prev: Date Formats, Up: Diary
Commands to Add to the Diary
savings time should occur. For Cambridge, Massachusetts both variables'
values are 120.
-\1f
-File: xemacs.info, Node: Diary Customizing, Next: Hebrew/Islamic Entries, Prev: Daylight Savings, Up: Calendar Customization
-
-Customizing the Diary
-.....................
-
- Ordinarily, the mode line of the diary buffer window indicates any
-holidays that fall on the date of the diary entries. The process of
-checking for holidays can take several seconds, so including holiday
-information delays the display of the diary buffer noticeably. If you'd
-prefer to have a faster display of the diary buffer but without the
-holiday information, set the variable `holidays-in-diary-buffer' to
-`nil'.
-
- The variable `number-of-diary-entries' controls the number of days
-of diary entries to be displayed at one time. It affects the initial
-display when `view-diary-entries-initially' is `t', as well as the
-command `M-x diary'. For example, the default value is 1, which says
-to display only the current day's diary entries. If the value is 2,
-both the current day's and the next day's entries are displayed. The
-value can also be a vector of seven elements: for example, if the value
-is `[0 2 2 2 2 4 1]' then no diary entries appear on Sunday, the
-current date's and the next day's diary entries appear Monday through
-Thursday, Friday through Monday's entries appear on Friday, while on
-Saturday only that day's entries appear.
-
- The variable `print-diary-entries-hook' is a normal hook run after
-preparation of a temporary buffer containing just the diary entries
-currently visible in the diary buffer. (The other, irrelevant diary
-entries are really absent from the temporary buffer; in the diary
-buffer, they are merely hidden.) The default value of this hook does
-the printing with the command `lpr-buffer'. If you want to use a
-different command to do the printing, just change the value of this
-hook. Other uses might include, for example, rearranging the lines into
-order by day and time.
-
- You can customize the form of dates in your diary file, if neither
-the standard American nor European styles suits your needs, by setting
-the variable `diary-date-forms'. This variable is a list of patterns
-for recognizing a date. Each date pattern is a list whose elements may
-be regular expressions (*note Regexps::) or the symbols `month', `day',
-`year', `monthname', and `dayname'. All these elements serve as
-patterns that match certain kinds of text in the diary file. In order
-for the date pattern, as a whole, to match, all of its elements must
-match consecutively.
-
- A regular expression in a date pattern matches in its usual fashion,
-using the standard syntax table altered so that `*' is a word
-constituent.
-
- The symbols `month', `day', `year', `monthname', and `dayname' match
-the month number, day number, year number, month name, and day name of
-the date being considered. The symbols that match numbers allow
-leading zeros; those that match names allow three-letter abbreviations
-and capitalization. All the symbols can match `*'; since `*' in a
-diary entry means "any day", "any month", and so on, it should match
-regardless of the date being considered.
-
- The default value of `diary-date-forms' in the American style is
-this:
-
- ((month "/" day "[^/0-9]")
- (month "/" day "/" year "[^0-9]")
- (monthname " *" day "[^,0-9]")
- (monthname " *" day ", *" year "[^0-9]")
- (dayname "\\W"))
-
-Emacs matches of the diary entries with the date forms is done with the
-standard syntax table from Fundamental mode (*note Syntax Tables:
-(lispref)Syntax Tables.), but with the `*' changed so that it is a word
-constituent.
-
- The date patterns in the list must be _mutually exclusive_ and must
-not match any portion of the diary entry itself, just the date and one
-character of whitespace. If, to be mutually exclusive, the pattern
-must match a portion of the diary entry text--beyond the whitespace
-that ends the date--then the first element of the date pattern _must_
-be `backup'. This causes the date recognizer to back up to the
-beginning of the current word of the diary entry, after finishing the
-match. Even if you use `backup', the date pattern must absolutely not
-match more than a portion of the first word of the diary entry. The
-default value of `diary-date-forms' in the European style is this list:
-
- ((day "/" month "[^/0-9]")
- (day "/" month "/" year "[^0-9]")
- (backup day " *" monthname "\\W+\\<[^*0-9]")
- (day " *" monthname " *" year "[^0-9]")
- (dayname "\\W"))
-
-Notice the use of `backup' in the third pattern, because it needs to
-match part of a word beyond the date itself to distinguish it from the
-fourth pattern.
-
-\1f
-File: xemacs.info, Node: Hebrew/Islamic Entries, Next: Fancy Diary Display, Prev: Diary Customizing, Up: Calendar Customization
-
-Hebrew- and Islamic-Date Diary Entries
-......................................
-
- Your diary file can have entries based on Hebrew or Islamic dates, as
-well as entries based on the world-standard Gregorian calendar.
-However, because recognition of such entries is time-consuming and most
-people don't use them, you must explicitly enable their use. If you
-want the diary to recognize Hebrew-date diary entries, for example, you
-must do this:
-
- (add-hook 'nongregorian-diary-listing-hook 'list-hebrew-diary-entries)
- (add-hook 'nongregorian-diary-marking-hook 'mark-hebrew-diary-entries)
-
-If you want Islamic-date entries, do this:
-
- (add-hook 'nongregorian-diary-listing-hook 'list-islamic-diary-entries)
- (add-hook 'nongregorian-diary-marking-hook 'mark-islamic-diary-entries)
-
- Hebrew- and Islamic-date diary entries have the same formats as
-Gregorian-date diary entries, except that `H' precedes a Hebrew date
-and `I' precedes an Islamic date. Moreover, because the Hebrew and
-Islamic month names are not uniquely specified by the first three
-letters, you may not abbreviate them. For example, a diary entry for
-the Hebrew date Heshvan 25 could look like this:
-
- HHeshvan 25 Happy Hebrew birthday!
-
-and would appear in the diary for any date that corresponds to Heshvan
-25 on the Hebrew calendar. And here is Islamic-date diary entry that
-matches Dhu al-Qada 25:
-
- IDhu al-Qada 25 Happy Islamic birthday!
-
-and would appear in the diary for any date that corresponds to Dhu
-al-Qada 25 on the Islamic calendar.
-
- As with Gregorian-date diary entries, Hebrew- and Islamic-date
-entries are nonmarking if they are preceded with an ampersand (`&').
-
- Here is a table of commands used in the calendar to create diary
-entries that match the selected date and other dates that are similar
-in the Hebrew or Islamic calendar:
-
-`i h d'
- Add a diary entry for the Hebrew date corresponding to the
- selected date (`insert-hebrew-diary-entry').
-
-`i h m'
- Add a diary entry for the day of the Hebrew month corresponding to
- the selected date (`insert-monthly-hebrew-diary-entry'). This
- diary entry matches any date that has the same Hebrew
- day-within-month as the selected date.
-
-`i h y'
- Add a diary entry for the day of the Hebrew year corresponding to
- the selected date (`insert-yearly-hebrew-diary-entry'). This diary
- entry matches any date which has the same Hebrew month and
- day-within-month as the selected date.
-
-`i i d'
- Add a diary entry for the Islamic date corresponding to the
- selected date (`insert-islamic-diary-entry').
-
-`i i m'
- Add a diary entry for the day of the Islamic month corresponding
- to the selected date (`insert-monthly-islamic-diary-entry').
-
-`i i y'
- Add a diary entry for the day of the Islamic year corresponding to
- the selected date (`insert-yearly-islamic-diary-entry').
-
- These commands work much like the corresponding commands for ordinary
-diary entries: they apply to the date that point is on in the calendar
-window, and what they do is insert just the date portion of a diary
-entry at the end of your diary file. You must then insert the rest of
-the diary entry.
-
-\1f
-File: xemacs.info, Node: Fancy Diary Display, Next: Included Diary Files, Prev: Hebrew/Islamic Entries, Up: Calendar Customization
-
-Fancy Diary Display
-...................
-
- Diary display works by preparing the diary buffer and then running
-the hook `diary-display-hook'. The default value of this hook
-(`simple-diary-display') hides the irrelevant diary entries and then
-displays the buffer. However, if you specify the hook as follows,
-
- (add-hook 'diary-display-hook 'fancy-diary-display)
-
-this enables fancy diary display. It displays diary entries and
-holidays by copying them into a special buffer that exists only for the
-sake of display. Copying to a separate buffer provides an opportunity
-to change the displayed text to make it prettier--for example, to sort
-the entries by the dates they apply to.
-
- As with simple diary display, you can print a hard copy of the buffer
-with `print-diary-entries'. To print a hard copy of a day-by-day diary
-for a week by positioning point on Sunday of that week, type `7 d' and
-then do `M-x print-diary-entries'. As usual, the inclusion of the
-holidays slows down the display slightly; you can speed things up by
-setting the variable `holidays-in-diary-buffer' to `nil'.
-
- Ordinarily, the fancy diary buffer does not show days for which
-there are no diary entries, even if that day is a holiday. If you want
-such days to be shown in the fancy diary buffer, set the variable
-`diary-list-include-blanks' to `t'.
-
- If you use the fancy diary display, you can use the normal hook
-`list-diary-entries-hook' to sort each day's diary entries by their
-time of day. Add this line to your init file:
-
- (add-hook 'list-diary-entries-hook 'sort-diary-entries t)
-
- *Note Init File::.
-
-For each day, this sorts diary entries that begin with a recognizable
-time of day according to their times. Diary entries without times come
-first within each day.
-
-\1f
-File: xemacs.info, Node: Included Diary Files, Next: Sexp Diary Entries, Prev: Fancy Diary Display, Up: Calendar Customization
-
-Included Diary Files
-....................
-
- Fancy diary display also has the ability to process included diary
-files. This permits a group of people to share a diary file for events
-that apply to all of them. Lines in the diary file of this form:
-
- #include "FILENAME"
-
-includes the diary entries from the file FILENAME in the fancy diary
-buffer. The include mechanism is recursive, so that included files can
-include other files, and so on; you must be careful not to have a cycle
-of inclusions, of course. Here is how to enable the include facility:
-
- (add-hook 'list-diary-entries-hook 'include-other-diary-files)
- (add-hook 'mark-diary-entries-hook 'mark-included-diary-files)
-
- The include mechanism works only with the fancy diary display,
-because ordinary diary display shows the entries directly from your
-diary file.
-
-\1f
-File: xemacs.info, Node: Sexp Diary Entries, Next: Appt Customizing, Prev: Included Diary Files, Up: Calendar Customization
-
-Sexp Entries and the Fancy Diary Display
-........................................
-
- Sexp diary entries allow you to do more than just have complicated
-conditions under which a diary entry applies. If you use the fancy
-diary display, sexp entries can generate the text of the entry depending
-on the date itself. For example, an anniversary diary entry can insert
-the number of years since the anniversary date into the text of the
-diary entry. Thus the `%d' in this dairy entry:
-
- %%(diary-anniversary 10 31 1948) Arthur's birthday (%d years old)
-
-gets replaced by the age, so on October 31, 1990 the entry appears in
-the fancy diary buffer like this:
-
- Arthur's birthday (42 years old)
-
-If the diary file instead contains this entry:
-
- %%(diary-anniversary 10 31 1948) Arthur's %d%s birthday
-
-the entry in the fancy diary buffer for October 31, 1990 appears like
-this:
-
- Arthur's 42nd birthday
-
- Similarly, cyclic diary entries can interpolate the number of
-repetitions that have occurred:
-
- %%(diary-cyclic 50 1 1 1990) Renew medication (%d%s time)
-
-looks like this:
-
- Renew medication (5th time)
-
-in the fancy diary display on September 8, 1990.
-
- The generality of sexp diary entries lets you specify any diary entry
-that you can describe algorithmically. A sexp diary entry contains an
-expression that computes whether the entry applies to any given date.
-If its value is non-`nil', the entry applies to that date; otherwise,
-it does not. The expression can use the variable `date' to find the
-date being considered; its value is a list (MONTH DAY YEAR) that refers
-to the Gregorian calendar.
-
- Suppose you get paid on the 21st of the month if it is a weekday, and
-on the Friday before if the 21st is on a weekend. Here is how to write
-a sexp diary entry that matches those dates:
-
- &%%(let ((dayname (calendar-day-of-week date))
- (day (car (cdr date))))
- (or (and (= day 21) (memq dayname '(1 2 3 4 5)))
- (and (memq day '(19 20)) (= dayname 5)))
- ) Pay check deposited
-
-applies to just those dates. This example illustrates how the sexp can
-depend on the variable `date'; this variable is a list (MONTH DAY YEAR)
-that gives the Gregorian date for which the diary entries are being
-found. If the value of the expression is `t', the entry applies to
-that date. If the expression evaluates to `nil', the entry does _not_
-apply to that date.
-
- The following sexp diary entries take advantage of the ability (in
-the fancy diary display) to concoct diary entries whose text varies
-based on the date:
-
-`%%(diary-sunrise-sunset)'
- Make a diary entry for the local times of today's sunrise and
- sunset.
-
-`%%(diary-phases-of-moon)'
- Make a diary entry for the phases (quarters) of the moon.
-
-`%%(diary-day-of-year)'
- Make a diary entry with today's day number in the current year and
- the number of days remaining in the current year.
-
-`%%(diary-iso-date)'
- Make a diary entry with today's equivalent ISO commercial date.
-
-`%%(diary-julian-date)'
- Make a diary entry with today's equivalent date on the Julian
- calendar.
-
-`%%(diary-astro-day-number)'
- Make a diary entry with today's equivalent astronomical (Julian)
- day number.
-
-`%%(diary-hebrew-date)'
- Make a diary entry with today's equivalent date on the Hebrew
- calendar.
-
-`%%(diary-islamic-date)'
- Make a diary entry with today's equivalent date on the Islamic
- calendar.
-
-`%%(diary-french-date)'
- Make a diary entry with today's equivalent date on the French
- Revolutionary calendar.
-
-`%%(diary-mayan-date)'
- Make a diary entry with today's equivalent date on the Mayan
- calendar.
-
-Thus including the diary entry
-
- &%%(diary-hebrew-date)
-
-causes every day's diary display to contain the equivalent date on the
-Hebrew calendar, if you are using the fancy diary display. (With simple
-diary display, the line `&%%(diary-hebrew-date)' appears in the diary
-for any date, but does nothing particularly useful.)
-
- These functions can be used to construct sexp diary entries based on
-the Hebrew calendar in certain standard ways:
-
-`%%(diary-rosh-hodesh)'
- Make a diary entry that tells the occurrence and ritual
- announcement of each new Hebrew month.
-
-`%%(diary-parasha)'
- Make a Saturday diary entry that tells the weekly synagogue
- scripture reading.
-
-`%%(diary-sabbath-candles)'
- Make a Friday diary entry that tells the _local time_ of Sabbath
- candle lighting.
-
-`%%(diary-omer)'
- Make a diary entry that gives the omer count, when appropriate.
-
-`%%(diary-yahrzeit MONTH DAY YEAR) NAME'
- Make a diary entry marking the anniversary of a date of death.
- The date is the _Gregorian_ (civil) date of death. The diary
- entry appears on the proper Hebrew calendar anniversary and on the
- day before. (In the European style, the order of the parameters
- is changed to DAY, MONTH, YEAR.)
-
-\1f
-File: xemacs.info, Node: Appt Customizing, Prev: Sexp Diary Entries, Up: Calendar Customization
-
-Customizing Appointment Reminders
-.................................
-
- You can specify exactly how Emacs reminds you of an appointment, and
-how far in advance it begins doing so, by setting these variables:
-
-`appt-message-warning-time'
- The time in minutes before an appointment that the reminder
- begins. The default is 10 minutes.
-
-`appt-audible'
- If this is `t' (the default), Emacs rings the terminal bell for
- appointment reminders.
-
-`appt-visible'
- If this is `t' (the default), Emacs displays the appointment
- message in echo area.
-
-`appt-display-mode-line'
- If this is `t' (the default), Emacs displays the number of minutes
- to the appointment on the mode line.
-
-`appt-msg-window'
- If this is `t' (the default), Emacs displays the appointment
- message in another window.
-
-`appt-display-duration'
- The number of seconds an appointment message is displayed. The
- default is 5 seconds.
-
-\1f
-File: xemacs.info, Node: Sorting, Next: Shell, Prev: Calendar/Diary, Up: Top
-
-Sorting Text
-============
-
- XEmacs provides several commands for sorting text in a buffer. All
-operate on the contents of the region (the text between point and the
-mark). They divide the text of the region into many "sort records",
-identify a "sort key" for each record, and then reorder the records
-using the order determined by the sort keys. The records are ordered so
-that their keys are in alphabetical order, or, for numerical sorting, in
-numerical order. In alphabetical sorting, all upper-case letters `A'
-through `Z' come before lower-case `a', in accordance with the ASCII
-character sequence.
-
- The sort commands differ in how they divide the text into sort
-records and in which part of each record they use as the sort key.
-Most of the commands make each line a separate sort record, but some
-commands use paragraphs or pages as sort records. Most of the sort
-commands use each entire sort record as its own sort key, but some use
-only a portion of the record as the sort key.
-
-`M-x sort-lines'
- Divide the region into lines and sort by comparing the entire text
- of a line. A prefix argument means sort in descending order.
-
-`M-x sort-paragraphs'
- Divide the region into paragraphs and sort by comparing the entire
- text of a paragraph (except for leading blank lines). A prefix
- argument means sort in descending order.
-
-`M-x sort-pages'
- Divide the region into pages and sort by comparing the entire text
- of a page (except for leading blank lines). A prefix argument
- means sort in descending order.
-
-`M-x sort-fields'
- Divide the region into lines and sort by comparing the contents of
- one field in each line. Fields are defined as separated by
- whitespace, so the first run of consecutive non-whitespace
- characters in a line constitutes field 1, the second such run
- constitutes field 2, etc.
-
- You specify which field to sort by with a numeric argument: 1 to
- sort by field 1, etc. A negative argument means sort in descending
- order. Thus, minus 2 means sort by field 2 in reverse-alphabetical
- order.
-
-`M-x sort-numeric-fields'
- Like `M-x sort-fields', except the specified field is converted to
- a number for each line and the numbers are compared. `10' comes
- before `2' when considered as text, but after it when considered
- as a number.
-
-`M-x sort-columns'
- Like `M-x sort-fields', except that the text within each line used
- for comparison comes from a fixed range of columns. An explanation
- is given below.
-
- For example, if the buffer contains:
-
- On systems where clash detection (locking of files being edited) is
- implemented, XEmacs also checks the first time you modify a buffer
- whether the file has changed on disk since it was last visited or
- saved. If it has, you are asked to confirm that you want to change
- the buffer.
-
-then if you apply `M-x sort-lines' to the entire buffer you get:
-
- On systems where clash detection (locking of files being edited) is
- implemented, XEmacs also checks the first time you modify a buffer
- saved. If it has, you are asked to confirm that you want to change
- the buffer.
- whether the file has changed on disk since it was last visited or
-
-where the upper case `O' comes before all lower case letters. If you
-apply instead `C-u 2 M-x sort-fields' you get:
-
- saved. If it has, you are asked to confirm that you want to change
- implemented, XEmacs also checks the first time you modify a buffer
- the buffer.
- On systems where clash detection (locking of files being edited) is
- whether the file has changed on disk since it was last visited or
-
-where the sort keys were `If', `XEmacs', `buffer', `systems', and `the'.
-
- `M-x sort-columns' requires more explanation. You specify the
-columns by putting point at one of the columns and the mark at the other
-column. Because this means you cannot put point or the mark at the
-beginning of the first line to sort, this command uses an unusual
-definition of `region': all of the line point is in is considered part
-of the region, and so is all of the line the mark is in.
-
- For example, to sort a table by information found in columns 10 to
-15, you could put the mark on column 10 in the first line of the table,
-and point on column 15 in the last line of the table, and then use this
-command. Or you could put the mark on column 15 in the first line and
-point on column 10 in the last line.
-
- This can be thought of as sorting the rectangle specified by point
-and the mark, except that the text on each line to the left or right of
-the rectangle moves along with the text inside the rectangle. *Note
-Rectangles::.
-
-\1f
-File: xemacs.info, Node: Shell, Next: Narrowing, Prev: Sorting, Up: Top
-
-Running Shell Commands from XEmacs
-==================================
-
- XEmacs has commands for passing single command lines to inferior
-shell processes; it can also run a shell interactively with input and
-output to an XEmacs buffer `*shell*'.
-
-`M-!'
- Run a specified shell command line and display the output
- (`shell-command').
-
-`M-|'
- Run a specified shell command line with region contents as input;
- optionally replace the region with the output
- (`shell-command-on-region').
-
-`M-x shell'
- Run a subshell with input and output through an XEmacs buffer.
- You can then give commands interactively.
-
-`M-x term'
- Run a subshell with input and output through an XEmacs buffer.
- You can then give commands interactively. Full terminal emulation
- is available.
-
-* Menu:
-
-* Single Shell:: How to run one shell command and return.
-* Interactive Shell:: Permanent shell taking input via XEmacs.
-* Shell Mode:: Special XEmacs commands used with permanent shell.
-* Terminal emulator:: An XEmacs window as a terminal emulator.
-* Term Mode:: Special XEmacs commands used in Term mode.
-* Paging in Term:: Paging in the terminal emulator.
-
-\1f
-File: xemacs.info, Node: Single Shell, Next: Interactive Shell, Prev: Shell, Up: Shell
-
-Single Shell Commands
----------------------
-
- `M-!' (`shell-command') reads a line of text using the minibuffer
-and creates an inferior shell to execute the line as a command.
-Standard input from the command comes from the null device. If the
-shell command produces any output, the output goes to an XEmacs buffer
-named `*Shell Command Output*', which is displayed in another window
-but not selected. A numeric argument, as in `M-1 M-!', directs this
-command to insert any output into the current buffer. In that case,
-point is left before the output and the mark is set after the output.
-
- `M-|' (`shell-command-on-region') is like `M-!' but passes the
-contents of the region as input to the shell command, instead of no
-input. If a numeric argument is used to direct output to the current
-buffer, then the old region is deleted first and the output replaces it
-as the contents of the region.
-
- Both `M-!' and `M-|' use `shell-file-name' to specify the shell to
-use. This variable is initialized based on your `SHELL' environment
-variable when you start XEmacs. If the file name does not specify a
-directory, the directories in the list `exec-path' are searched; this
-list is initialized based on the `PATH' environment variable when you
-start XEmacs. You can override either or both of these default
-initializations in your init file. *Note Init File::.
-
- When you use `M-!' and `M-|', XEmacs has to wait until the shell
-command completes. You can quit with `C-g'; that terminates the shell
-command.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Diary Customizing, Next: Hebrew/Islamic Entries, Prev: Daylight Savings, Up: Calendar Customization
+
+Customizing the Diary
+.....................
+
+ Ordinarily, the mode line of the diary buffer window indicates any
+holidays that fall on the date of the diary entries. The process of
+checking for holidays can take several seconds, so including holiday
+information delays the display of the diary buffer noticeably. If you'd
+prefer to have a faster display of the diary buffer but without the
+holiday information, set the variable `holidays-in-diary-buffer' to
+`nil'.
+
+ The variable `number-of-diary-entries' controls the number of days
+of diary entries to be displayed at one time. It affects the initial
+display when `view-diary-entries-initially' is `t', as well as the
+command `M-x diary'. For example, the default value is 1, which says
+to display only the current day's diary entries. If the value is 2,
+both the current day's and the next day's entries are displayed. The
+value can also be a vector of seven elements: for example, if the value
+is `[0 2 2 2 2 4 1]' then no diary entries appear on Sunday, the
+current date's and the next day's diary entries appear Monday through
+Thursday, Friday through Monday's entries appear on Friday, while on
+Saturday only that day's entries appear.
+
+ The variable `print-diary-entries-hook' is a normal hook run after
+preparation of a temporary buffer containing just the diary entries
+currently visible in the diary buffer. (The other, irrelevant diary
+entries are really absent from the temporary buffer; in the diary
+buffer, they are merely hidden.) The default value of this hook does
+the printing with the command `lpr-buffer'. If you want to use a
+different command to do the printing, just change the value of this
+hook. Other uses might include, for example, rearranging the lines into
+order by day and time.
+
+ You can customize the form of dates in your diary file, if neither
+the standard American nor European styles suits your needs, by setting
+the variable `diary-date-forms'. This variable is a list of patterns
+for recognizing a date. Each date pattern is a list whose elements may
+be regular expressions (*note Regexps::) or the symbols `month', `day',
+`year', `monthname', and `dayname'. All these elements serve as
+patterns that match certain kinds of text in the diary file. In order
+for the date pattern, as a whole, to match, all of its elements must
+match consecutively.
+
+ A regular expression in a date pattern matches in its usual fashion,
+using the standard syntax table altered so that `*' is a word
+constituent.
+
+ The symbols `month', `day', `year', `monthname', and `dayname' match
+the month number, day number, year number, month name, and day name of
+the date being considered. The symbols that match numbers allow
+leading zeros; those that match names allow three-letter abbreviations
+and capitalization. All the symbols can match `*'; since `*' in a
+diary entry means "any day", "any month", and so on, it should match
+regardless of the date being considered.
+
+ The default value of `diary-date-forms' in the American style is
+this:
+
+ ((month "/" day "[^/0-9]")
+ (month "/" day "/" year "[^0-9]")
+ (monthname " *" day "[^,0-9]")
+ (monthname " *" day ", *" year "[^0-9]")
+ (dayname "\\W"))
+
+Emacs matches of the diary entries with the date forms is done with the
+standard syntax table from Fundamental mode (*note Syntax Tables:
+(lispref)Syntax Tables.), but with the `*' changed so that it is a word
+constituent.
+
+ The date patterns in the list must be _mutually exclusive_ and must
+not match any portion of the diary entry itself, just the date and one
+character of whitespace. If, to be mutually exclusive, the pattern
+must match a portion of the diary entry text--beyond the whitespace
+that ends the date--then the first element of the date pattern _must_
+be `backup'. This causes the date recognizer to back up to the
+beginning of the current word of the diary entry, after finishing the
+match. Even if you use `backup', the date pattern must absolutely not
+match more than a portion of the first word of the diary entry. The
+default value of `diary-date-forms' in the European style is this list:
+
+ ((day "/" month "[^/0-9]")
+ (day "/" month "/" year "[^0-9]")
+ (backup day " *" monthname "\\W+\\<[^*0-9]")
+ (day " *" monthname " *" year "[^0-9]")
+ (dayname "\\W"))
+
+Notice the use of `backup' in the third pattern, because it needs to
+match part of a word beyond the date itself to distinguish it from the
+fourth pattern.
+
+\1f
+File: xemacs.info, Node: Hebrew/Islamic Entries, Next: Fancy Diary Display, Prev: Diary Customizing, Up: Calendar Customization
+
+Hebrew- and Islamic-Date Diary Entries
+......................................
+
+ Your diary file can have entries based on Hebrew or Islamic dates, as
+well as entries based on the world-standard Gregorian calendar.
+However, because recognition of such entries is time-consuming and most
+people don't use them, you must explicitly enable their use. If you
+want the diary to recognize Hebrew-date diary entries, for example, you
+must do this:
+
+ (add-hook 'nongregorian-diary-listing-hook 'list-hebrew-diary-entries)
+ (add-hook 'nongregorian-diary-marking-hook 'mark-hebrew-diary-entries)
+
+If you want Islamic-date entries, do this:
+
+ (add-hook 'nongregorian-diary-listing-hook 'list-islamic-diary-entries)
+ (add-hook 'nongregorian-diary-marking-hook 'mark-islamic-diary-entries)
+
+ Hebrew- and Islamic-date diary entries have the same formats as
+Gregorian-date diary entries, except that `H' precedes a Hebrew date
+and `I' precedes an Islamic date. Moreover, because the Hebrew and
+Islamic month names are not uniquely specified by the first three
+letters, you may not abbreviate them. For example, a diary entry for
+the Hebrew date Heshvan 25 could look like this:
+
+ HHeshvan 25 Happy Hebrew birthday!
+
+and would appear in the diary for any date that corresponds to Heshvan
+25 on the Hebrew calendar. And here is Islamic-date diary entry that
+matches Dhu al-Qada 25:
+
+ IDhu al-Qada 25 Happy Islamic birthday!
+
+and would appear in the diary for any date that corresponds to Dhu
+al-Qada 25 on the Islamic calendar.
+
+ As with Gregorian-date diary entries, Hebrew- and Islamic-date
+entries are nonmarking if they are preceded with an ampersand (`&').
+
+ Here is a table of commands used in the calendar to create diary
+entries that match the selected date and other dates that are similar
+in the Hebrew or Islamic calendar:
+
+`i h d'
+ Add a diary entry for the Hebrew date corresponding to the
+ selected date (`insert-hebrew-diary-entry').
+
+`i h m'
+ Add a diary entry for the day of the Hebrew month corresponding to
+ the selected date (`insert-monthly-hebrew-diary-entry'). This
+ diary entry matches any date that has the same Hebrew
+ day-within-month as the selected date.
+
+`i h y'
+ Add a diary entry for the day of the Hebrew year corresponding to
+ the selected date (`insert-yearly-hebrew-diary-entry'). This diary
+ entry matches any date which has the same Hebrew month and
+ day-within-month as the selected date.
+
+`i i d'
+ Add a diary entry for the Islamic date corresponding to the
+ selected date (`insert-islamic-diary-entry').
+
+`i i m'
+ Add a diary entry for the day of the Islamic month corresponding
+ to the selected date (`insert-monthly-islamic-diary-entry').
+
+`i i y'
+ Add a diary entry for the day of the Islamic year corresponding to
+ the selected date (`insert-yearly-islamic-diary-entry').
+
+ These commands work much like the corresponding commands for ordinary
+diary entries: they apply to the date that point is on in the calendar
+window, and what they do is insert just the date portion of a diary
+entry at the end of your diary file. You must then insert the rest of
+the diary entry.
+
+\1f
+File: xemacs.info, Node: Fancy Diary Display, Next: Included Diary Files, Prev: Hebrew/Islamic Entries, Up: Calendar Customization
+
+Fancy Diary Display
+...................
+
+ Diary display works by preparing the diary buffer and then running
+the hook `diary-display-hook'. The default value of this hook
+(`simple-diary-display') hides the irrelevant diary entries and then
+displays the buffer. However, if you specify the hook as follows,
+
+ (add-hook 'diary-display-hook 'fancy-diary-display)
+
+this enables fancy diary display. It displays diary entries and
+holidays by copying them into a special buffer that exists only for the
+sake of display. Copying to a separate buffer provides an opportunity
+to change the displayed text to make it prettier--for example, to sort
+the entries by the dates they apply to.
+
+ As with simple diary display, you can print a hard copy of the buffer
+with `print-diary-entries'. To print a hard copy of a day-by-day diary
+for a week by positioning point on Sunday of that week, type `7 d' and
+then do `M-x print-diary-entries'. As usual, the inclusion of the
+holidays slows down the display slightly; you can speed things up by
+setting the variable `holidays-in-diary-buffer' to `nil'.
+
+ Ordinarily, the fancy diary buffer does not show days for which
+there are no diary entries, even if that day is a holiday. If you want
+such days to be shown in the fancy diary buffer, set the variable
+`diary-list-include-blanks' to `t'.
+
+ If you use the fancy diary display, you can use the normal hook
+`list-diary-entries-hook' to sort each day's diary entries by their
+time of day. Add this line to your init file:
+
+ (add-hook 'list-diary-entries-hook 'sort-diary-entries t)
+
+ *Note Init File::.
+
+For each day, this sorts diary entries that begin with a recognizable
+time of day according to their times. Diary entries without times come
+first within each day.
+
+\1f
+File: xemacs.info, Node: Included Diary Files, Next: Sexp Diary Entries, Prev: Fancy Diary Display, Up: Calendar Customization
+
+Included Diary Files
+....................
+
+ Fancy diary display also has the ability to process included diary
+files. This permits a group of people to share a diary file for events
+that apply to all of them. Lines in the diary file of this form:
+
+ #include "FILENAME"
+
+includes the diary entries from the file FILENAME in the fancy diary
+buffer. The include mechanism is recursive, so that included files can
+include other files, and so on; you must be careful not to have a cycle
+of inclusions, of course. Here is how to enable the include facility:
+
+ (add-hook 'list-diary-entries-hook 'include-other-diary-files)
+ (add-hook 'mark-diary-entries-hook 'mark-included-diary-files)
+
+ The include mechanism works only with the fancy diary display,
+because ordinary diary display shows the entries directly from your
+diary file.
+
+\1f
+File: xemacs.info, Node: Sexp Diary Entries, Next: Appt Customizing, Prev: Included Diary Files, Up: Calendar Customization
+
+Sexp Entries and the Fancy Diary Display
+........................................
+
+ Sexp diary entries allow you to do more than just have complicated
+conditions under which a diary entry applies. If you use the fancy
+diary display, sexp entries can generate the text of the entry depending
+on the date itself. For example, an anniversary diary entry can insert
+the number of years since the anniversary date into the text of the
+diary entry. Thus the `%d' in this dairy entry:
+
+ %%(diary-anniversary 10 31 1948) Arthur's birthday (%d years old)
+
+gets replaced by the age, so on October 31, 1990 the entry appears in
+the fancy diary buffer like this:
+
+ Arthur's birthday (42 years old)
+
+If the diary file instead contains this entry:
+
+ %%(diary-anniversary 10 31 1948) Arthur's %d%s birthday
+
+the entry in the fancy diary buffer for October 31, 1990 appears like
+this:
+
+ Arthur's 42nd birthday
+
+ Similarly, cyclic diary entries can interpolate the number of
+repetitions that have occurred:
+
+ %%(diary-cyclic 50 1 1 1990) Renew medication (%d%s time)
+
+looks like this:
+
+ Renew medication (5th time)
+
+in the fancy diary display on September 8, 1990.
+
+ The generality of sexp diary entries lets you specify any diary entry
+that you can describe algorithmically. A sexp diary entry contains an
+expression that computes whether the entry applies to any given date.
+If its value is non-`nil', the entry applies to that date; otherwise,
+it does not. The expression can use the variable `date' to find the
+date being considered; its value is a list (MONTH DAY YEAR) that refers
+to the Gregorian calendar.
+
+ Suppose you get paid on the 21st of the month if it is a weekday, and
+on the Friday before if the 21st is on a weekend. Here is how to write
+a sexp diary entry that matches those dates:
+
+ &%%(let ((dayname (calendar-day-of-week date))
+ (day (car (cdr date))))
+ (or (and (= day 21) (memq dayname '(1 2 3 4 5)))
+ (and (memq day '(19 20)) (= dayname 5)))
+ ) Pay check deposited
+
+applies to just those dates. This example illustrates how the sexp can
+depend on the variable `date'; this variable is a list (MONTH DAY YEAR)
+that gives the Gregorian date for which the diary entries are being
+found. If the value of the expression is `t', the entry applies to
+that date. If the expression evaluates to `nil', the entry does _not_
+apply to that date.
+
+ The following sexp diary entries take advantage of the ability (in
+the fancy diary display) to concoct diary entries whose text varies
+based on the date:
+
+`%%(diary-sunrise-sunset)'
+ Make a diary entry for the local times of today's sunrise and
+ sunset.
+
+`%%(diary-phases-of-moon)'
+ Make a diary entry for the phases (quarters) of the moon.
+
+`%%(diary-day-of-year)'
+ Make a diary entry with today's day number in the current year and
+ the number of days remaining in the current year.
+
+`%%(diary-iso-date)'
+ Make a diary entry with today's equivalent ISO commercial date.
+
+`%%(diary-julian-date)'
+ Make a diary entry with today's equivalent date on the Julian
+ calendar.
+
+`%%(diary-astro-day-number)'
+ Make a diary entry with today's equivalent astronomical (Julian)
+ day number.
+
+`%%(diary-hebrew-date)'
+ Make a diary entry with today's equivalent date on the Hebrew
+ calendar.
+
+`%%(diary-islamic-date)'
+ Make a diary entry with today's equivalent date on the Islamic
+ calendar.
+
+`%%(diary-french-date)'
+ Make a diary entry with today's equivalent date on the French
+ Revolutionary calendar.
+
+`%%(diary-mayan-date)'
+ Make a diary entry with today's equivalent date on the Mayan
+ calendar.
+
+Thus including the diary entry
+
+ &%%(diary-hebrew-date)
+
+causes every day's diary display to contain the equivalent date on the
+Hebrew calendar, if you are using the fancy diary display. (With simple
+diary display, the line `&%%(diary-hebrew-date)' appears in the diary
+for any date, but does nothing particularly useful.)
+
+ These functions can be used to construct sexp diary entries based on
+the Hebrew calendar in certain standard ways:
+
+`%%(diary-rosh-hodesh)'
+ Make a diary entry that tells the occurrence and ritual
+ announcement of each new Hebrew month.
+
+`%%(diary-parasha)'
+ Make a Saturday diary entry that tells the weekly synagogue
+ scripture reading.
+
+`%%(diary-sabbath-candles)'
+ Make a Friday diary entry that tells the _local time_ of Sabbath
+ candle lighting.
+
+`%%(diary-omer)'
+ Make a diary entry that gives the omer count, when appropriate.
+
+`%%(diary-yahrzeit MONTH DAY YEAR) NAME'
+ Make a diary entry marking the anniversary of a date of death.
+ The date is the _Gregorian_ (civil) date of death. The diary
+ entry appears on the proper Hebrew calendar anniversary and on the
+ day before. (In the European style, the order of the parameters
+ is changed to DAY, MONTH, YEAR.)
+
+\1f
+File: xemacs.info, Node: Appt Customizing, Prev: Sexp Diary Entries, Up: Calendar Customization
+
+Customizing Appointment Reminders
+.................................
+
+ You can specify exactly how Emacs reminds you of an appointment, and
+how far in advance it begins doing so, by setting these variables:
+
+`appt-message-warning-time'
+ The time in minutes before an appointment that the reminder
+ begins. The default is 10 minutes.
+
+`appt-audible'
+ If this is `t' (the default), Emacs rings the terminal bell for
+ appointment reminders.
+
+`appt-visible'
+ If this is `t' (the default), Emacs displays the appointment
+ message in echo area.
+
+`appt-display-mode-line'
+ If this is `t' (the default), Emacs displays the number of minutes
+ to the appointment on the mode line.
+
+`appt-msg-window'
+ If this is `t' (the default), Emacs displays the appointment
+ message in another window.
+
+`appt-display-duration'
+ The number of seconds an appointment message is displayed. The
+ default is 5 seconds.
+
+\1f
+File: xemacs.info, Node: Sorting, Next: Shell, Prev: Calendar/Diary, Up: Top
+
+Sorting Text
+============
+
+ XEmacs provides several commands for sorting text in a buffer. All
+operate on the contents of the region (the text between point and the
+mark). They divide the text of the region into many "sort records",
+identify a "sort key" for each record, and then reorder the records
+using the order determined by the sort keys. The records are ordered so
+that their keys are in alphabetical order, or, for numerical sorting, in
+numerical order. In alphabetical sorting, all upper-case letters `A'
+through `Z' come before lower-case `a', in accordance with the ASCII
+character sequence.
+
+ The sort commands differ in how they divide the text into sort
+records and in which part of each record they use as the sort key.
+Most of the commands make each line a separate sort record, but some
+commands use paragraphs or pages as sort records. Most of the sort
+commands use each entire sort record as its own sort key, but some use
+only a portion of the record as the sort key.
+
+`M-x sort-lines'
+ Divide the region into lines and sort by comparing the entire text
+ of a line. A prefix argument means sort in descending order.
+
+`M-x sort-paragraphs'
+ Divide the region into paragraphs and sort by comparing the entire
+ text of a paragraph (except for leading blank lines). A prefix
+ argument means sort in descending order.
+
+`M-x sort-pages'
+ Divide the region into pages and sort by comparing the entire text
+ of a page (except for leading blank lines). A prefix argument
+ means sort in descending order.
+
+`M-x sort-fields'
+ Divide the region into lines and sort by comparing the contents of
+ one field in each line. Fields are defined as separated by
+ whitespace, so the first run of consecutive non-whitespace
+ characters in a line constitutes field 1, the second such run
+ constitutes field 2, etc.
+
+ You specify which field to sort by with a numeric argument: 1 to
+ sort by field 1, etc. A negative argument means sort in descending
+ order. Thus, minus 2 means sort by field 2 in reverse-alphabetical
+ order.
+
+`M-x sort-numeric-fields'
+ Like `M-x sort-fields', except the specified field is converted to
+ a number for each line and the numbers are compared. `10' comes
+ before `2' when considered as text, but after it when considered
+ as a number.
+
+`M-x sort-columns'
+ Like `M-x sort-fields', except that the text within each line used
+ for comparison comes from a fixed range of columns. An explanation
+ is given below.
+
+ For example, if the buffer contains:
+
+ On systems where clash detection (locking of files being edited) is
+ implemented, XEmacs also checks the first time you modify a buffer
+ whether the file has changed on disk since it was last visited or
+ saved. If it has, you are asked to confirm that you want to change
+ the buffer.
+
+then if you apply `M-x sort-lines' to the entire buffer you get:
+
+ On systems where clash detection (locking of files being edited) is
+ implemented, XEmacs also checks the first time you modify a buffer
+ saved. If it has, you are asked to confirm that you want to change
+ the buffer.
+ whether the file has changed on disk since it was last visited or
+
+where the upper case `O' comes before all lower case letters. If you
+apply instead `C-u 2 M-x sort-fields' you get:
+
+ saved. If it has, you are asked to confirm that you want to change
+ implemented, XEmacs also checks the first time you modify a buffer
+ the buffer.
+ On systems where clash detection (locking of files being edited) is
+ whether the file has changed on disk since it was last visited or
+
+where the sort keys were `If', `XEmacs', `buffer', `systems', and `the'.
+
+ `M-x sort-columns' requires more explanation. You specify the
+columns by putting point at one of the columns and the mark at the other
+column. Because this means you cannot put point or the mark at the
+beginning of the first line to sort, this command uses an unusual
+definition of `region': all of the line point is in is considered part
+of the region, and so is all of the line the mark is in.
+
+ For example, to sort a table by information found in columns 10 to
+15, you could put the mark on column 10 in the first line of the table,
+and point on column 15 in the last line of the table, and then use this
+command. Or you could put the mark on column 15 in the first line and
+point on column 10 in the last line.
+
+ This can be thought of as sorting the rectangle specified by point
+and the mark, except that the text on each line to the left or right of
+the rectangle moves along with the text inside the rectangle. *Note
+Rectangles::.
+
+\1f
+File: xemacs.info, Node: Shell, Next: Narrowing, Prev: Sorting, Up: Top
+
+Running Shell Commands from XEmacs
+==================================
+
+ XEmacs has commands for passing single command lines to inferior
+shell processes; it can also run a shell interactively with input and
+output to an XEmacs buffer `*shell*'.
+
+`M-!'
+ Run a specified shell command line and display the output
+ (`shell-command').
+
+`M-|'
+ Run a specified shell command line with region contents as input;
+ optionally replace the region with the output
+ (`shell-command-on-region').
+
+`M-x shell'
+ Run a subshell with input and output through an XEmacs buffer.
+ You can then give commands interactively.
+
+`M-x term'
+ Run a subshell with input and output through an XEmacs buffer.
+ You can then give commands interactively. Full terminal emulation
+ is available.
+
+* Menu:
+
+* Single Shell:: How to run one shell command and return.
+* Interactive Shell:: Permanent shell taking input via XEmacs.
+* Shell Mode:: Special XEmacs commands used with permanent shell.
+* Terminal emulator:: An XEmacs window as a terminal emulator.
+* Term Mode:: Special XEmacs commands used in Term mode.
+* Paging in Term:: Paging in the terminal emulator.
+
+\1f
+File: xemacs.info, Node: Single Shell, Next: Interactive Shell, Prev: Shell, Up: Shell
+
+Single Shell Commands
+---------------------
+
+ `M-!' (`shell-command') reads a line of text using the minibuffer
+and creates an inferior shell to execute the line as a command.
+Standard input from the command comes from the null device. If the
+shell command produces any output, the output goes to an XEmacs buffer
+named `*Shell Command Output*', which is displayed in another window
+but not selected. A numeric argument, as in `M-1 M-!', directs this
+command to insert any output into the current buffer. In that case,
+point is left before the output and the mark is set after the output.
+
+ `M-|' (`shell-command-on-region') is like `M-!' but passes the
+contents of the region as input to the shell command, instead of no
+input. If a numeric argument is used to direct output to the current
+buffer, then the old region is deleted first and the output replaces it
+as the contents of the region.
+
+ Both `M-!' and `M-|' use `shell-file-name' to specify the shell to
+use. This variable is initialized based on your `SHELL' environment
+variable when you start XEmacs. If the file name does not specify a
+directory, the directories in the list `exec-path' are searched; this
+list is initialized based on the `PATH' environment variable when you
+start XEmacs. You can override either or both of these default
+initializations in your init file. *Note Init File::.
+
+ When you use `M-!' and `M-|', XEmacs has to wait until the shell
+command completes. You can quit with `C-g'; that terminates the shell
+command.
+
+\1f
File: xemacs.info, Node: Interactive Shell, Next: Shell Mode, Prev: Single Shell, Up: Shell
Interactive Inferior Shell
* X Resources:: X resources controlling various aspects of the
behavior of XEmacs.
-\1f
-File: xemacs.info, Node: Minor Modes, Next: Variables, Up: Customization
-
-Minor Modes
-===========
-
- Minor modes are options which you can use or not. For example, Auto
-Fill mode is a minor mode in which <SPC> breaks lines between words as
-you type. All the minor modes are independent of each other and of the
-selected major mode. Most minor modes inform you in the mode line when
-they are on; for example, `Fill' in the mode line means that Auto Fill
-mode is on.
-
- Append `-mode' to the name of a minor mode to get the name of a
-command function that turns the mode on or off. Thus, the command to
-enable or disable Auto Fill mode is called `M-x auto-fill-mode'. These
-commands are usually invoked with `M-x', but you can bind keys to them
-if you wish. With no argument, the function turns the mode on if it was
-off and off if it was on. This is known as "toggling". A positive
-argument always turns the mode on, and an explicit zero argument or a
-negative argument always turns it off.
-
- Auto Fill mode allows you to enter filled text without breaking lines
-explicitly. Emacs inserts newlines as necessary to prevent lines from
-becoming too long. *Note Filling::.
-
- Overwrite mode causes ordinary printing characters to replace
-existing text instead of moving it to the right. For example, if point
-is in front of the `B' in `FOOBAR', and you type a `G' in Overwrite
-mode, it changes to `FOOGAR', instead of `FOOGBAR'.
-
- Abbrev mode allows you to define abbreviations that automatically
-expand as you type them. For example, `amd' might expand to `abbrev
-mode'. *Note Abbrevs::, for full information.
-
-\1f
-File: xemacs.info, Node: Variables, Next: Keyboard Macros, Prev: Minor Modes, Up: Customization
-
-Variables
-=========
-
- A "variable" is a Lisp symbol which has a value. Variable names can
-contain any characters, but by convention they are words separated by
-hyphens. A variable can also have a documentation string, which
-describes what kind of value it should have and how the value will be
-used.
-
- Lisp allows any variable to have any kind of value, but most
-variables that Emacs uses require a value of a certain type. Often the
-value has to be a string or a number. Sometimes we say that a certain
-feature is turned on if a variable is "non-`nil'," meaning that if the
-variable's value is `nil', the feature is off, but the feature is on
-for any other value. The conventional value to turn on the
-feature--since you have to pick one particular value when you set the
-variable--is `t'.
-
- Emacs uses many Lisp variables for internal recordkeeping, as any
-Lisp program must, but the most interesting variables for you are the
-ones that exist for the sake of customization. Emacs does not
-(usually) change the values of these variables; instead, you set the
-values, and thereby alter and control the behavior of certain Emacs
-commands. These variables are called "options". Most options are
-documented in this manual and appear in the Variable Index (*note
-Variable Index::).
-
- One example of a variable which is an option is `fill-column', which
-specifies the position of the right margin (as a number of characters
-from the left margin) to be used by the fill commands (*note Filling::).
-
-* Menu:
-
-* Examining:: Examining or setting one variable's value.
-* Easy Customization:: Convenient and easy customization of variables.
-* Edit Options:: Examining or editing list of all variables' values.
-* Locals:: Per-buffer values of variables.
-* File Variables:: How files can specify variable values.
-
-\1f
-File: xemacs.info, Node: Examining, Next: Easy Customization, Up: Variables
-
-Examining and Setting Variables
--------------------------------
-
-`C-h v'
-`M-x describe-variable'
- Print the value and documentation of a variable.
-
-`M-x set-variable'
- Change the value of a variable.
-
- To examine the value of a single variable, use `C-h v'
-(`describe-variable'), which reads a variable name using the
-minibuffer, with completion. It prints both the value and the
-documentation of the variable.
-
- C-h v fill-column <RET>
-
-prints something like:
-
- fill-column's value is 75
-
- Documentation:
- *Column beyond which automatic line-wrapping should happen.
- Automatically becomes local when set in any fashion.
-
-The star at the beginning of the documentation indicates that this
-variable is an option. `C-h v' is not restricted to options; it allows
-any variable name.
-
- If you know which option you want to set, you can use `M-x
-set-variable' to set it. This prompts for the variable name in the
-minibuffer (with completion), and then prompts for a Lisp expression
-for the new value using the minibuffer a second time. For example,
-
- M-x set-variable <RET> fill-column <RET> 75 <RET>
-
-sets `fill-column' to 75, as if you had executed the Lisp expression
-`(setq fill-column 75)'.
-
- Setting variables in this way, like all means of customizing Emacs
-except where explicitly stated, affects only the current Emacs session.
-
-\1f
-File: xemacs.info, Node: Easy Customization, Next: Edit Options, Prev: Examining, Up: Variables
-
-Easy Customization Interface
-----------------------------
-
- A convenient way to find the user option variables that you want to
-change, and then change them, is with `M-x customize'. This command
-creates a "customization buffer" with which you can browse through the
-Emacs user options in a logically organized structure, then edit and
-set their values. You can also use the customization buffer to save
-settings permanently. (Not all Emacs user options are included in this
-structure as of yet, but we are adding the rest.)
-
-* Menu:
-
-* Groups: Customization Groups.
- How options are classified in a structure.
-* Changing an Option:: How to edit a value and set an option.
-* Face Customization:: How to edit the attributes of a face.
-* Specific Customization:: Making a customization buffer for specific
- options, faces, or groups.
-
-\1f
-File: xemacs.info, Node: Customization Groups, Next: Changing an Option, Up: Easy Customization
-
-Customization Groups
-....................
-
- For customization purposes, user options are organized into "groups"
-to help you find them. Groups are collected into bigger groups, all
-the way up to a master group called `Emacs'.
-
- `M-x customize' creates a customization buffer that shows the
-top-level `Emacs' group and the second-level groups immediately under
-it. It looks like this, in part:
-
- /- Emacs group: ---------------------------------------------------\
- [State]: visible group members are all at standard settings.
- Customization of the One True Editor.
- See also [Manual].
-
- [Open] Editing group
- Basic text editing facilities.
-
- [Open] External group
- Interfacing to external utilities.
-
- MORE SECOND-LEVEL GROUPS
-
- \- Emacs group end ------------------------------------------------/
-
-This says that the buffer displays the contents of the `Emacs' group.
-The other groups are listed because they are its contents. But they
-are listed differently, without indentation and dashes, because _their_
-contents are not included. Each group has a single-line documentation
-string; the `Emacs' group also has a `[State]' line.
-
- Most of the text in the customization buffer is read-only, but it
-typically includes some "editable fields" that you can edit. There are
-also "active fields"; this means a field that does something when you
-"invoke" it. To invoke an active field, either click on it with
-`Mouse-1', or move point to it and type <RET>.
-
- For example, the phrase `[Open]' that appears in a second-level
-group is an active field. Invoking the `[Open]' field for a group
-opens up a new customization buffer, which shows that group and its
-contents. This field is a kind of hypertext link to another group.
-
- The `Emacs' group does not include any user options itself, but
-other groups do. By examining various groups, you will eventually find
-the options and faces that belong to the feature you are interested in
-customizing. Then you can use the customization buffer to set them.
-
- You can view the structure of customization groups on a larger scale
-with `M-x customize-browse'. This command creates a special kind of
-customization buffer which shows only the names of the groups (and
-options and faces), and their structure.
-
- In this buffer, you can show the contents of a group by invoking
-`[+]'. When the group contents are visible, this button changes to
-`[-]'; invoking that hides the group contents.
-
- Each group, option or face name in this buffer has an active field
-which says `[Group]', `[Option]' or `[Face]'. Invoking that active
-field creates an ordinary customization buffer showing just that group
-and its contents, just that option, or just that face. This is the way
-to set values in it.
-
-\1f
-File: xemacs.info, Node: Changing an Option, Next: Face Customization, Prev: Customization Groups, Up: Easy Customization
-
-Changing an Option
-..................
-
- Here is an example of what a user option looks like in the
-customization buffer:
-
- Kill Ring Max: [Hide] 30
- [State]: this option is unchanged from its standard setting.
- Maximum length of kill ring before oldest elements are thrown away.
-
- The text following `[Hide]', `30' in this case, indicates the
-current value of the option. If you see `[Show]' instead of `[Hide]',
-it means that the value is hidden; the customization buffer initially
-hides values that take up several lines. Invoke `[Show]' to show the
-value.
-
- The line after the option name indicates the "customization state"
-of the option: in the example above, it says you have not changed the
-option yet. The word `[State]' at the beginning of this line is
-active; you can get a menu of various operations by invoking it with
-`Mouse-1' or <RET>. These operations are essential for customizing the
-variable.
-
- The line after the `[State]' line displays the beginning of the
-option's documentation string. If there are more lines of
-documentation, this line ends with `[More]'; invoke this to show the
-full documentation string.
-
- To enter a new value for `Kill Ring Max', move point to the value
-and edit it textually. For example, you can type `M-d', then insert
-another number.
-
- When you begin to alter the text, you will see the `[State]' line
-change to say that you have edited the value:
-
- [State]: you have edited the value as text, but not set the option.
-
- Editing the value does not actually set the option variable. To do
-that, you must "set" the option. To do this, invoke the word `[State]'
-and choose `Set for Current Session'.
-
- The state of the option changes visibly when you set it:
-
- [State]: you have set this option, but not saved it for future sessions.
-
- You don't have to worry about specifying a value that is not valid;
-setting the option checks for validity and will not really install an
-unacceptable value.
-
- While editing a value or field that is a file name, directory name,
-command name, or anything else for which completion is defined, you can
-type `M-<TAB>' (`widget-complete') to do completion.
-
- Some options have a small fixed set of possible legitimate values.
-These options don't let you edit the value textually. Instead, an
-active field `[Value Menu]' appears before the value; invoke this field
-to edit the value. For a boolean "on or off" value, the active field
-says `[Toggle]', and it changes to the other value. `[Value Menu]' and
-`[Toggle]' edit the buffer; the changes take effect when you use the
-`Set for Current Session' operation.
-
- Some options have values with complex structure. For example, the
-value of `load-path' is a list of directories. Here is how it appears
-in the customization buffer:
-
- Load Path:
- [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/site-lisp
- [INS] [DEL] [Current dir?]: /usr/local/share/emacs/site-lisp
- [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/leim
- [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/lisp
- [INS] [DEL] [Current dir?]: /build/emacs/e19/lisp
- [INS] [DEL] [Current dir?]: /build/emacs/e19/lisp/gnus
- [INS]
- [State]: this item has been changed outside the customization buffer.
- List of directories to search for files to load....
-
-Each directory in the list appears on a separate line, and each line has
-several editable or active fields.
-
- You can edit any of the directory names. To delete a directory from
-the list, invoke `[DEL]' on that line. To insert a new directory in
-the list, invoke `[INS]' at the point where you want to insert it.
-
- You can also invoke `[Current dir?]' to switch between including a
-specific named directory in the path, and including `nil' in the path.
-(`nil' in a search path means "try the current directory.")
-
- Two special commands, <TAB> and `S-<TAB>', are useful for moving
-through the customization buffer. <TAB> (`widget-forward') moves
-forward to the next active or editable field; `S-<TAB>'
-(`widget-backward') moves backward to the previous active or editable
-field.
-
- Typing <RET> on an editable field also moves forward, just like
-<TAB>. The reason for this is that people have a tendency to type
-<RET> when they are finished editing a field. If you have occasion to
-insert a newline in an editable field, use `C-o' or `C-q C-j',
-
- Setting the option changes its value in the current Emacs session;
-"saving" the value changes it for future sessions as well. This works
-by writing code into your init file so as to set the option variable
-again each time you start Emacs. *Note Init File::. To save the
-option, invoke `[State]' and select the `Save for Future Sessions'
-operation.
-
- You can also restore the option to its standard value by invoking
-`[State]' and selecting the `Reset' operation. There are actually
-three reset operations:
-
-`Reset to Current'
- If you have made some modifications and not yet set the option,
- this restores the text in the customization buffer to match the
- actual value.
-
-`Reset to Saved'
- This restores the value of the option to the last saved value, and
- updates the text accordingly.
-
-`Reset to Standard Settings'
- This sets the option to its standard value, and updates the text
- accordingly. This also eliminates any saved value for the option,
- so that you will get the standard value in future Emacs sessions.
-
- The state of a group indicates whether anything in that group has
-been edited, set or saved. You can select `Set for Current Session',
-`Save for Future Sessions' and the various kinds of `Reset' operation
-for the group; these operations on the group apply to all options in
-the group and its subgroups.
-
- Near the top of the customization buffer there are two lines
-containing several active fields:
-
- [Set] [Save] [Reset] [Done]
-
-Invoking `[Done]' buries this customization buffer. Each of the other
-fields performs an operation--set, save or reset--on each of the items
-in the buffer that could meaningfully be set, saved or reset.
-
-\1f
-File: xemacs.info, Node: Face Customization, Next: Specific Customization, Prev: Changing an Option, Up: Easy Customization
-
-Customizing Faces
-.................
-
- In addition to user options, some customization groups also include
-faces. When you show the contents of a group, both the user options and
-the faces in the group appear in the customization buffer. Here is an
-example of how a face looks:
-
- Custom Changed Face: (sample)
- [State]: this face is unchanged from its standard setting.
- Face used when the customize item has been changed.
- Parent groups: [Custom Magic Faces]
- Attributes: [ ] Bold: [Toggle] off (nil)
- [ ] Italic: [Toggle] off (nil)
- [ ] Underline: [Toggle] off (nil)
- [ ] Foreground: white (sample)
- [ ] Background: blue (sample)
- [ ] Inverse: [Toggle] off (nil)
- [ ] Stipple:
- [ ] Font Family:
- [ ] Size:
- [ ] Strikethru: off
-
- Each face attribute has its own line. The `[X]' field before the
-attribute name indicates whether the attribute is "enabled"; `X' means
-that it is. You can enable or disable the attribute by invoking that
-field. When the attribute is enabled, you can change the attribute
-value in the usual ways.
-
- Setting, saving and resetting a face work like the same operations
-for options (*note Changing an Option::).
-
- A face can specify different appearances for different types of
-display. For example, a face can make text red on a color display, but
-use a bold font on a monochrome display. To specify multiple
-appearances for a face, select `Show Display Types' in the menu you get
-from invoking `[State]'.
-
-\1f
-File: xemacs.info, Node: Specific Customization, Prev: Face Customization, Up: Easy Customization
-
-Customizing Specific Items
-..........................
-
- Instead of finding the options you want to change by moving down
-through the structure of groups, you can specify the particular option,
-face or group that you want to customize.
-
-`M-x customize-option <RET> OPTION <RET>'
- Set up a customization buffer with just one option, OPTION.
-
-`M-x customize-face <RET> FACE <RET>'
- Set up a customization buffer with just one face, FACE.
-
-`M-x customize-group <RET> GROUP <RET>'
- Set up a customization buffer with just one group, GROUP.
-
-`M-x customize-apropos <RET> REGEXP <RET>'
- Set up a customization buffer with all the options, faces and
- groups that match REGEXP.
-
-`M-x customize-saved'
- Set up a customization buffer containing all options and faces
- that you have saved with customization buffers.
-
-`M-x customize-customized'
- Set up a customization buffer containing all options and faces
- that you have customized but not saved.
-
- If you want to alter a particular user option variable with the
-customization buffer, and you know its name, you can use the command
-`M-x customize-option' and specify the option name. This sets up the
-customization buffer with just one option--the one that you asked for.
-Editing, setting and saving the value work as described above, but only
-for the specified option.
-
- Likewise, you can modify a specific face, chosen by name, using `M-x
-customize-face'.
-
- You can also set up the customization buffer with a specific group,
-using `M-x customize-group'. The immediate contents of the chosen
-group, including option variables, faces, and other groups, all appear
-as well. However, these subgroups' own contents start out hidden. You
-can show their contents in the usual way, by invoking `[Show]'.
-
- To control more precisely what to customize, you can use `M-x
-customize-apropos'. You specify a regular expression as argument; then
-all options, faces and groups whose names match this regular expression
-are set up in the customization buffer. If you specify an empty regular
-expression, this includes _all_ groups, options and faces in the
-customization buffer (but that takes a long time).
-
- If you change option values and then decide the change was a mistake,
-you can use two special commands to revisit your previous changes. Use
-`customize-saved' to look at the options and faces that you have saved.
-Use `M-x customize-customized' to look at the options and faces that
-you have set but not saved.
-
-\1f
-File: xemacs.info, Node: Edit Options, Next: Locals, Prev: Easy Customization, Up: Variables
-
-Editing Variable Values
------------------------
-
-`M-x list-options'
- Display a buffer listing names, values, and documentation of all
- options.
-
-`M-x edit-options'
- Change option values by editing a list of options.
-
- `M-x list-options' displays a list of all Emacs option variables in
-an Emacs buffer named `*List Options*'. Each option is shown with its
-documentation and its current value. Here is what a portion of it might
-look like:
-
- ;; exec-path:
- ("." "/usr/local/bin" "/usr/ucb" "/bin" "/usr/bin" "/u2/emacs/etc")
- *List of directories to search programs to run in subprocesses.
- Each element is a string (directory name)
- or nil (try the default directory).
- ;;
- ;; fill-column:
- 75
- *Column beyond which automatic line-wrapping should happen.
- Automatically becomes local when set in any fashion.
- ;;
-
- `M-x edit-options' goes one step further and immediately selects the
-`*List Options*' buffer; this buffer uses the major mode Options mode,
-which provides commands that allow you to point at an option and change
-its value:
-
-`s'
- Set the variable point is in or near to a new value read using the
- minibuffer.
-
-`x'
- Toggle the variable point is in or near: if the value was `nil',
- it becomes `t'; otherwise it becomes `nil'.
-
-`1'
- Set the variable point is in or near to `t'.
-
-`0'
- Set the variable point is in or near to `nil'.
-
-`n'
-`p'
- Move to the next or previous variable.
-
-\1f
-File: xemacs.info, Node: Locals, Next: File Variables, Prev: Edit Options, Up: Variables
-
-Local Variables
----------------
-
-`M-x make-local-variable'
- Make a variable have a local value in the current buffer.
-
-`M-x kill-local-variable'
- Make a variable use its global value in the current buffer.
-
-`M-x make-variable-buffer-local'
- Mark a variable so that setting it will make it local to the
- buffer that is current at that time.
-
- You can make any variable "local" to a specific Emacs buffer. This
-means that the variable's value in that buffer is independent of its
-value in other buffers. A few variables are always local in every
-buffer. All other Emacs variables have a "global" value which is in
-effect in all buffers that have not made the variable local.
-
- Major modes always make the variables they set local to the buffer.
-This is why changing major modes in one buffer has no effect on other
-buffers.
-
- `M-x make-local-variable' reads the name of a variable and makes it
-local to the current buffer. Further changes in this buffer will not
-affect others, and changes in the global value will not affect this
-buffer.
-
- `M-x make-variable-buffer-local' reads the name of a variable and
-changes the future behavior of the variable so that it automatically
-becomes local when it is set. More precisely, once you have marked a
-variable in this way, the usual ways of setting the variable will
-automatically invoke `make-local-variable' first. We call such
-variables "per-buffer" variables.
-
- Some important variables have been marked per-buffer already. They
-include `abbrev-mode', `auto-fill-function', `case-fold-search',
-`comment-column', `ctl-arrow', `fill-column', `fill-prefix',
-`indent-tabs-mode', `left-margin',
-`mode-line-format', `overwrite-mode', `selective-display-ellipses',
-`selective-display', `tab-width', and `truncate-lines'. Some other
-variables are always local in every buffer, but they are used for
-internal purposes.
-
- Note: the variable `auto-fill-function' was formerly named
-`auto-fill-hook'.
-
- If you want a variable to cease to be local to the current buffer,
-call `M-x kill-local-variable' and provide the name of a variable to
-the prompt. The global value of the variable is again in effect in
-this buffer. Setting the major mode kills all the local variables of
-the buffer.
-
- To set the global value of a variable, regardless of whether the
-variable has a local value in the current buffer, you can use the Lisp
-function `setq-default'. It works like `setq'. If there is a local
-value in the current buffer, the local value is not affected by
-`setq-default'; thus, the new global value may not be visible until you
-switch to another buffer, as in the case of:
-
- (setq-default fill-column 75)
-
-`setq-default' is the only way to set the global value of a variable
-that has been marked with `make-variable-buffer-local'.
-
- Programs can look at a variable's default value with `default-value'.
-This function takes a symbol as an argument and returns its default
-value. The argument is evaluated; usually you must quote it
-explicitly, as in the case of:
-
- (default-value 'fill-column)
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Minor Modes, Next: Variables, Up: Customization
+
+Minor Modes
+===========
+
+ Minor modes are options which you can use or not. For example, Auto
+Fill mode is a minor mode in which <SPC> breaks lines between words as
+you type. All the minor modes are independent of each other and of the
+selected major mode. Most minor modes inform you in the mode line when
+they are on; for example, `Fill' in the mode line means that Auto Fill
+mode is on.
+
+ Append `-mode' to the name of a minor mode to get the name of a
+command function that turns the mode on or off. Thus, the command to
+enable or disable Auto Fill mode is called `M-x auto-fill-mode'. These
+commands are usually invoked with `M-x', but you can bind keys to them
+if you wish. With no argument, the function turns the mode on if it was
+off and off if it was on. This is known as "toggling". A positive
+argument always turns the mode on, and an explicit zero argument or a
+negative argument always turns it off.
+
+ Auto Fill mode allows you to enter filled text without breaking lines
+explicitly. Emacs inserts newlines as necessary to prevent lines from
+becoming too long. *Note Filling::.
+
+ Overwrite mode causes ordinary printing characters to replace
+existing text instead of moving it to the right. For example, if point
+is in front of the `B' in `FOOBAR', and you type a `G' in Overwrite
+mode, it changes to `FOOGAR', instead of `FOOGBAR'.
+
+ Abbrev mode allows you to define abbreviations that automatically
+expand as you type them. For example, `amd' might expand to `abbrev
+mode'. *Note Abbrevs::, for full information.
+
+\1f
+File: xemacs.info, Node: Variables, Next: Keyboard Macros, Prev: Minor Modes, Up: Customization
+
+Variables
+=========
+
+ A "variable" is a Lisp symbol which has a value. Variable names can
+contain any characters, but by convention they are words separated by
+hyphens. A variable can also have a documentation string, which
+describes what kind of value it should have and how the value will be
+used.
+
+ Lisp allows any variable to have any kind of value, but most
+variables that Emacs uses require a value of a certain type. Often the
+value has to be a string or a number. Sometimes we say that a certain
+feature is turned on if a variable is "non-`nil'," meaning that if the
+variable's value is `nil', the feature is off, but the feature is on
+for any other value. The conventional value to turn on the
+feature--since you have to pick one particular value when you set the
+variable--is `t'.
+
+ Emacs uses many Lisp variables for internal recordkeeping, as any
+Lisp program must, but the most interesting variables for you are the
+ones that exist for the sake of customization. Emacs does not
+(usually) change the values of these variables; instead, you set the
+values, and thereby alter and control the behavior of certain Emacs
+commands. These variables are called "options". Most options are
+documented in this manual and appear in the Variable Index (*note
+Variable Index::).
+
+ One example of a variable which is an option is `fill-column', which
+specifies the position of the right margin (as a number of characters
+from the left margin) to be used by the fill commands (*note Filling::).
+
+* Menu:
+
+* Examining:: Examining or setting one variable's value.
+* Easy Customization:: Convenient and easy customization of variables.
+* Edit Options:: Examining or editing list of all variables' values.
+* Locals:: Per-buffer values of variables.
+* File Variables:: How files can specify variable values.
+
+\1f
+File: xemacs.info, Node: Examining, Next: Easy Customization, Up: Variables
+
+Examining and Setting Variables
+-------------------------------
+
+`C-h v'
+`M-x describe-variable'
+ Print the value and documentation of a variable.
+
+`M-x set-variable'
+ Change the value of a variable.
+
+ To examine the value of a single variable, use `C-h v'
+(`describe-variable'), which reads a variable name using the
+minibuffer, with completion. It prints both the value and the
+documentation of the variable.
+
+ C-h v fill-column <RET>
+
+prints something like:
+
+ fill-column's value is 75
+
+ Documentation:
+ *Column beyond which automatic line-wrapping should happen.
+ Automatically becomes local when set in any fashion.
+
+The star at the beginning of the documentation indicates that this
+variable is an option. `C-h v' is not restricted to options; it allows
+any variable name.
+
+ If you know which option you want to set, you can use `M-x
+set-variable' to set it. This prompts for the variable name in the
+minibuffer (with completion), and then prompts for a Lisp expression
+for the new value using the minibuffer a second time. For example,
+
+ M-x set-variable <RET> fill-column <RET> 75 <RET>
+
+sets `fill-column' to 75, as if you had executed the Lisp expression
+`(setq fill-column 75)'.
+
+ Setting variables in this way, like all means of customizing Emacs
+except where explicitly stated, affects only the current Emacs session.
+
+\1f
+File: xemacs.info, Node: Easy Customization, Next: Edit Options, Prev: Examining, Up: Variables
+
+Easy Customization Interface
+----------------------------
+
+ A convenient way to find the user option variables that you want to
+change, and then change them, is with `M-x customize'. This command
+creates a "customization buffer" with which you can browse through the
+Emacs user options in a logically organized structure, then edit and
+set their values. You can also use the customization buffer to save
+settings permanently. (Not all Emacs user options are included in this
+structure as of yet, but we are adding the rest.)
+
+* Menu:
+
+* Groups: Customization Groups.
+ How options are classified in a structure.
+* Changing an Option:: How to edit a value and set an option.
+* Face Customization:: How to edit the attributes of a face.
+* Specific Customization:: Making a customization buffer for specific
+ options, faces, or groups.
+
+\1f
+File: xemacs.info, Node: Customization Groups, Next: Changing an Option, Up: Easy Customization
+
+Customization Groups
+....................
+
+ For customization purposes, user options are organized into "groups"
+to help you find them. Groups are collected into bigger groups, all
+the way up to a master group called `Emacs'.
+
+ `M-x customize' creates a customization buffer that shows the
+top-level `Emacs' group and the second-level groups immediately under
+it. It looks like this, in part:
+
+ /- Emacs group: ---------------------------------------------------\
+ [State]: visible group members are all at standard settings.
+ Customization of the One True Editor.
+ See also [Manual].
+
+ [Open] Editing group
+ Basic text editing facilities.
+
+ [Open] External group
+ Interfacing to external utilities.
+
+ MORE SECOND-LEVEL GROUPS
+
+ \- Emacs group end ------------------------------------------------/
+
+This says that the buffer displays the contents of the `Emacs' group.
+The other groups are listed because they are its contents. But they
+are listed differently, without indentation and dashes, because _their_
+contents are not included. Each group has a single-line documentation
+string; the `Emacs' group also has a `[State]' line.
+
+ Most of the text in the customization buffer is read-only, but it
+typically includes some "editable fields" that you can edit. There are
+also "active fields"; this means a field that does something when you
+"invoke" it. To invoke an active field, either click on it with
+`Mouse-1', or move point to it and type <RET>.
+
+ For example, the phrase `[Open]' that appears in a second-level
+group is an active field. Invoking the `[Open]' field for a group
+opens up a new customization buffer, which shows that group and its
+contents. This field is a kind of hypertext link to another group.
+
+ The `Emacs' group does not include any user options itself, but
+other groups do. By examining various groups, you will eventually find
+the options and faces that belong to the feature you are interested in
+customizing. Then you can use the customization buffer to set them.
+
+ You can view the structure of customization groups on a larger scale
+with `M-x customize-browse'. This command creates a special kind of
+customization buffer which shows only the names of the groups (and
+options and faces), and their structure.
+
+ In this buffer, you can show the contents of a group by invoking
+`[+]'. When the group contents are visible, this button changes to
+`[-]'; invoking that hides the group contents.
+
+ Each group, option or face name in this buffer has an active field
+which says `[Group]', `[Option]' or `[Face]'. Invoking that active
+field creates an ordinary customization buffer showing just that group
+and its contents, just that option, or just that face. This is the way
+to set values in it.
+
+\1f
+File: xemacs.info, Node: Changing an Option, Next: Face Customization, Prev: Customization Groups, Up: Easy Customization
+
+Changing an Option
+..................
+
+ Here is an example of what a user option looks like in the
+customization buffer:
+
+ Kill Ring Max: [Hide] 30
+ [State]: this option is unchanged from its standard setting.
+ Maximum length of kill ring before oldest elements are thrown away.
+
+ The text following `[Hide]', `30' in this case, indicates the
+current value of the option. If you see `[Show]' instead of `[Hide]',
+it means that the value is hidden; the customization buffer initially
+hides values that take up several lines. Invoke `[Show]' to show the
+value.
+
+ The line after the option name indicates the "customization state"
+of the option: in the example above, it says you have not changed the
+option yet. The word `[State]' at the beginning of this line is
+active; you can get a menu of various operations by invoking it with
+`Mouse-1' or <RET>. These operations are essential for customizing the
+variable.
+
+ The line after the `[State]' line displays the beginning of the
+option's documentation string. If there are more lines of
+documentation, this line ends with `[More]'; invoke this to show the
+full documentation string.
+
+ To enter a new value for `Kill Ring Max', move point to the value
+and edit it textually. For example, you can type `M-d', then insert
+another number.
+
+ When you begin to alter the text, you will see the `[State]' line
+change to say that you have edited the value:
+
+ [State]: you have edited the value as text, but not set the option.
+
+ Editing the value does not actually set the option variable. To do
+that, you must "set" the option. To do this, invoke the word `[State]'
+and choose `Set for Current Session'.
+
+ The state of the option changes visibly when you set it:
+
+ [State]: you have set this option, but not saved it for future sessions.
+
+ You don't have to worry about specifying a value that is not valid;
+setting the option checks for validity and will not really install an
+unacceptable value.
+
+ While editing a value or field that is a file name, directory name,
+command name, or anything else for which completion is defined, you can
+type `M-<TAB>' (`widget-complete') to do completion.
+
+ Some options have a small fixed set of possible legitimate values.
+These options don't let you edit the value textually. Instead, an
+active field `[Value Menu]' appears before the value; invoke this field
+to edit the value. For a boolean "on or off" value, the active field
+says `[Toggle]', and it changes to the other value. `[Value Menu]' and
+`[Toggle]' edit the buffer; the changes take effect when you use the
+`Set for Current Session' operation.
+
+ Some options have values with complex structure. For example, the
+value of `load-path' is a list of directories. Here is how it appears
+in the customization buffer:
+
+ Load Path:
+ [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/site-lisp
+ [INS] [DEL] [Current dir?]: /usr/local/share/emacs/site-lisp
+ [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/leim
+ [INS] [DEL] [Current dir?]: /usr/local/share/emacs/19.34.94/lisp
+ [INS] [DEL] [Current dir?]: /build/emacs/e19/lisp
+ [INS] [DEL] [Current dir?]: /build/emacs/e19/lisp/gnus
+ [INS]
+ [State]: this item has been changed outside the customization buffer.
+ List of directories to search for files to load....
+
+Each directory in the list appears on a separate line, and each line has
+several editable or active fields.
+
+ You can edit any of the directory names. To delete a directory from
+the list, invoke `[DEL]' on that line. To insert a new directory in
+the list, invoke `[INS]' at the point where you want to insert it.
+
+ You can also invoke `[Current dir?]' to switch between including a
+specific named directory in the path, and including `nil' in the path.
+(`nil' in a search path means "try the current directory.")
+
+ Two special commands, <TAB> and `S-<TAB>', are useful for moving
+through the customization buffer. <TAB> (`widget-forward') moves
+forward to the next active or editable field; `S-<TAB>'
+(`widget-backward') moves backward to the previous active or editable
+field.
+
+ Typing <RET> on an editable field also moves forward, just like
+<TAB>. The reason for this is that people have a tendency to type
+<RET> when they are finished editing a field. If you have occasion to
+insert a newline in an editable field, use `C-o' or `C-q C-j',
+
+ Setting the option changes its value in the current Emacs session;
+"saving" the value changes it for future sessions as well. This works
+by writing code into your init file so as to set the option variable
+again each time you start Emacs. *Note Init File::. To save the
+option, invoke `[State]' and select the `Save for Future Sessions'
+operation.
+
+ You can also restore the option to its standard value by invoking
+`[State]' and selecting the `Reset' operation. There are actually
+three reset operations:
+
+`Reset to Current'
+ If you have made some modifications and not yet set the option,
+ this restores the text in the customization buffer to match the
+ actual value.
+
+`Reset to Saved'
+ This restores the value of the option to the last saved value, and
+ updates the text accordingly.
+
+`Reset to Standard Settings'
+ This sets the option to its standard value, and updates the text
+ accordingly. This also eliminates any saved value for the option,
+ so that you will get the standard value in future Emacs sessions.
+
+ The state of a group indicates whether anything in that group has
+been edited, set or saved. You can select `Set for Current Session',
+`Save for Future Sessions' and the various kinds of `Reset' operation
+for the group; these operations on the group apply to all options in
+the group and its subgroups.
+
+ Near the top of the customization buffer there are two lines
+containing several active fields:
+
+ [Set] [Save] [Reset] [Done]
+
+Invoking `[Done]' buries this customization buffer. Each of the other
+fields performs an operation--set, save or reset--on each of the items
+in the buffer that could meaningfully be set, saved or reset.
+
+\1f
+File: xemacs.info, Node: Face Customization, Next: Specific Customization, Prev: Changing an Option, Up: Easy Customization
+
+Customizing Faces
+.................
+
+ In addition to user options, some customization groups also include
+faces. When you show the contents of a group, both the user options and
+the faces in the group appear in the customization buffer. Here is an
+example of how a face looks:
+
+ Custom Changed Face: (sample)
+ [State]: this face is unchanged from its standard setting.
+ Face used when the customize item has been changed.
+ Parent groups: [Custom Magic Faces]
+ Attributes: [ ] Bold: [Toggle] off (nil)
+ [ ] Italic: [Toggle] off (nil)
+ [ ] Underline: [Toggle] off (nil)
+ [ ] Foreground: white (sample)
+ [ ] Background: blue (sample)
+ [ ] Inverse: [Toggle] off (nil)
+ [ ] Stipple:
+ [ ] Font Family:
+ [ ] Size:
+ [ ] Strikethru: off
+
+ Each face attribute has its own line. The `[X]' field before the
+attribute name indicates whether the attribute is "enabled"; `X' means
+that it is. You can enable or disable the attribute by invoking that
+field. When the attribute is enabled, you can change the attribute
+value in the usual ways.
+
+ Setting, saving and resetting a face work like the same operations
+for options (*note Changing an Option::).
+
+ A face can specify different appearances for different types of
+display. For example, a face can make text red on a color display, but
+use a bold font on a monochrome display. To specify multiple
+appearances for a face, select `Show Display Types' in the menu you get
+from invoking `[State]'.
+
+\1f
+File: xemacs.info, Node: Specific Customization, Prev: Face Customization, Up: Easy Customization
+
+Customizing Specific Items
+..........................
+
+ Instead of finding the options you want to change by moving down
+through the structure of groups, you can specify the particular option,
+face or group that you want to customize.
+
+`M-x customize-option <RET> OPTION <RET>'
+ Set up a customization buffer with just one option, OPTION.
+
+`M-x customize-face <RET> FACE <RET>'
+ Set up a customization buffer with just one face, FACE.
+
+`M-x customize-group <RET> GROUP <RET>'
+ Set up a customization buffer with just one group, GROUP.
+
+`M-x customize-apropos <RET> REGEXP <RET>'
+ Set up a customization buffer with all the options, faces and
+ groups that match REGEXP.
+
+`M-x customize-saved'
+ Set up a customization buffer containing all options and faces
+ that you have saved with customization buffers.
+
+`M-x customize-customized'
+ Set up a customization buffer containing all options and faces
+ that you have customized but not saved.
+
+ If you want to alter a particular user option variable with the
+customization buffer, and you know its name, you can use the command
+`M-x customize-option' and specify the option name. This sets up the
+customization buffer with just one option--the one that you asked for.
+Editing, setting and saving the value work as described above, but only
+for the specified option.
+
+ Likewise, you can modify a specific face, chosen by name, using `M-x
+customize-face'.
+
+ You can also set up the customization buffer with a specific group,
+using `M-x customize-group'. The immediate contents of the chosen
+group, including option variables, faces, and other groups, all appear
+as well. However, these subgroups' own contents start out hidden. You
+can show their contents in the usual way, by invoking `[Show]'.
+
+ To control more precisely what to customize, you can use `M-x
+customize-apropos'. You specify a regular expression as argument; then
+all options, faces and groups whose names match this regular expression
+are set up in the customization buffer. If you specify an empty regular
+expression, this includes _all_ groups, options and faces in the
+customization buffer (but that takes a long time).
+
+ If you change option values and then decide the change was a mistake,
+you can use two special commands to revisit your previous changes. Use
+`customize-saved' to look at the options and faces that you have saved.
+Use `M-x customize-customized' to look at the options and faces that
+you have set but not saved.
+
+\1f
+File: xemacs.info, Node: Edit Options, Next: Locals, Prev: Easy Customization, Up: Variables
+
+Editing Variable Values
+-----------------------
+
+`M-x list-options'
+ Display a buffer listing names, values, and documentation of all
+ options.
+
+`M-x edit-options'
+ Change option values by editing a list of options.
+
+ `M-x list-options' displays a list of all Emacs option variables in
+an Emacs buffer named `*List Options*'. Each option is shown with its
+documentation and its current value. Here is what a portion of it might
+look like:
+
+ ;; exec-path:
+ ("." "/usr/local/bin" "/usr/ucb" "/bin" "/usr/bin" "/u2/emacs/etc")
+ *List of directories to search programs to run in subprocesses.
+ Each element is a string (directory name)
+ or nil (try the default directory).
+ ;;
+ ;; fill-column:
+ 75
+ *Column beyond which automatic line-wrapping should happen.
+ Automatically becomes local when set in any fashion.
+ ;;
+
+ `M-x edit-options' goes one step further and immediately selects the
+`*List Options*' buffer; this buffer uses the major mode Options mode,
+which provides commands that allow you to point at an option and change
+its value:
+
+`s'
+ Set the variable point is in or near to a new value read using the
+ minibuffer.
+
+`x'
+ Toggle the variable point is in or near: if the value was `nil',
+ it becomes `t'; otherwise it becomes `nil'.
+
+`1'
+ Set the variable point is in or near to `t'.
+
+`0'
+ Set the variable point is in or near to `nil'.
+
+`n'
+`p'
+ Move to the next or previous variable.
+
+\1f
+File: xemacs.info, Node: Locals, Next: File Variables, Prev: Edit Options, Up: Variables
+
+Local Variables
+---------------
+
+`M-x make-local-variable'
+ Make a variable have a local value in the current buffer.
+
+`M-x kill-local-variable'
+ Make a variable use its global value in the current buffer.
+
+`M-x make-variable-buffer-local'
+ Mark a variable so that setting it will make it local to the
+ buffer that is current at that time.
+
+ You can make any variable "local" to a specific Emacs buffer. This
+means that the variable's value in that buffer is independent of its
+value in other buffers. A few variables are always local in every
+buffer. All other Emacs variables have a "global" value which is in
+effect in all buffers that have not made the variable local.
+
+ Major modes always make the variables they set local to the buffer.
+This is why changing major modes in one buffer has no effect on other
+buffers.
+
+ `M-x make-local-variable' reads the name of a variable and makes it
+local to the current buffer. Further changes in this buffer will not
+affect others, and changes in the global value will not affect this
+buffer.
+
+ `M-x make-variable-buffer-local' reads the name of a variable and
+changes the future behavior of the variable so that it automatically
+becomes local when it is set. More precisely, once you have marked a
+variable in this way, the usual ways of setting the variable will
+automatically invoke `make-local-variable' first. We call such
+variables "per-buffer" variables.
+
+ Some important variables have been marked per-buffer already. They
+include `abbrev-mode', `auto-fill-function', `case-fold-search',
+`comment-column', `ctl-arrow', `fill-column', `fill-prefix',
+`indent-tabs-mode', `left-margin',
+`mode-line-format', `overwrite-mode', `selective-display-ellipses',
+`selective-display', `tab-width', and `truncate-lines'. Some other
+variables are always local in every buffer, but they are used for
+internal purposes.
+
+ Note: the variable `auto-fill-function' was formerly named
+`auto-fill-hook'.
+
+ If you want a variable to cease to be local to the current buffer,
+call `M-x kill-local-variable' and provide the name of a variable to
+the prompt. The global value of the variable is again in effect in
+this buffer. Setting the major mode kills all the local variables of
+the buffer.
+
+ To set the global value of a variable, regardless of whether the
+variable has a local value in the current buffer, you can use the Lisp
+function `setq-default'. It works like `setq'. If there is a local
+value in the current buffer, the local value is not affected by
+`setq-default'; thus, the new global value may not be visible until you
+switch to another buffer, as in the case of:
+
+ (setq-default fill-column 75)
+
+`setq-default' is the only way to set the global value of a variable
+that has been marked with `make-variable-buffer-local'.
+
+ Programs can look at a variable's default value with `default-value'.
+This function takes a symbol as an argument and returns its default
+value. The argument is evaluated; usually you must quote it
+explicitly, as in the case of:
+
+ (default-value 'fill-column)
+
+\1f
File: xemacs.info, Node: File Variables, Prev: Locals, Up: Variables
Local Variables in Files
control [ escape
control @ control space
-\1f
-File: xemacs.info, Node: Disabling, Prev: Rebinding, Up: Key Bindings
-
-Disabling Commands
-------------------
-
- Disabling a command marks it as requiring confirmation before it can
-be executed. The purpose of disabling a command is to prevent
-beginning users from executing it by accident and being confused.
-
- The direct mechanism for disabling a command is to have a non-`nil'
-`disabled' property on the Lisp symbol for the command. These
-properties are normally set by the user's init file with Lisp
-expressions such as:
-
- (put 'delete-region 'disabled t)
-
- *Note Init File::.
-
- If the value of the `disabled' property is a string, that string is
-included in the message printed when the command is used:
-
- (put 'delete-region 'disabled
- "Text deleted this way cannot be yanked back!\n")
-
- You can disable a command either by editing the init file directly
-or with the command `M-x disable-command', which edits the init file
-for you. *Note Init File::.
-
- When you attempt to invoke a disabled command interactively in Emacs,
-a window is displayed containing the command's name, its documentation,
-and some instructions on what to do next; then Emacs asks for input
-saying whether to execute the command as requested, enable it and
-execute, or cancel it. If you decide to enable the command, you are
-asked whether to do this permanently or just for the current session.
-Enabling permanently works by automatically editing your init file.
-You can use `M-x enable-command' at any time to enable any command
-permanently.
-
- Whether a command is disabled is independent of what key is used to
-invoke it; it also applies if the command is invoked using `M-x'.
-Disabling a command has no effect on calling it as a function from Lisp
-programs.
-
-\1f
-File: xemacs.info, Node: Syntax, Next: Init File, Prev: Key Bindings, Up: Customization
-
-The Syntax Table
-================
-
- All the Emacs commands which parse words or balance parentheses are
-controlled by the "syntax table". The syntax table specifies which
-characters are opening delimiters, which are parts of words, which are
-string quotes, and so on. Actually, each major mode has its own syntax
-table (though sometimes related major modes use the same one) which it
-installs in each buffer that uses that major mode. The syntax table
-installed in the current buffer is the one that all commands use, so we
-call it "the" syntax table. A syntax table is a Lisp object, a vector
-of length 256 whose elements are numbers.
-
-* Menu:
-
-* Entry: Syntax Entry. What the syntax table records for each character.
-* Change: Syntax Change. How to change the information.
-
-\1f
-File: xemacs.info, Node: Syntax Entry, Next: Syntax Change, Up: Syntax
-
-Information About Each Character
---------------------------------
-
- The syntax table entry for a character is a number that encodes six
-pieces of information:
-
- * The syntactic class of the character, represented as a small
- integer
-
- * The matching delimiter, for delimiter characters only (the
- matching delimiter of `(' is `)', and vice versa)
-
- * A flag saying whether the character is the first character of a
- two-character comment starting sequence
-
- * A flag saying whether the character is the second character of a
- two-character comment starting sequence
-
- * A flag saying whether the character is the first character of a
- two-character comment ending sequence
-
- * A flag saying whether the character is the second character of a
- two-character comment ending sequence
-
- The syntactic classes are stored internally as small integers, but
-are usually described to or by the user with characters. For example,
-`(' is used to specify the syntactic class of opening delimiters. Here
-is a table of syntactic classes, with the characters that specify them.
-
-` '
- The class of whitespace characters.
-
-`w'
- The class of word-constituent characters.
-
-`_'
- The class of characters that are part of symbol names but not
- words. This class is represented by `_' because the character `_'
- has this class in both C and Lisp.
-
-`.'
- The class of punctuation characters that do not fit into any other
- special class.
-
-`('
- The class of opening delimiters.
-
-`)'
- The class of closing delimiters.
-
-`''
- The class of expression-adhering characters. These characters are
- part of a symbol if found within or adjacent to one, and are part
- of a following expression if immediately preceding one, but are
- like whitespace if surrounded by whitespace.
-
-`"'
- The class of string-quote characters. They match each other in
- pairs, and the characters within the pair all lose their syntactic
- significance except for the `\' and `/' classes of escape
- characters, which can be used to include a string-quote inside the
- string.
-
-`$'
- The class of self-matching delimiters. This is intended for TeX's
- `$', which is used both to enter and leave math mode. Thus, a
- pair of matching `$' characters surround each piece of math mode
- TeX input. A pair of adjacent `$' characters act like a single
- one for purposes of matching.
-
-`/'
- The class of escape characters that always just deny the following
- character its special syntactic significance. The character after
- one of these escapes is always treated as alphabetic.
-
-`\'
- The class of C-style escape characters. In practice, these are
- treated just like `/'-class characters, because the extra
- possibilities for C escapes (such as being followed by digits)
- have no effect on where the containing expression ends.
-
-`<'
- The class of comment-starting characters. Only single-character
- comment starters (such as `;' in Lisp mode) are represented this
- way.
-
-`>'
- The class of comment-ending characters. Newline has this syntax in
- Lisp mode.
-
- The characters flagged as part of two-character comment delimiters
-can have other syntactic functions most of the time. For example, `/'
-and `*' in C code, when found separately, have nothing to do with
-comments. The comment-delimiter significance overrides when the pair of
-characters occur together in the proper order. Only the list and sexp
-commands use the syntax table to find comments; the commands
-specifically for comments have other variables that tell them where to
-find comments. Moreover, the list and sexp commands notice comments
-only if `parse-sexp-ignore-comments' is non-`nil'. This variable is set
-to `nil' in modes where comment-terminator sequences are liable to
-appear where there is no comment, for example, in Lisp mode where the
-comment terminator is a newline but not every newline ends a comment.
-
-\1f
-File: xemacs.info, Node: Syntax Change, Prev: Syntax Entry, Up: Syntax
-
-Altering Syntax Information
----------------------------
-
- It is possible to alter a character's syntax table entry by storing
-a new number in the appropriate element of the syntax table, but it
-would be hard to determine what number to use. Emacs therefore
-provides a command that allows you to specify the syntactic properties
-of a character in a convenient way.
-
- `M-x modify-syntax-entry' is the command to change a character's
-syntax. It can be used interactively and is also used by major modes
-to initialize their own syntax tables. Its first argument is the
-character to change. The second argument is a string that specifies the
-new syntax. When called from Lisp code, there is a third, optional
-argument, which specifies the syntax table in which to make the change.
-If not supplied, or if this command is called interactively, the third
-argument defaults to the current buffer's syntax table.
-
- 1. The first character in the string specifies the syntactic class.
- It is one of the characters in the previous table (*note Syntax
- Entry::).
-
- 2. The second character is the matching delimiter. For a character
- that is not an opening or closing delimiter, this should be a
- space, and may be omitted if no following characters are needed.
-
- 3. The remaining characters are flags. The flag characters allowed
- are:
-
- `1'
- Flag this character as the first of a two-character comment
- starting sequence.
-
- `2'
- Flag this character as the second of a two-character comment
- starting sequence.
-
- `3'
- Flag this character as the first of a two-character comment
- ending sequence.
-
- `4'
- Flag this character as the second of a two-character comment
- ending sequence.
-
- Use `C-h s' (`describe-syntax') to display a description of the
-contents of the current syntax table. The description of each
-character includes both the string you have to pass to
-`modify-syntax-entry' to set up that character's current syntax, and
-some English to explain that string if necessary.
-
-\1f
-File: xemacs.info, Node: Init File, Next: Audible Bell, Prev: Syntax, Up: Customization
-
-The Init File
-=============
-
- When you start Emacs, it normally loads either `.xemacs/init.el' or
-the file `.emacs' (whichever comes first) in your home directory. This
-file, if it exists, should contain Lisp code. It is called your
-initialization file or "init file". Use the command line switch `-q'
-to tell Emacs whether to load an init file (*note Entering Emacs::).
-Use the command line switch `-user-init-file' (*note Command
-Switches::) to tell Emacs to load a different file instead of
-`~/.xemacs/init.el'/`~/.emacs'.
-
- When the init file is read, the variable `user-init-file' says which
-init file was loaded.
-
- At some sites there is a "default init file", which is the library
-named `default.el', found via the standard search path for libraries.
-The Emacs distribution contains no such library; your site may create
-one for local customizations. If this library exists, it is loaded
-whenever you start Emacs. But your init file, if any, is loaded first;
-if it sets `inhibit-default-init' non-`nil', then `default' is not
-loaded.
-
- If you have a large amount of code in your init file, you should
-byte-compile it to `~/.xemacs/init.elc' or `~/.emacs.elc'.
-
-* Menu:
-
-* Init Syntax:: Syntax of constants in Emacs Lisp.
-* Init Examples:: How to do some things with an init file.
-* Terminal Init:: Each terminal type can have an init file.
-
-\1f
-File: xemacs.info, Node: Init Syntax, Next: Init Examples, Up: Init File
-
-Init File Syntax
-----------------
-
- The init file contains one or more Lisp function call expressions.
-Each consists of a function name followed by arguments, all surrounded
-by parentheses. For example, `(setq fill-column 60)' represents a call
-to the function `setq' which is used to set the variable `fill-column'
-(*note Filling::) to 60.
-
- The second argument to `setq' is an expression for the new value of
-the variable. This can be a constant, a variable, or a function call
-expression. In the init file, constants are used most of the time.
-They can be:
-
-Numbers
- Integers are written in decimal, with an optional initial minus
- sign.
-
- If a sequence of digits is followed by a period and another
- sequence of digits, it is interpreted as a floating point number.
-
- The number prefixes `#b', `#o', and `#x' are supported to
- represent numbers in binary, octal, and hexadecimal notation (or
- radix).
-
-Strings
- Lisp string syntax is the same as C string syntax with a few extra
- features. Use a double-quote character to begin and end a string
- constant.
-
- Newlines and special characters may be present literally in
- strings. They can also be represented as backslash sequences:
- `\n' for newline, `\b' for backspace, `\r' for return, `\t' for
- tab, `\f' for formfeed (control-l), `\e' for escape, `\\' for a
- backslash, `\"' for a double-quote, or `\OOO' for the character
- whose octal code is OOO. Backslash and double-quote are the only
- characters for which backslash sequences are mandatory.
-
- You can use `\C-' as a prefix for a control character, as in
- `\C-s' for ASCII Control-S, and `\M-' as a prefix for a Meta
- character, as in `\M-a' for Meta-A or `\M-\C-a' for Control-Meta-A.
-
-Characters
- Lisp character constant syntax consists of a `?' followed by
- either a character or an escape sequence starting with `\'.
- Examples: `?x', `?\n', `?\"', `?\)'. Note that strings and
- characters are not interchangeable in Lisp; some contexts require
- one and some contexts require the other.
-
-True
- `t' stands for `true'.
-
-False
- `nil' stands for `false'.
-
-Other Lisp objects
- Write a single-quote (') followed by the Lisp object you want.
-
-\1f
-File: xemacs.info, Node: Init Examples, Next: Terminal Init, Prev: Init Syntax, Up: Init File
-
-Init File Examples
-------------------
-
- Here are some examples of doing certain commonly desired things with
-Lisp expressions:
-
- * Make <TAB> in C mode just insert a tab if point is in the middle
- of a line.
-
- (setq c-tab-always-indent nil)
-
- Here we have a variable whose value is normally `t' for `true' and
- the alternative is `nil' for `false'.
-
- * Make searches case sensitive by default (in all buffers that do not
- override this).
-
- (setq-default case-fold-search nil)
-
- This sets the default value, which is effective in all buffers
- that do not have local values for the variable. Setting
- `case-fold-search' with `setq' affects only the current buffer's
- local value, which is probably not what you want to do in an init
- file.
-
- * Make Text mode the default mode for new buffers.
-
- (setq default-major-mode 'text-mode)
-
- Note that `text-mode' is used because it is the command for
- entering the mode we want. A single-quote is written before it to
- make a symbol constant; otherwise, `text-mode' would be treated as
- a variable name.
-
- * Turn on Auto Fill mode automatically in Text mode and related
- modes.
-
- (setq text-mode-hook
- '(lambda () (auto-fill-mode 1)))
-
- Here we have a variable whose value should be a Lisp function. The
- function we supply is a list starting with `lambda', and a single
- quote is written in front of it to make it (for the purpose of this
- `setq') a list constant rather than an expression. Lisp functions
- are not explained here; for mode hooks it is enough to know that
- `(auto-fill-mode 1)' is an expression that will be executed when
- Text mode is entered. You could replace it with any other
- expression that you like, or with several expressions in a row.
-
- (setq text-mode-hook 'turn-on-auto-fill)
-
- This is another way to accomplish the same result.
- `turn-on-auto-fill' is a symbol whose function definition is
- `(lambda () (auto-fill-mode 1))'.
-
- * Load the installed Lisp library named `foo' (actually a file
- `foo.elc' or `foo.el' in a standard Emacs directory).
-
- (load "foo")
-
- When the argument to `load' is a relative pathname, not starting
- with `/' or `~', `load' searches the directories in `load-path'
- (*note Loading::).
-
- * Load the compiled Lisp file `foo.elc' from your home directory.
-
- (load "~/foo.elc")
-
- Here an absolute file name is used, so no searching is done.
-
- * Rebind the key `C-x l' to run the function `make-symbolic-link'.
-
- (global-set-key "\C-xl" 'make-symbolic-link)
-
- or
-
- (define-key global-map "\C-xl" 'make-symbolic-link)
-
- Note once again the single-quote used to refer to the symbol
- `make-symbolic-link' instead of its value as a variable.
-
- * Do the same thing for C mode only.
-
- (define-key c-mode-map "\C-xl" 'make-symbolic-link)
-
- * Bind the function key <F1> to a command in C mode. Note that the
- names of function keys must be lower case.
-
- (define-key c-mode-map 'f1 'make-symbolic-link)
-
- * Bind the shifted version of <F1> to a command.
-
- (define-key c-mode-map '(shift f1) 'make-symbolic-link)
-
- * Redefine all keys which now run `next-line' in Fundamental mode to
- run `forward-line' instead.
-
- (substitute-key-definition 'next-line 'forward-line
- global-map)
-
- * Make `C-x C-v' undefined.
-
- (global-unset-key "\C-x\C-v")
-
- One reason to undefine a key is so that you can make it a prefix.
- Simply defining `C-x C-v ANYTHING' would make `C-x C-v' a prefix,
- but `C-x C-v' must be freed of any non-prefix definition first.
-
- * Make `$' have the syntax of punctuation in Text mode. Note the
- use of a character constant for `$'.
-
- (modify-syntax-entry ?\$ "." text-mode-syntax-table)
-
- * Enable the use of the command `eval-expression' without
- confirmation.
-
- (put 'eval-expression 'disabled nil)
-
-\1f
-File: xemacs.info, Node: Terminal Init, Prev: Init Examples, Up: Init File
-
-Terminal-Specific Initialization
---------------------------------
-
- Each terminal type can have a Lisp library to be loaded into Emacs
-when it is run on that type of terminal. For a terminal type named
-TERMTYPE, the library is called `term/TERMTYPE' and it is found by
-searching the directories `load-path' as usual and trying the suffixes
-`.elc' and `.el'. Normally it appears in the subdirectory `term' of
-the directory where most Emacs libraries are kept.
-
- The usual purpose of the terminal-specific library is to define the
-escape sequences used by the terminal's function keys using the library
-`keypad.el'. See the file `term/vt100.el' for an example of how this
-is done.
-
- When the terminal type contains a hyphen, only the part of the name
-before the first hyphen is significant in choosing the library name.
-Thus, terminal types `aaa-48' and `aaa-30-rv' both use the library
-`term/aaa'. The code in the library can use `(getenv "TERM")' to find
-the full terminal type name.
-
- The library's name is constructed by concatenating the value of the
-variable `term-file-prefix' and the terminal type. Your init file can
-prevent the loading of the terminal-specific library by setting
-`term-file-prefix' to `nil'. *Note Init File::.
-
- The value of the variable `term-setup-hook', if not `nil', is called
-as a function of no arguments at the end of Emacs initialization, after
-both your init file and any terminal-specific library have been read.
-*Note Init File::. You can set the value in the init file to override
-part of any of the terminal-specific libraries and to define
-initializations for terminals that do not have a library.
-
-\1f
-File: xemacs.info, Node: Audible Bell, Next: Faces, Prev: Init File, Up: Customization
-
-Changing the Bell Sound
-=======================
-
- You can now change how the audible bell sounds using the variable
-`sound-alist'.
-
- `sound-alist''s value is an list associating symbols with, among
-other things, strings of audio-data. When `ding' is called with one of
-the symbols, the associated sound data is played instead of the
-standard beep. This only works if you are logged in on the console of a
-machine with audio hardware. To listen to a sound of the provided type,
-call the function `play-sound' with the argument SOUND. You can also
-set the volume of the sound with the optional argument VOLUME.
-
- Each element of `sound-alist' is a list describing a sound. The
-first element of the list is the name of the sound being defined.
-Subsequent elements of the list are alternating keyword/value pairs:
-
-`sound'
- A string of raw sound data, or the name of another sound to play.
- The symbol `t' here means use the default X beep.
-
-`volume'
- An integer from 0-100, defaulting to `bell-volume'.
-
-`pitch'
- If using the default X beep, the pitch (Hz) to generate.
-
-`duration'
- If using the default X beep, the duration (milliseconds).
-
- For compatibility, elements of `sound-alist' may also be of the form:
-
- ( SOUND-NAME . <SOUND> )
- ( SOUND-NAME <VOLUME> <SOUND> )
-
- You should probably add things to this list by calling the function
-`load-sound-file'.
-
- Note that you can only play audio data if running on the console
-screen of a machine with audio hardware which emacs understands, which
-at this time means a Sun SparcStation, SGI, or HP9000s700.
-
- Also note that the pitch, duration, and volume options are available
-everywhere, but most X servers ignore the `pitch' option.
-
- The variable `bell-volume' should be an integer from 0 to 100, with
-100 being loudest, which controls how loud the sounds emacs makes
-should be. Elements of the `sound-alist' may override this value.
-This variable applies to the standard X bell sound as well as sound
-files.
-
- If the symbol `t' is in place of a sound-string, Emacs uses the
-default X beep. This allows you to define beep-types of different
-volumes even when not running on the console.
-
- You can add things to this list by calling the function
-`load-sound-file', which reads in an audio-file and adds its data to
-the sound-alist. You can specify the sound with the SOUND-NAME argument
-and the file into which the sounds are loaded with the FILENAME
-argument. The optional VOLUME argument sets the volume.
-
- `load-sound-file (FILENAME SOUND-NAME &optional VOLUME)'
-
- To load and install some sound files as beep-types, use the function
-`load-default-sounds' (note that this only works if you are on display
-0 of a machine with audio hardware).
-
- The following beep-types are used by Emacs itself. Other Lisp
-packages may use other beep types, but these are the ones that the C
-kernel of Emacs uses.
-
-`auto-save-error'
- An auto-save does not succeed
-
-`command-error'
- The Emacs command loop catches an error
-
-`undefined-key'
- You type a key that is undefined
-
-`undefined-click'
- You use an undefined mouse-click combination
-
-`no-completion'
- Completion was not possible
-
-`y-or-n-p'
- You type something other than the required `y' or `n'
-
-`yes-or-no-p'
- You type something other than `yes' or `no'
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Disabling, Prev: Rebinding, Up: Key Bindings
+
+Disabling Commands
+------------------
+
+ Disabling a command marks it as requiring confirmation before it can
+be executed. The purpose of disabling a command is to prevent
+beginning users from executing it by accident and being confused.
+
+ The direct mechanism for disabling a command is to have a non-`nil'
+`disabled' property on the Lisp symbol for the command. These
+properties are normally set by the user's init file with Lisp
+expressions such as:
+
+ (put 'delete-region 'disabled t)
+
+ *Note Init File::.
+
+ If the value of the `disabled' property is a string, that string is
+included in the message printed when the command is used:
+
+ (put 'delete-region 'disabled
+ "Text deleted this way cannot be yanked back!\n")
+
+ You can disable a command either by editing the init file directly
+or with the command `M-x disable-command', which edits the init file
+for you. *Note Init File::.
+
+ When you attempt to invoke a disabled command interactively in Emacs,
+a window is displayed containing the command's name, its documentation,
+and some instructions on what to do next; then Emacs asks for input
+saying whether to execute the command as requested, enable it and
+execute, or cancel it. If you decide to enable the command, you are
+asked whether to do this permanently or just for the current session.
+Enabling permanently works by automatically editing your init file.
+You can use `M-x enable-command' at any time to enable any command
+permanently.
+
+ Whether a command is disabled is independent of what key is used to
+invoke it; it also applies if the command is invoked using `M-x'.
+Disabling a command has no effect on calling it as a function from Lisp
+programs.
+
+\1f
+File: xemacs.info, Node: Syntax, Next: Init File, Prev: Key Bindings, Up: Customization
+
+The Syntax Table
+================
+
+ All the Emacs commands which parse words or balance parentheses are
+controlled by the "syntax table". The syntax table specifies which
+characters are opening delimiters, which are parts of words, which are
+string quotes, and so on. Actually, each major mode has its own syntax
+table (though sometimes related major modes use the same one) which it
+installs in each buffer that uses that major mode. The syntax table
+installed in the current buffer is the one that all commands use, so we
+call it "the" syntax table. A syntax table is a Lisp object, a vector
+of length 256 whose elements are numbers.
+
+* Menu:
+
+* Entry: Syntax Entry. What the syntax table records for each character.
+* Change: Syntax Change. How to change the information.
+
+\1f
+File: xemacs.info, Node: Syntax Entry, Next: Syntax Change, Up: Syntax
+
+Information About Each Character
+--------------------------------
+
+ The syntax table entry for a character is a number that encodes six
+pieces of information:
+
+ * The syntactic class of the character, represented as a small
+ integer
+
+ * The matching delimiter, for delimiter characters only (the
+ matching delimiter of `(' is `)', and vice versa)
+
+ * A flag saying whether the character is the first character of a
+ two-character comment starting sequence
+
+ * A flag saying whether the character is the second character of a
+ two-character comment starting sequence
+
+ * A flag saying whether the character is the first character of a
+ two-character comment ending sequence
+
+ * A flag saying whether the character is the second character of a
+ two-character comment ending sequence
+
+ The syntactic classes are stored internally as small integers, but
+are usually described to or by the user with characters. For example,
+`(' is used to specify the syntactic class of opening delimiters. Here
+is a table of syntactic classes, with the characters that specify them.
+
+` '
+ The class of whitespace characters.
+
+`w'
+ The class of word-constituent characters.
+
+`_'
+ The class of characters that are part of symbol names but not
+ words. This class is represented by `_' because the character `_'
+ has this class in both C and Lisp.
+
+`.'
+ The class of punctuation characters that do not fit into any other
+ special class.
+
+`('
+ The class of opening delimiters.
+
+`)'
+ The class of closing delimiters.
+
+`''
+ The class of expression-adhering characters. These characters are
+ part of a symbol if found within or adjacent to one, and are part
+ of a following expression if immediately preceding one, but are
+ like whitespace if surrounded by whitespace.
+
+`"'
+ The class of string-quote characters. They match each other in
+ pairs, and the characters within the pair all lose their syntactic
+ significance except for the `\' and `/' classes of escape
+ characters, which can be used to include a string-quote inside the
+ string.
+
+`$'
+ The class of self-matching delimiters. This is intended for TeX's
+ `$', which is used both to enter and leave math mode. Thus, a
+ pair of matching `$' characters surround each piece of math mode
+ TeX input. A pair of adjacent `$' characters act like a single
+ one for purposes of matching.
+
+`/'
+ The class of escape characters that always just deny the following
+ character its special syntactic significance. The character after
+ one of these escapes is always treated as alphabetic.
+
+`\'
+ The class of C-style escape characters. In practice, these are
+ treated just like `/'-class characters, because the extra
+ possibilities for C escapes (such as being followed by digits)
+ have no effect on where the containing expression ends.
+
+`<'
+ The class of comment-starting characters. Only single-character
+ comment starters (such as `;' in Lisp mode) are represented this
+ way.
+
+`>'
+ The class of comment-ending characters. Newline has this syntax in
+ Lisp mode.
+
+ The characters flagged as part of two-character comment delimiters
+can have other syntactic functions most of the time. For example, `/'
+and `*' in C code, when found separately, have nothing to do with
+comments. The comment-delimiter significance overrides when the pair of
+characters occur together in the proper order. Only the list and sexp
+commands use the syntax table to find comments; the commands
+specifically for comments have other variables that tell them where to
+find comments. Moreover, the list and sexp commands notice comments
+only if `parse-sexp-ignore-comments' is non-`nil'. This variable is set
+to `nil' in modes where comment-terminator sequences are liable to
+appear where there is no comment, for example, in Lisp mode where the
+comment terminator is a newline but not every newline ends a comment.
+
+\1f
+File: xemacs.info, Node: Syntax Change, Prev: Syntax Entry, Up: Syntax
+
+Altering Syntax Information
+---------------------------
+
+ It is possible to alter a character's syntax table entry by storing
+a new number in the appropriate element of the syntax table, but it
+would be hard to determine what number to use. Emacs therefore
+provides a command that allows you to specify the syntactic properties
+of a character in a convenient way.
+
+ `M-x modify-syntax-entry' is the command to change a character's
+syntax. It can be used interactively and is also used by major modes
+to initialize their own syntax tables. Its first argument is the
+character to change. The second argument is a string that specifies the
+new syntax. When called from Lisp code, there is a third, optional
+argument, which specifies the syntax table in which to make the change.
+If not supplied, or if this command is called interactively, the third
+argument defaults to the current buffer's syntax table.
+
+ 1. The first character in the string specifies the syntactic class.
+ It is one of the characters in the previous table (*note Syntax
+ Entry::).
+
+ 2. The second character is the matching delimiter. For a character
+ that is not an opening or closing delimiter, this should be a
+ space, and may be omitted if no following characters are needed.
+
+ 3. The remaining characters are flags. The flag characters allowed
+ are:
+
+ `1'
+ Flag this character as the first of a two-character comment
+ starting sequence.
+
+ `2'
+ Flag this character as the second of a two-character comment
+ starting sequence.
+
+ `3'
+ Flag this character as the first of a two-character comment
+ ending sequence.
+
+ `4'
+ Flag this character as the second of a two-character comment
+ ending sequence.
+
+ Use `C-h s' (`describe-syntax') to display a description of the
+contents of the current syntax table. The description of each
+character includes both the string you have to pass to
+`modify-syntax-entry' to set up that character's current syntax, and
+some English to explain that string if necessary.
+
+\1f
+File: xemacs.info, Node: Init File, Next: Audible Bell, Prev: Syntax, Up: Customization
+
+The Init File
+=============
+
+ When you start Emacs, it normally loads either `.xemacs/init.el' or
+the file `.emacs' (whichever comes first) in your home directory. This
+file, if it exists, should contain Lisp code. It is called your
+initialization file or "init file". Use the command line switch `-q'
+to tell Emacs whether to load an init file (*note Entering Emacs::).
+Use the command line switch `-user-init-file' (*note Command
+Switches::) to tell Emacs to load a different file instead of
+`~/.xemacs/init.el'/`~/.emacs'.
+
+ When the init file is read, the variable `user-init-file' says which
+init file was loaded.
+
+ At some sites there is a "default init file", which is the library
+named `default.el', found via the standard search path for libraries.
+The Emacs distribution contains no such library; your site may create
+one for local customizations. If this library exists, it is loaded
+whenever you start Emacs. But your init file, if any, is loaded first;
+if it sets `inhibit-default-init' non-`nil', then `default' is not
+loaded.
+
+ If you have a large amount of code in your init file, you should
+byte-compile it to `~/.xemacs/init.elc' or `~/.emacs.elc'.
+
+* Menu:
+
+* Init Syntax:: Syntax of constants in Emacs Lisp.
+* Init Examples:: How to do some things with an init file.
+* Terminal Init:: Each terminal type can have an init file.
+
+\1f
+File: xemacs.info, Node: Init Syntax, Next: Init Examples, Up: Init File
+
+Init File Syntax
+----------------
+
+ The init file contains one or more Lisp function call expressions.
+Each consists of a function name followed by arguments, all surrounded
+by parentheses. For example, `(setq fill-column 60)' represents a call
+to the function `setq' which is used to set the variable `fill-column'
+(*note Filling::) to 60.
+
+ The second argument to `setq' is an expression for the new value of
+the variable. This can be a constant, a variable, or a function call
+expression. In the init file, constants are used most of the time.
+They can be:
+
+Numbers
+ Integers are written in decimal, with an optional initial minus
+ sign.
+
+ If a sequence of digits is followed by a period and another
+ sequence of digits, it is interpreted as a floating point number.
+
+ The number prefixes `#b', `#o', and `#x' are supported to
+ represent numbers in binary, octal, and hexadecimal notation (or
+ radix).
+
+Strings
+ Lisp string syntax is the same as C string syntax with a few extra
+ features. Use a double-quote character to begin and end a string
+ constant.
+
+ Newlines and special characters may be present literally in
+ strings. They can also be represented as backslash sequences:
+ `\n' for newline, `\b' for backspace, `\r' for return, `\t' for
+ tab, `\f' for formfeed (control-l), `\e' for escape, `\\' for a
+ backslash, `\"' for a double-quote, or `\OOO' for the character
+ whose octal code is OOO. Backslash and double-quote are the only
+ characters for which backslash sequences are mandatory.
+
+ You can use `\C-' as a prefix for a control character, as in
+ `\C-s' for ASCII Control-S, and `\M-' as a prefix for a Meta
+ character, as in `\M-a' for Meta-A or `\M-\C-a' for Control-Meta-A.
+
+Characters
+ Lisp character constant syntax consists of a `?' followed by
+ either a character or an escape sequence starting with `\'.
+ Examples: `?x', `?\n', `?\"', `?\)'. Note that strings and
+ characters are not interchangeable in Lisp; some contexts require
+ one and some contexts require the other.
+
+True
+ `t' stands for `true'.
+
+False
+ `nil' stands for `false'.
+
+Other Lisp objects
+ Write a single-quote (') followed by the Lisp object you want.
+
+\1f
+File: xemacs.info, Node: Init Examples, Next: Terminal Init, Prev: Init Syntax, Up: Init File
+
+Init File Examples
+------------------
+
+ Here are some examples of doing certain commonly desired things with
+Lisp expressions:
+
+ * Make <TAB> in C mode just insert a tab if point is in the middle
+ of a line.
+
+ (setq c-tab-always-indent nil)
+
+ Here we have a variable whose value is normally `t' for `true' and
+ the alternative is `nil' for `false'.
+
+ * Make searches case sensitive by default (in all buffers that do not
+ override this).
+
+ (setq-default case-fold-search nil)
+
+ This sets the default value, which is effective in all buffers
+ that do not have local values for the variable. Setting
+ `case-fold-search' with `setq' affects only the current buffer's
+ local value, which is probably not what you want to do in an init
+ file.
+
+ * Make Text mode the default mode for new buffers.
+
+ (setq default-major-mode 'text-mode)
+
+ Note that `text-mode' is used because it is the command for
+ entering the mode we want. A single-quote is written before it to
+ make a symbol constant; otherwise, `text-mode' would be treated as
+ a variable name.
+
+ * Turn on Auto Fill mode automatically in Text mode and related
+ modes.
+
+ (setq text-mode-hook
+ '(lambda () (auto-fill-mode 1)))
+
+ Here we have a variable whose value should be a Lisp function. The
+ function we supply is a list starting with `lambda', and a single
+ quote is written in front of it to make it (for the purpose of this
+ `setq') a list constant rather than an expression. Lisp functions
+ are not explained here; for mode hooks it is enough to know that
+ `(auto-fill-mode 1)' is an expression that will be executed when
+ Text mode is entered. You could replace it with any other
+ expression that you like, or with several expressions in a row.
+
+ (setq text-mode-hook 'turn-on-auto-fill)
+
+ This is another way to accomplish the same result.
+ `turn-on-auto-fill' is a symbol whose function definition is
+ `(lambda () (auto-fill-mode 1))'.
+
+ * Load the installed Lisp library named `foo' (actually a file
+ `foo.elc' or `foo.el' in a standard Emacs directory).
+
+ (load "foo")
+
+ When the argument to `load' is a relative pathname, not starting
+ with `/' or `~', `load' searches the directories in `load-path'
+ (*note Loading::).
+
+ * Load the compiled Lisp file `foo.elc' from your home directory.
+
+ (load "~/foo.elc")
+
+ Here an absolute file name is used, so no searching is done.
+
+ * Rebind the key `C-x l' to run the function `make-symbolic-link'.
+
+ (global-set-key "\C-xl" 'make-symbolic-link)
+
+ or
+
+ (define-key global-map "\C-xl" 'make-symbolic-link)
+
+ Note once again the single-quote used to refer to the symbol
+ `make-symbolic-link' instead of its value as a variable.
+
+ * Do the same thing for C mode only.
+
+ (define-key c-mode-map "\C-xl" 'make-symbolic-link)
+
+ * Bind the function key <F1> to a command in C mode. Note that the
+ names of function keys must be lower case.
+
+ (define-key c-mode-map 'f1 'make-symbolic-link)
+
+ * Bind the shifted version of <F1> to a command.
+
+ (define-key c-mode-map '(shift f1) 'make-symbolic-link)
+
+ * Redefine all keys which now run `next-line' in Fundamental mode to
+ run `forward-line' instead.
+
+ (substitute-key-definition 'next-line 'forward-line
+ global-map)
+
+ * Make `C-x C-v' undefined.
+
+ (global-unset-key "\C-x\C-v")
+
+ One reason to undefine a key is so that you can make it a prefix.
+ Simply defining `C-x C-v ANYTHING' would make `C-x C-v' a prefix,
+ but `C-x C-v' must be freed of any non-prefix definition first.
+
+ * Make `$' have the syntax of punctuation in Text mode. Note the
+ use of a character constant for `$'.
+
+ (modify-syntax-entry ?\$ "." text-mode-syntax-table)
+
+ * Enable the use of the command `eval-expression' without
+ confirmation.
+
+ (put 'eval-expression 'disabled nil)
+
+\1f
+File: xemacs.info, Node: Terminal Init, Prev: Init Examples, Up: Init File
+
+Terminal-Specific Initialization
+--------------------------------
+
+ Each terminal type can have a Lisp library to be loaded into Emacs
+when it is run on that type of terminal. For a terminal type named
+TERMTYPE, the library is called `term/TERMTYPE' and it is found by
+searching the directories `load-path' as usual and trying the suffixes
+`.elc' and `.el'. Normally it appears in the subdirectory `term' of
+the directory where most Emacs libraries are kept.
+
+ The usual purpose of the terminal-specific library is to define the
+escape sequences used by the terminal's function keys using the library
+`keypad.el'. See the file `term/vt100.el' for an example of how this
+is done.
+
+ When the terminal type contains a hyphen, only the part of the name
+before the first hyphen is significant in choosing the library name.
+Thus, terminal types `aaa-48' and `aaa-30-rv' both use the library
+`term/aaa'. The code in the library can use `(getenv "TERM")' to find
+the full terminal type name.
+
+ The library's name is constructed by concatenating the value of the
+variable `term-file-prefix' and the terminal type. Your init file can
+prevent the loading of the terminal-specific library by setting
+`term-file-prefix' to `nil'. *Note Init File::.
+
+ The value of the variable `term-setup-hook', if not `nil', is called
+as a function of no arguments at the end of Emacs initialization, after
+both your init file and any terminal-specific library have been read.
+*Note Init File::. You can set the value in the init file to override
+part of any of the terminal-specific libraries and to define
+initializations for terminals that do not have a library.
+
+\1f
+File: xemacs.info, Node: Audible Bell, Next: Faces, Prev: Init File, Up: Customization
+
+Changing the Bell Sound
+=======================
+
+ You can now change how the audible bell sounds using the variable
+`sound-alist'.
+
+ `sound-alist''s value is an list associating symbols with, among
+other things, strings of audio-data. When `ding' is called with one of
+the symbols, the associated sound data is played instead of the
+standard beep. This only works if you are logged in on the console of a
+machine with audio hardware. To listen to a sound of the provided type,
+call the function `play-sound' with the argument SOUND. You can also
+set the volume of the sound with the optional argument VOLUME.
+
+ Each element of `sound-alist' is a list describing a sound. The
+first element of the list is the name of the sound being defined.
+Subsequent elements of the list are alternating keyword/value pairs:
+
+`sound'
+ A string of raw sound data, or the name of another sound to play.
+ The symbol `t' here means use the default X beep.
+
+`volume'
+ An integer from 0-100, defaulting to `bell-volume'.
+
+`pitch'
+ If using the default X beep, the pitch (Hz) to generate.
+
+`duration'
+ If using the default X beep, the duration (milliseconds).
+
+ For compatibility, elements of `sound-alist' may also be of the form:
+
+ ( SOUND-NAME . <SOUND> )
+ ( SOUND-NAME <VOLUME> <SOUND> )
+
+ You should probably add things to this list by calling the function
+`load-sound-file'.
+
+ Note that you can only play audio data if running on the console
+screen of a machine with audio hardware which emacs understands, which
+at this time means a Sun SparcStation, SGI, or HP9000s700.
+
+ Also note that the pitch, duration, and volume options are available
+everywhere, but most X servers ignore the `pitch' option.
+
+ The variable `bell-volume' should be an integer from 0 to 100, with
+100 being loudest, which controls how loud the sounds emacs makes
+should be. Elements of the `sound-alist' may override this value.
+This variable applies to the standard X bell sound as well as sound
+files.
+
+ If the symbol `t' is in place of a sound-string, Emacs uses the
+default X beep. This allows you to define beep-types of different
+volumes even when not running on the console.
+
+ You can add things to this list by calling the function
+`load-sound-file', which reads in an audio-file and adds its data to
+the sound-alist. You can specify the sound with the SOUND-NAME argument
+and the file into which the sounds are loaded with the FILENAME
+argument. The optional VOLUME argument sets the volume.
+
+ `load-sound-file (FILENAME SOUND-NAME &optional VOLUME)'
+
+ To load and install some sound files as beep-types, use the function
+`load-default-sounds' (note that this only works if you are on display
+0 of a machine with audio hardware).
+
+ The following beep-types are used by Emacs itself. Other Lisp
+packages may use other beep types, but these are the ones that the C
+kernel of Emacs uses.
+
+`auto-save-error'
+ An auto-save does not succeed
+
+`command-error'
+ The Emacs command loop catches an error
+
+`undefined-key'
+ You type a key that is undefined
+
+`undefined-click'
+ You use an undefined mouse-click combination
+
+`no-completion'
+ Completion was not possible
+
+`y-or-n-p'
+ You type something other than the required `y' or `n'
+
+`yes-or-no-p'
+ You type something other than `yes' or `no'
+
+\1f
File: xemacs.info, Node: Faces, Next: Frame Components, Prev: Audible Bell, Up: Customization
Faces
recursive editing level. To do so, type `M-x top-level'. This is
called getting back to top level. *Note Recursive Edit::.
-\1f
-File: xemacs.info, Node: Screen Garbled, Next: Text Garbled, Prev: Stuck Recursive, Up: Lossage
-
-Garbage on the Screen
----------------------
-
- If the data on the screen looks wrong, the first thing to do is see
-whether the text is actually wrong. Type `C-l', to redisplay the
-entire screen. If the text appears correct after this, the problem was
-entirely in the previous screen update.
-
- Display updating problems often result from an incorrect termcap
-entry for the terminal you are using. The file `etc/TERMS' in the Emacs
-distribution gives the fixes for known problems of this sort.
-`INSTALL' contains general advice for these problems in one of its
-sections. Very likely there is simply insufficient padding for certain
-display operations. To investigate the possibility that you have this
-sort of problem, try Emacs on another terminal made by a different
-manufacturer. If problems happen frequently on one kind of terminal but
-not another kind, the real problem is likely to be a bad termcap entry,
-though it could also be due to a bug in Emacs that appears for terminals
-that have or lack specific features.
-
-\1f
-File: xemacs.info, Node: Text Garbled, Next: Unasked-for Search, Prev: Screen Garbled, Up: Lossage
-
-Garbage in the Text
--------------------
-
- If `C-l' shows that the text is wrong, try undoing the changes to it
-using `C-x u' until it gets back to a state you consider correct. Also
-try `C-h l' to find out what command you typed to produce the observed
-results.
-
- If a large portion of text appears to be missing at the beginning or
-end of the buffer, check for the word `Narrow' in the mode line. If it
-appears, the text is still present, but marked off-limits. To make it
-visible again, type `C-x n w'. *Note Narrowing::.
-
-\1f
-File: xemacs.info, Node: Unasked-for Search, Next: Emergency Escape, Prev: Text Garbled, Up: Lossage
-
-Spontaneous Entry to Incremental Search
----------------------------------------
-
- If Emacs spontaneously displays `I-search:' at the bottom of the
-screen, it means that the terminal is sending `C-s' and `C-q' according
-to the poorly designed xon/xoff "flow control" protocol. You should
-try to prevent this by putting the terminal in a mode where it will not
-use flow control, or by giving it enough padding that it will never
-send a `C-s'. If that cannot be done, you must tell Emacs to expect
-flow control to be used, until you can get a properly designed terminal.
-
- Information on how to do these things can be found in the file
-`INSTALL' in the Emacs distribution.
-
-\1f
-File: xemacs.info, Node: Emergency Escape, Next: Total Frustration, Prev: Unasked-for Search, Up: Lossage
-
-Emergency Escape
-----------------
-
- Because at times there have been bugs causing Emacs to loop without
-checking `quit-flag', a special feature causes Emacs to be suspended
-immediately if you type a second `C-g' while the flag is already set,
-so you can always get out of XEmacs. Normally Emacs recognizes and
-clears `quit-flag' (and quits!) quickly enough to prevent this from
-happening.
-
- When you resume Emacs after a suspension caused by multiple `C-g', it
-asks two questions before going back to what it had been doing:
-
- Auto-save? (y or n)
- Abort (and dump core)? (y or n)
-
-Answer each one with `y' or `n' followed by <RET>.
-
- Saying `y' to `Auto-save?' causes immediate auto-saving of all
-modified buffers in which auto-saving is enabled.
-
- Saying `y' to `Abort (and dump core)?' causes an illegal instruction
-to be executed, dumping core. This is to enable a wizard to figure out
-why Emacs was failing to quit in the first place. Execution does not
-continue after a core dump. If you answer `n', execution does
-continue. With luck, Emacs will ultimately check `quit-flag' and quit
-normally. If not, and you type another `C-g', it is suspended again.
-
- If Emacs is not really hung, but is just being slow, you may invoke
-the double `C-g' feature without really meaning to. In that case,
-simply resume and answer `n' to both questions, and you will arrive at
-your former state. Presumably the quit you requested will happen soon.
-
- The double-`C-g' feature may be turned off when Emacs is running
-under a window system, since the window system always enables you to
-kill Emacs or to create another window and run another program.
-
-\1f
-File: xemacs.info, Node: Total Frustration, Prev: Emergency Escape, Up: Lossage
-
-Help for Total Frustration
---------------------------
-
- If using Emacs (or something else) becomes terribly frustrating and
-none of the techniques described above solve the problem, Emacs can
-still help you.
-
- First, if the Emacs you are using is not responding to commands, type
-`C-g C-g' to get out of it and then start a new one.
-
- Second, type `M-x doctor <RET>'.
-
- The doctor will make you feel better. Each time you say something to
-the doctor, you must end it by typing <RET> <RET>. This lets the
-doctor know you are finished.
-
-\1f
-File: xemacs.info, Node: Bugs, Prev: Lossage, Up: Top
-
-Reporting Bugs
-==============
-
- Sometimes you will encounter a bug in Emacs. Although we cannot
-promise we can or will fix the bug, and we might not even agree that it
-is a bug, we want to hear about bugs you encounter in case we do want
-to fix them.
-
- To make it possible for us to fix a bug, you must report it. In
-order to do so effectively, you must know when and how to do it.
-
-When Is There a Bug
--------------------
-
- If Emacs executes an illegal instruction, or dies with an operating
-system error message that indicates a problem in the program (as
-opposed to something like "disk full"), then it is certainly a bug.
-
- If Emacs updates the display in a way that does not correspond to
-what is in the buffer, then it is certainly a bug. If a command seems
-to do the wrong thing but the problem corrects itself if you type
-`C-l', it is a case of incorrect display updating.
-
- Taking forever to complete a command can be a bug, but you must make
-certain that it was really Emacs's fault. Some commands simply take a
-long time. Type `C-g' and then `C-h l' to see whether the input Emacs
-received was what you intended to type; if the input was such that you
-KNOW it should have been processed quickly, report a bug. If you don't
-know whether the command should take a long time, find out by looking
-in the manual or by asking for assistance.
-
- If a command you are familiar with causes an Emacs error message in a
-case where its usual definition ought to be reasonable, it is probably a
-bug.
-
- If a command does the wrong thing, that is a bug. But be sure you
-know for certain what it ought to have done. If you aren't familiar
-with the command, or don't know for certain how the command is supposed
-to work, then it might actually be working right. Rather than jumping
-to conclusions, show the problem to someone who knows for certain.
-
- Finally, a command's intended definition may not be best for editing
-with. This is a very important sort of problem, but it is also a
-matter of judgment. Also, it is easy to come to such a conclusion out
-of ignorance of some of the existing features. It is probably best not
-to complain about such a problem until you have checked the
-documentation in the usual ways, feel confident that you understand it,
-and know for certain that what you want is not available. If you are
-not sure what the command is supposed to do after a careful reading of
-the manual, check the index and glossary for any terms that may be
-unclear. If you still do not understand, this indicates a bug in the
-manual. The manual's job is to make everything clear. It is just as
-important to report documentation bugs as program bugs.
-
- If the online documentation string of a function or variable
-disagrees with the manual, one of them must be wrong, so report the bug.
-
-How to Report a Bug
--------------------
-
- When you decide that there is a bug, it is important to report it
-and to report it in a way which is useful. What is most useful is an
-exact description of what commands you type, starting with the shell
-command to run Emacs, until the problem happens. Always include the
-version number of Emacs that you are using; type `M-x emacs-version' to
-print this.
-
- The most important principle in reporting a bug is to report FACTS,
-not hypotheses or categorizations. It is always easier to report the
-facts, but people seem to prefer to strain to posit explanations and
-report them instead. If the explanations are based on guesses about
-how Emacs is implemented, they will be useless; we will have to try to
-figure out what the facts must have been to lead to such speculations.
-Sometimes this is impossible. But in any case, it is unnecessary work
-for us.
-
- For example, suppose that you type `C-x C-f /glorp/baz.ugh <RET>',
-visiting a file which (you know) happens to be rather large, and Emacs
-prints out `I feel pretty today'. The best way to report the bug is
-with a sentence like the preceding one, because it gives all the facts
-and nothing but the facts.
-
- Do not assume that the problem is due to the size of the file and
-say, "When I visit a large file, Emacs prints out `I feel pretty
-today'." This is what we mean by "guessing explanations". The problem
-is just as likely to be due to the fact that there is a `z' in the file
-name. If this is so, then when we got your report, we would try out
-the problem with some "large file", probably with no `z' in its name,
-and not find anything wrong. There is no way in the world that we
-could guess that we should try visiting a file with a `z' in its name.
-
- Alternatively, the problem might be due to the fact that the file
-starts with exactly 25 spaces. For this reason, you should make sure
-that you inform us of the exact contents of any file that is needed to
-reproduce the bug. What if the problem only occurs when you have typed
-the `C-x a l' command previously? This is why we ask you to give the
-exact sequence of characters you typed since starting to use Emacs.
-
- You should not even say "visit a file" instead of `C-x C-f' unless
-you know that it makes no difference which visiting command is used.
-Similarly, rather than saying "if I have three characters on the line,"
-say "after I type `<RET> A B C <RET> C-p'," if that is the way you
-entered the text.
-
- If you are not in Fundamental mode when the problem occurs, you
-should say what mode you are in.
-
- If the manifestation of the bug is an Emacs error message, it is
-important to report not just the text of the error message but a
-backtrace showing how the Lisp program in Emacs arrived at the error.
-To make the backtrace, you must execute the Lisp expression `(setq
-debug-on-error t)' before the error happens (that is to say, you must
-execute that expression and then make the bug happen). This causes the
-Lisp debugger to run (*note Lisp Debug::). The debugger's backtrace
-can be copied as text into the bug report. This use of the debugger is
-possible only if you know how to make the bug happen again. Do note
-the error message the first time the bug happens, so if you can't make
-it happen again, you can report at least that.
-
- Check whether any programs you have loaded into the Lisp world,
-including your init file, set any variables that may affect the
-functioning of Emacs. *Note Init File::. Also, see whether the
-problem happens in a freshly started Emacs without loading your init
-file (start Emacs with the `-q' switch to prevent loading the init
-file). If the problem does NOT occur then, it is essential that we
-know the contents of any programs that you must load into the Lisp
-world in order to cause the problem to occur.
-
- If the problem does depend on an init file or other Lisp programs
-that are not part of the standard Emacs system, then you should make
-sure it is not a bug in those programs by complaining to their
-maintainers first. After they verify that they are using Emacs in a
-way that is supposed to work, they should report the bug.
-
- If you can tell us a way to cause the problem without visiting any
-files, please do so. This makes it much easier to debug. If you do
-need files, make sure you arrange for us to see their exact contents.
-For example, it can often matter whether there are spaces at the ends
-of lines, or a newline after the last line in the buffer (nothing ought
-to care whether the last line is terminated, but tell that to the bugs).
-
- The easy way to record the input to Emacs precisely is to write a
-dribble file; execute the Lisp expression:
-
- (open-dribble-file "~/dribble")
-
-using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
-Emacs. From then on, all Emacs input will be written in the specified
-dribble file until the Emacs process is killed.
-
- For possible display bugs, it is important to report the terminal
-type (the value of environment variable `TERM'), the complete termcap
-entry for the terminal from `/etc/termcap' (since that file is not
-identical on all machines), and the output that Emacs actually sent to
-the terminal. The way to collect this output is to execute the Lisp
-expression:
-
- (open-termscript "~/termscript")
-
-using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
-Emacs. From then on, all output from Emacs to the terminal will be
-written in the specified termscript file as well, until the Emacs
-process is killed. If the problem happens when Emacs starts up, put
-this expression into your init file so that the termscript file will be
-open when Emacs displays the screen for the first time. *Note Init
-File::. Be warned: it is often difficult, and sometimes impossible, to
-fix a terminal-dependent bug without access to a terminal of the type
-that stimulates the bug.
-
- The newsgroup `comp.emacs.xemacs' may be used for bug reports, other
-discussions and requests for assistance.
-
- If you don't have access to this newgroup, you can subscribe to the
-mailing list version: the newsgroup is bidirectionally gatewayed into
-the mailing list `xemacs@xemacs.org'.
-
- To be added or removed from this mailing list, send mail to
-`xemacs-request@xemacs.org'. Do not send requests for addition to the
-mailing list itself.
-
- The mailing lists and newsgroups are archived on our anonymous FTP
-server, `ftp.xemacs.org', and at various other archive sites around the
-net. You should also check the `FAQ' in `/pub/xemacs' on our anonymous
-FTP server. It provides some introductory information and help for
-initial configuration problems.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Screen Garbled, Next: Text Garbled, Prev: Stuck Recursive, Up: Lossage
+
+Garbage on the Screen
+---------------------
+
+ If the data on the screen looks wrong, the first thing to do is see
+whether the text is actually wrong. Type `C-l', to redisplay the
+entire screen. If the text appears correct after this, the problem was
+entirely in the previous screen update.
+
+ Display updating problems often result from an incorrect termcap
+entry for the terminal you are using. The file `etc/TERMS' in the Emacs
+distribution gives the fixes for known problems of this sort.
+`INSTALL' contains general advice for these problems in one of its
+sections. Very likely there is simply insufficient padding for certain
+display operations. To investigate the possibility that you have this
+sort of problem, try Emacs on another terminal made by a different
+manufacturer. If problems happen frequently on one kind of terminal but
+not another kind, the real problem is likely to be a bad termcap entry,
+though it could also be due to a bug in Emacs that appears for terminals
+that have or lack specific features.
+
+\1f
+File: xemacs.info, Node: Text Garbled, Next: Unasked-for Search, Prev: Screen Garbled, Up: Lossage
+
+Garbage in the Text
+-------------------
+
+ If `C-l' shows that the text is wrong, try undoing the changes to it
+using `C-x u' until it gets back to a state you consider correct. Also
+try `C-h l' to find out what command you typed to produce the observed
+results.
+
+ If a large portion of text appears to be missing at the beginning or
+end of the buffer, check for the word `Narrow' in the mode line. If it
+appears, the text is still present, but marked off-limits. To make it
+visible again, type `C-x n w'. *Note Narrowing::.
+
+\1f
+File: xemacs.info, Node: Unasked-for Search, Next: Emergency Escape, Prev: Text Garbled, Up: Lossage
+
+Spontaneous Entry to Incremental Search
+---------------------------------------
+
+ If Emacs spontaneously displays `I-search:' at the bottom of the
+screen, it means that the terminal is sending `C-s' and `C-q' according
+to the poorly designed xon/xoff "flow control" protocol. You should
+try to prevent this by putting the terminal in a mode where it will not
+use flow control, or by giving it enough padding that it will never
+send a `C-s'. If that cannot be done, you must tell Emacs to expect
+flow control to be used, until you can get a properly designed terminal.
+
+ Information on how to do these things can be found in the file
+`INSTALL' in the Emacs distribution.
+
+\1f
+File: xemacs.info, Node: Emergency Escape, Next: Total Frustration, Prev: Unasked-for Search, Up: Lossage
+
+Emergency Escape
+----------------
+
+ Because at times there have been bugs causing Emacs to loop without
+checking `quit-flag', a special feature causes Emacs to be suspended
+immediately if you type a second `C-g' while the flag is already set,
+so you can always get out of XEmacs. Normally Emacs recognizes and
+clears `quit-flag' (and quits!) quickly enough to prevent this from
+happening.
+
+ When you resume Emacs after a suspension caused by multiple `C-g', it
+asks two questions before going back to what it had been doing:
+
+ Auto-save? (y or n)
+ Abort (and dump core)? (y or n)
+
+Answer each one with `y' or `n' followed by <RET>.
+
+ Saying `y' to `Auto-save?' causes immediate auto-saving of all
+modified buffers in which auto-saving is enabled.
+
+ Saying `y' to `Abort (and dump core)?' causes an illegal instruction
+to be executed, dumping core. This is to enable a wizard to figure out
+why Emacs was failing to quit in the first place. Execution does not
+continue after a core dump. If you answer `n', execution does
+continue. With luck, Emacs will ultimately check `quit-flag' and quit
+normally. If not, and you type another `C-g', it is suspended again.
+
+ If Emacs is not really hung, but is just being slow, you may invoke
+the double `C-g' feature without really meaning to. In that case,
+simply resume and answer `n' to both questions, and you will arrive at
+your former state. Presumably the quit you requested will happen soon.
+
+ The double-`C-g' feature may be turned off when Emacs is running
+under a window system, since the window system always enables you to
+kill Emacs or to create another window and run another program.
+
+\1f
+File: xemacs.info, Node: Total Frustration, Prev: Emergency Escape, Up: Lossage
+
+Help for Total Frustration
+--------------------------
+
+ If using Emacs (or something else) becomes terribly frustrating and
+none of the techniques described above solve the problem, Emacs can
+still help you.
+
+ First, if the Emacs you are using is not responding to commands, type
+`C-g C-g' to get out of it and then start a new one.
+
+ Second, type `M-x doctor <RET>'.
+
+ The doctor will make you feel better. Each time you say something to
+the doctor, you must end it by typing <RET> <RET>. This lets the
+doctor know you are finished.
+
+\1f
+File: xemacs.info, Node: Bugs, Prev: Lossage, Up: Top
+
+Reporting Bugs
+==============
+
+ Sometimes you will encounter a bug in Emacs. Although we cannot
+promise we can or will fix the bug, and we might not even agree that it
+is a bug, we want to hear about bugs you encounter in case we do want
+to fix them.
+
+ To make it possible for us to fix a bug, you must report it. In
+order to do so effectively, you must know when and how to do it.
+
+When Is There a Bug
+-------------------
+
+ If Emacs executes an illegal instruction, or dies with an operating
+system error message that indicates a problem in the program (as
+opposed to something like "disk full"), then it is certainly a bug.
+
+ If Emacs updates the display in a way that does not correspond to
+what is in the buffer, then it is certainly a bug. If a command seems
+to do the wrong thing but the problem corrects itself if you type
+`C-l', it is a case of incorrect display updating.
+
+ Taking forever to complete a command can be a bug, but you must make
+certain that it was really Emacs's fault. Some commands simply take a
+long time. Type `C-g' and then `C-h l' to see whether the input Emacs
+received was what you intended to type; if the input was such that you
+KNOW it should have been processed quickly, report a bug. If you don't
+know whether the command should take a long time, find out by looking
+in the manual or by asking for assistance.
+
+ If a command you are familiar with causes an Emacs error message in a
+case where its usual definition ought to be reasonable, it is probably a
+bug.
+
+ If a command does the wrong thing, that is a bug. But be sure you
+know for certain what it ought to have done. If you aren't familiar
+with the command, or don't know for certain how the command is supposed
+to work, then it might actually be working right. Rather than jumping
+to conclusions, show the problem to someone who knows for certain.
+
+ Finally, a command's intended definition may not be best for editing
+with. This is a very important sort of problem, but it is also a
+matter of judgment. Also, it is easy to come to such a conclusion out
+of ignorance of some of the existing features. It is probably best not
+to complain about such a problem until you have checked the
+documentation in the usual ways, feel confident that you understand it,
+and know for certain that what you want is not available. If you are
+not sure what the command is supposed to do after a careful reading of
+the manual, check the index and glossary for any terms that may be
+unclear. If you still do not understand, this indicates a bug in the
+manual. The manual's job is to make everything clear. It is just as
+important to report documentation bugs as program bugs.
+
+ If the online documentation string of a function or variable
+disagrees with the manual, one of them must be wrong, so report the bug.
+
+How to Report a Bug
+-------------------
+
+ When you decide that there is a bug, it is important to report it
+and to report it in a way which is useful. What is most useful is an
+exact description of what commands you type, starting with the shell
+command to run Emacs, until the problem happens. Always include the
+version number of Emacs that you are using; type `M-x emacs-version' to
+print this.
+
+ The most important principle in reporting a bug is to report FACTS,
+not hypotheses or categorizations. It is always easier to report the
+facts, but people seem to prefer to strain to posit explanations and
+report them instead. If the explanations are based on guesses about
+how Emacs is implemented, they will be useless; we will have to try to
+figure out what the facts must have been to lead to such speculations.
+Sometimes this is impossible. But in any case, it is unnecessary work
+for us.
+
+ For example, suppose that you type `C-x C-f /glorp/baz.ugh <RET>',
+visiting a file which (you know) happens to be rather large, and Emacs
+prints out `I feel pretty today'. The best way to report the bug is
+with a sentence like the preceding one, because it gives all the facts
+and nothing but the facts.
+
+ Do not assume that the problem is due to the size of the file and
+say, "When I visit a large file, Emacs prints out `I feel pretty
+today'." This is what we mean by "guessing explanations". The problem
+is just as likely to be due to the fact that there is a `z' in the file
+name. If this is so, then when we got your report, we would try out
+the problem with some "large file", probably with no `z' in its name,
+and not find anything wrong. There is no way in the world that we
+could guess that we should try visiting a file with a `z' in its name.
+
+ Alternatively, the problem might be due to the fact that the file
+starts with exactly 25 spaces. For this reason, you should make sure
+that you inform us of the exact contents of any file that is needed to
+reproduce the bug. What if the problem only occurs when you have typed
+the `C-x a l' command previously? This is why we ask you to give the
+exact sequence of characters you typed since starting to use Emacs.
+
+ You should not even say "visit a file" instead of `C-x C-f' unless
+you know that it makes no difference which visiting command is used.
+Similarly, rather than saying "if I have three characters on the line,"
+say "after I type `<RET> A B C <RET> C-p'," if that is the way you
+entered the text.
+
+ If you are not in Fundamental mode when the problem occurs, you
+should say what mode you are in.
+
+ If the manifestation of the bug is an Emacs error message, it is
+important to report not just the text of the error message but a
+backtrace showing how the Lisp program in Emacs arrived at the error.
+To make the backtrace, you must execute the Lisp expression `(setq
+debug-on-error t)' before the error happens (that is to say, you must
+execute that expression and then make the bug happen). This causes the
+Lisp debugger to run (*note Lisp Debug::). The debugger's backtrace
+can be copied as text into the bug report. This use of the debugger is
+possible only if you know how to make the bug happen again. Do note
+the error message the first time the bug happens, so if you can't make
+it happen again, you can report at least that.
+
+ Check whether any programs you have loaded into the Lisp world,
+including your init file, set any variables that may affect the
+functioning of Emacs. *Note Init File::. Also, see whether the
+problem happens in a freshly started Emacs without loading your init
+file (start Emacs with the `-q' switch to prevent loading the init
+file). If the problem does NOT occur then, it is essential that we
+know the contents of any programs that you must load into the Lisp
+world in order to cause the problem to occur.
+
+ If the problem does depend on an init file or other Lisp programs
+that are not part of the standard Emacs system, then you should make
+sure it is not a bug in those programs by complaining to their
+maintainers first. After they verify that they are using Emacs in a
+way that is supposed to work, they should report the bug.
+
+ If you can tell us a way to cause the problem without visiting any
+files, please do so. This makes it much easier to debug. If you do
+need files, make sure you arrange for us to see their exact contents.
+For example, it can often matter whether there are spaces at the ends
+of lines, or a newline after the last line in the buffer (nothing ought
+to care whether the last line is terminated, but tell that to the bugs).
+
+ The easy way to record the input to Emacs precisely is to write a
+dribble file; execute the Lisp expression:
+
+ (open-dribble-file "~/dribble")
+
+using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
+Emacs. From then on, all Emacs input will be written in the specified
+dribble file until the Emacs process is killed.
+
+ For possible display bugs, it is important to report the terminal
+type (the value of environment variable `TERM'), the complete termcap
+entry for the terminal from `/etc/termcap' (since that file is not
+identical on all machines), and the output that Emacs actually sent to
+the terminal. The way to collect this output is to execute the Lisp
+expression:
+
+ (open-termscript "~/termscript")
+
+using `Meta-<ESC>' or from the `*scratch*' buffer just after starting
+Emacs. From then on, all output from Emacs to the terminal will be
+written in the specified termscript file as well, until the Emacs
+process is killed. If the problem happens when Emacs starts up, put
+this expression into your init file so that the termscript file will be
+open when Emacs displays the screen for the first time. *Note Init
+File::. Be warned: it is often difficult, and sometimes impossible, to
+fix a terminal-dependent bug without access to a terminal of the type
+that stimulates the bug.
+
+ The newsgroup `comp.emacs.xemacs' may be used for bug reports, other
+discussions and requests for assistance.
+
+ If you don't have access to this newgroup, you can subscribe to the
+mailing list version: the newsgroup is bidirectionally gatewayed into
+the mailing list `xemacs@xemacs.org'.
+
+ To be added or removed from this mailing list, send mail to
+`xemacs-request@xemacs.org'. Do not send requests for addition to the
+mailing list itself.
+
+ The mailing lists and newsgroups are archived on our anonymous FTP
+server, `ftp.xemacs.org', and at various other archive sites around the
+net. You should also check the `FAQ' in `/pub/xemacs' on our anonymous
+FTP server. It provides some introductory information and help for
+initial configuration problems.
+
+\1f
File: xemacs.info, Node: Glossary, Next: Manifesto, Prev: Intro, Up: Top
Glossary
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
-File: xemacs.info, Node: Mode Line, Next: XEmacs under X, Prev: Echo Area, Up: Frame
+File: xemacs.info, Node: Mode Line, Next: GUI Components, Prev: Echo Area, Up: Frame
The Mode Line
=============
appropriately.
\1f
-File: xemacs.info, Node: XEmacs under X, Prev: Mode Line, Up: Frame
+File: xemacs.info, Node: GUI Components, Next: XEmacs under X, Prev: Mode Line, Up: Frame
+
+GUI Components
+==============
+
+ When executed in a graphical windowing environment such as the X
+Window System or Microsoft Windows, XEmacs displays several graphical
+user interface components such as scrollbars, menubars, toolbars, and
+gutters. By default there is a vertical scrollbar at the right of each
+frame, and at the top of the frame there is a menubar, a toolbar, and a
+gutter, in that order. Gutters can contain any of several widgets, but
+the default configuration puts a set of "notebook tabs" which you can
+use as a shortcut for selecting any of several related buffers in a
+given frame. Operating the GUI components is "obvious": click on the
+menubar to pull down a menu, on a button in the toolbar to invoke a
+function, and on a tab in the gutter to switch buffers.
+
+* Menu:
+
+* Menubar Basics:: How XEmacs uses the menubar.
+* Scrollbar Basics:: How XEmacs uses scrollbars.
+* Toolbar Basics:: How XEmacs uses toolbars.
+* Gutter Basics:: How XEmacs uses gutters.
+* Inhibiting:: What if you don't like GUI?
+* Customizing:: Position, orientation, and appearance of GUI objects.
+
+\1f
+File: xemacs.info, Node: Menubar Basics, Next: Scrollbar Basics, Up: GUI Components
+
+The XEmacs Menubar
+==================
+
+ The XEmacs menubar is intended to be conformant to the usual
+conventions for menubars, although conformance is not yet perfect. The
+menu at the extreme right is the `Help' menu, which should always be
+available. It provides access to all the XEmacs help facilities
+available through `C-h', as well as samples of various configuration
+files like `~/.Xdefaults' and `~/.emacs'. At the extreme left is the
+`Files' menu, which provides the usual file reading, writing, and
+printing operations, as well as operations like revert buffer from most
+recent save. The next menu from the left is the `Edit' menu, which
+provides the `Undo' operation as well as cutting and pasting,
+searching, and keyboard macro definition and execution.
+
+ XEmacs provides a very dynamic environment, and the Lisp language
+makes for highly flexible applications. The menubar reflects this:
+many menus (eg, the `Buffers' menu, *note Buffers Menu::) contain items
+determined by the current state of XEmacs, and most major modes and many
+minor modes add items to menus and even whole menus to the menubar. In
+fact, some applications like w3.el and VM provide so many menus that
+they define a whole new menubar and add a button that allows convenient
+switching between the "XEmacs menubar" and the "application menubar".
+Such applications normally bind themselves to a particular frame, and
+this switching only takes place on frames where such an application is
+active (ie, the current window of the frame is displaying a buffer in
+the appropriate major mode).
+
+ Other menus which are typically available are the `Options',
+`Tools', `Buffers', `Apps', and `Mule' menus. For detailed
+descriptions of these menus, *Note Pull-down Menus::. (In 21.2
+XEmacsen, the `Mule' menu will be moved under `Options'.)
+
+\1f
+File: xemacs.info, Node: Scrollbar Basics, Next: Toolbar Basics, Prev: Menubar Basics, Up: GUI Components
+
+XEmacs Scrollbars
+=================
+
+ XEmacs scrollbars provide the usual interface. Arrow buttons at
+either end allow for line by line scrolling, including autorepeat.
+Clicking in the scrollbar itself provides scrolling by windowsfull,
+depending on which side of the slider is clicked. The slider itself
+may be dragged for smooth scrolling.
+
+ The position of the slider corresponds to the position of the window
+in the buffer. In particular, the length of the slider is proportional
+to the fraction of the buffer which appears in the window.
+
+ The presence of the scrollbars is under control of the application or
+may be customized by the user. By default a vertical scrollbar is
+present in all windows (except the minibuffer), and there is no
+horizontal scrollbar.
+
+\1f
+File: xemacs.info, Node: Toolbar Basics, Next: Gutter Basics, Prev: Scrollbar Basics, Up: GUI Components
+
+XEmacs Toolbars
+===============
+
+ XEmacs has a default toolbar which provides shortcuts for some of the
+commonly used operations (such as opening files) and applications (such
+as the Info manual reader). Operations which require arguments will pop
+up dialogs to get them.
+
+ The position of the default toolbar can be customized. Also, several
+toolbars may be present simultaneously (in different positions). VM,
+for example, provides an application toolbar which shortcuts for
+mail-specific operations like sending, saving, and deleting messages.
+
+\1f
+File: xemacs.info, Node: Gutter Basics, Next: Inhibiting, Prev: Toolbar Basics, Up: GUI Components
+
+XEmacs Gutters
+==============
+
+ Gutters are the most flexible of the GUI components described in this
+section. In theory, the other GUI components could be implemented by
+customizing a gutter, but in practice the other components were
+introduced earlier and have their own special implementations. Gutters
+tend to be more transient than the other components. Buffer tabs, for
+example, change every time the selected buffer in the frame changes.
+And for progress gauges a gutter to contain the gauge is typically
+created on the fly when needed, then destroyed when the operation whose
+staus is being displayed is completed.
+
+ Buffer tabs, having somewhat complex behavior, deserve a closer look.
+By default, a row of buffer tabs is displayed at the top of every frame.
+(The tabs could be placed in the bottom gutter, but would be oriented
+the same way and look rather odd. The horizontal orientation makes
+putting them in a side gutter utterly impractical.) The buffer
+displayed in the current window of a frame can be changed to a specific
+buffer by clicking [mouse-1] on the corresponding tab in the gutter.
+
+ Each tab contains the name of its buffer. The tab for the current
+buffer in each frame is displayed in raised relief. The list of buffers
+chosen for display in the buffer tab row is derived by filtering the
+buffer list (like the `Buffers' menu). The list starts out with all
+existing buffers, with more recently selected buffers coming earlier in
+the list.
+
+ Then "uninteresting" buffers, like internal XEmacs buffers, the
+`*Message Log*' buffer, and so on are deleted from the list. Next, the
+frame's selected buffer is determined. Buffers with a different major
+mode from the selected buffer are removed from the list. Finally, if
+the list is too long, the least recently used buffers are deleted from
+the list. By default up to 6 most recently used buffers with the same
+mode are displayed on tabs in the gutter.
+
+\1f
+File: xemacs.info, Node: Inhibiting, Next: Customizing, Prev: Gutter Basics, Up: GUI Components
+
+Inhibiting Display of GUI Components
+====================================
+
+ Use of GUI facilities is a personal thing. Almost everyone agrees
+that drawing via keyboard-based "turtle graphics" is acceptable to
+hardly anyone if a mouse is available, but conversely emulating a
+keyboard with a screenful of buttons is a painful experience. But
+between those extremes the complete novice will require a fair amount
+of time before toolbars and menus become dispensable, but many an
+"Ancien Haquer" sees them as a complete waste of precious frame space
+that could be filled with text.
+
+ Display of all of the GUI components created by XEmacs can be
+inhibited through the use of Customize. Customize can be accessed
+through `Options | Customize' in the menu bar, or via `M-x customize'.
+Then navigate through the Customize tree to `Emacs | Environment'.
+Scrollbar and toolbar visibility is controlled via the `Display' group,
+options `Scrollbars visible' and `Toolbar visible' respectively.
+Gutter visibility is controlled by group `Gutter', option `Visible'.
+
+ Or they can be controlled directly by `M-x customize-variable', by
+changing the values of the variables `menubar-visible-p',
+`scrollbars-visible-p', `toolbar-visible-p', or
+`gutter-buffers-tab-visible-p' respectively. (The strange form of the
+last variable is due to the fact that gutters are often used to display
+transient widgets like progress gauges, which you probably don't want
+to inhibit. It is more likely that you want to inhibit the default
+display of the buffers tab widget, which is what that variable controls.
+This interface is subject to change depending on developer experience
+and user feedback.)
+
+ Control of frame configuration can controlled automatically
+according to various parameters such as buffer or frame because these
+are "specifiers" *Note Specifiers: (lispref)Specifiers. Using these
+features requires programming in Lisp; Customize is not yet that
+sophisticated. Also, components that appear in various positions and
+orientations can have display suppressed according to position. `C-h a
+visible-p' gives a list of variables which can be customized. E.g., to
+control the visibility of specifically the left-side toolbar only,
+customize `left-toolbar-visible-p'.
+
+\1f
+File: xemacs.info, Node: Customizing, Prev: Inhibiting, Up: GUI Components
+
+Changing the Position, Orientation, and Appearance of GUI Components
+====================================================================
+
+ #### Not documented yet.
+
+\1f
+File: xemacs.info, Node: XEmacs under X, Next: XEmacs under MS Windows, Prev: GUI Components, Up: Frame
Using XEmacs Under the X Window System
======================================
things, and the title is simply what appears above the window.)
\1f
+File: xemacs.info, Node: XEmacs under MS Windows, Prev: XEmacs under X, Up: Frame
+
+Using XEmacs Under Microsoft Windows
+====================================
+
+ Use of XEmacs under MS Windows is not separately documented here, but
+most operations available under the X Window System are also available
+with MS Windows.
+
+ Where possible, native MS Windows GUI components and capabilities are
+used in XEmacs.
+
+\1f
File: xemacs.info, Node: Keystrokes, Next: Pull-down Menus, Prev: Frame, Up: Top
Keystrokes, Key Sequences, and Key Bindings
For some of the menu items, there are sub-menus which you will need to
select.
-\1f
-File: xemacs.info, Node: Options Menu, Next: Buffers Menu, Prev: Apps Menu, Up: Pull-down Menus
-
-The Options Menu
-----------------
-
- The Options pull-down menu contains the Read Only, Case Sensitive
-Search, Overstrike, Auto Delete Selection, Teach Extended Commands,
-Syntax Highlighting, Paren Highlighting, Font, Size, Weight, Buffers
-Menu Length..., Buffers Sub-Menus and Save Options menu items. When
-you select a menu item, Emacs executes the equivalent command. For
-some of the menu items, there are sub-menus which you will need to
-select.
-
-Read Only
- Selecting this item will cause the buffer to visit the file in a
- read-only mode. Changes to the file will not be allowed. This is
- equivalent to the Emacs command `toggle-read-only' (`C-x C-q').
-
-Case Sensitive Search
- Selecting this item will cause searches to be case-sensitive. If
- its not selected then searches will ignore case. This option is
- local to the buffer.
-
-Overstrike
- After selecting this item, when you type letters they will replace
- existing text on a one-to-one basis, rather than pushing it to the
- right. At the end of a line, such characters extend the line.
- Before a tab, such characters insert until the tab is filled in.
- This is the same as Emacs command `quoted-insert' (`C-q').
-
-Auto Delete Selection
- Selecting this item will cause automatic deletion of the selected
- region. The typed text will replace the selection if the selection
- is active (i.e. if its highlighted). If the option is not selected
- then the typed text is just inserted at the point.
-
-Teach Extended Commands
- After you select this item, any time you execute a command with
- `M-x'which has a shorter keybinding, you will be shown the
- alternate binding before the command executes.
-
-Syntax Highlighting
- You can customize your init file to include the font-lock mode so
- that when you select this item, the comments will be displayed in
- one face, strings in another, reserved words in another, and so
- on. *Note Init File::. When Fonts is selected, different parts of
- the program will appear in different Fonts. When Colors is
- selected, then the program will be displayed in different colors.
- Selecting None causes the program to appear in just one Font and
- Color. Selecting Less resets the Fonts and Colors to a fast,
- minimal set of decorations. Selecting More resets the Fonts and
- Colors to a larger set of decorations. For example, if Less is
- selected (which is the default setting) then you might have all
- comments in green color. Whereas, if More is selected then a
- function name in the comments themselves might appear in a
- different Color or Font.
-
-Paren Highlighting
- After selecting Blink from this item, if you place the cursor on a
- parenthesis, the matching parenthesis will blink. If you select
- Highlight and place the cursor on a parenthesis, the whole
- expression of the parenthesis under the cursor will be highlighted.
- Selecting None will turn off the options (regarding Paren
- Highlighting) which you had selected earlier.
-
-Font
- You can select any Font for your program by choosing from one of
- the available Fonts.
-
-Size
- You can select any size ranging from 2 to 24 by selecting the
- appropriate option.
-
-Weight
- You can choose either Bold or Medium for the weight.
-
-Buffers Menu Length...
- Prompts you for the number of buffers to display. Then it will
- display that number of most recently selected buffers.
-
-Buffers Sub-Menus
- After selection of this item the Buffers menu will contain several
- commands, as submenus of each buffer line. If this item is
- unselected, then there are no submenus for each buffer line, the
- only command available will be selecting that buffer.
-
-Save Options
- Selecting this item will save the current settings of your Options
- menu to your init file. *Note Init File::.
-
-\1f
-File: xemacs.info, Node: Buffers Menu, Next: Tools Menu, Prev: Options Menu, Up: Pull-down Menus
-
-The Buffers Menu
-----------------
-
- The Buffers menu provides a selection of up to ten buffers and the
-item List All Buffers, which provides a Buffer List. *Note List
-Buffers::, for more information.
-
-\1f
-File: xemacs.info, Node: Tools Menu, Next: Help Menu, Prev: Buffers Menu, Up: Pull-down Menus
-
-The Tools Menu
---------------
-
- The Tools pull-down menu contains the Grep..., Compile..., Shell
-Command..., Shell Command on Region..., Debug(GDB)... and
-Debug(DBX)... menu items, and the Compare, Merge, Apply Patch and Tags
-sub-menus. When you select a menu item, Emacs executes the equivalent
-command. For some of the menu items, there are sub-menus which you
-will need to select.
-
-\1f
-File: xemacs.info, Node: Help Menu, Next: Menu Customization, Prev: Tools Menu, Up: Pull-down Menus
-
-The Help Menu
--------------
-
- The Help Menu gives you access to Emacs Info and provides a menu
-equivalent for each of the choices you have when using `C-h'. *Note
-Help::, for more information.
-
- The Help menu also gives access to UNIX online manual pages via the
-UNIX Manual Page option.
-
-\1f
-File: xemacs.info, Node: Menu Customization, Prev: Help Menu, Up: Pull-down Menus
-
-Customizing XEmacs Menus
-------------------------
-
- You can customize any of the pull-down menus by adding or removing
-menu items and disabling or enabling existing menu items.
-
- The following functions are available:
-`add-menu: (MENU-PATH MENU-NAME MENU-ITEMS &optional BEFORE)'
- Add a menu to the menu bar or one of its submenus.
-
-`add-menu-item: (MENU-PATH ITEM-NAME FUNCTION'
- ENABLED-P &optional BEFORE) Add a menu item to a menu, creating
- the menu first if necessary.
-
-`delete-menu-item: (PATH)'
- Remove the menu item defined by PATH from the menu hierarchy.
-
-`disable-menu-item: (PATH)'
- Disable the specified menu item.
-
-`enable-menu-item: (PATH)'
- Enable the specified previously disabled menu item.
-
-`relabel-menu-item: (PATH NEW-NAME)'
- Change the string of the menu item specified by PATH to NEW-NAME.
-
- Use the function `add-menu' to add a new menu or submenu. If a menu
-or submenu of the given name exists already, it is changed.
-
- MENU-PATH identifies the menu under which the new menu should be
-inserted. It is a list of strings; for example, `("File")' names the
-top-level File menu. `("File" "Foo")' names a hypothetical submenu of
-File. If MENU-PATH is `nil', the menu is added to the menu bar itself.
-
- MENU-NAME is the string naming the menu to be added.
-
- MENU-ITEMS is a list of menu item descriptions. Each menu item
-should be a vector of three elements:
-
- * A string, which is the name of the menu item
-
- * A symbol naming a command, or a form to evaluate
-
- * `t' or `nil' to indicate whether the item is selectable
-
- The optional argument BEFORE is the name of the menu before which
-the new menu or submenu should be added. If the menu is already
-present, it is not moved.
-
- The function `add-menu-item' adds a menu item to the specified menu,
-creating the menu first if necessary. If the named item already
-exists, the menu remains unchanged.
-
- MENU-PATH identifies the menu into which the new menu item should be
-inserted. It is a list of strings; for example, `("File")' names the
-top-level File menu. `("File" "Foo")' names a hypothetical submenu of
-File.
-
- ITEM-NAME is the string naming the menu item to add.
-
- FUNCTION is the command to invoke when this menu item is selected.
-If it is a symbol, it is invoked with `call-interactively', in the same
-way that functions bound to keys are invoked. If it is a list, the
-list is simply evaluated.
-
- ENABLED-P controls whether the item is selectable or not. It should
-be `t', `nil', or a form to evaluate to decide. This form will be
-evaluated just before the menu is displayed, and the menu item will be
-selectable if that form returns non-`nil'.
-
- For example, to make the `rename-file' command available from the
-File menu, use the following code:
-
- (add-menu-item '("File") "Rename File" 'rename-file t)
-
- To add a submenu of file management commands using a File Management
-item, use the following code:
-
- (add-menu-item '("File" "File Management") "Copy File" 'copy-file t)
- (add-menu-item '("File" "File Management") "Delete File" 'delete-file t)
- (add-menu-item '("File" "File Management") "Rename File" 'rename-file t)
-
- The optional BEFORE argument is the name of a menu item before which
-the new item should be added. If the item is already present, it is
-not moved.
-
- To remove a specified menu item from the menu hierarchy, use
-`delete-menu-item'.
-
- PATH is a list of strings that identify the position of the menu
-item in the menu hierarchy. `("File" "Save")' means the menu item
-called Save under the top level File menu. `("Menu" "Foo" "Item")'
-means the menu item called Item under the Foo submenu of Menu.
-
- To disable a menu item, use `disable-menu-item'. The disabled menu
-item is grayed and can no longer be selected. To make the item
-selectable again, use `enable-menu-item'. `disable-menu-item' and
-`enable-menu-item' both have the argument PATH.
-
- To change the string of the specified menu item, use
-`relabel-menu-item'. This function also takes the argument PATH.
-
- NEW-NAME is the string to which the menu item will be changed.
-
-\1f
-File: xemacs.info, Node: Entering Emacs, Next: Exiting, Prev: Pull-down Menus, Up: Top
-
-Entering and Exiting Emacs
-**************************
-
- The usual way to invoke XEmacs is to type `xemacs <RET>' at the
-shell. XEmacs clears the screen and then displays an initial advisory
-message and copyright notice. You can begin typing XEmacs commands
-immediately afterward.
-
- Some operating systems insist on discarding all type-ahead when
-XEmacs starts up; they give XEmacs no way to prevent this. Therefore,
-it is advisable to wait until XEmacs clears the screen before typing
-your first editing command.
-
- If you run XEmacs from a shell window under the X Window System, run
-it in the background with `xemacs&'. This way, XEmacs does not tie up
-the shell window, so you can use that to run other shell commands while
-XEmacs operates its own X windows. You can begin typing XEmacs commands
-as soon as you direct your keyboard input to the XEmacs frame.
-
- Before Emacs reads the first command, you have not had a chance to
-give a command to specify a file to edit. Since Emacs must always have
-a current buffer for editing, it presents a buffer, by default, a buffer
-named `*scratch*'. The buffer is in Lisp Interaction mode; you can use
-it to type Lisp expressions and evaluate them, or you can ignore that
-capability and simply doodle. (You can specify a different major mode
-for this buffer by setting the variable `initial-major-mode' in your
-init file. *Note Init File::.)
-
- It is possible to specify files to be visited, Lisp files to be
-loaded, and functions to be called, by giving Emacs arguments in the
-shell command line. *Note Command Switches::. But we don't recommend
-doing this. The feature exists mainly for compatibility with other
-editors.
-
- Many other editors are designed to be started afresh each time you
-want to edit. You edit one file and then exit the editor. The next
-time you want to edit either another file or the same one, you must run
-the editor again. With these editors, it makes sense to use a
-command-line argument to say which file to edit.
-
- But starting a new Emacs each time you want to edit a different file
-does not make sense. For one thing, this would be annoyingly slow. For
-another, this would fail to take advantage of Emacs's ability to visit
-more than one file in a single editing session. And it would lose the
-other accumulated context, such as registers, undo history, and the mark
-ring.
-
- The recommended way to use XEmacs is to start it only once, just
-after you log in, and do all your editing in the same Emacs session.
-Each time you want to edit a different file, you visit it with the
-existing Emacs, which eventually comes to have many files in it ready
-for editing. Usually you do not kill the Emacs until you are about to
-log out. *Note Files::, for more information on visiting more than one
-file.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Options Menu, Next: Buffers Menu, Prev: Apps Menu, Up: Pull-down Menus
+
+The Options Menu
+----------------
+
+ The Options pull-down menu contains the Read Only, Case Sensitive
+Search, Overstrike, Auto Delete Selection, Teach Extended Commands,
+Syntax Highlighting, Paren Highlighting, Font, Size, Weight, Buffers
+Menu Length..., Buffers Sub-Menus and Save Options menu items. When
+you select a menu item, Emacs executes the equivalent command. For
+some of the menu items, there are sub-menus which you will need to
+select.
+
+Read Only
+ Selecting this item will cause the buffer to visit the file in a
+ read-only mode. Changes to the file will not be allowed. This is
+ equivalent to the Emacs command `toggle-read-only' (`C-x C-q').
+
+Case Sensitive Search
+ Selecting this item will cause searches to be case-sensitive. If
+ its not selected then searches will ignore case. This option is
+ local to the buffer.
+
+Overstrike
+ After selecting this item, when you type letters they will replace
+ existing text on a one-to-one basis, rather than pushing it to the
+ right. At the end of a line, such characters extend the line.
+ Before a tab, such characters insert until the tab is filled in.
+ This is the same as Emacs command `quoted-insert' (`C-q').
+
+Auto Delete Selection
+ Selecting this item will cause automatic deletion of the selected
+ region. The typed text will replace the selection if the selection
+ is active (i.e. if its highlighted). If the option is not selected
+ then the typed text is just inserted at the point.
+
+Teach Extended Commands
+ After you select this item, any time you execute a command with
+ `M-x'which has a shorter keybinding, you will be shown the
+ alternate binding before the command executes.
+
+Syntax Highlighting
+ You can customize your init file to include the font-lock mode so
+ that when you select this item, the comments will be displayed in
+ one face, strings in another, reserved words in another, and so
+ on. *Note Init File::. When Fonts is selected, different parts of
+ the program will appear in different Fonts. When Colors is
+ selected, then the program will be displayed in different colors.
+ Selecting None causes the program to appear in just one Font and
+ Color. Selecting Less resets the Fonts and Colors to a fast,
+ minimal set of decorations. Selecting More resets the Fonts and
+ Colors to a larger set of decorations. For example, if Less is
+ selected (which is the default setting) then you might have all
+ comments in green color. Whereas, if More is selected then a
+ function name in the comments themselves might appear in a
+ different Color or Font.
+
+Paren Highlighting
+ After selecting Blink from this item, if you place the cursor on a
+ parenthesis, the matching parenthesis will blink. If you select
+ Highlight and place the cursor on a parenthesis, the whole
+ expression of the parenthesis under the cursor will be highlighted.
+ Selecting None will turn off the options (regarding Paren
+ Highlighting) which you had selected earlier.
+
+Font
+ You can select any Font for your program by choosing from one of
+ the available Fonts.
+
+Size
+ You can select any size ranging from 2 to 24 by selecting the
+ appropriate option.
+
+Weight
+ You can choose either Bold or Medium for the weight.
+
+Buffers Menu Length...
+ Prompts you for the number of buffers to display. Then it will
+ display that number of most recently selected buffers.
+
+Buffers Sub-Menus
+ After selection of this item the Buffers menu will contain several
+ commands, as submenus of each buffer line. If this item is
+ unselected, then there are no submenus for each buffer line, the
+ only command available will be selecting that buffer.
+
+Save Options
+ Selecting this item will save the current settings of your Options
+ menu to your init file. *Note Init File::.
+
+\1f
+File: xemacs.info, Node: Buffers Menu, Next: Tools Menu, Prev: Options Menu, Up: Pull-down Menus
+
+The Buffers Menu
+----------------
+
+ The Buffers menu provides a selection of up to ten buffers and the
+item List All Buffers, which provides a Buffer List. *Note List
+Buffers::, for more information.
+
+\1f
+File: xemacs.info, Node: Tools Menu, Next: Help Menu, Prev: Buffers Menu, Up: Pull-down Menus
+
+The Tools Menu
+--------------
+
+ The Tools pull-down menu contains the Grep..., Compile..., Shell
+Command..., Shell Command on Region..., Debug(GDB)... and
+Debug(DBX)... menu items, and the Compare, Merge, Apply Patch and Tags
+sub-menus. When you select a menu item, Emacs executes the equivalent
+command. For some of the menu items, there are sub-menus which you
+will need to select.
+
+\1f
+File: xemacs.info, Node: Help Menu, Next: Menu Customization, Prev: Tools Menu, Up: Pull-down Menus
+
+The Help Menu
+-------------
+
+ The Help Menu gives you access to Emacs Info and provides a menu
+equivalent for each of the choices you have when using `C-h'. *Note
+Help::, for more information.
+
+ The Help menu also gives access to UNIX online manual pages via the
+UNIX Manual Page option.
+
+\1f
+File: xemacs.info, Node: Menu Customization, Prev: Help Menu, Up: Pull-down Menus
+
+Customizing XEmacs Menus
+------------------------
+
+ You can customize any of the pull-down menus by adding or removing
+menu items and disabling or enabling existing menu items.
+
+ The following functions are available:
+`add-menu: (MENU-PATH MENU-NAME MENU-ITEMS &optional BEFORE)'
+ Add a menu to the menu bar or one of its submenus.
+
+`add-menu-item: (MENU-PATH ITEM-NAME FUNCTION'
+ ENABLED-P &optional BEFORE) Add a menu item to a menu, creating
+ the menu first if necessary.
+
+`delete-menu-item: (PATH)'
+ Remove the menu item defined by PATH from the menu hierarchy.
+
+`disable-menu-item: (PATH)'
+ Disable the specified menu item.
+
+`enable-menu-item: (PATH)'
+ Enable the specified previously disabled menu item.
+
+`relabel-menu-item: (PATH NEW-NAME)'
+ Change the string of the menu item specified by PATH to NEW-NAME.
+
+ Use the function `add-menu' to add a new menu or submenu. If a menu
+or submenu of the given name exists already, it is changed.
+
+ MENU-PATH identifies the menu under which the new menu should be
+inserted. It is a list of strings; for example, `("File")' names the
+top-level File menu. `("File" "Foo")' names a hypothetical submenu of
+File. If MENU-PATH is `nil', the menu is added to the menu bar itself.
+
+ MENU-NAME is the string naming the menu to be added.
+
+ MENU-ITEMS is a list of menu item descriptions. Each menu item
+should be a vector of three elements:
+
+ * A string, which is the name of the menu item
+
+ * A symbol naming a command, or a form to evaluate
+
+ * `t' or `nil' to indicate whether the item is selectable
+
+ The optional argument BEFORE is the name of the menu before which
+the new menu or submenu should be added. If the menu is already
+present, it is not moved.
+
+ The function `add-menu-item' adds a menu item to the specified menu,
+creating the menu first if necessary. If the named item already
+exists, the menu remains unchanged.
+
+ MENU-PATH identifies the menu into which the new menu item should be
+inserted. It is a list of strings; for example, `("File")' names the
+top-level File menu. `("File" "Foo")' names a hypothetical submenu of
+File.
+
+ ITEM-NAME is the string naming the menu item to add.
+
+ FUNCTION is the command to invoke when this menu item is selected.
+If it is a symbol, it is invoked with `call-interactively', in the same
+way that functions bound to keys are invoked. If it is a list, the
+list is simply evaluated.
+
+ ENABLED-P controls whether the item is selectable or not. It should
+be `t', `nil', or a form to evaluate to decide. This form will be
+evaluated just before the menu is displayed, and the menu item will be
+selectable if that form returns non-`nil'.
+
+ For example, to make the `rename-file' command available from the
+File menu, use the following code:
+
+ (add-menu-item '("File") "Rename File" 'rename-file t)
+
+ To add a submenu of file management commands using a File Management
+item, use the following code:
+
+ (add-menu-item '("File" "File Management") "Copy File" 'copy-file t)
+ (add-menu-item '("File" "File Management") "Delete File" 'delete-file t)
+ (add-menu-item '("File" "File Management") "Rename File" 'rename-file t)
+
+ The optional BEFORE argument is the name of a menu item before which
+the new item should be added. If the item is already present, it is
+not moved.
+
+ To remove a specified menu item from the menu hierarchy, use
+`delete-menu-item'.
+
+ PATH is a list of strings that identify the position of the menu
+item in the menu hierarchy. `("File" "Save")' means the menu item
+called Save under the top level File menu. `("Menu" "Foo" "Item")'
+means the menu item called Item under the Foo submenu of Menu.
+
+ To disable a menu item, use `disable-menu-item'. The disabled menu
+item is grayed and can no longer be selected. To make the item
+selectable again, use `enable-menu-item'. `disable-menu-item' and
+`enable-menu-item' both have the argument PATH.
+
+ To change the string of the specified menu item, use
+`relabel-menu-item'. This function also takes the argument PATH.
+
+ NEW-NAME is the string to which the menu item will be changed.
+
+\1f
+File: xemacs.info, Node: Entering Emacs, Next: Exiting, Prev: Pull-down Menus, Up: Top
+
+Entering and Exiting Emacs
+**************************
+
+ The usual way to invoke XEmacs is to type `xemacs <RET>' at the
+shell. XEmacs clears the screen and then displays an initial advisory
+message and copyright notice. You can begin typing XEmacs commands
+immediately afterward.
+
+ Some operating systems insist on discarding all type-ahead when
+XEmacs starts up; they give XEmacs no way to prevent this. Therefore,
+it is advisable to wait until XEmacs clears the screen before typing
+your first editing command.
+
+ If you run XEmacs from a shell window under the X Window System, run
+it in the background with `xemacs&'. This way, XEmacs does not tie up
+the shell window, so you can use that to run other shell commands while
+XEmacs operates its own X windows. You can begin typing XEmacs commands
+as soon as you direct your keyboard input to the XEmacs frame.
+
+ Before Emacs reads the first command, you have not had a chance to
+give a command to specify a file to edit. Since Emacs must always have
+a current buffer for editing, it presents a buffer, by default, a buffer
+named `*scratch*'. The buffer is in Lisp Interaction mode; you can use
+it to type Lisp expressions and evaluate them, or you can ignore that
+capability and simply doodle. (You can specify a different major mode
+for this buffer by setting the variable `initial-major-mode' in your
+init file. *Note Init File::.)
+
+ It is possible to specify files to be visited, Lisp files to be
+loaded, and functions to be called, by giving Emacs arguments in the
+shell command line. *Note Command Switches::. But we don't recommend
+doing this. The feature exists mainly for compatibility with other
+editors.
+
+ Many other editors are designed to be started afresh each time you
+want to edit. You edit one file and then exit the editor. The next
+time you want to edit either another file or the same one, you must run
+the editor again. With these editors, it makes sense to use a
+command-line argument to say which file to edit.
+
+ But starting a new Emacs each time you want to edit a different file
+does not make sense. For one thing, this would be annoyingly slow. For
+another, this would fail to take advantage of Emacs's ability to visit
+more than one file in a single editing session. And it would lose the
+other accumulated context, such as registers, undo history, and the mark
+ring.
+
+ The recommended way to use XEmacs is to start it only once, just
+after you log in, and do all your editing in the same Emacs session.
+Each time you want to edit a different file, you visit it with the
+existing Emacs, which eventually comes to have many files in it ready
+for editing. Usually you do not kill the Emacs until you are about to
+log out. *Note Files::, for more information on visiting more than one
+file.
+
+\1f
File: xemacs.info, Node: Exiting, Next: Command Switches, Prev: Entering Emacs, Up: Top
Exiting Emacs
seldom needed.
Emacs accepts command-line arguments that specify files to visit,
-functions to call, and other activities and operating modes. If you are
-running XEmacs under the X window system, a number of standard Xt
-command line arguments are available as well.
+functions to call, and other activities and operating modes. If you
+are running XEmacs under the X window system, a number of standard Xt
+command line arguments are available, as well as a few X parameters
+that are XEmacs-specific.
+
+ Options with long names with a single initial hyphen are also
+recognized with the GNU double initial hyphen syntax. (The reverse is
+not true.)
The following subsections list:
* Command line arguments that you can always use
what `M-x insert-buffer' does; *Note Misc File Ops::.
`-kill'
- Exit from Emacs without asking for confirmation.
+ Exit from Emacs without asking for confirmation. Always the last
+ argument processed, no matter where it appears in the command line.
`-version'
`-V'
command line. If more than one of them appears, they must appear in the
order in which they appear in this table.
+`--show-dump-id'
+`-sd'
+ Print the ID for the new portable dumper's dump file on the
+ terminal and exit. (Prints an error message and exits if XEmacs
+ was not configured `--pdump'.)
+
+`--no-dump-file'
+`-nd'
+ Don't load the dump file. Roughly equivalent to old temacs.
+ (Ignored if XEmacs was not configured `--pdump'.)
+
+`--terminal FILE'
`-t FILE'
Use FILE instead of the terminal for input and output. This
implies the `-nw' option, documented below.
processed. In addition, auto-saving is not done except in buffers
for which it has been explicitly requested.
+`--no-windows'
`-nw'
Start up XEmacs in TTY mode (using the TTY XEmacs was started
from), rather than trying to connect to an X display. Note that
`-u USER'
Equivalent to `-user-init-file ~USER/.xemacs/init.el
-user-init-directory ~USER/.xemacs', or `-user-init-file
- ~USER/.emacs -user-init-directory ~USER/.xemacs'. whichever init
+ ~USER/.emacs -user-init-directory ~USER/.xemacs', whichever init
file comes first. *Note Init File::.
Note that the init file can get access to the command line argument
*Note Display Vars::, for additional variables that affect how text
is displayed.
-\1f
-File: xemacs.info, Node: Position Info, Next: Arguments, Prev: Continuation Lines, Up: Basic
-
-Cursor Position Information
-===========================
-
- If you are accustomed to other display editors, you may be surprised
-that Emacs does not always display the page number or line number of
-point in the mode line. In Emacs, this information is only rarely
-needed, and a number of commands are available to compute and print it.
-Since text is stored in a way that makes it difficult to compute the
-information, it is not displayed all the time.
-
-`M-x what-page'
- Print page number of point, and line number within page.
-
-`M-x what-line'
- Print line number of point in the buffer.
-
-`M-x line-number-mode'
- Toggle automatic display of current line number.
-
-`M-='
- Print number of lines and characters in the current region
- (`count-lines-region'). *Note Mark::, for information about the
- region.
-
-`C-x ='
- Print character code of character after point, character position
- of point, and column of point (`what-cursor-position').
-
- There are several commands for printing line numbers:
-
- * `M-x what-line' counts lines from the beginning of the file and
- prints the line number point is on. The first line of the file is
- line number 1. You can use these numbers as arguments to `M-x
- goto-line'.
-
- * `M-x what-page' counts pages from the beginning of the file, and
- counts lines within the page, printing both of them. *Note
- Pages::, for the command `C-x l', which counts the lines in the
- current page.
-
- * `M-=' (`count-lines-region') prints the number of lines in the
- region (*note Mark::). *Note Pages::, for the command `C-x l'
- which counts the lines in the
-
- The command `C-x =' (`what-cursor-position') can be used to find out
-the column that the cursor is in, and other miscellaneous information
-about point. It prints a line in the echo area that looks like this:
-
- Char: c (0143, 99, 0x63) point=18862 of 24800(76%) column 53
-
-(In fact, this is the output produced when point is before `column 53'
-in the example.)
-
- The four values after `Char:' describe the character that follows
-point, first by showing it and then by giving its character code in
-octal, decimal and hex.
-
- `point=' is followed by the position of point expressed as a
-character count. The front of the buffer counts as position 1, one
-character later as 2, and so on. The next, larger number is the total
-number of characters in the buffer. Afterward in parentheses comes the
-position expressed as a percentage of the total size.
-
- `column' is followed by the horizontal position of point, in columns
-from the left edge of the window.
-
- If the buffer has been narrowed, making some of the text at the
-beginning and the end temporarily invisible, `C-x =' prints additional
-text describing the current visible range. For example, it might say:
-
- Char: c (0143, 99, 0x63) point=19674 of 24575(80%) <19591 - 19703> column 69
-
-where the two extra numbers give the smallest and largest character
-position that point is allowed to assume. The characters between those
-two positions are the visible ones. *Note Narrowing::.
-
- If point is at the end of the buffer (or the end of the visible
-part), `C-x =' omits any description of the character after point. The
-output looks like
-
- point=563026 of 563025(100%) column 0
-
-\1f
-File: xemacs.info, Node: Arguments, Prev: Position Info, Up: Basic
-
-Numeric Arguments
-=================
-
- In mathematics and computer usage, the word "argument" means "data
-provided to a function or operation." Any Emacs command can be given a
-"numeric argument" (also called a "prefix argument"). Some commands
-interpret the argument as a repetition count. For example, giving an
-argument of ten to the key `C-f' (the command `forward-char', move
-forward one character) moves forward ten characters. With these
-commands, no argument is equivalent to an argument of one. Negative
-arguments are allowed. Often they tell a command to move or act in
-the opposite direction.
-
- If your keyboard has a <META> key (labelled with a diamond on
-Sun-type keyboards and labelled `Alt' on some other keyboards), the
-easiest way to specify a numeric argument is to type digits and/or a
-minus sign while holding down the <META> key. For example,
- M-5 C-n
-
-would move down five lines. The characters `Meta-1', `Meta-2', and so
-on, as well as `Meta--', do this because they are keys bound to
-commands (`digit-argument' and `negative-argument') that are defined to
-contribute to an argument for the next command. Digits and `-'
-modified with Control, or Control and Meta, also specify numeric
-arguments.
-
- Another way of specifying an argument is to use the `C-u'
-(`universal-argument') command followed by the digits of the argument.
-With `C-u', you can type the argument digits without holding down
-modifier keys; `C-u' works on all terminals. To type a negative
-argument, type a minus sign after `C-u'. Just a minus sign without
-digits normally means -1.
-
- `C-u' followed by a character which is neither a digit nor a minus
-sign has the special meaning of "multiply by four". It multiplies the
-argument for the next command by four. `C-u' twice multiplies it by
-sixteen. Thus, `C-u C-u C-f' moves forward sixteen characters. This
-is a good way to move forward "fast", since it moves about 1/5 of a line
-in the usual size frame. Other useful combinations are `C-u C-n', `C-u
-C-u C-n' (move down a good fraction of a frame), `C-u C-u C-o' (make "a
-lot" of blank lines), and `C-u C-k' (kill four lines).
-
- Some commands care only about whether there is an argument and not
-about its value. For example, the command `M-q' (`fill-paragraph') with
-no argument fills text; with an argument, it justifies the text as well.
-(*Note Filling::, for more information on `M-q'.) Just `C-u' is a
-handy way of providing an argument for such commands.
-
- Some commands use the value of the argument as a repeat count, but do
-something peculiar when there is no argument. For example, the command
-`C-k' (`kill-line') with argument N kills N lines, including their
-terminating newlines. But `C-k' with no argument is special: it kills
-the text up to the next newline, or, if point is right at the end of
-the line, it kills the newline itself. Thus, two `C-k' commands with
-no arguments can kill a non-blank line, just like `C-k' with an
-argument of one. (*Note Killing::, for more information on `C-k'.)
-
- A few commands treat a plain `C-u' differently from an ordinary
-argument. A few others may treat an argument of just a minus sign
-differently from an argument of -1. These unusual cases are described
-when they come up; they are always for reasons of convenience of use of
-the individual command.
-
- You can use a numeric argument to insert multiple copies of a
-character. This is straightforward unless the character is a digit; for
-example, `C-u 6 4 a' inserts 64 copies of the character `a'. But this
-does not work for inserting digits; `C-u 6 4 1' specifies an argument
-of 641, rather than inserting anything. To separate the digit to
-insert from the argument, type another `C-u'; for example, `C-u 6 4 C-u
-1' does insert 64 copies of the character `1'.
-
- We use the term "prefix argument" as well as "numeric argument" to
-emphasize that you type the argument before the command, and to
-distinguish these arguments from minibuffer arguments that come after
-the command.
-
-\1f
-File: xemacs.info, Node: Undo, Next: Minibuffer, Prev: Basic, Up: Top
-
-Undoing Changes
-***************
-
- Emacs allows you to undo all changes you make to the text of a
-buffer, up to a certain amount of change (8000 characters). Each
-buffer records changes individually, and the undo command always
-applies to the current buffer. Usually each editing command makes a
-separate entry in the undo records, but some commands such as
-`query-replace' make many entries, and very simple commands such as
-self-inserting characters are often grouped to make undoing less
-tedious.
-
-`C-x u'
- Undo one batch of changes (usually, one command's worth) (`undo').
-
-`C-_'
- The same.
-
- The command `C-x u' or `C-_' allows you to undo changes. The first
-time you give this command, it undoes the last change. Point moves to
-the text affected by the undo, so you can see what was undone.
-
- Consecutive repetitions of the `C-_' or `C-x u' commands undo
-earlier and earlier changes, back to the limit of what has been
-recorded. If all recorded changes have already been undone, the undo
-command prints an error message and does nothing.
-
- Any command other than an undo command breaks the sequence of undo
-commands. Starting at this moment, the previous undo commands are
-considered ordinary changes that can themselves be undone. Thus, you
-can redo changes you have undone by typing `C-f' or any other command
-that have no important effect, and then using more undo commands.
-
- If you notice that a buffer has been modified accidentally, the
-easiest way to recover is to type `C-_' repeatedly until the stars
-disappear from the front of the mode line. When that happens, all the
-modifications you made have been canceled. If you do not remember
-whether you changed the buffer deliberately, type `C-_' once. When you
-see Emacs undo the last change you made, you probably remember why you
-made it. If the change was an accident, leave it undone. If it was
-deliberate, redo the change as described in the preceding paragraph.
-
- Whenever an undo command makes the stars disappear from the mode
-line, the buffer contents is the same as it was when the file was last
-read in or saved.
-
- Not all buffers record undo information. Buffers whose names start
-with spaces don't; these buffers are used internally by Emacs and its
-extensions to hold text that users don't normally look at or edit.
-Minibuffers, help buffers, and documentation buffers also don't record
-undo information.
-
- Emacs can remember at most 8000 or so characters of deleted or
-modified text in any one buffer for reinsertion by the undo command.
-There is also a limit on the number of individual insert, delete, or
-change actions that Emacs can remember.
-
- There are two keys to run the `undo' command, `C-x u' and `C-_',
-because on some keyboards, it is not obvious how to type `C-_'. `C-x u'
-is an alternative you can type in the same fashion on any terminal.
-
-\1f
-File: xemacs.info, Node: Minibuffer, Next: M-x, Prev: Undo, Up: Top
-
-The Minibuffer
-**************
-
- The "minibuffer" is the facility used by XEmacs commands to read
-arguments more complicated than a single number. Minibuffer arguments
-can be file names, buffer names, Lisp function names, XEmacs command
-names, Lisp expressions, and many other things, depending on the command
-reading the argument. You can use the usual XEmacs editing commands in
-the minibuffer to edit the argument text.
-
- When the minibuffer is in use, it appears in the echo area, and the
-cursor moves there. The beginning of the minibuffer line displays a
-"prompt" which says what kind of input you should supply and how it
-will be used. Often this prompt is derived from the name of the command
-that the argument is for. The prompt normally ends with a colon.
-
- Sometimes a "default argument" appears in parentheses after the
-colon; it, too, is part of the prompt. The default is used as the
-argument value if you enter an empty argument (e.g., by just typing
-<RET>). For example, commands that read buffer names always show a
-default, which is the name of the buffer that will be used if you type
-just <RET>.
-
- The simplest way to enter a minibuffer argument is to type the text
-you want, terminated by <RET> which exits the minibuffer. You can
-cancel the command that wants the argument, and get out of the
-minibuffer, by typing `C-g'.
-
- Since the minibuffer uses the screen space of the echo area, it can
-conflict with other ways XEmacs customarily uses the echo area. Here is
-how XEmacs handles such conflicts:
-
- * If a command gets an error while you are in the minibuffer, this
- does not cancel the minibuffer. However, the echo area is needed
- for the error message and therefore the minibuffer itself is
- hidden for a while. It comes back after a few seconds, or as soon
- as you type anything.
-
- * If in the minibuffer you use a command whose purpose is to print a
- message in the echo area, such as `C-x =', the message is printed
- normally, and the minibuffer is hidden for a while. It comes back
- after a few seconds, or as soon as you type anything.
-
- * Echoing of keystrokes does not take place while the minibuffer is
- in use.
-
-* Menu:
-
-* File: Minibuffer File. Entering file names with the minibuffer.
-* Edit: Minibuffer Edit. How to edit in the minibuffer.
-* Completion:: An abbreviation facility for minibuffer input.
-* Minibuffer History:: Reusing recent minibuffer arguments.
-* Repetition:: Re-executing commands that used the minibuffer.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Position Info, Next: Arguments, Prev: Continuation Lines, Up: Basic
+
+Cursor Position Information
+===========================
+
+ If you are accustomed to other display editors, you may be surprised
+that Emacs does not always display the page number or line number of
+point in the mode line. In Emacs, this information is only rarely
+needed, and a number of commands are available to compute and print it.
+Since text is stored in a way that makes it difficult to compute the
+information, it is not displayed all the time.
+
+`M-x what-page'
+ Print page number of point, and line number within page.
+
+`M-x what-line'
+ Print line number of point in the buffer.
+
+`M-x line-number-mode'
+ Toggle automatic display of current line number.
+
+`M-='
+ Print number of lines and characters in the current region
+ (`count-lines-region'). *Note Mark::, for information about the
+ region.
+
+`C-x ='
+ Print character code of character after point, character position
+ of point, and column of point (`what-cursor-position').
+
+ There are several commands for printing line numbers:
+
+ * `M-x what-line' counts lines from the beginning of the file and
+ prints the line number point is on. The first line of the file is
+ line number 1. You can use these numbers as arguments to `M-x
+ goto-line'.
+
+ * `M-x what-page' counts pages from the beginning of the file, and
+ counts lines within the page, printing both of them. *Note
+ Pages::, for the command `C-x l', which counts the lines in the
+ current page.
+
+ * `M-=' (`count-lines-region') prints the number of lines in the
+ region (*note Mark::). *Note Pages::, for the command `C-x l'
+ which counts the lines in the
+
+ The command `C-x =' (`what-cursor-position') can be used to find out
+the column that the cursor is in, and other miscellaneous information
+about point. It prints a line in the echo area that looks like this:
+
+ Char: c (0143, 99, 0x63) point=18862 of 24800(76%) column 53
+
+(In fact, this is the output produced when point is before `column 53'
+in the example.)
+
+ The four values after `Char:' describe the character that follows
+point, first by showing it and then by giving its character code in
+octal, decimal and hex.
+
+ `point=' is followed by the position of point expressed as a
+character count. The front of the buffer counts as position 1, one
+character later as 2, and so on. The next, larger number is the total
+number of characters in the buffer. Afterward in parentheses comes the
+position expressed as a percentage of the total size.
+
+ `column' is followed by the horizontal position of point, in columns
+from the left edge of the window.
+
+ If the buffer has been narrowed, making some of the text at the
+beginning and the end temporarily invisible, `C-x =' prints additional
+text describing the current visible range. For example, it might say:
+
+ Char: c (0143, 99, 0x63) point=19674 of 24575(80%) <19591 - 19703> column 69
+
+where the two extra numbers give the smallest and largest character
+position that point is allowed to assume. The characters between those
+two positions are the visible ones. *Note Narrowing::.
+
+ If point is at the end of the buffer (or the end of the visible
+part), `C-x =' omits any description of the character after point. The
+output looks like
+
+ point=563026 of 563025(100%) column 0
+
+\1f
+File: xemacs.info, Node: Arguments, Prev: Position Info, Up: Basic
+
+Numeric Arguments
+=================
+
+ In mathematics and computer usage, the word "argument" means "data
+provided to a function or operation." Any Emacs command can be given a
+"numeric argument" (also called a "prefix argument"). Some commands
+interpret the argument as a repetition count. For example, giving an
+argument of ten to the key `C-f' (the command `forward-char', move
+forward one character) moves forward ten characters. With these
+commands, no argument is equivalent to an argument of one. Negative
+arguments are allowed. Often they tell a command to move or act in
+the opposite direction.
+
+ If your keyboard has a <META> key (labelled with a diamond on
+Sun-type keyboards and labelled `Alt' on some other keyboards), the
+easiest way to specify a numeric argument is to type digits and/or a
+minus sign while holding down the <META> key. For example,
+ M-5 C-n
+
+would move down five lines. The characters `Meta-1', `Meta-2', and so
+on, as well as `Meta--', do this because they are keys bound to
+commands (`digit-argument' and `negative-argument') that are defined to
+contribute to an argument for the next command. Digits and `-'
+modified with Control, or Control and Meta, also specify numeric
+arguments.
+
+ Another way of specifying an argument is to use the `C-u'
+(`universal-argument') command followed by the digits of the argument.
+With `C-u', you can type the argument digits without holding down
+modifier keys; `C-u' works on all terminals. To type a negative
+argument, type a minus sign after `C-u'. Just a minus sign without
+digits normally means -1.
+
+ `C-u' followed by a character which is neither a digit nor a minus
+sign has the special meaning of "multiply by four". It multiplies the
+argument for the next command by four. `C-u' twice multiplies it by
+sixteen. Thus, `C-u C-u C-f' moves forward sixteen characters. This
+is a good way to move forward "fast", since it moves about 1/5 of a line
+in the usual size frame. Other useful combinations are `C-u C-n', `C-u
+C-u C-n' (move down a good fraction of a frame), `C-u C-u C-o' (make "a
+lot" of blank lines), and `C-u C-k' (kill four lines).
+
+ Some commands care only about whether there is an argument and not
+about its value. For example, the command `M-q' (`fill-paragraph') with
+no argument fills text; with an argument, it justifies the text as well.
+(*Note Filling::, for more information on `M-q'.) Just `C-u' is a
+handy way of providing an argument for such commands.
+
+ Some commands use the value of the argument as a repeat count, but do
+something peculiar when there is no argument. For example, the command
+`C-k' (`kill-line') with argument N kills N lines, including their
+terminating newlines. But `C-k' with no argument is special: it kills
+the text up to the next newline, or, if point is right at the end of
+the line, it kills the newline itself. Thus, two `C-k' commands with
+no arguments can kill a non-blank line, just like `C-k' with an
+argument of one. (*Note Killing::, for more information on `C-k'.)
+
+ A few commands treat a plain `C-u' differently from an ordinary
+argument. A few others may treat an argument of just a minus sign
+differently from an argument of -1. These unusual cases are described
+when they come up; they are always for reasons of convenience of use of
+the individual command.
+
+ You can use a numeric argument to insert multiple copies of a
+character. This is straightforward unless the character is a digit; for
+example, `C-u 6 4 a' inserts 64 copies of the character `a'. But this
+does not work for inserting digits; `C-u 6 4 1' specifies an argument
+of 641, rather than inserting anything. To separate the digit to
+insert from the argument, type another `C-u'; for example, `C-u 6 4 C-u
+1' does insert 64 copies of the character `1'.
+
+ We use the term "prefix argument" as well as "numeric argument" to
+emphasize that you type the argument before the command, and to
+distinguish these arguments from minibuffer arguments that come after
+the command.
+
+\1f
+File: xemacs.info, Node: Undo, Next: Minibuffer, Prev: Basic, Up: Top
+
+Undoing Changes
+***************
+
+ Emacs allows you to undo all changes you make to the text of a
+buffer, up to a certain amount of change (8000 characters). Each
+buffer records changes individually, and the undo command always
+applies to the current buffer. Usually each editing command makes a
+separate entry in the undo records, but some commands such as
+`query-replace' make many entries, and very simple commands such as
+self-inserting characters are often grouped to make undoing less
+tedious.
+
+`C-x u'
+ Undo one batch of changes (usually, one command's worth) (`undo').
+
+`C-_'
+ The same.
+
+ The command `C-x u' or `C-_' allows you to undo changes. The first
+time you give this command, it undoes the last change. Point moves to
+the text affected by the undo, so you can see what was undone.
+
+ Consecutive repetitions of the `C-_' or `C-x u' commands undo
+earlier and earlier changes, back to the limit of what has been
+recorded. If all recorded changes have already been undone, the undo
+command prints an error message and does nothing.
+
+ Any command other than an undo command breaks the sequence of undo
+commands. Starting at this moment, the previous undo commands are
+considered ordinary changes that can themselves be undone. Thus, you
+can redo changes you have undone by typing `C-f' or any other command
+that have no important effect, and then using more undo commands.
+
+ If you notice that a buffer has been modified accidentally, the
+easiest way to recover is to type `C-_' repeatedly until the stars
+disappear from the front of the mode line. When that happens, all the
+modifications you made have been canceled. If you do not remember
+whether you changed the buffer deliberately, type `C-_' once. When you
+see Emacs undo the last change you made, you probably remember why you
+made it. If the change was an accident, leave it undone. If it was
+deliberate, redo the change as described in the preceding paragraph.
+
+ Whenever an undo command makes the stars disappear from the mode
+line, the buffer contents is the same as it was when the file was last
+read in or saved.
+
+ Not all buffers record undo information. Buffers whose names start
+with spaces don't; these buffers are used internally by Emacs and its
+extensions to hold text that users don't normally look at or edit.
+Minibuffers, help buffers, and documentation buffers also don't record
+undo information.
+
+ Emacs can remember at most 8000 or so characters of deleted or
+modified text in any one buffer for reinsertion by the undo command.
+There is also a limit on the number of individual insert, delete, or
+change actions that Emacs can remember.
+
+ There are two keys to run the `undo' command, `C-x u' and `C-_',
+because on some keyboards, it is not obvious how to type `C-_'. `C-x u'
+is an alternative you can type in the same fashion on any terminal.
+
+\1f
+File: xemacs.info, Node: Minibuffer, Next: M-x, Prev: Undo, Up: Top
+
+The Minibuffer
+**************
+
+ The "minibuffer" is the facility used by XEmacs commands to read
+arguments more complicated than a single number. Minibuffer arguments
+can be file names, buffer names, Lisp function names, XEmacs command
+names, Lisp expressions, and many other things, depending on the command
+reading the argument. You can use the usual XEmacs editing commands in
+the minibuffer to edit the argument text.
+
+ When the minibuffer is in use, it appears in the echo area, and the
+cursor moves there. The beginning of the minibuffer line displays a
+"prompt" which says what kind of input you should supply and how it
+will be used. Often this prompt is derived from the name of the command
+that the argument is for. The prompt normally ends with a colon.
+
+ Sometimes a "default argument" appears in parentheses after the
+colon; it, too, is part of the prompt. The default is used as the
+argument value if you enter an empty argument (e.g., by just typing
+<RET>). For example, commands that read buffer names always show a
+default, which is the name of the buffer that will be used if you type
+just <RET>.
+
+ The simplest way to enter a minibuffer argument is to type the text
+you want, terminated by <RET> which exits the minibuffer. You can
+cancel the command that wants the argument, and get out of the
+minibuffer, by typing `C-g'.
+
+ Since the minibuffer uses the screen space of the echo area, it can
+conflict with other ways XEmacs customarily uses the echo area. Here is
+how XEmacs handles such conflicts:
+
+ * If a command gets an error while you are in the minibuffer, this
+ does not cancel the minibuffer. However, the echo area is needed
+ for the error message and therefore the minibuffer itself is
+ hidden for a while. It comes back after a few seconds, or as soon
+ as you type anything.
+
+ * If in the minibuffer you use a command whose purpose is to print a
+ message in the echo area, such as `C-x =', the message is printed
+ normally, and the minibuffer is hidden for a while. It comes back
+ after a few seconds, or as soon as you type anything.
+
+ * Echoing of keystrokes does not take place while the minibuffer is
+ in use.
+
+* Menu:
+
+* File: Minibuffer File. Entering file names with the minibuffer.
+* Edit: Minibuffer Edit. How to edit in the minibuffer.
+* Completion:: An abbreviation facility for minibuffer input.
+* Minibuffer History:: Reusing recent minibuffer arguments.
+* Repetition:: Re-executing commands that used the minibuffer.
+
+\1f
File: xemacs.info, Node: Minibuffer File, Next: Minibuffer Edit, Prev: Minibuffer, Up: Minibuffer
Minibuffers for File Names
symbol property listed in the Apropos buffer, you can click on it with
`Mouse-2' or move there and type <RET>.
-\1f
-File: xemacs.info, Node: Library Keywords, Next: Help Mode, Prev: Apropos, Up: Help
-
-Keyword Search for Lisp Libraries
-=================================
-
- The `C-h p' command lets you search the standard Emacs Lisp
-libraries by topic keywords. Here is a partial list of keywords you can
-use:
-
- abbrev abbreviation handling, typing shortcuts, macros
- bib code related to the `bib' bibliography processor
- c C, C++, and Objective-C language support
- calendar calendar and time management support
- comm communications, networking, remote access to files
- data support for editing files of data
- docs support for Emacs documentation
- dumped files preloaded into Emacs
- emulations emulations of other editors
- extensions Emacs Lisp language extensions
- faces support for multiple fonts
- frames support for Emacs frames and window systems
- games games, jokes and amusements
- hardware support for interfacing with exotic hardware
- help support for on-line help systems
- hypermedia support for links between text or other media types
- i18n internationalization and alternate character-set support
- internal code for Emacs internals, build process, defaults
- languages specialized modes for editing programming languages
- lisp Lisp support, including Emacs Lisp
- local code local to your site
- maint maintenance aids for the Emacs development group
- mail modes for electronic-mail handling
- matching various sorts of searching and matching
- mouse mouse support
- mule multi-language extensions
- news support for netnews reading and posting
- oop support for object-oriented programming
- outlines support for hierarchical outlining
- processes process, subshell, compilation, and job control support
- terminals support for terminal types
- tex code related to the TeX formatter
- tools programming tools
- unix front-ends/assistants for, or emulators of, UNIX features
- vms support code for vms
- wp word processing
-
-\1f
-File: xemacs.info, Node: Help Mode, Next: Misc Help, Prev: Library Keywords, Up: Help
-
-Help Mode Commands
-==================
-
- Help buffers provide the commands of View mode (*note Misc File
-Ops::), plus a few special commands of their own.
-
-`<SPC>'
- Scroll forward.
-
-`<DEL>'
-`<BS>'
- Scroll backward.
-
- When a command name (*note Running Commands by Name: M-x.) or
-variable name (*note Variables::) appears in the documentation, it
-normally appears inside paired single-quotes.
-
-\1f
-File: xemacs.info, Node: Misc Help, Prev: Help Mode, Up: Help
-
-Other Help Commands
-===================
-
- `C-h i' (`info') runs the Info program, which is used for browsing
-through structured documentation files. The entire XEmacs manual is
-available within Info. Eventually all the documentation of the GNU
-system will be available. Type `h' after entering Info to run a
-tutorial on using Info.
-
- If you specify a numeric argument, `C-h i' prompts for the name of a
-documentation file. This way, you can browse a file which doesn't have
-an entry in the top-level Info menu. It is also handy when you need to
-get to the documentation quickly, and you know the exact name of the
-file.
-
- There are two special help commands for accessing XEmacs
-documentation through Info. `C-h C-f FUNCTION <RET>' enters Info and
-goes straight to the documentation of the XEmacs function FUNCTION.
-`C-h C-k KEY' enters Info and goes straight to the documentation of the
-key KEY. These two keys run the commands `Info-elisp-ref' and
-`Info-goto-emacs-key-command-node'.
-
- If something surprising happens, and you are not sure what commands
-you typed, use `C-h l' (`view-lossage'). `C-h l' prints the last 100
-command characters you typed in. If you see commands that you don't
-know, you can use `C-h c' to find out what they do.
-
- XEmacs has several major modes. Each mode redefines a few keys and
-makes a few other changes in how editing works. `C-h m'
-(`describe-mode') prints documentation on the current major mode, which
-normally describes all the commands that are changed in this mode.
-
- `C-h b' (`describe-bindings') and `C-h s' (`describe-syntax')
-present information about the current XEmacs mode that is not covered
-by `C-h m'. `C-h b' displays a list of all the key bindings currently
-in effect, with the local bindings of the current major mode first,
-followed by the global bindings (*note Key Bindings::). `C-h s'
-displays the contents of the syntax table with explanations of each
-character's syntax (*note Syntax::).
-
- You can get a similar list for a particular prefix key by typing
-`C-h' after the prefix key. (There are a few prefix keys for which
-this does not work--those that provide their own bindings for `C-h'.
-One of these is <ESC>, because `<ESC> C-h' is actually `C-M-h', which
-marks a defun.)
-
- The other `C-h' options display various files of useful information.
-`C-h C-w' (`describe-no-warranty') displays the full details on the
-complete absence of warranty for XEmacs. `C-h n' (`view-emacs-news')
-displays the file `xemacs/etc/NEWS', which contains documentation on
-XEmacs changes arranged chronologically. `C-h F' (`xemacs-local-faq')
-displays local version of the XEmacs
-frequently-answered-questions-list. `C-h t' (`help-with-tutorial')
-displays the learn-by-doing XEmacs tutorial. `C-h C-c'
-(`describe-copying') displays the file `xemacs/etc/COPYING', which
-tells you the conditions you must obey in distributing copies of
-XEmacs. `C-h C-d' (`describe-distribution') displays another file named
-`xemacs/etc/DISTRIB', which tells you how you can order a copy of the
-latest version of XEmacs.
-
-\1f
-File: xemacs.info, Node: Mark, Next: Mouse Selection, Prev: Help, Up: Top
-
-Selecting Text
-**************
-
- Many Emacs commands operate on an arbitrary contiguous part of the
-current buffer. You can select text in two ways:
-
- * You use special keys to select text by defining a region between
- point and the mark.
-
- * If you are running XEmacs under X, you can also select text with
- the mouse.
-
-The Mark and the Region
-=======================
-
- To specify the text for a command to operate on, set "the mark" at
-one end of it, and move point to the other end. The text between point
-and the mark is called "the region". You can move point or the mark to
-adjust the boundaries of the region. It doesn't matter which one is
-set first chronologically, or which one comes earlier in the text.
-
- Once the mark has been set, it remains until it is set again at
-another place. The mark remains fixed with respect to the preceding
-character if text is inserted or deleted in a buffer. Each Emacs
-buffer has its own mark; when you return to a buffer that had been
-selected previously, it has the same mark it had before.
-
- Many commands that insert text, such as `C-y' (`yank') and `M-x
-insert-buffer', position the mark at one end of the inserted text--the
-opposite end from where point is positioned, so that the region
-contains the text just inserted.
-
- Aside from delimiting the region, the mark is useful for marking a
-spot that you may want to go back to. To make this feature more useful,
-Emacs remembers 16 previous locations of the mark in the `mark ring'.
-
-* Menu:
-
-* Setting Mark:: Commands to set the mark.
-* Using Region:: Summary of ways to operate on contents of the region.
-* Marking Objects:: Commands to put region around textual units.
-* Mark Ring:: Previous mark positions saved so you can go back there.
-
-\1f
-File: xemacs.info, Node: Setting Mark, Next: Using Region, Prev: Mark, Up: Mark
-
-Setting the Mark
-----------------
-
- Here are some commands for setting the mark:
-
-`C-<SPC>'
- Set the mark where point is (`set-mark-command').
-
-`C-@'
- The same.
-
-`C-x C-x'
- Interchange mark and point (`exchange-point-and-mark').
-
-`C-<'
- Pushes a mark at the beginning of the buffer.
-
-`C->'
- Pushes a mark at the end of the buffer.
-
- For example, to convert part of the buffer to all upper-case, you
-can use the `C-x C-u' (`upcase-region') command, which operates on the
-text in the region. First go to the beginning of the text you want to
-capitalize and type `C-<SPC>' to put the mark there, then move to the
-end, and then type `C-x C-u' to capitalize the selected region. You
-can also set the mark at the end of the text, move to the beginning,
-and then type `C-x C-u'. Most commands that operate on the text in the
-region have the word `region' in their names.
-
- The most common way to set the mark is with the `C-<SPC>' command
-(`set-mark-command'). This command sets the mark where point is. You
-can then move point away, leaving the mark behind. It is actually
-incorrect to speak of the character `C-<SPC>'; there is no such
-character. When you type <SPC> while holding down <CTRL>, you get the
-character `C-@' on most terminals. This character is actually bound to
-`set-mark-command'. But unless you are unlucky enough to have a
-terminal where typing `C-<SPC>' does not produce `C-@', you should
-think of this character as `C-<SPC>'.
-
- Since terminals have only one cursor, Emacs cannot show you where the
-mark is located. Most people use the mark soon after they set it, before
-they forget where it is. But you can see where the mark is with the
-command `C-x C-x' (`exchange-point-and-mark') which puts the mark where
-point was and point where the mark was. The extent of the region is
-unchanged, but the cursor and point are now at the previous location of
-the mark.
-
- Another way to set the mark is to push the mark to the beginning of a
-buffer while leaving point at its original location. If you supply an
-argument to `C-<' (`mark-beginning-of-buffer'), the mark is pushed N/10
-of the way from the true beginning of the buffer. You can also set the
-mark at the end of a buffer with `C->' (`mark-end-of-buffer'). It
-pushes the mark to the end of the buffer, leaving point alone.
-Supplying an argument to the command pushes the mark N/10 of the way
-from the true end of the buffer.
-
- If you are using XEmacs under the X window system, you can set the
-variable `zmacs-regions' to `t'. This makes the current region (defined
-by point and mark) highlight and makes it available as the X clipboard
-selection, which means you can use the menu bar items on it. *Note
-Active Regions::, for more information.
-
- `C-x C-x' is also useful when you are satisfied with the location of
-point but want to move the mark; do `C-x C-x' to put point there and
-then you can move it. A second use of `C-x C-x', if necessary, puts
-the mark at the new location with point back at its original location.
-
-\1f
-File: xemacs.info, Node: Using Region, Next: Marking Objects, Prev: Setting Mark, Up: Mark
-
-Operating on the Region
------------------------
-
- Once you have created an active region, you can do many things to
-the text in it:
- * Kill it with `C-w' (*note Killing::).
-
- * Save it in a register with `C-x r s' (*note Registers::).
-
- * Save it in a buffer or a file (*note Accumulating Text::).
-
- * Convert case with `C-x C-l' or `C-x C-u'
- (*note Case::).
-
- * Evaluate it as Lisp code with `M-x eval-region' (*note Lisp
- Eval::).
-
- * Fill it as text with `M-q' (*note Filling::).
-
- * Print hardcopy with `M-x print-region' (*note Hardcopy::).
-
- * Indent it with `C-x <TAB>' or `C-M-\' (*note Indentation::).
-
-\1f
-File: xemacs.info, Node: Marking Objects, Next: Mark Ring, Prev: Using Region, Up: Mark
-
-Commands to Mark Textual Objects
---------------------------------
-
- There are commands for placing point and the mark around a textual
-object such as a word, list, paragraph or page.
-
-`M-@'
- Set mark after end of next word (`mark-word'). This command and
- the following one do not move point.
-
-`C-M-@'
- Set mark after end of next Lisp expression (`mark-sexp').
-
-`M-h'
- Put region around current paragraph (`mark-paragraph').
-
-`C-M-h'
- Put region around current Lisp defun (`mark-defun').
-
-`C-x h'
- Put region around entire buffer (`mark-whole-buffer').
-
-`C-x C-p'
- Put region around current page (`mark-page').
-
- `M-@' (`mark-word') puts the mark at the end of the next word, while
-`C-M-@' (`mark-sexp') puts it at the end of the next Lisp expression.
-These characters sometimes save you some typing.
-
- A number of commands are available that set both point and mark and
-thus delimit an object in the buffer. `M-h' (`mark-paragraph') moves
-point to the beginning of the paragraph that surrounds or follows
-point, and puts the mark at the end of that paragraph (*note
-Paragraphs::). You can then indent, case-convert, or kill the whole
-paragraph. In the same fashion, `C-M-h' (`mark-defun') puts point
-before and the mark after the current or following defun (*note
-Defuns::). `C-x C-p' (`mark-page') puts point before the current page
-(or the next or previous, depending on the argument), and mark at the
-end (*note Pages::). The mark goes after the terminating page
-delimiter (to include it), while point goes after the preceding page
-delimiter (to exclude it). Finally, `C-x h' (`mark-whole-buffer') sets
-up the entire buffer as the region by putting point at the beginning
-and the mark at the end.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Library Keywords, Next: Help Mode, Prev: Apropos, Up: Help
+
+Keyword Search for Lisp Libraries
+=================================
+
+ The `C-h p' command lets you search the standard Emacs Lisp
+libraries by topic keywords. Here is a partial list of keywords you can
+use:
+
+ abbrev abbreviation handling, typing shortcuts, macros
+ bib code related to the `bib' bibliography processor
+ c C, C++, and Objective-C language support
+ calendar calendar and time management support
+ comm communications, networking, remote access to files
+ data support for editing files of data
+ docs support for Emacs documentation
+ dumped files preloaded into Emacs
+ emulations emulations of other editors
+ extensions Emacs Lisp language extensions
+ faces support for multiple fonts
+ frames support for Emacs frames and window systems
+ games games, jokes and amusements
+ hardware support for interfacing with exotic hardware
+ help support for on-line help systems
+ hypermedia support for links between text or other media types
+ i18n internationalization and alternate character-set support
+ internal code for Emacs internals, build process, defaults
+ languages specialized modes for editing programming languages
+ lisp Lisp support, including Emacs Lisp
+ local code local to your site
+ maint maintenance aids for the Emacs development group
+ mail modes for electronic-mail handling
+ matching various sorts of searching and matching
+ mouse mouse support
+ mule multi-language extensions
+ news support for netnews reading and posting
+ oop support for object-oriented programming
+ outlines support for hierarchical outlining
+ processes process, subshell, compilation, and job control support
+ terminals support for terminal types
+ tex code related to the TeX formatter
+ tools programming tools
+ unix front-ends/assistants for, or emulators of, UNIX features
+ vms support code for vms
+ wp word processing
+
+\1f
+File: xemacs.info, Node: Help Mode, Next: Misc Help, Prev: Library Keywords, Up: Help
+
+Help Mode Commands
+==================
+
+ Help buffers provide the commands of View mode (*note Misc File
+Ops::), plus a few special commands of their own.
+
+`<SPC>'
+ Scroll forward.
+
+`<DEL>'
+`<BS>'
+ Scroll backward.
+
+ When a command name (*note Running Commands by Name: M-x.) or
+variable name (*note Variables::) appears in the documentation, it
+normally appears inside paired single-quotes.
+
+\1f
+File: xemacs.info, Node: Misc Help, Prev: Help Mode, Up: Help
+
+Other Help Commands
+===================
+
+ `C-h i' (`info') runs the Info program, which is used for browsing
+through structured documentation files. The entire XEmacs manual is
+available within Info. Eventually all the documentation of the GNU
+system will be available. Type `h' after entering Info to run a
+tutorial on using Info.
+
+ If you specify a numeric argument, `C-h i' prompts for the name of a
+documentation file. This way, you can browse a file which doesn't have
+an entry in the top-level Info menu. It is also handy when you need to
+get to the documentation quickly, and you know the exact name of the
+file.
+
+ There are two special help commands for accessing XEmacs
+documentation through Info. `C-h C-f FUNCTION <RET>' enters Info and
+goes straight to the documentation of the XEmacs function FUNCTION.
+`C-h C-k KEY' enters Info and goes straight to the documentation of the
+key KEY. These two keys run the commands `Info-elisp-ref' and
+`Info-goto-emacs-key-command-node'.
+
+ If something surprising happens, and you are not sure what commands
+you typed, use `C-h l' (`view-lossage'). `C-h l' prints the last 100
+command characters you typed in. If you see commands that you don't
+know, you can use `C-h c' to find out what they do.
+
+ XEmacs has several major modes. Each mode redefines a few keys and
+makes a few other changes in how editing works. `C-h m'
+(`describe-mode') prints documentation on the current major mode, which
+normally describes all the commands that are changed in this mode.
+
+ `C-h b' (`describe-bindings') and `C-h s' (`describe-syntax')
+present information about the current XEmacs mode that is not covered
+by `C-h m'. `C-h b' displays a list of all the key bindings currently
+in effect, with the local bindings of the current major mode first,
+followed by the global bindings (*note Key Bindings::). `C-h s'
+displays the contents of the syntax table with explanations of each
+character's syntax (*note Syntax::).
+
+ You can get a similar list for a particular prefix key by typing
+`C-h' after the prefix key. (There are a few prefix keys for which
+this does not work--those that provide their own bindings for `C-h'.
+One of these is <ESC>, because `<ESC> C-h' is actually `C-M-h', which
+marks a defun.)
+
+ The other `C-h' options display various files of useful information.
+`C-h C-w' (`describe-no-warranty') displays the full details on the
+complete absence of warranty for XEmacs. `C-h n' (`view-emacs-news')
+displays the file `xemacs/etc/NEWS', which contains documentation on
+XEmacs changes arranged chronologically. `C-h F' (`xemacs-local-faq')
+displays local version of the XEmacs
+frequently-answered-questions-list. `C-h t' (`help-with-tutorial')
+displays the learn-by-doing XEmacs tutorial. `C-h C-c'
+(`describe-copying') displays the file `xemacs/etc/COPYING', which
+tells you the conditions you must obey in distributing copies of
+XEmacs. `C-h C-d' (`describe-distribution') displays another file named
+`xemacs/etc/DISTRIB', which tells you how you can order a copy of the
+latest version of XEmacs.
+
+\1f
+File: xemacs.info, Node: Mark, Next: Mouse Selection, Prev: Help, Up: Top
+
+Selecting Text
+**************
+
+ Many Emacs commands operate on an arbitrary contiguous part of the
+current buffer. You can select text in two ways:
+
+ * You use special keys to select text by defining a region between
+ point and the mark.
+
+ * If you are running XEmacs under X, you can also select text with
+ the mouse.
+
+The Mark and the Region
+=======================
+
+ To specify the text for a command to operate on, set "the mark" at
+one end of it, and move point to the other end. The text between point
+and the mark is called "the region". You can move point or the mark to
+adjust the boundaries of the region. It doesn't matter which one is
+set first chronologically, or which one comes earlier in the text.
+
+ Once the mark has been set, it remains until it is set again at
+another place. The mark remains fixed with respect to the preceding
+character if text is inserted or deleted in a buffer. Each Emacs
+buffer has its own mark; when you return to a buffer that had been
+selected previously, it has the same mark it had before.
+
+ Many commands that insert text, such as `C-y' (`yank') and `M-x
+insert-buffer', position the mark at one end of the inserted text--the
+opposite end from where point is positioned, so that the region
+contains the text just inserted.
+
+ Aside from delimiting the region, the mark is useful for marking a
+spot that you may want to go back to. To make this feature more useful,
+Emacs remembers 16 previous locations of the mark in the `mark ring'.
+
+* Menu:
+
+* Setting Mark:: Commands to set the mark.
+* Using Region:: Summary of ways to operate on contents of the region.
+* Marking Objects:: Commands to put region around textual units.
+* Mark Ring:: Previous mark positions saved so you can go back there.
+
+\1f
+File: xemacs.info, Node: Setting Mark, Next: Using Region, Prev: Mark, Up: Mark
+
+Setting the Mark
+----------------
+
+ Here are some commands for setting the mark:
+
+`C-<SPC>'
+ Set the mark where point is (`set-mark-command').
+
+`C-@'
+ The same.
+
+`C-x C-x'
+ Interchange mark and point (`exchange-point-and-mark').
+
+`C-<'
+ Pushes a mark at the beginning of the buffer.
+
+`C->'
+ Pushes a mark at the end of the buffer.
+
+ For example, to convert part of the buffer to all upper-case, you
+can use the `C-x C-u' (`upcase-region') command, which operates on the
+text in the region. First go to the beginning of the text you want to
+capitalize and type `C-<SPC>' to put the mark there, then move to the
+end, and then type `C-x C-u' to capitalize the selected region. You
+can also set the mark at the end of the text, move to the beginning,
+and then type `C-x C-u'. Most commands that operate on the text in the
+region have the word `region' in their names.
+
+ The most common way to set the mark is with the `C-<SPC>' command
+(`set-mark-command'). This command sets the mark where point is. You
+can then move point away, leaving the mark behind. It is actually
+incorrect to speak of the character `C-<SPC>'; there is no such
+character. When you type <SPC> while holding down <CTRL>, you get the
+character `C-@' on most terminals. This character is actually bound to
+`set-mark-command'. But unless you are unlucky enough to have a
+terminal where typing `C-<SPC>' does not produce `C-@', you should
+think of this character as `C-<SPC>'.
+
+ Since terminals have only one cursor, Emacs cannot show you where the
+mark is located. Most people use the mark soon after they set it, before
+they forget where it is. But you can see where the mark is with the
+command `C-x C-x' (`exchange-point-and-mark') which puts the mark where
+point was and point where the mark was. The extent of the region is
+unchanged, but the cursor and point are now at the previous location of
+the mark.
+
+ Another way to set the mark is to push the mark to the beginning of a
+buffer while leaving point at its original location. If you supply an
+argument to `C-<' (`mark-beginning-of-buffer'), the mark is pushed N/10
+of the way from the true beginning of the buffer. You can also set the
+mark at the end of a buffer with `C->' (`mark-end-of-buffer'). It
+pushes the mark to the end of the buffer, leaving point alone.
+Supplying an argument to the command pushes the mark N/10 of the way
+from the true end of the buffer.
+
+ If you are using XEmacs under the X window system, you can set the
+variable `zmacs-regions' to `t'. This makes the current region (defined
+by point and mark) highlight and makes it available as the X clipboard
+selection, which means you can use the menu bar items on it. *Note
+Active Regions::, for more information.
+
+ `C-x C-x' is also useful when you are satisfied with the location of
+point but want to move the mark; do `C-x C-x' to put point there and
+then you can move it. A second use of `C-x C-x', if necessary, puts
+the mark at the new location with point back at its original location.
+
+\1f
+File: xemacs.info, Node: Using Region, Next: Marking Objects, Prev: Setting Mark, Up: Mark
+
+Operating on the Region
+-----------------------
+
+ Once you have created an active region, you can do many things to
+the text in it:
+ * Kill it with `C-w' (*note Killing::).
+
+ * Save it in a register with `C-x r s' (*note Registers::).
+
+ * Save it in a buffer or a file (*note Accumulating Text::).
+
+ * Convert case with `C-x C-l' or `C-x C-u'
+ (*note Case::).
+
+ * Evaluate it as Lisp code with `M-x eval-region' (*note Lisp
+ Eval::).
+
+ * Fill it as text with `M-q' (*note Filling::).
+
+ * Print hardcopy with `M-x print-region' (*note Hardcopy::).
+
+ * Indent it with `C-x <TAB>' or `C-M-\' (*note Indentation::).
+
+\1f
+File: xemacs.info, Node: Marking Objects, Next: Mark Ring, Prev: Using Region, Up: Mark
+
+Commands to Mark Textual Objects
+--------------------------------
+
+ There are commands for placing point and the mark around a textual
+object such as a word, list, paragraph or page.
+
+`M-@'
+ Set mark after end of next word (`mark-word'). This command and
+ the following one do not move point.
+
+`C-M-@'
+ Set mark after end of next Lisp expression (`mark-sexp').
+
+`M-h'
+ Put region around current paragraph (`mark-paragraph').
+
+`C-M-h'
+ Put region around current Lisp defun (`mark-defun').
+
+`C-x h'
+ Put region around entire buffer (`mark-whole-buffer').
+
+`C-x C-p'
+ Put region around current page (`mark-page').
+
+ `M-@' (`mark-word') puts the mark at the end of the next word, while
+`C-M-@' (`mark-sexp') puts it at the end of the next Lisp expression.
+These characters sometimes save you some typing.
+
+ A number of commands are available that set both point and mark and
+thus delimit an object in the buffer. `M-h' (`mark-paragraph') moves
+point to the beginning of the paragraph that surrounds or follows
+point, and puts the mark at the end of that paragraph (*note
+Paragraphs::). You can then indent, case-convert, or kill the whole
+paragraph. In the same fashion, `C-M-h' (`mark-defun') puts point
+before and the mark after the current or following defun (*note
+Defuns::). `C-x C-p' (`mark-page') puts point before the current page
+(or the next or previous, depending on the argument), and mark at the
+end (*note Pages::). The mark goes after the terminating page
+delimiter (to include it), while point goes after the preceding page
+delimiter (to exclude it). Finally, `C-x h' (`mark-whole-buffer') sets
+up the entire buffer as the region by putting point at the beginning
+and the mark at the end.
+
+\1f
File: xemacs.info, Node: Mark Ring, Prev: Marking Objects, Up: Mark
The Mark Ring
results, because the file's text inside Emacs does not change while the
file itself changes.
-\1f
-File: xemacs.info, Node: Rectangles, Next: Registers, Prev: Accumulating Text, Up: Top
-
-Rectangles
-==========
-
- The rectangle commands affect rectangular areas of text: all
-characters between a certain pair of columns, in a certain range of
-lines. Commands are provided to kill rectangles, yank killed
-rectangles, clear them out, or delete them. Rectangle commands are
-useful with text in multicolumnar formats, like code with comments at
-the right, or for changing text into or out of such formats.
-
- To specify the rectangle a command should work on, put the mark at
-one corner and point at the opposite corner. The specified rectangle is
-called the "region-rectangle" because it is controlled about the same
-way the region is controlled. Remember that a given combination of
-point and mark values can be interpreted either as specifying a region
-or as specifying a rectangle; it is up to the command that uses them to
-choose the interpretation.
-
-`M-x delete-rectangle'
- Delete the text of the region-rectangle, moving any following text
- on each line leftward to the left edge of the region-rectangle.
-
-`M-x kill-rectangle'
- Similar, but also save the contents of the region-rectangle as the
- "last killed rectangle".
-
-`M-x yank-rectangle'
- Yank the last killed rectangle with its upper left corner at point.
-
-`M-x open-rectangle'
- Insert blank space to fill the space of the region-rectangle. The
- previous contents of the region-rectangle are pushed rightward.
-
-`M-x clear-rectangle'
- Clear the region-rectangle by replacing its contents with spaces.
-
- The rectangle operations fall into two classes: commands deleting and
-moving rectangles, and commands for blank rectangles.
-
- There are two ways to get rid of the text in a rectangle: you can
-discard the text (delete it) or save it as the "last killed" rectangle.
-The commands for these two ways are `M-x delete-rectangle' and `M-x
-kill-rectangle'. In either case, the portion of each line that falls
-inside the rectangle's boundaries is deleted, causing following text
-(if any) on the line to move left.
-
- Note that "killing" a rectangle is not killing in the usual sense;
-the rectangle is not stored in the kill ring, but in a special place
-that only records the most recently killed rectangle (that is, does not
-append to a killed rectangle). Different yank commands have to be used
-and only one rectangle is stored, because yanking a rectangle is quite
-different from yanking linear text and yank-popping commands are
-difficult to make sense of.
-
- Inserting a rectangle is the opposite of deleting one. You specify
-where to put the upper left corner by putting point there. The
-rectangle's first line is inserted at point, the rectangle's second line
-is inserted at a point one line vertically down, and so on. The number
-of lines affected is determined by the height of the saved rectangle.
-
- To insert the last killed rectangle, type `M-x yank-rectangle'.
-This can be used to convert single-column lists into double-column
-lists; kill the second half of the list as a rectangle and then yank it
-beside the first line of the list.
-
- There are two commands for working with blank rectangles: `M-x
-clear-rectangle' erases existing text, and `M-x open-rectangle' inserts
-a blank rectangle. Clearing a rectangle is equivalent to deleting it
-and then inserting a blank rectangle of the same size.
-
- Rectangles can also be copied into and out of registers. *Note
-Rectangle Registers: RegRect.
-
-\1f
-File: xemacs.info, Node: Registers, Next: Display, Prev: Rectangles, Up: Top
-
-Registers
-*********
-
- XEmacs "registers" are places in which you can save text or
-positions for later use. Once you save text or a rectangle in a
-register, you can copy it into the buffer once or many times; a position
-saved in a register is used by moving point to that position.
-Rectangles can also be copied into and out of registers (*note
-Rectangles::).
-
- Each register has a name which is a single character. A register can
-store a piece of text, a rectangle, a position, a window configuration,
-or a file name, but only one thing at any given time. Whatever you
-store in a register remains there until you store something else in that
-register. To see what a register R contains, use `M-x view-register'.
-
-`M-x view-register <RET> R'
- Display a description of what register R contains.
-
- `M-x view-register' reads a register name as an argument and then
-displays the contents of the specified register.
-
-* Menu:
-
-* Position: RegPos. Saving positions in registers.
-* Text: RegText. Saving text in registers.
-* Rectangle: RegRect. Saving rectangles in registers.
-* Configurations: RegConfig. Saving window configurations in registers.
-* Files: RegFiles. File names in registers.
-* Numbers: RegNumbers. Numbers in registers.
-* Bookmarks:: Bookmarks are like registers, but persistent.
-
-\1f
-File: xemacs.info, Node: RegPos, Next: RegText, Prev: Registers, Up: Registers
-
-Saving Positions in Registers
-=============================
-
- Saving a position records a place in a buffer so that you can move
-back there later. Moving to a saved position switches to that buffer
-and moves point to that place in it.
-
-`C-x r <SPC> R'
- Save position of point in register R (`point-to-register').
-
-`C-x r j R'
- Jump to the position saved in register R (`jump-to-register').
-
- To save the current position of point in a register, choose a name R
-and type `C-x r <SPC> R'. The register R retains the position thus
-saved until you store something else in that register.
-
- The command `C-x r j R' moves point to the position recorded in
-register R. The register is not affected; it continues to record the
-same location. You can jump to the same position using the same
-register as often as you want.
-
- If you use `C-x r j' to go to a saved position, but the buffer it
-was saved from has been killed, `C-x r j' tries to create the buffer
-again by visiting the same file. Of course, this works only for buffers
-that were visiting files.
-
-\1f
-File: xemacs.info, Node: RegText, Next: RegRect, Prev: RegPos, Up: Registers
-
-Saving Text in Registers
-========================
-
- When you want to insert a copy of the same piece of text many times,
-it can be impractical to use the kill ring, since each subsequent kill
-moves the piece of text further down on the ring. It becomes hard to
-keep track of the argument needed to retrieve the same text with `C-y'.
-An alternative is to store the text in a register with `C-x r s'
-(`copy-to-register') and then retrieve it with `C-x r i'
-(`insert-register').
-
-`C-x r s R'
- Copy region into register R (`copy-to-register').
-
-`C-x r g R'
-`C-x r i R'
- Insert text contents of register R (`insert-register').
-
- `C-x r s R' stores a copy of the text of the region into the
-register named R. Given a numeric argument, `C-x r s R' deletes the
-text from the buffer as well.
-
- `C-x r i R' inserts the text from register R in the buffer. By
-default it leaves point before the text and places the mark after it.
-With a numeric argument (`C-u'), it puts point after the text and the
-mark before it.
-
-\1f
-File: xemacs.info, Node: RegRect, Next: RegConfig, Prev: RegText, Up: Registers
-
-Saving Rectangles in Registers
-==============================
-
- A register can contain a rectangle instead of lines of text. The
-rectangle is represented as a list of strings. *Note Rectangles::, for
-basic information on rectangles and how to specify rectangles in a
-buffer.
-
-`C-x r r R'
- Copy the region-rectangle into register R
- (`copy-rectangle-to-register'). With a numeric argument, delete it
- as well.
-
-`C-x r g R'
-`C-x r i R'
- Insert the rectangle stored in register R (if it contains a
- rectangle) (`insert-register').
-
- The `C-x r i R' command inserts linear text if the register
-contains that, or inserts a rectangle if the register contains one.
-
- See also the command `sort-columns', which you can think of as
-sorting a rectangle. *Note Sorting::.
-
-\1f
-File: xemacs.info, Node: RegConfig, Next: RegNumbers, Prev: RegRect, Up: Registers
-
-Saving Window Configurations in Registers
-=========================================
-
- You can save the window configuration of the selected frame in a
-register, or even the configuration of all windows in all frames, and
-restore the configuration later.
-
-`C-x r w R'
- Save the state of the selected frame's windows in register R
- (`window-configuration-to-register').
-
-`M-x frame-configuration-to-register <RET> R'
- Save the state of all frames, including all their windows, in
- register R (`frame-configuration-to-register').
-
- Use `C-x r j R' to restore a window or frame configuration. This is
-the same command used to restore a cursor position. When you restore a
-frame configuration, any existing frames not included in the
-configuration become invisible. If you wish to delete these frames
-instead, use `C-u C-x r j R'.
-
-\1f
-File: xemacs.info, Node: RegNumbers, Next: RegFiles, Prev: RegConfig, Up: Registers
-
-Keeping Numbers in Registers
-============================
-
- There are commands to store a number in a register, to insert the
-number in the buffer in decimal, and to increment it. These commands
-can be useful in keyboard macros (*note Keyboard Macros::).
-
-`C-u NUMBER C-x r n REG'
- Store NUMBER into register REG (`number-to-register').
-
-`C-u NUMBER C-x r + REG'
- Increment the number in register REG by NUMBER
- (`increment-register').
-
-`C-x r g REG'
- Insert the number from register REG into the buffer.
-
- `C-x r g' is the same command used to insert any other sort of
-register contents into the buffer.
-
-\1f
-File: xemacs.info, Node: RegFiles, Next: Bookmarks, Prev: RegNumbers, Up: Registers
-
-Keeping File Names in Registers
-===============================
-
- If you visit certain file names frequently, you can visit them more
-conveniently if you put their names in registers. Here's the Lisp code
-used to put a file name in a register:
-
- (set-register ?R '(file . NAME))
-
-For example,
-
- (set-register ?z '(file . "/usr/src/xemacs/src/ChangeLog"))
-
-puts the file name shown in register `z'.
-
- To visit the file whose name is in register R, type `C-x r j R'.
-(This is the same command used to jump to a position or restore a frame
-configuration.)
-
-\1f
-File: xemacs.info, Node: Bookmarks, Prev: RegFiles, Up: Registers
-
-Bookmarks
-=========
-
- "Bookmarks" are somewhat like registers in that they record
-positions you can jump to. Unlike registers, they have long names, and
-they persist automatically from one Emacs session to the next. The
-prototypical use of bookmarks is to record "where you were reading" in
-various files.
-
- Note: bookmark.el is distributed in edit-utils package. You need to
-install that to use bookmark facility (*note Packages::).
-
-`C-x r m <RET>'
- Set the bookmark for the visited file, at point.
-
-`C-x r m BOOKMARK <RET>'
- Set the bookmark named BOOKMARK at point (`bookmark-set').
-
-`C-x r b BOOKMARK <RET>'
- Jump to the bookmark named BOOKMARK (`bookmark-jump').
-
-`C-x r l'
- List all bookmarks (`list-bookmarks').
-
-`M-x bookmark-save'
- Save all the current bookmark values in the default bookmark file.
-
- The prototypical use for bookmarks is to record one current position
-in each of several files. So the command `C-x r m', which sets a
-bookmark, uses the visited file name as the default for the bookmark
-name. If you name each bookmark after the file it points to, then you
-can conveniently revisit any of those files with `C-x r b', and move to
-the position of the bookmark at the same time.
-
- To display a list of all your bookmarks in a separate buffer, type
-`C-x r l' (`list-bookmarks'). If you switch to that buffer, you can
-use it to edit your bookmark definitions or annotate the bookmarks.
-Type `C-h m' in that buffer for more information about its special
-editing commands.
-
- When you kill XEmacs, XEmacs offers to save your bookmark values in
-your default bookmark file, `~/.emacs.bmk', if you have changed any
-bookmark values. You can also save the bookmarks at any time with the
-`M-x bookmark-save' command. The bookmark commands load your default
-bookmark file automatically. This saving and loading is how bookmarks
-persist from one XEmacs session to the next.
-
- If you set the variable `bookmark-save-flag' to 1, then each command
-that sets a bookmark will also save your bookmarks; this way, you don't
-lose any bookmark values even if XEmacs crashes. (The value, if a
-number, says how many bookmark modifications should go by between
-saving.)
-
- Bookmark position values are saved with surrounding context, so that
-`bookmark-jump' can find the proper position even if the file is
-modified slightly. The variable `bookmark-search-size' says how many
-characters of context to record, on each side of the bookmark's
-position.
-
- Here are some additional commands for working with bookmarks:
-
-`M-x bookmark-load <RET> FILENAME <RET>'
- Load a file named FILENAME that contains a list of bookmark
- values. You can use this command, as well as `bookmark-write', to
- work with other files of bookmark values in addition to your
- default bookmark file.
-
-`M-x bookmark-write <RET> FILENAME <RET>'
- Save all the current bookmark values in the file FILENAME.
-
-`M-x bookmark-delete <RET> BOOKMARK <RET>'
- Delete the bookmark named BOOKMARK.
-
-`M-x bookmark-insert-location <RET> BOOKMARK <RET>'
- Insert in the buffer the name of the file that bookmark BOOKMARK
- points to.
-
-`M-x bookmark-insert <RET> BOOKMARK <RET>'
- Insert in the buffer the _contents_ of the file that bookmark
- BOOKMARK points to.
-
-\1f
-File: xemacs.info, Node: Display, Next: Search, Prev: Registers, Up: Top
-
-Controlling the Display
-***********************
-
- Since only part of a large buffer fits in the window, XEmacs tries
-to show the part that is likely to be interesting. The display control
-commands allow you to specify which part of the text you want to see.
-
-`C-l'
- Clear frame and redisplay, scrolling the selected window to center
- point vertically within it (`recenter').
-
-`C-v'
-`pgdn'
-`next'
- Scroll forward (a windowful or a specified number of lines)
- (`scroll-up'). On most X keyboards, you can get this
- functionality using the key labelled `Page Down', which generates
- either `next' or `pgdn'.
-
-`M-v'
-`pgup'
-`prior'
- Scroll backward (`scroll-down'). On most X keyboards, you can get
- this functionality using the key labelled `Page Up', which
- generates either `prior' or `pgup'.
-
-`ARG C-l'
- Scroll so point is on line ARG (`recenter').
-
-`C-x <'
-`C-pgdn'
-`C-next'
- Scroll text in current window to the left (`scroll-left').
-
-`C-x >'
-`C-pgup'
-`C-prior'
- Scroll to the right (`scroll-right').
-
-`C-x $'
- Make deeply indented lines invisible (`set-selective-display').
-
-* Menu:
-
-* Scrolling:: Moving text up and down in a window.
-* Horizontal Scrolling:: Moving text left and right in a window.
-* Selective Display:: Hiding lines with lots of indentation.
-* Display Vars:: Information on variables for customizing display.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Rectangles, Next: Registers, Prev: Accumulating Text, Up: Top
+
+Rectangles
+==========
+
+ The rectangle commands affect rectangular areas of text: all
+characters between a certain pair of columns, in a certain range of
+lines. Commands are provided to kill rectangles, yank killed
+rectangles, clear them out, or delete them. Rectangle commands are
+useful with text in multicolumnar formats, like code with comments at
+the right, or for changing text into or out of such formats.
+
+ To specify the rectangle a command should work on, put the mark at
+one corner and point at the opposite corner. The specified rectangle is
+called the "region-rectangle" because it is controlled about the same
+way the region is controlled. Remember that a given combination of
+point and mark values can be interpreted either as specifying a region
+or as specifying a rectangle; it is up to the command that uses them to
+choose the interpretation.
+
+`M-x delete-rectangle'
+ Delete the text of the region-rectangle, moving any following text
+ on each line leftward to the left edge of the region-rectangle.
+
+`M-x kill-rectangle'
+ Similar, but also save the contents of the region-rectangle as the
+ "last killed rectangle".
+
+`M-x yank-rectangle'
+ Yank the last killed rectangle with its upper left corner at point.
+
+`M-x open-rectangle'
+ Insert blank space to fill the space of the region-rectangle. The
+ previous contents of the region-rectangle are pushed rightward.
+
+`M-x clear-rectangle'
+ Clear the region-rectangle by replacing its contents with spaces.
+
+ The rectangle operations fall into two classes: commands deleting and
+moving rectangles, and commands for blank rectangles.
+
+ There are two ways to get rid of the text in a rectangle: you can
+discard the text (delete it) or save it as the "last killed" rectangle.
+The commands for these two ways are `M-x delete-rectangle' and `M-x
+kill-rectangle'. In either case, the portion of each line that falls
+inside the rectangle's boundaries is deleted, causing following text
+(if any) on the line to move left.
+
+ Note that "killing" a rectangle is not killing in the usual sense;
+the rectangle is not stored in the kill ring, but in a special place
+that only records the most recently killed rectangle (that is, does not
+append to a killed rectangle). Different yank commands have to be used
+and only one rectangle is stored, because yanking a rectangle is quite
+different from yanking linear text and yank-popping commands are
+difficult to make sense of.
+
+ Inserting a rectangle is the opposite of deleting one. You specify
+where to put the upper left corner by putting point there. The
+rectangle's first line is inserted at point, the rectangle's second line
+is inserted at a point one line vertically down, and so on. The number
+of lines affected is determined by the height of the saved rectangle.
+
+ To insert the last killed rectangle, type `M-x yank-rectangle'.
+This can be used to convert single-column lists into double-column
+lists; kill the second half of the list as a rectangle and then yank it
+beside the first line of the list.
+
+ There are two commands for working with blank rectangles: `M-x
+clear-rectangle' erases existing text, and `M-x open-rectangle' inserts
+a blank rectangle. Clearing a rectangle is equivalent to deleting it
+and then inserting a blank rectangle of the same size.
+
+ Rectangles can also be copied into and out of registers. *Note
+Rectangle Registers: RegRect.
+
+\1f
+File: xemacs.info, Node: Registers, Next: Display, Prev: Rectangles, Up: Top
+
+Registers
+*********
+
+ XEmacs "registers" are places in which you can save text or
+positions for later use. Once you save text or a rectangle in a
+register, you can copy it into the buffer once or many times; a position
+saved in a register is used by moving point to that position.
+Rectangles can also be copied into and out of registers (*note
+Rectangles::).
+
+ Each register has a name which is a single character. A register can
+store a piece of text, a rectangle, a position, a window configuration,
+or a file name, but only one thing at any given time. Whatever you
+store in a register remains there until you store something else in that
+register. To see what a register R contains, use `M-x view-register'.
+
+`M-x view-register <RET> R'
+ Display a description of what register R contains.
+
+ `M-x view-register' reads a register name as an argument and then
+displays the contents of the specified register.
+
+* Menu:
+
+* Position: RegPos. Saving positions in registers.
+* Text: RegText. Saving text in registers.
+* Rectangle: RegRect. Saving rectangles in registers.
+* Configurations: RegConfig. Saving window configurations in registers.
+* Files: RegFiles. File names in registers.
+* Numbers: RegNumbers. Numbers in registers.
+* Bookmarks:: Bookmarks are like registers, but persistent.
+
+\1f
+File: xemacs.info, Node: RegPos, Next: RegText, Prev: Registers, Up: Registers
+
+Saving Positions in Registers
+=============================
+
+ Saving a position records a place in a buffer so that you can move
+back there later. Moving to a saved position switches to that buffer
+and moves point to that place in it.
+
+`C-x r <SPC> R'
+ Save position of point in register R (`point-to-register').
+
+`C-x r j R'
+ Jump to the position saved in register R (`jump-to-register').
+
+ To save the current position of point in a register, choose a name R
+and type `C-x r <SPC> R'. The register R retains the position thus
+saved until you store something else in that register.
+
+ The command `C-x r j R' moves point to the position recorded in
+register R. The register is not affected; it continues to record the
+same location. You can jump to the same position using the same
+register as often as you want.
+
+ If you use `C-x r j' to go to a saved position, but the buffer it
+was saved from has been killed, `C-x r j' tries to create the buffer
+again by visiting the same file. Of course, this works only for buffers
+that were visiting files.
+
+\1f
+File: xemacs.info, Node: RegText, Next: RegRect, Prev: RegPos, Up: Registers
+
+Saving Text in Registers
+========================
+
+ When you want to insert a copy of the same piece of text many times,
+it can be impractical to use the kill ring, since each subsequent kill
+moves the piece of text further down on the ring. It becomes hard to
+keep track of the argument needed to retrieve the same text with `C-y'.
+An alternative is to store the text in a register with `C-x r s'
+(`copy-to-register') and then retrieve it with `C-x r i'
+(`insert-register').
+
+`C-x r s R'
+ Copy region into register R (`copy-to-register').
+
+`C-x r g R'
+`C-x r i R'
+ Insert text contents of register R (`insert-register').
+
+ `C-x r s R' stores a copy of the text of the region into the
+register named R. Given a numeric argument, `C-x r s R' deletes the
+text from the buffer as well.
+
+ `C-x r i R' inserts the text from register R in the buffer. By
+default it leaves point before the text and places the mark after it.
+With a numeric argument (`C-u'), it puts point after the text and the
+mark before it.
+
+\1f
+File: xemacs.info, Node: RegRect, Next: RegConfig, Prev: RegText, Up: Registers
+
+Saving Rectangles in Registers
+==============================
+
+ A register can contain a rectangle instead of lines of text. The
+rectangle is represented as a list of strings. *Note Rectangles::, for
+basic information on rectangles and how to specify rectangles in a
+buffer.
+
+`C-x r r R'
+ Copy the region-rectangle into register R
+ (`copy-rectangle-to-register'). With a numeric argument, delete it
+ as well.
+
+`C-x r g R'
+`C-x r i R'
+ Insert the rectangle stored in register R (if it contains a
+ rectangle) (`insert-register').
+
+ The `C-x r i R' command inserts linear text if the register
+contains that, or inserts a rectangle if the register contains one.
+
+ See also the command `sort-columns', which you can think of as
+sorting a rectangle. *Note Sorting::.
+
+\1f
+File: xemacs.info, Node: RegConfig, Next: RegNumbers, Prev: RegRect, Up: Registers
+
+Saving Window Configurations in Registers
+=========================================
+
+ You can save the window configuration of the selected frame in a
+register, or even the configuration of all windows in all frames, and
+restore the configuration later.
+
+`C-x r w R'
+ Save the state of the selected frame's windows in register R
+ (`window-configuration-to-register').
+
+`M-x frame-configuration-to-register <RET> R'
+ Save the state of all frames, including all their windows, in
+ register R (`frame-configuration-to-register').
+
+ Use `C-x r j R' to restore a window or frame configuration. This is
+the same command used to restore a cursor position. When you restore a
+frame configuration, any existing frames not included in the
+configuration become invisible. If you wish to delete these frames
+instead, use `C-u C-x r j R'.
+
+\1f
+File: xemacs.info, Node: RegNumbers, Next: RegFiles, Prev: RegConfig, Up: Registers
+
+Keeping Numbers in Registers
+============================
+
+ There are commands to store a number in a register, to insert the
+number in the buffer in decimal, and to increment it. These commands
+can be useful in keyboard macros (*note Keyboard Macros::).
+
+`C-u NUMBER C-x r n REG'
+ Store NUMBER into register REG (`number-to-register').
+
+`C-u NUMBER C-x r + REG'
+ Increment the number in register REG by NUMBER
+ (`increment-register').
+
+`C-x r g REG'
+ Insert the number from register REG into the buffer.
+
+ `C-x r g' is the same command used to insert any other sort of
+register contents into the buffer.
+
+\1f
+File: xemacs.info, Node: RegFiles, Next: Bookmarks, Prev: RegNumbers, Up: Registers
+
+Keeping File Names in Registers
+===============================
+
+ If you visit certain file names frequently, you can visit them more
+conveniently if you put their names in registers. Here's the Lisp code
+used to put a file name in a register:
+
+ (set-register ?R '(file . NAME))
+
+For example,
+
+ (set-register ?z '(file . "/usr/src/xemacs/src/ChangeLog"))
+
+puts the file name shown in register `z'.
+
+ To visit the file whose name is in register R, type `C-x r j R'.
+(This is the same command used to jump to a position or restore a frame
+configuration.)
+
+\1f
+File: xemacs.info, Node: Bookmarks, Prev: RegFiles, Up: Registers
+
+Bookmarks
+=========
+
+ "Bookmarks" are somewhat like registers in that they record
+positions you can jump to. Unlike registers, they have long names, and
+they persist automatically from one Emacs session to the next. The
+prototypical use of bookmarks is to record "where you were reading" in
+various files.
+
+ Note: bookmark.el is distributed in edit-utils package. You need to
+install that to use bookmark facility (*note Packages::).
+
+`C-x r m <RET>'
+ Set the bookmark for the visited file, at point.
+
+`C-x r m BOOKMARK <RET>'
+ Set the bookmark named BOOKMARK at point (`bookmark-set').
+
+`C-x r b BOOKMARK <RET>'
+ Jump to the bookmark named BOOKMARK (`bookmark-jump').
+
+`C-x r l'
+ List all bookmarks (`list-bookmarks').
+
+`M-x bookmark-save'
+ Save all the current bookmark values in the default bookmark file.
+
+ The prototypical use for bookmarks is to record one current position
+in each of several files. So the command `C-x r m', which sets a
+bookmark, uses the visited file name as the default for the bookmark
+name. If you name each bookmark after the file it points to, then you
+can conveniently revisit any of those files with `C-x r b', and move to
+the position of the bookmark at the same time.
+
+ To display a list of all your bookmarks in a separate buffer, type
+`C-x r l' (`list-bookmarks'). If you switch to that buffer, you can
+use it to edit your bookmark definitions or annotate the bookmarks.
+Type `C-h m' in that buffer for more information about its special
+editing commands.
+
+ When you kill XEmacs, XEmacs offers to save your bookmark values in
+your default bookmark file, `~/.emacs.bmk', if you have changed any
+bookmark values. You can also save the bookmarks at any time with the
+`M-x bookmark-save' command. The bookmark commands load your default
+bookmark file automatically. This saving and loading is how bookmarks
+persist from one XEmacs session to the next.
+
+ If you set the variable `bookmark-save-flag' to 1, then each command
+that sets a bookmark will also save your bookmarks; this way, you don't
+lose any bookmark values even if XEmacs crashes. (The value, if a
+number, says how many bookmark modifications should go by between
+saving.)
+
+ Bookmark position values are saved with surrounding context, so that
+`bookmark-jump' can find the proper position even if the file is
+modified slightly. The variable `bookmark-search-size' says how many
+characters of context to record, on each side of the bookmark's
+position.
+
+ Here are some additional commands for working with bookmarks:
+
+`M-x bookmark-load <RET> FILENAME <RET>'
+ Load a file named FILENAME that contains a list of bookmark
+ values. You can use this command, as well as `bookmark-write', to
+ work with other files of bookmark values in addition to your
+ default bookmark file.
+
+`M-x bookmark-write <RET> FILENAME <RET>'
+ Save all the current bookmark values in the file FILENAME.
+
+`M-x bookmark-delete <RET> BOOKMARK <RET>'
+ Delete the bookmark named BOOKMARK.
+
+`M-x bookmark-insert-location <RET> BOOKMARK <RET>'
+ Insert in the buffer the name of the file that bookmark BOOKMARK
+ points to.
+
+`M-x bookmark-insert <RET> BOOKMARK <RET>'
+ Insert in the buffer the _contents_ of the file that bookmark
+ BOOKMARK points to.
+
+\1f
+File: xemacs.info, Node: Display, Next: Search, Prev: Registers, Up: Top
+
+Controlling the Display
+***********************
+
+ Since only part of a large buffer fits in the window, XEmacs tries
+to show the part that is likely to be interesting. The display control
+commands allow you to specify which part of the text you want to see.
+
+`C-l'
+ Clear frame and redisplay, scrolling the selected window to center
+ point vertically within it (`recenter').
+
+`C-v'
+`pgdn'
+`next'
+ Scroll forward (a windowful or a specified number of lines)
+ (`scroll-up'). On most X keyboards, you can get this
+ functionality using the key labelled `Page Down', which generates
+ either `next' or `pgdn'.
+
+`M-v'
+`pgup'
+`prior'
+ Scroll backward (`scroll-down'). On most X keyboards, you can get
+ this functionality using the key labelled `Page Up', which
+ generates either `prior' or `pgup'.
+
+`ARG C-l'
+ Scroll so point is on line ARG (`recenter').
+
+`C-x <'
+`C-pgdn'
+`C-next'
+ Scroll text in current window to the left (`scroll-left').
+
+`C-x >'
+`C-pgup'
+`C-prior'
+ Scroll to the right (`scroll-right').
+
+`C-x $'
+ Make deeply indented lines invisible (`set-selective-display').
+
+* Menu:
+
+* Scrolling:: Moving text up and down in a window.
+* Horizontal Scrolling:: Moving text left and right in a window.
+* Selective Display:: Hiding lines with lots of indentation.
+* Display Vars:: Information on variables for customizing display.
+
+\1f
File: xemacs.info, Node: Scrolling, Next: Horizontal Scrolling, Prev: Display, Up: Display
Scrolling
way of incremental regexp search with `M-C-s <RET>'; similarly for
`re-search-backward' with `M-C-r <RET>'.
-\1f
-File: xemacs.info, Node: Regexps, Next: Search Case, Prev: Regexp Search, Up: Search
-
-Syntax of Regular Expressions
-=============================
-
- Regular expressions have a syntax in which a few characters are
-special constructs and the rest are "ordinary". An ordinary character
-is a simple regular expression that matches that character and nothing
-else. The special characters are `.', `*', `+', `?', `[', `]', `^',
-`$', and `\'; no new special characters will be defined in the future.
-Any other character appearing in a regular expression is ordinary,
-unless a `\' precedes it.
-
- For example, `f' is not a special character, so it is ordinary, and
-therefore `f' is a regular expression that matches the string `f' and
-no other string. (It does _not_ match the string `ff'.) Likewise, `o'
-is a regular expression that matches only `o'.
-
- Any two regular expressions A and B can be concatenated. The result
-is a regular expression that matches a string if A matches some amount
-of the beginning of that string and B matches the rest of the string.
-
- As a simple example, we can concatenate the regular expressions `f'
-and `o' to get the regular expression `fo', which matches only the
-string `fo'. Still trivial. To do something more powerful, you need
-to use one of the special characters. Here is a list of them:
-
-`. (Period)'
- is a special character that matches any single character except a
- newline. Using concatenation, we can make regular expressions
- like `a.b', which matches any three-character string that begins
- with `a' and ends with `b'.
-
-`*'
- is not a construct by itself; it is a quantifying suffix operator
- that means to repeat the preceding regular expression as many
- times as possible. In `fo*', the `*' applies to the `o', so `fo*'
- matches one `f' followed by any number of `o's. The case of zero
- `o's is allowed: `fo*' does match `f'.
-
- `*' always applies to the _smallest_ possible preceding
- expression. Thus, `fo*' has a repeating `o', not a repeating `fo'.
-
- The matcher processes a `*' construct by matching, immediately, as
- many repetitions as can be found; it is "greedy". Then it
- continues with the rest of the pattern. If that fails,
- backtracking occurs, discarding some of the matches of the
- `*'-modified construct in case that makes it possible to match the
- rest of the pattern. For example, in matching `ca*ar' against the
- string `caaar', the `a*' first tries to match all three `a's; but
- the rest of the pattern is `ar' and there is only `r' left to
- match, so this try fails. The next alternative is for `a*' to
- match only two `a's. With this choice, the rest of the regexp
- matches successfully.
-
- Nested repetition operators can be extremely slow if they specify
- backtracking loops. For example, it could take hours for the
- regular expression `\(x+y*\)*a' to match the sequence
- `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz'. The slowness is because
- Emacs must try each imaginable way of grouping the 35 `x''s before
- concluding that none of them can work. To make sure your regular
- expressions run fast, check nested repetitions carefully.
-
-`+'
- is a quantifying suffix operator similar to `*' except that the
- preceding expression must match at least once. It is also
- "greedy". So, for example, `ca+r' matches the strings `car' and
- `caaaar' but not the string `cr', whereas `ca*r' matches all three
- strings.
-
-`?'
- is a quantifying suffix operator similar to `*', except that the
- preceding expression can match either once or not at all. For
- example, `ca?r' matches `car' or `cr', but does not match anything
- else.
-
-`*?'
- works just like `*', except that rather than matching the longest
- match, it matches the shortest match. `*?' is known as a
- "non-greedy" quantifier, a regexp construct borrowed from Perl.
-
- This construct is very useful for when you want to match the text
- inside a pair of delimiters. For instance, `/\*.*?\*/' will match
- C comments in a string. This could not easily be achieved without
- the use of a non-greedy quantifier.
-
- This construct has not been available prior to XEmacs 20.4. It is
- not available in FSF Emacs.
-
-`+?'
- is the non-greedy version of `+'.
-
-`??'
- is the non-greedy version of `?'.
-
-`\{n,m\}'
- serves as an interval quantifier, analogous to `*' or `+', but
- specifies that the expression must match at least N times, but no
- more than M times. This syntax is supported by most Unix regexp
- utilities, and has been introduced to XEmacs for the version 20.3.
-
- Unfortunately, the non-greedy version of this quantifier does not
- exist currently, although it does in Perl.
-
-`[ ... ]'
- `[' begins a "character set", which is terminated by a `]'. In
- the simplest case, the characters between the two brackets form
- the set. Thus, `[ad]' matches either one `a' or one `d', and
- `[ad]*' matches any string composed of just `a's and `d's
- (including the empty string), from which it follows that `c[ad]*r'
- matches `cr', `car', `cdr', `caddaar', etc.
-
- The usual regular expression special characters are not special
- inside a character set. A completely different set of special
- characters exists inside character sets: `]', `-' and `^'.
-
- `-' is used for ranges of characters. To write a range, write two
- characters with a `-' between them. Thus, `[a-z]' matches any
- lower case letter. Ranges may be intermixed freely with individual
- characters, as in `[a-z$%.]', which matches any lower case letter
- or `$', `%', or a period.
-
- To include a `]' in a character set, make it the first character.
- For example, `[]a]' matches `]' or `a'. To include a `-', write
- `-' as the first character in the set, or put it immediately after
- a range. (You can replace one individual character C with the
- range `C-C' to make a place to put the `-'.) There is no way to
- write a set containing just `-' and `]'.
-
- To include `^' in a set, put it anywhere but at the beginning of
- the set.
-
-`[^ ... ]'
- `[^' begins a "complement character set", which matches any
- character except the ones specified. Thus, `[^a-z0-9A-Z]' matches
- all characters _except_ letters and digits.
-
- `^' is not special in a character set unless it is the first
- character. The character following the `^' is treated as if it
- were first (thus, `-' and `]' are not special there).
-
- Note that a complement character set can match a newline, unless
- newline is mentioned as one of the characters not to match.
-
-`^'
- is a special character that matches the empty string, but only at
- the beginning of a line in the text being matched. Otherwise it
- fails to match anything. Thus, `^foo' matches a `foo' that occurs
- at the beginning of a line.
-
- When matching a string instead of a buffer, `^' matches at the
- beginning of the string or after a newline character `\n'.
-
-`$'
- is similar to `^' but matches only at the end of a line. Thus,
- `x+$' matches a string of one `x' or more at the end of a line.
-
- When matching a string instead of a buffer, `$' matches at the end
- of the string or before a newline character `\n'.
-
-`\'
- has two functions: it quotes the special characters (including
- `\'), and it introduces additional special constructs.
-
- Because `\' quotes special characters, `\$' is a regular
- expression that matches only `$', and `\[' is a regular expression
- that matches only `[', and so on.
-
- *Please note:* For historical compatibility, special characters are
-treated as ordinary ones if they are in contexts where their special
-meanings make no sense. For example, `*foo' treats `*' as ordinary
-since there is no preceding expression on which the `*' can act. It is
-poor practice to depend on this behavior; quote the special character
-anyway, regardless of where it appears.
-
- For the most part, `\' followed by any character matches only that
-character. However, there are several exceptions: characters that,
-when preceded by `\', are special constructs. Such characters are
-always ordinary when encountered on their own. Here is a table of `\'
-constructs:
-
-`\|'
- specifies an alternative. Two regular expressions A and B with
- `\|' in between form an expression that matches anything that
- either A or B matches.
-
- Thus, `foo\|bar' matches either `foo' or `bar' but no other string.
-
- `\|' applies to the largest possible surrounding expressions.
- Only a surrounding `\( ... \)' grouping can limit the grouping
- power of `\|'.
-
- Full backtracking capability exists to handle multiple uses of
- `\|'.
-
-`\( ... \)'
- is a grouping construct that serves three purposes:
-
- 1. To enclose a set of `\|' alternatives for other operations.
- Thus, `\(foo\|bar\)x' matches either `foox' or `barx'.
-
- 2. To enclose an expression for a suffix operator such as `*' to
- act on. Thus, `ba\(na\)*' matches `bananana', etc., with any
- (zero or more) number of `na' strings.
-
- 3. To record a matched substring for future reference.
-
- This last application is not a consequence of the idea of a
- parenthetical grouping; it is a separate feature that happens to be
- assigned as a second meaning to the same `\( ... \)' construct
- because there is no conflict in practice between the two meanings.
- Here is an explanation of this feature:
-
-`\DIGIT'
- matches the same text that matched the DIGITth occurrence of a `\(
- ... \)' construct.
-
- In other words, after the end of a `\( ... \)' construct. the
- matcher remembers the beginning and end of the text matched by that
- construct. Then, later on in the regular expression, you can use
- `\' followed by DIGIT to match that same text, whatever it may
- have been.
-
- The strings matching the first nine `\( ... \)' constructs
- appearing in a regular expression are assigned numbers 1 through 9
- in the order that the open parentheses appear in the regular
- expression. So you can use `\1' through `\9' to refer to the text
- matched by the corresponding `\( ... \)' constructs.
-
- For example, `\(.*\)\1' matches any newline-free string that is
- composed of two identical halves. The `\(.*\)' matches the first
- half, which may be anything, but the `\1' that follows must match
- the same exact text.
-
-`\(?: ... \)'
- is called a "shy" grouping operator, and it is used just like `\(
- ... \)', except that it does not cause the matched substring to be
- recorded for future reference.
-
- This is useful when you need a lot of grouping `\( ... \)'
- constructs, but only want to remember one or two - or if you have
- more than nine groupings and need to use backreferences to refer to
- the groupings at the end.
-
- Using `\(?: ... \)' rather than `\( ... \)' when you don't need
- the captured substrings ought to speed up your programs some,
- since it shortens the code path followed by the regular expression
- engine, as well as the amount of memory allocation and string
- copying it must do. The actual performance gain to be observed
- has not been measured or quantified as of this writing.
-
- The shy grouping operator has been borrowed from Perl, and has not
- been available prior to XEmacs 20.3, nor is it available in FSF
- Emacs.
-
-`\w'
- matches any word-constituent character. The editor syntax table
- determines which characters these are. *Note Syntax::.
-
-`\W'
- matches any character that is not a word constituent.
-
-`\sCODE'
- matches any character whose syntax is CODE. Here CODE is a
- character that represents a syntax code: thus, `w' for word
- constituent, `-' for whitespace, `(' for open parenthesis, etc.
- *Note Syntax::, for a list of syntax codes and the characters that
- stand for them.
-
-`\SCODE'
- matches any character whose syntax is not CODE.
-
- The following regular expression constructs match the empty
-string--that is, they don't use up any characters--but whether they
-match depends on the context.
-
-`\`'
- matches the empty string, but only at the beginning of the buffer
- or string being matched against.
-
-`\''
- matches the empty string, but only at the end of the buffer or
- string being matched against.
-
-`\='
- matches the empty string, but only at point. (This construct is
- not defined when matching against a string.)
-
-`\b'
- matches the empty string, but only at the beginning or end of a
- word. Thus, `\bfoo\b' matches any occurrence of `foo' as a
- separate word. `\bballs?\b' matches `ball' or `balls' as a
- separate word.
-
-`\B'
- matches the empty string, but _not_ at the beginning or end of a
- word.
-
-`\<'
- matches the empty string, but only at the beginning of a word.
-
-`\>'
- matches the empty string, but only at the end of a word.
-
- Here is a complicated regexp used by Emacs to recognize the end of a
-sentence together with any whitespace that follows. It is given in Lisp
-syntax to enable you to distinguish the spaces from the tab characters.
-In Lisp syntax, the string constant begins and ends with a
-double-quote. `\"' stands for a double-quote as part of the regexp,
-`\\' for a backslash as part of the regexp, `\t' for a tab and `\n' for
-a newline.
-
- "[.?!][]\"')]*\\($\\|\t\\| \\)[ \t\n]*"
-
-This regexp contains four parts: a character set matching period, `?'
-or `!'; a character set matching close-brackets, quotes or parentheses,
-repeated any number of times; an alternative in backslash-parentheses
-that matches end-of-line, a tab or two spaces; and a character set
-matching whitespace characters, repeated any number of times.
-
-\1f
-File: xemacs.info, Node: Search Case, Next: Replace, Prev: Regexps, Up: Search
-
-Searching and Case
-==================
-
- All searches in Emacs normally ignore the case of the text they are
-searching through; if you specify searching for `FOO', `Foo' and `foo'
-are also considered a match. Regexps, and in particular character
-sets, are included: `[aB]' matches `a' or `A' or `b' or `B'.
-
- If you want a case-sensitive search, set the variable
-`case-fold-search' to `nil'. Then all letters must match exactly,
-including case. `case-fold-search' is a per-buffer variable; altering
-it affects only the current buffer, but there is a default value which
-you can change as well. *Note Locals::. You can also use Case
-Sensitive Search from the Options menu on your screen.
-
-\1f
-File: xemacs.info, Node: Replace, Next: Other Repeating Search, Prev: Search Case, Up: Search
-
-Replacement Commands
-====================
-
- Global search-and-replace operations are not needed as often in
-Emacs as they are in other editors, but they are available. In
-addition to the simple `replace-string' command which is like that
-found in most editors, there is a `query-replace' command which asks
-you, for each occurrence of a pattern, whether to replace it.
-
- The replace commands all replace one string (or regexp) with one
-replacement string. It is possible to perform several replacements in
-parallel using the command `expand-region-abbrevs'. *Note Expanding
-Abbrevs::.
-
-* Menu:
-
-* Unconditional Replace:: Replacing all matches for a string.
-* Regexp Replace:: Replacing all matches for a regexp.
-* Replacement and Case:: How replacements preserve case of letters.
-* Query Replace:: How to use querying.
-
-\1f
-File: xemacs.info, Node: Unconditional Replace, Next: Regexp Replace, Prev: Replace, Up: Replace
-
-Unconditional Replacement
--------------------------
-
-`M-x replace-string <RET> STRING <RET> NEWSTRING <RET>'
- Replace every occurrence of STRING with NEWSTRING.
-
-`M-x replace-regexp <RET> REGEXP <RET> NEWSTRING <RET>'
- Replace every match for REGEXP with NEWSTRING.
-
- To replace every instance of `foo' after point with `bar', use the
-command `M-x replace-string' with the two arguments `foo' and `bar'.
-Replacement occurs only after point: if you want to cover the whole
-buffer you must go to the beginning first. By default, all occurrences
-up to the end of the buffer are replaced. To limit replacement to part
-of the buffer, narrow to that part of the buffer before doing the
-replacement (*note Narrowing::).
-
- When `replace-string' exits, point is left at the last occurrence
-replaced. The value of point when the `replace-string' command was
-issued is remembered on the mark ring; `C-u C-<SPC>' moves back there.
-
- A numeric argument restricts replacement to matches that are
-surrounded by word boundaries.
-
-\1f
-File: xemacs.info, Node: Regexp Replace, Next: Replacement and Case, Prev: Unconditional Replace, Up: Replace
-
-Regexp Replacement
-------------------
-
- `replace-string' replaces exact matches for a single string. The
-similar command `replace-regexp' replaces any match for a specified
-pattern.
-
- In `replace-regexp', the NEWSTRING need not be constant. It can
-refer to all or part of what is matched by the REGEXP. `\&' in
-NEWSTRING stands for the entire text being replaced. `\D' in
-NEWSTRING, where D is a digit, stands for whatever matched the D'th
-parenthesized grouping in REGEXP. For example,
-
- M-x replace-regexp <RET> c[ad]+r <RET> \&-safe <RET>
-
-would replace (for example) `cadr' with `cadr-safe' and `cddr' with
-`cddr-safe'.
-
- M-x replace-regexp <RET> \(c[ad]+r\)-safe <RET> \1 <RET>
-
-would perform exactly the opposite replacements. To include a `\' in
-the text to replace with, you must give `\\'.
-
-\1f
-File: xemacs.info, Node: Replacement and Case, Next: Query Replace, Prev: Regexp Replace, Up: Replace
-
-Replace Commands and Case
--------------------------
-
- If the arguments to a replace command are in lower case, the command
-preserves case when it makes a replacement. Thus, the following
-command:
-
- M-x replace-string <RET> foo <RET> bar <RET>
-
-replaces a lower-case `foo' with a lower case `bar', `FOO' with `BAR',
-and `Foo' with `Bar'. If upper-case letters are used in the second
-argument, they remain upper-case every time that argument is inserted.
-If upper-case letters are used in the first argument, the second
-argument is always substituted exactly as given, with no case
-conversion. Likewise, if the variable `case-replace' is set to `nil',
-replacement is done without case conversion. If `case-fold-search' is
-set to `nil', case is significant in matching occurrences of `foo' to
-replace; also, case conversion of the replacement string is not done.
-
-\1f
-File: xemacs.info, Node: Query Replace, Prev: Replacement and Case, Up: Replace
-
-Query Replace
--------------
-
-`M-% STRING <RET> NEWSTRING <RET>'
-`M-x query-replace <RET> STRING <RET> NEWSTRING <RET>'
- Replace some occurrences of STRING with NEWSTRING.
-
-`M-x query-replace-regexp <RET> REGEXP <RET> NEWSTRING <RET>'
- Replace some matches for REGEXP with NEWSTRING.
-
- If you want to change only some of the occurrences of `foo' to
-`bar', not all of them, you can use `query-replace' instead of `M-%'.
-This command finds occurrences of `foo' one by one, displays each
-occurrence, and asks you whether to replace it. A numeric argument to
-`query-replace' tells it to consider only occurrences that are bounded
-by word-delimiter characters.
-
- Aside from querying, `query-replace' works just like
-`replace-string', and `query-replace-regexp' works just like
-`replace-regexp'.
-
- The things you can type when you are shown an occurrence of STRING
-or a match for REGEXP are:
-
-`<SPC>'
- to replace the occurrence with NEWSTRING. This preserves case,
- just like `replace-string', provided `case-replace' is non-`nil',
- as it normally is.
-
-`<DEL>'
- to skip to the next occurrence without replacing this one.
-
-`, (Comma)'
- to replace this occurrence and display the result. You are then
- prompted for another input character. However, since the
- replacement has already been made, <DEL> and <SPC> are equivalent.
- At this point, you can type `C-r' (see below) to alter the
- replaced text. To undo the replacement, you can type `C-x u'.
- This exits the `query-replace'. If you want to do further
- replacement you must use `C-x ESC' to restart (*note Repetition::).
-
-`<ESC>'
- to exit without doing any more replacements.
-
-`. (Period)'
- to replace this occurrence and then exit.
-
-`!'
- to replace all remaining occurrences without asking again.
-
-`^'
- to go back to the location of the previous occurrence (or what
- used to be an occurrence), in case you changed it by mistake.
- This works by popping the mark ring. Only one `^' in a row is
- allowed, because only one previous replacement location is kept
- during `query-replace'.
-
-`C-r'
- to enter a recursive editing level, in case the occurrence needs
- to be edited rather than just replaced with NEWSTRING. When you
- are done, exit the recursive editing level with `C-M-c' and the
- next occurrence will be displayed. *Note Recursive Edit::.
-
-`C-w'
- to delete the occurrence, and then enter a recursive editing level
- as in `C-r'. Use the recursive edit to insert text to replace the
- deleted occurrence of STRING. When done, exit the recursive
- editing level with `C-M-c' and the next occurrence will be
- displayed.
-
-`C-l'
- to redisplay the screen and then give another answer.
-
-`C-h'
- to display a message summarizing these options, then give another
- answer.
-
- If you type any other character, Emacs exits the `query-replace', and
-executes the character as a command. To restart the `query-replace',
-use `C-x <ESC>', which repeats the `query-replace' because it used the
-minibuffer to read its arguments. *Note C-x ESC: Repetition.
-
-\1f
-File: xemacs.info, Node: Other Repeating Search, Prev: Replace, Up: Search
-
-Other Search-and-Loop Commands
-==============================
-
- Here are some other commands that find matches for a regular
-expression. They all operate from point to the end of the buffer.
-
-`M-x occur'
- Print each line that follows point and contains a match for the
- specified regexp. A numeric argument specifies the number of
- context lines to print before and after each matching line; the
- default is none.
-
- The buffer `*Occur*' containing the output serves as a menu for
- finding occurrences in their original context. Find an occurrence
- as listed in `*Occur*', position point there, and type `C-c C-c';
- this switches to the buffer that was searched and moves point to
- the original of the same occurrence.
-
-`M-x list-matching-lines'
- Synonym for `M-x occur'.
-
-`M-x count-matches'
- Print the number of matches following point for the specified
- regexp.
-
-`M-x delete-non-matching-lines'
- Delete each line that follows point and does not contain a match
- for the specified regexp.
-
-`M-x delete-matching-lines'
- Delete each line that follows point and contains a match for the
- specified regexp.
-
-\1f
-File: xemacs.info, Node: Fixit, Next: Files, Prev: Search, Up: Top
-
-Commands for Fixing Typos
-*************************
-
- This chapter describes commands that are especially useful when you
-catch a mistake in your text just after you have made it, or when you
-change your mind while composing text on line.
-
-* Menu:
-
-* Kill Errors:: Commands to kill a batch of recently entered text.
-* Transpose:: Exchanging two characters, words, lines, lists...
-* Fixing Case:: Correcting case of last word entered.
-* Spelling:: Apply spelling checker to a word, or a whole file.
-
-\1f
-File: xemacs.info, Node: Kill Errors, Next: Transpose, Prev: Fixit, Up: Fixit
-
-Killing Your Mistakes
-=====================
-
-`<DEL>'
- Delete last character (`delete-backward-char').
-
-`M-<DEL>'
- Kill last word (`backward-kill-word').
-
-`C-x <DEL>'
- Kill to beginning of sentence (`backward-kill-sentence').
-
- The <DEL> character (`delete-backward-char') is the most important
-correction command. When used among graphic (self-inserting)
-characters, it can be thought of as canceling the last character typed.
-
- When your mistake is longer than a couple of characters, it might be
-more convenient to use `M-<DEL>' or `C-x <DEL>'. `M-<DEL>' kills back
-to the start of the last word, and `C-x <DEL>' kills back to the start
-of the last sentence. `C-x <DEL>' is particularly useful when you are
-thinking of what to write as you type it, in case you change your mind
-about phrasing. `M-<DEL>' and `C-x <DEL>' save the killed text for
-`C-y' and `M-y' to retrieve. *Note Yanking::.
-
- `M-<DEL>' is often useful even when you have typed only a few
-characters wrong, if you know you are confused in your typing and aren't
-sure exactly what you typed. At such a time, you cannot correct with
-<DEL> except by looking at the screen to see what you did. It requires
-less thought to kill the whole word and start over.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Regexps, Next: Search Case, Prev: Regexp Search, Up: Search
+
+Syntax of Regular Expressions
+=============================
+
+ Regular expressions have a syntax in which a few characters are
+special constructs and the rest are "ordinary". An ordinary character
+is a simple regular expression that matches that character and nothing
+else. The special characters are `.', `*', `+', `?', `[', `]', `^',
+`$', and `\'; no new special characters will be defined in the future.
+Any other character appearing in a regular expression is ordinary,
+unless a `\' precedes it.
+
+ For example, `f' is not a special character, so it is ordinary, and
+therefore `f' is a regular expression that matches the string `f' and
+no other string. (It does _not_ match the string `ff'.) Likewise, `o'
+is a regular expression that matches only `o'.
+
+ Any two regular expressions A and B can be concatenated. The result
+is a regular expression that matches a string if A matches some amount
+of the beginning of that string and B matches the rest of the string.
+
+ As a simple example, we can concatenate the regular expressions `f'
+and `o' to get the regular expression `fo', which matches only the
+string `fo'. Still trivial. To do something more powerful, you need
+to use one of the special characters. Here is a list of them:
+
+`. (Period)'
+ is a special character that matches any single character except a
+ newline. Using concatenation, we can make regular expressions
+ like `a.b', which matches any three-character string that begins
+ with `a' and ends with `b'.
+
+`*'
+ is not a construct by itself; it is a quantifying suffix operator
+ that means to repeat the preceding regular expression as many
+ times as possible. In `fo*', the `*' applies to the `o', so `fo*'
+ matches one `f' followed by any number of `o's. The case of zero
+ `o's is allowed: `fo*' does match `f'.
+
+ `*' always applies to the _smallest_ possible preceding
+ expression. Thus, `fo*' has a repeating `o', not a repeating `fo'.
+
+ The matcher processes a `*' construct by matching, immediately, as
+ many repetitions as can be found; it is "greedy". Then it
+ continues with the rest of the pattern. If that fails,
+ backtracking occurs, discarding some of the matches of the
+ `*'-modified construct in case that makes it possible to match the
+ rest of the pattern. For example, in matching `ca*ar' against the
+ string `caaar', the `a*' first tries to match all three `a's; but
+ the rest of the pattern is `ar' and there is only `r' left to
+ match, so this try fails. The next alternative is for `a*' to
+ match only two `a's. With this choice, the rest of the regexp
+ matches successfully.
+
+ Nested repetition operators can be extremely slow if they specify
+ backtracking loops. For example, it could take hours for the
+ regular expression `\(x+y*\)*a' to match the sequence
+ `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz'. The slowness is because
+ Emacs must try each imaginable way of grouping the 35 `x''s before
+ concluding that none of them can work. To make sure your regular
+ expressions run fast, check nested repetitions carefully.
+
+`+'
+ is a quantifying suffix operator similar to `*' except that the
+ preceding expression must match at least once. It is also
+ "greedy". So, for example, `ca+r' matches the strings `car' and
+ `caaaar' but not the string `cr', whereas `ca*r' matches all three
+ strings.
+
+`?'
+ is a quantifying suffix operator similar to `*', except that the
+ preceding expression can match either once or not at all. For
+ example, `ca?r' matches `car' or `cr', but does not match anything
+ else.
+
+`*?'
+ works just like `*', except that rather than matching the longest
+ match, it matches the shortest match. `*?' is known as a
+ "non-greedy" quantifier, a regexp construct borrowed from Perl.
+
+ This construct is very useful for when you want to match the text
+ inside a pair of delimiters. For instance, `/\*.*?\*/' will match
+ C comments in a string. This could not easily be achieved without
+ the use of a non-greedy quantifier.
+
+ This construct has not been available prior to XEmacs 20.4. It is
+ not available in FSF Emacs.
+
+`+?'
+ is the non-greedy version of `+'.
+
+`??'
+ is the non-greedy version of `?'.
+
+`\{n,m\}'
+ serves as an interval quantifier, analogous to `*' or `+', but
+ specifies that the expression must match at least N times, but no
+ more than M times. This syntax is supported by most Unix regexp
+ utilities, and has been introduced to XEmacs for the version 20.3.
+
+ Unfortunately, the non-greedy version of this quantifier does not
+ exist currently, although it does in Perl.
+
+`[ ... ]'
+ `[' begins a "character set", which is terminated by a `]'. In
+ the simplest case, the characters between the two brackets form
+ the set. Thus, `[ad]' matches either one `a' or one `d', and
+ `[ad]*' matches any string composed of just `a's and `d's
+ (including the empty string), from which it follows that `c[ad]*r'
+ matches `cr', `car', `cdr', `caddaar', etc.
+
+ The usual regular expression special characters are not special
+ inside a character set. A completely different set of special
+ characters exists inside character sets: `]', `-' and `^'.
+
+ `-' is used for ranges of characters. To write a range, write two
+ characters with a `-' between them. Thus, `[a-z]' matches any
+ lower case letter. Ranges may be intermixed freely with individual
+ characters, as in `[a-z$%.]', which matches any lower case letter
+ or `$', `%', or a period.
+
+ To include a `]' in a character set, make it the first character.
+ For example, `[]a]' matches `]' or `a'. To include a `-', write
+ `-' as the first character in the set, or put it immediately after
+ a range. (You can replace one individual character C with the
+ range `C-C' to make a place to put the `-'.) There is no way to
+ write a set containing just `-' and `]'.
+
+ To include `^' in a set, put it anywhere but at the beginning of
+ the set.
+
+`[^ ... ]'
+ `[^' begins a "complement character set", which matches any
+ character except the ones specified. Thus, `[^a-z0-9A-Z]' matches
+ all characters _except_ letters and digits.
+
+ `^' is not special in a character set unless it is the first
+ character. The character following the `^' is treated as if it
+ were first (thus, `-' and `]' are not special there).
+
+ Note that a complement character set can match a newline, unless
+ newline is mentioned as one of the characters not to match.
+
+`^'
+ is a special character that matches the empty string, but only at
+ the beginning of a line in the text being matched. Otherwise it
+ fails to match anything. Thus, `^foo' matches a `foo' that occurs
+ at the beginning of a line.
+
+ When matching a string instead of a buffer, `^' matches at the
+ beginning of the string or after a newline character `\n'.
+
+`$'
+ is similar to `^' but matches only at the end of a line. Thus,
+ `x+$' matches a string of one `x' or more at the end of a line.
+
+ When matching a string instead of a buffer, `$' matches at the end
+ of the string or before a newline character `\n'.
+
+`\'
+ has two functions: it quotes the special characters (including
+ `\'), and it introduces additional special constructs.
+
+ Because `\' quotes special characters, `\$' is a regular
+ expression that matches only `$', and `\[' is a regular expression
+ that matches only `[', and so on.
+
+ *Please note:* For historical compatibility, special characters are
+treated as ordinary ones if they are in contexts where their special
+meanings make no sense. For example, `*foo' treats `*' as ordinary
+since there is no preceding expression on which the `*' can act. It is
+poor practice to depend on this behavior; quote the special character
+anyway, regardless of where it appears.
+
+ For the most part, `\' followed by any character matches only that
+character. However, there are several exceptions: characters that,
+when preceded by `\', are special constructs. Such characters are
+always ordinary when encountered on their own. Here is a table of `\'
+constructs:
+
+`\|'
+ specifies an alternative. Two regular expressions A and B with
+ `\|' in between form an expression that matches anything that
+ either A or B matches.
+
+ Thus, `foo\|bar' matches either `foo' or `bar' but no other string.
+
+ `\|' applies to the largest possible surrounding expressions.
+ Only a surrounding `\( ... \)' grouping can limit the grouping
+ power of `\|'.
+
+ Full backtracking capability exists to handle multiple uses of
+ `\|'.
+
+`\( ... \)'
+ is a grouping construct that serves three purposes:
+
+ 1. To enclose a set of `\|' alternatives for other operations.
+ Thus, `\(foo\|bar\)x' matches either `foox' or `barx'.
+
+ 2. To enclose an expression for a suffix operator such as `*' to
+ act on. Thus, `ba\(na\)*' matches `bananana', etc., with any
+ (zero or more) number of `na' strings.
+
+ 3. To record a matched substring for future reference.
+
+ This last application is not a consequence of the idea of a
+ parenthetical grouping; it is a separate feature that happens to be
+ assigned as a second meaning to the same `\( ... \)' construct
+ because there is no conflict in practice between the two meanings.
+ Here is an explanation of this feature:
+
+`\DIGIT'
+ matches the same text that matched the DIGITth occurrence of a `\(
+ ... \)' construct.
+
+ In other words, after the end of a `\( ... \)' construct. the
+ matcher remembers the beginning and end of the text matched by that
+ construct. Then, later on in the regular expression, you can use
+ `\' followed by DIGIT to match that same text, whatever it may
+ have been.
+
+ The strings matching the first nine `\( ... \)' constructs
+ appearing in a regular expression are assigned numbers 1 through 9
+ in the order that the open parentheses appear in the regular
+ expression. So you can use `\1' through `\9' to refer to the text
+ matched by the corresponding `\( ... \)' constructs.
+
+ For example, `\(.*\)\1' matches any newline-free string that is
+ composed of two identical halves. The `\(.*\)' matches the first
+ half, which may be anything, but the `\1' that follows must match
+ the same exact text.
+
+`\(?: ... \)'
+ is called a "shy" grouping operator, and it is used just like `\(
+ ... \)', except that it does not cause the matched substring to be
+ recorded for future reference.
+
+ This is useful when you need a lot of grouping `\( ... \)'
+ constructs, but only want to remember one or two - or if you have
+ more than nine groupings and need to use backreferences to refer to
+ the groupings at the end.
+
+ Using `\(?: ... \)' rather than `\( ... \)' when you don't need
+ the captured substrings ought to speed up your programs some,
+ since it shortens the code path followed by the regular expression
+ engine, as well as the amount of memory allocation and string
+ copying it must do. The actual performance gain to be observed
+ has not been measured or quantified as of this writing.
+
+ The shy grouping operator has been borrowed from Perl, and has not
+ been available prior to XEmacs 20.3, nor is it available in FSF
+ Emacs.
+
+`\w'
+ matches any word-constituent character. The editor syntax table
+ determines which characters these are. *Note Syntax::.
+
+`\W'
+ matches any character that is not a word constituent.
+
+`\sCODE'
+ matches any character whose syntax is CODE. Here CODE is a
+ character that represents a syntax code: thus, `w' for word
+ constituent, `-' for whitespace, `(' for open parenthesis, etc.
+ *Note Syntax::, for a list of syntax codes and the characters that
+ stand for them.
+
+`\SCODE'
+ matches any character whose syntax is not CODE.
+
+ The following regular expression constructs match the empty
+string--that is, they don't use up any characters--but whether they
+match depends on the context.
+
+`\`'
+ matches the empty string, but only at the beginning of the buffer
+ or string being matched against.
+
+`\''
+ matches the empty string, but only at the end of the buffer or
+ string being matched against.
+
+`\='
+ matches the empty string, but only at point. (This construct is
+ not defined when matching against a string.)
+
+`\b'
+ matches the empty string, but only at the beginning or end of a
+ word. Thus, `\bfoo\b' matches any occurrence of `foo' as a
+ separate word. `\bballs?\b' matches `ball' or `balls' as a
+ separate word.
+
+`\B'
+ matches the empty string, but _not_ at the beginning or end of a
+ word.
+
+`\<'
+ matches the empty string, but only at the beginning of a word.
+
+`\>'
+ matches the empty string, but only at the end of a word.
+
+ Here is a complicated regexp used by Emacs to recognize the end of a
+sentence together with any whitespace that follows. It is given in Lisp
+syntax to enable you to distinguish the spaces from the tab characters.
+In Lisp syntax, the string constant begins and ends with a
+double-quote. `\"' stands for a double-quote as part of the regexp,
+`\\' for a backslash as part of the regexp, `\t' for a tab and `\n' for
+a newline.
+
+ "[.?!][]\"')]*\\($\\|\t\\| \\)[ \t\n]*"
+
+This regexp contains four parts: a character set matching period, `?'
+or `!'; a character set matching close-brackets, quotes or parentheses,
+repeated any number of times; an alternative in backslash-parentheses
+that matches end-of-line, a tab or two spaces; and a character set
+matching whitespace characters, repeated any number of times.
+
+\1f
+File: xemacs.info, Node: Search Case, Next: Replace, Prev: Regexps, Up: Search
+
+Searching and Case
+==================
+
+ All searches in Emacs normally ignore the case of the text they are
+searching through; if you specify searching for `FOO', `Foo' and `foo'
+are also considered a match. Regexps, and in particular character
+sets, are included: `[aB]' matches `a' or `A' or `b' or `B'.
+
+ If you want a case-sensitive search, set the variable
+`case-fold-search' to `nil'. Then all letters must match exactly,
+including case. `case-fold-search' is a per-buffer variable; altering
+it affects only the current buffer, but there is a default value which
+you can change as well. *Note Locals::. You can also use Case
+Sensitive Search from the Options menu on your screen.
+
+\1f
+File: xemacs.info, Node: Replace, Next: Other Repeating Search, Prev: Search Case, Up: Search
+
+Replacement Commands
+====================
+
+ Global search-and-replace operations are not needed as often in
+Emacs as they are in other editors, but they are available. In
+addition to the simple `replace-string' command which is like that
+found in most editors, there is a `query-replace' command which asks
+you, for each occurrence of a pattern, whether to replace it.
+
+ The replace commands all replace one string (or regexp) with one
+replacement string. It is possible to perform several replacements in
+parallel using the command `expand-region-abbrevs'. *Note Expanding
+Abbrevs::.
+
+* Menu:
+
+* Unconditional Replace:: Replacing all matches for a string.
+* Regexp Replace:: Replacing all matches for a regexp.
+* Replacement and Case:: How replacements preserve case of letters.
+* Query Replace:: How to use querying.
+
+\1f
+File: xemacs.info, Node: Unconditional Replace, Next: Regexp Replace, Prev: Replace, Up: Replace
+
+Unconditional Replacement
+-------------------------
+
+`M-x replace-string <RET> STRING <RET> NEWSTRING <RET>'
+ Replace every occurrence of STRING with NEWSTRING.
+
+`M-x replace-regexp <RET> REGEXP <RET> NEWSTRING <RET>'
+ Replace every match for REGEXP with NEWSTRING.
+
+ To replace every instance of `foo' after point with `bar', use the
+command `M-x replace-string' with the two arguments `foo' and `bar'.
+Replacement occurs only after point: if you want to cover the whole
+buffer you must go to the beginning first. By default, all occurrences
+up to the end of the buffer are replaced. To limit replacement to part
+of the buffer, narrow to that part of the buffer before doing the
+replacement (*note Narrowing::).
+
+ When `replace-string' exits, point is left at the last occurrence
+replaced. The value of point when the `replace-string' command was
+issued is remembered on the mark ring; `C-u C-<SPC>' moves back there.
+
+ A numeric argument restricts replacement to matches that are
+surrounded by word boundaries.
+
+\1f
+File: xemacs.info, Node: Regexp Replace, Next: Replacement and Case, Prev: Unconditional Replace, Up: Replace
+
+Regexp Replacement
+------------------
+
+ `replace-string' replaces exact matches for a single string. The
+similar command `replace-regexp' replaces any match for a specified
+pattern.
+
+ In `replace-regexp', the NEWSTRING need not be constant. It can
+refer to all or part of what is matched by the REGEXP. `\&' in
+NEWSTRING stands for the entire text being replaced. `\D' in
+NEWSTRING, where D is a digit, stands for whatever matched the D'th
+parenthesized grouping in REGEXP. For example,
+
+ M-x replace-regexp <RET> c[ad]+r <RET> \&-safe <RET>
+
+would replace (for example) `cadr' with `cadr-safe' and `cddr' with
+`cddr-safe'.
+
+ M-x replace-regexp <RET> \(c[ad]+r\)-safe <RET> \1 <RET>
+
+would perform exactly the opposite replacements. To include a `\' in
+the text to replace with, you must give `\\'.
+
+\1f
+File: xemacs.info, Node: Replacement and Case, Next: Query Replace, Prev: Regexp Replace, Up: Replace
+
+Replace Commands and Case
+-------------------------
+
+ If the arguments to a replace command are in lower case, the command
+preserves case when it makes a replacement. Thus, the following
+command:
+
+ M-x replace-string <RET> foo <RET> bar <RET>
+
+replaces a lower-case `foo' with a lower case `bar', `FOO' with `BAR',
+and `Foo' with `Bar'. If upper-case letters are used in the second
+argument, they remain upper-case every time that argument is inserted.
+If upper-case letters are used in the first argument, the second
+argument is always substituted exactly as given, with no case
+conversion. Likewise, if the variable `case-replace' is set to `nil',
+replacement is done without case conversion. If `case-fold-search' is
+set to `nil', case is significant in matching occurrences of `foo' to
+replace; also, case conversion of the replacement string is not done.
+
+\1f
+File: xemacs.info, Node: Query Replace, Prev: Replacement and Case, Up: Replace
+
+Query Replace
+-------------
+
+`M-% STRING <RET> NEWSTRING <RET>'
+`M-x query-replace <RET> STRING <RET> NEWSTRING <RET>'
+ Replace some occurrences of STRING with NEWSTRING.
+
+`M-x query-replace-regexp <RET> REGEXP <RET> NEWSTRING <RET>'
+ Replace some matches for REGEXP with NEWSTRING.
+
+ If you want to change only some of the occurrences of `foo' to
+`bar', not all of them, you can use `query-replace' instead of `M-%'.
+This command finds occurrences of `foo' one by one, displays each
+occurrence, and asks you whether to replace it. A numeric argument to
+`query-replace' tells it to consider only occurrences that are bounded
+by word-delimiter characters.
+
+ Aside from querying, `query-replace' works just like
+`replace-string', and `query-replace-regexp' works just like
+`replace-regexp'.
+
+ The things you can type when you are shown an occurrence of STRING
+or a match for REGEXP are:
+
+`<SPC>'
+ to replace the occurrence with NEWSTRING. This preserves case,
+ just like `replace-string', provided `case-replace' is non-`nil',
+ as it normally is.
+
+`<DEL>'
+ to skip to the next occurrence without replacing this one.
+
+`, (Comma)'
+ to replace this occurrence and display the result. You are then
+ prompted for another input character. However, since the
+ replacement has already been made, <DEL> and <SPC> are equivalent.
+ At this point, you can type `C-r' (see below) to alter the
+ replaced text. To undo the replacement, you can type `C-x u'.
+ This exits the `query-replace'. If you want to do further
+ replacement you must use `C-x ESC' to restart (*note Repetition::).
+
+`<ESC>'
+ to exit without doing any more replacements.
+
+`. (Period)'
+ to replace this occurrence and then exit.
+
+`!'
+ to replace all remaining occurrences without asking again.
+
+`^'
+ to go back to the location of the previous occurrence (or what
+ used to be an occurrence), in case you changed it by mistake.
+ This works by popping the mark ring. Only one `^' in a row is
+ allowed, because only one previous replacement location is kept
+ during `query-replace'.
+
+`C-r'
+ to enter a recursive editing level, in case the occurrence needs
+ to be edited rather than just replaced with NEWSTRING. When you
+ are done, exit the recursive editing level with `C-M-c' and the
+ next occurrence will be displayed. *Note Recursive Edit::.
+
+`C-w'
+ to delete the occurrence, and then enter a recursive editing level
+ as in `C-r'. Use the recursive edit to insert text to replace the
+ deleted occurrence of STRING. When done, exit the recursive
+ editing level with `C-M-c' and the next occurrence will be
+ displayed.
+
+`C-l'
+ to redisplay the screen and then give another answer.
+
+`C-h'
+ to display a message summarizing these options, then give another
+ answer.
+
+ If you type any other character, Emacs exits the `query-replace', and
+executes the character as a command. To restart the `query-replace',
+use `C-x <ESC>', which repeats the `query-replace' because it used the
+minibuffer to read its arguments. *Note C-x ESC: Repetition.
+
+\1f
+File: xemacs.info, Node: Other Repeating Search, Prev: Replace, Up: Search
+
+Other Search-and-Loop Commands
+==============================
+
+ Here are some other commands that find matches for a regular
+expression. They all operate from point to the end of the buffer.
+
+`M-x occur'
+ Print each line that follows point and contains a match for the
+ specified regexp. A numeric argument specifies the number of
+ context lines to print before and after each matching line; the
+ default is none.
+
+ The buffer `*Occur*' containing the output serves as a menu for
+ finding occurrences in their original context. Find an occurrence
+ as listed in `*Occur*', position point there, and type `C-c C-c';
+ this switches to the buffer that was searched and moves point to
+ the original of the same occurrence.
+
+`M-x list-matching-lines'
+ Synonym for `M-x occur'.
+
+`M-x count-matches'
+ Print the number of matches following point for the specified
+ regexp.
+
+`M-x delete-non-matching-lines'
+ Delete each line that follows point and does not contain a match
+ for the specified regexp.
+
+`M-x delete-matching-lines'
+ Delete each line that follows point and contains a match for the
+ specified regexp.
+
+\1f
+File: xemacs.info, Node: Fixit, Next: Files, Prev: Search, Up: Top
+
+Commands for Fixing Typos
+*************************
+
+ This chapter describes commands that are especially useful when you
+catch a mistake in your text just after you have made it, or when you
+change your mind while composing text on line.
+
+* Menu:
+
+* Kill Errors:: Commands to kill a batch of recently entered text.
+* Transpose:: Exchanging two characters, words, lines, lists...
+* Fixing Case:: Correcting case of last word entered.
+* Spelling:: Apply spelling checker to a word, or a whole file.
+
+\1f
+File: xemacs.info, Node: Kill Errors, Next: Transpose, Prev: Fixit, Up: Fixit
+
+Killing Your Mistakes
+=====================
+
+`<DEL>'
+ Delete last character (`delete-backward-char').
+
+`M-<DEL>'
+ Kill last word (`backward-kill-word').
+
+`C-x <DEL>'
+ Kill to beginning of sentence (`backward-kill-sentence').
+
+ The <DEL> character (`delete-backward-char') is the most important
+correction command. When used among graphic (self-inserting)
+characters, it can be thought of as canceling the last character typed.
+
+ When your mistake is longer than a couple of characters, it might be
+more convenient to use `M-<DEL>' or `C-x <DEL>'. `M-<DEL>' kills back
+to the start of the last word, and `C-x <DEL>' kills back to the start
+of the last sentence. `C-x <DEL>' is particularly useful when you are
+thinking of what to write as you type it, in case you change your mind
+about phrasing. `M-<DEL>' and `C-x <DEL>' save the killed text for
+`C-y' and `M-y' to retrieve. *Note Yanking::.
+
+ `M-<DEL>' is often useful even when you have typed only a few
+characters wrong, if you know you are confused in your typing and aren't
+sure exactly what you typed. At such a time, you cannot correct with
+<DEL> except by looking at the screen to see what you did. It requires
+less thought to kill the whole word and start over.
+
+\1f
File: xemacs.info, Node: Transpose, Next: Fixing Case, Prev: Kill Errors, Up: Fixit
Transposing Text
locally sets `version-control' to `never' to make sure that there is
only one backup for an Rmail file. *Note Locals::.
-\1f
-File: xemacs.info, Node: Backup Deletion, Next: Backup Copying, Prev: Backup Names, Up: Backup
-
-Automatic Deletion of Backups
-.............................
-
- To prevent unlimited consumption of disk space, Emacs can delete
-numbered backup versions automatically. Generally Emacs keeps the
-first few backups and the latest few backups, deleting any in between.
-This happens every time a new backup is made. The two variables that
-control the deletion are `kept-old-versions' and `kept-new-versions'.
-Their values are, respectively the number of oldest (lowest-numbered)
-backups to keep and the number of newest (highest-numbered) ones to
-keep, each time a new backup is made. The values are used just after a
-new backup version is made; that newly made backup is included in the
-count in `kept-new-versions'. By default, both variables are 2.
-
- If `delete-old-versions' is non-`nil', excess middle versions are
-deleted without notification. If it is `nil', the default, you are
-asked whether the excess middle versions should really be deleted.
-
- You can also use Dired's `.' (Period) command to delete old versions.
-*Note Dired::.
-
-\1f
-File: xemacs.info, Node: Backup Copying, Prev: Backup Deletion, Up: Backup
-
-Copying vs. Renaming
-....................
-
- You can make backup files by copying the old file or by renaming it.
-This makes a difference when the old file has multiple names. If you
-rename the old file into the backup file, the alternate names become
-names for the backup file. If you copy the old file instead, the
-alternate names remain names for the file that you are editing, and the
-contents accessed by those names will be the new contents.
-
- How you make a backup file may also affect the file's owner and
-group. If you use copying, they do not change. If renaming is used,
-you become the file's owner, and the file's group becomes the default
-(different operating systems have different defaults for the group).
-
- Having the owner change is usually a good idea, because then the
-owner is always the person who last edited the file. Occasionally
-there is a file whose owner should not change. Since most files should
-change owners, it is a good idea to use local variable lists to set
-`backup-by-copying-when-mismatch' for the special cases where the owner
-should not change (*note File Variables::).
-
- Three variables control the choice of renaming or copying.
-Normally, renaming is done. If the variable `backup-by-copying' is
-non-`nil', copying is used. Otherwise, if the variable
-`backup-by-copying-when-linked' is non-`nil', copying is done for files
-that have multiple names, but renaming may still be done when the file
-being edited has only one name. If the variable
-`backup-by-copying-when-mismatch' is non-`nil', copying is done if
-renaming would cause the file's owner or group to change.
-
-\1f
-File: xemacs.info, Node: Interlocking, Prev: Backup, Up: Saving
-
-Protection Against Simultaneous Editing
----------------------------------------
-
- Simultaneous editing occurs when two users visit the same file, both
-make changes, and both save their changes. If no one was informed that
-this was happening, and you saved first, you would later find that your
-changes were lost. On some systems, Emacs notices immediately when the
-second user starts to change a file already being edited, and issues a
-warning. When this is not possible, or if the second user has started
-to change the file despite the warning, Emacs checks when the file is
-saved, and issues a second warning when a user is about to overwrite a
-file containing another user's changes. If you are the user editing the
-file, you can take corrective action at this point and prevent actual
-loss of work.
-
- When you make the first modification in an Emacs buffer that is
-visiting a file, Emacs records that you have locked the file. (It does
-this by writing another file in a directory reserved for this purpose.)
-The lock is removed when you save the changes. The idea is that the
-file is locked whenever the buffer is modified. If you begin to modify
-the buffer while the visited file is locked by someone else, this
-constitutes a collision, and Emacs asks you what to do. It does this
-by calling the Lisp function `ask-user-about-lock', which you can
-redefine to customize what it does. The standard definition of this
-function asks you a question and accepts three possible answers:
-
-`s'
- Steal the lock. Whoever was already changing the file loses the
- lock, and you get the lock.
-
-`p'
- Proceed. Go ahead and edit the file despite its being locked by
- someone else.
-
-`q'
- Quit. This causes an error (`file-locked') and the modification
- you were trying to make in the buffer does not actually take place.
-
- Note that locking works on the basis of a file name; if a file has
-multiple names, Emacs does not realize that the two names are the same
-file and cannot prevent two users from editing it simultaneously under
-different names. However, basing locking on names means that Emacs can
-interlock the editing of new files that do not really exist until they
-are saved.
-
- Some systems are not configured to allow Emacs to make locks. On
-these systems, Emacs cannot detect trouble in advance, but it can still
-detect it in time to prevent you from overwriting someone else's
-changes.
-
- Every time Emacs saves a buffer, it first checks the
-last-modification date of the existing file on disk to see that it has
-not changed since the file was last visited or saved. If the date does
-not match, it implies that changes were made in the file in some other
-way, and these changes are about to be lost if Emacs actually does
-save. To prevent this, Emacs prints a warning message and asks for
-confirmation before saving. Occasionally you will know why the file
-was changed and know that it does not matter; then you can answer `yes'
-and proceed. Otherwise, you should cancel the save with `C-g' and
-investigate the situation.
-
- The first thing you should do when notified that simultaneous editing
-has already taken place is to list the directory with `C-u C-x C-d'
-(*note Directory Listing: ListDir.). This will show the file's current
-author. You should attempt to contact that person and ask him not to
-continue editing. Often the next step is to save the contents of your
-Emacs buffer under a different name, and use `diff' to compare the two
-files.
-
- Simultaneous editing checks are also made when you visit a file that
-is already visited with `C-x C-f' and when you start to modify a file.
-This is not strictly necessary, but it is useful to find out about such
-a problem as early as possible, when corrective action takes less work.
-
- Another way to protect your file is to set the read, write, and
-executable permissions for the file. Use the function
-`set-default-file-modes' to set the UNIX `umask' value to the NMASK
-argument. The `umask' value is the default protection mode for new
-files.
-
-\1f
-File: xemacs.info, Node: Reverting, Next: Auto Save, Prev: Saving, Up: Files
-
-Reverting a Buffer
-==================
-
- If you have made extensive changes to a file and then change your
-mind about them, you can get rid of all changes by reading in the
-previous version of the file. To do this, use `M-x revert-buffer',
-which operates on the current buffer. Since reverting a buffer can
-result in very extensive changes, you must confirm it with `yes'.
-
- If the current buffer has been auto-saved more recently than it has
-been saved explicitly, `revert-buffer' offers to read the auto save file
-instead of the visited file (*note Auto Save::). Emacs asks you about
-the auto-save file before the request for confirmation of the
-`revert-buffer' operation, and demands `y' or `n' as an answer. If you
-have started to type `yes' for confirmation without realizing that the
-auto-save question was going to be asked, the `y' will answer that
-question, but the `es' will not be valid confirmation. This gives you
-a chance to cancel the operation with `C-g' and try again with the
-answers you really intend.
-
- `revert-buffer' keeps point at the same distance (measured in
-characters) from the beginning of the file. If the file was edited only
-slightly, you will be at approximately the same piece of text after
-reverting as before. If you have made more extensive changes, the
-value of point in the old file may bring you to a totally different
-piece of text than your last editing point.
-
- A buffer reverted from its visited file is marked "not modified"
-until you make a change.
-
- Some kinds of buffers whose contents reflect data bases other than
-files, such as Dired buffers, can also be reverted. For them,
-reverting means recalculating their contents from the appropriate data.
-Buffers created randomly with `C-x b' cannot be reverted;
-`revert-buffer' reports an error when asked to do so.
-
-\1f
-File: xemacs.info, Node: Auto Save, Next: Version Control, Prev: Reverting, Up: Files
-
-Auto-Saving: Protection Against Disasters
-=========================================
-
- Emacs saves all the visited files from time to time (based on
-counting your keystrokes) without being asked. This is called
-"auto-saving". It prevents you from losing more than a limited amount
-of work if the system crashes.
-
- When Emacs determines it is time for auto-saving, each buffer is
-considered and is auto-saved if auto-saving is turned on for it and it
-has changed since the last time it was auto-saved. If any auto-saving
-is done, the message `Auto-saving...' is displayed in the echo area
-until auto-saving is finished. Errors occurring during auto-saving are
-caught so that they do not interfere with the execution of commands you
-have been typing.
-
-* Menu:
-
-* Files: Auto Save Files.
-* Control: Auto Save Control.
-* Recover:: Recovering text from auto-save files.
-
-\1f
-File: xemacs.info, Node: Auto Save Files, Next: Auto Save Control, Prev: Auto Save, Up: Auto Save
-
-Auto-Save Files
----------------
-
- Auto-saving does not normally write to the files you visited, because
-it can be undesirable to save a program that is in an inconsistent
-state when you have made only half of a planned change. Instead,
-auto-saving is done in a different file called the "auto-save file",
-and the visited file is changed only when you save explicitly, for
-example, with `C-x C-s'.
-
- Normally, the name of the auto-save file is generated by appending
-`#' to the front and back of the visited file name. Thus, a buffer
-visiting file `foo.c' would be auto-saved in a file `#foo.c#'. Most
-buffers that are not visiting files are auto-saved only if you request
-it explicitly; when they are auto-saved, the auto-save file name is
-generated by appending `#%' to the front and `#' to the back of buffer
-name. For example, the `*mail*' buffer in which you compose messages
-to be sent is auto-saved in a file named `#%*mail*#'. Names of
-auto-save files are generated this way unless you customize the
-functions `make-auto-save-file-name' and `auto-save-file-name-p' to do
-something different. The file name to be used for auto-saving a buffer
-is calculated at the time auto-saving is turned on in that buffer.
-
- If you want auto-saving to be done in the visited file, set the
-variable `auto-save-visited-file-name' to be non-`nil'. In this mode,
-there is really no difference between auto-saving and explicit saving.
-
- Emacs deletes a buffer's auto-save file when you explicitly save the
-buffer. To inhibit the deletion, set the variable
-`delete-auto-save-files' to `nil'. Changing the visited file name with
-`C-x C-w' or `set-visited-file-name' renames any auto-save file to
-correspond to the new visited name.
-
-\1f
-File: xemacs.info, Node: Auto Save Control, Next: Recover, Prev: Auto Save Files, Up: Auto Save
-
-Controlling Auto-Saving
------------------------
-
- Each time you visit a file, auto-saving is turned on for that file's
-buffer if the variable `auto-save-default' is non-`nil' (but not in
-batch mode; *note Entering Emacs::). The default for this variable is
-`t', so Emacs auto-saves buffers that visit files by default. You can
-use the command `M-x auto-save-mode' to turn auto-saving for a buffer
-on or off. Like other minor mode commands, `M-x auto-save-mode' turns
-auto-saving on with a positive argument, off with a zero or negative
-argument; with no argument, it toggles.
-
- Emacs performs auto-saving periodically based on counting how many
-characters you have typed since the last time auto-saving happened. The
-variable `auto-save-interval' specifies the number of characters
-between auto-saves. By default, it is 300. Emacs also auto-saves
-whenever you call the function `do-auto-save'.
-
- Emacs also does auto-saving whenever it gets a fatal error. This
-includes killing the Emacs job with a shell command such as `kill
--emacs', or disconnecting a phone line or network connection.
-
- You can set the number of seconds of idle time before an auto-save is
-done. Setting the value of the variable `auto-save-timeout' to zero or
-`nil' will disable auto-saving due to idleness.
-
- The actual amount of idle time between auto-saves is logarithmically
-related to the size of the current buffer. This variable is the number
-of seconds after which an auto-save will happen when the current buffer
-is 50k or less; the timeout will be 2 1/4 times this in a 200k buffer, 3
-3/4 times this in a 1000k buffer, and 4 1/2 times this in a 2000k
-buffer.
-
- For this variable to have any effect, you must do `(require 'timer)'.
-
-\1f
-File: xemacs.info, Node: Recover, Prev: Auto Save Control, Up: Auto Save
-
-Recovering Data from Auto-Saves
--------------------------------
-
- If you want to use the contents of an auto-save file to recover from
-a loss of data, use the command `M-x recover-file <RET> FILE <RET>'.
-Emacs visits FILE and then (after your confirmation) restores the
-contents from the auto-save file `#FILE#'. You can then save the file
-with `C-x C-s' to put the recovered text into FILE itself. For
-example, to recover file `foo.c' from its auto-save file `#foo.c#', do:
-
- M-x recover-file <RET> foo.c <RET>
- C-x C-s
-
- Before asking for confirmation, `M-x recover-file' displays a
-directory listing describing the specified file and the auto-save file,
-so you can compare their sizes and dates. If the auto-save file is
-older, `M-x recover-file' does not offer to read it.
-
- Auto-saving is disabled by `M-x recover-file' because using this
-command implies that the auto-save file contains valuable data from a
-past session. If you save the data in the visited file and then go on
-to make new changes, turn auto-saving back on with `M-x auto-save-mode'.
-
-\1f
-File: xemacs.info, Node: Version Control, Next: ListDir, Prev: Auto Save, Up: Files
-
-Version Control
-===============
-
- "Version control systems" are packages that can record multiple
-versions of a source file, usually storing the unchanged parts of the
-file just once. Version control systems also record history information
-such as the creation time of each version, who created it, and a
-description of what was changed in that version.
-
- The GNU project recommends the version control system known as RCS,
-which is free software and available from the Free Software Foundation.
-Emacs supports use of either RCS or SCCS (a proprietary, but widely
-used, version control system that is not quite as powerful as RCS)
-through a facility called VC. The same Emacs commands work with either
-RCS or SCCS, so you hardly have to know which one of them you are using.
-
-* Menu:
-
-* Concepts of VC:: Basic version control information;
- checking files in and out.
-* Editing with VC:: Commands for editing a file maintained
- with version control.
-* Variables for Check-in/out:: Variables that affect the commands used
- to check files in or out.
-* Log Entries:: Logging your changes.
-* Change Logs and VC:: Generating a change log file from log
- entries.
-* Old Versions:: Examining and comparing old versions.
-* VC Status:: Commands to view the VC status of files and
- look at log entries.
-* Renaming and VC:: A command to rename both the source and
- master file correctly.
-* Snapshots:: How to make and use snapshots, a set of
- file versions that can be treated as a unit.
-* Version Headers:: Inserting version control headers into
- working files.
-
-\1f
-File: xemacs.info, Node: Concepts of VC, Next: Editing with VC, Prev: Version Control, Up: Version Control
-
-Concepts of Version Control
----------------------------
-
- When a file is under version control, we also say that it is
-"registered" in the version control system. Each registered file has a
-corresponding "master file" which represents the file's present state
-plus its change history, so that you can reconstruct from it either the
-current version or any specified earlier version. Usually the master
-file also records a "log entry" for each version describing what was
-changed in that version.
-
- The file that is maintained under version control is sometimes called
-the "work file" corresponding to its master file.
-
- To examine a file, you "check it out". This extracts a version of
-the source file (typically, the most recent) from the master file. If
-you want to edit the file, you must check it out "locked". Only one
-user can do this at a time for any given source file. (This kind of
-locking is completely unrelated to the locking that Emacs uses to
-detect simultaneous editing of a file.)
-
- When you are done with your editing, you must "check in" the new
-version. This records the new version in the master file, and unlocks
-the source file so that other people can lock it and thus modify it.
-
- Checkin and checkout are the basic operations of version control.
-You can do both of them with a single Emacs command: `C-x C-q'
-(`vc-toggle-read-only').
-
- A "snapshot" is a coherent collection of versions of the various
-files that make up a program. *Note Snapshots::.
-
-\1f
-File: xemacs.info, Node: Editing with VC, Next: Variables for Check-in/out, Prev: Concepts of VC, Up: Version Control
-
-Editing with Version Control
-----------------------------
-
- When you visit a file that is maintained using version control, the
-mode line displays `RCS' or `SCCS' to inform you that version control
-is in use, and also (in case you care) which low-level system the file
-is actually stored in. Normally, such a source file is read-only, and
-the mode line indicates this with `%%'. With RCS, the mode line also
-indicates the number of the head version, which is normally also the
-version you are looking at.
-
- These are the commands for editing a file maintained with version
-control:
-
-`C-x C-q'
- Check the visited file in or out.
-
-`C-x v u'
- Revert the buffer and the file to the last checked in version.
-
-`C-x v c'
- Remove the last-entered change from the master for the visited
- file. This undoes your last check-in.
-
-`C-x v i'
- Register the visited file in version control.
-
-(`C-x v' is the prefix key for version control commands; all of these
-commands except for `C-x C-q' start with `C-x v'.)
-
- When you want to modify a file maintained with version control, type
-`C-x C-q' (`vc-toggle-read-only'). This "checks out" the file, and
-tells RCS or SCCS to lock the file. This means making the file
-writable for you (but not for anyone else).
-
- When you are finished editing the file, type `C-x C-q' again. When
-used on a file that is checked out, this command checks the file in.
-But check-in does not start immediately; first, you must enter the "log
-entry"--a description of the changes in the new version. `C-x C-q'
-pops up a buffer for you to enter this in. When you are finished
-typing in the log entry, type `C-c C-c' to terminate it; this is when
-actual check-in takes place.
-
- Once you have checked in your changes, the file is unlocked, so that
-other users can lock it and modify it.
-
- Emacs does not save backup files for source files that are maintained
-with version control. If you want to make backup files despite version
-control, set the variable `vc-make-backup-files' to a non-`nil' value.
-
- Normally the work file exists all the time, whether it is locked or
-not. If you set `vc-keep-workfiles' to `nil', then checking in a new
-version with `C-x C-q' deletes the work file; but any attempt to visit
-the file with Emacs creates it again.
-
- It is not impossible to lock a file that someone else has locked. If
-you try to check out a file that is locked, `C-x C-q' asks you whether
-you want to "steal the lock." If you say yes, the file becomes locked
-by you, but a message is sent to the person who had formerly locked the
-file, to inform him of what has happened. The mode line indicates that
-a file is locked by someone else by displaying the login name of that
-person, before the version number.
-
- If you want to discard your current set of changes and revert to the
-last version checked in, use `C-x v u' (`vc-revert-buffer'). This
-cancels your last check-out, leaving the file unlocked. If you want to
-make a different set of changes, you must first check the file out
-again. `C-x v u' requires confirmation, unless it sees that you
-haven't made any changes since the last checked-in version.
-
- `C-x v u' is also the command to use if you lock a file and then
-don't actually change it.
-
- You can cancel a change after checking it in, with `C-x v c'
-(`vc-cancel-version'). This command discards all record of the most
-recent checked in version, so be careful about using it. It requires
-confirmation with `yes'. By default, `C-x v c' reverts your workfile
-and buffer to the previous version (the one that precedes the version
-that is deleted), but you can prevent the reversion by giving the
-command a prefix argument. Then the buffer does not change.
-
- This command with a prefix argument is useful when you have checked
-in a change and then discover a trivial error in it; you can cancel the
-erroneous check-in, fix the error, and repeat the check-in.
-
- Be careful when invoking `C-x v c', as it is easy to throw away a
-lot of work with it. To help you be careful, this command always
-requires confirmation with `yes'.
-
- You can register the visited file for version control using
-`C-x v i' (`vc-register'). If the variable `vc-default-back-end' is
-non-`nil', it specifies which version control system to use; otherwise,
-this uses RCS if it is installed on your system and SCCS if not. After
-`C-x v i', the file is unlocked and read-only. Type `C-x C-q' if you
-wish to edit it.
-
- By default, the initial version number is 1.1. If you want to use a
-different number, give `C-x v i' a prefix argument; then it reads the
-initial version number using the minibuffer.
-
- If `vc-initial-comment' is non-`nil', `C-x v i' reads an initial
-comment (much like a log entry) to describe the purpose of this source
-file.
-
- To specify the version number for a subsequent checkin, use the
-command `C-u C-x v v'. `C-x v v' (`vc-next-action') is the command
-that `C-x C-q' uses to do the "real work" when the visited file uses
-version control. When used for checkin, and given a prefix argument,
-it reads the version number with the minibuffer.
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Backup Deletion, Next: Backup Copying, Prev: Backup Names, Up: Backup
+
+Automatic Deletion of Backups
+.............................
+
+ To prevent unlimited consumption of disk space, Emacs can delete
+numbered backup versions automatically. Generally Emacs keeps the
+first few backups and the latest few backups, deleting any in between.
+This happens every time a new backup is made. The two variables that
+control the deletion are `kept-old-versions' and `kept-new-versions'.
+Their values are, respectively the number of oldest (lowest-numbered)
+backups to keep and the number of newest (highest-numbered) ones to
+keep, each time a new backup is made. The values are used just after a
+new backup version is made; that newly made backup is included in the
+count in `kept-new-versions'. By default, both variables are 2.
+
+ If `delete-old-versions' is non-`nil', excess middle versions are
+deleted without notification. If it is `nil', the default, you are
+asked whether the excess middle versions should really be deleted.
+
+ You can also use Dired's `.' (Period) command to delete old versions.
+*Note Dired::.
+
+\1f
+File: xemacs.info, Node: Backup Copying, Prev: Backup Deletion, Up: Backup
+
+Copying vs. Renaming
+....................
+
+ You can make backup files by copying the old file or by renaming it.
+This makes a difference when the old file has multiple names. If you
+rename the old file into the backup file, the alternate names become
+names for the backup file. If you copy the old file instead, the
+alternate names remain names for the file that you are editing, and the
+contents accessed by those names will be the new contents.
+
+ How you make a backup file may also affect the file's owner and
+group. If you use copying, they do not change. If renaming is used,
+you become the file's owner, and the file's group becomes the default
+(different operating systems have different defaults for the group).
+
+ Having the owner change is usually a good idea, because then the
+owner is always the person who last edited the file. Occasionally
+there is a file whose owner should not change. Since most files should
+change owners, it is a good idea to use local variable lists to set
+`backup-by-copying-when-mismatch' for the special cases where the owner
+should not change (*note File Variables::).
+
+ Three variables control the choice of renaming or copying.
+Normally, renaming is done. If the variable `backup-by-copying' is
+non-`nil', copying is used. Otherwise, if the variable
+`backup-by-copying-when-linked' is non-`nil', copying is done for files
+that have multiple names, but renaming may still be done when the file
+being edited has only one name. If the variable
+`backup-by-copying-when-mismatch' is non-`nil', copying is done if
+renaming would cause the file's owner or group to change.
+
+\1f
+File: xemacs.info, Node: Interlocking, Prev: Backup, Up: Saving
+
+Protection Against Simultaneous Editing
+---------------------------------------
+
+ Simultaneous editing occurs when two users visit the same file, both
+make changes, and both save their changes. If no one was informed that
+this was happening, and you saved first, you would later find that your
+changes were lost. On some systems, Emacs notices immediately when the
+second user starts to change a file already being edited, and issues a
+warning. When this is not possible, or if the second user has started
+to change the file despite the warning, Emacs checks when the file is
+saved, and issues a second warning when a user is about to overwrite a
+file containing another user's changes. If you are the user editing the
+file, you can take corrective action at this point and prevent actual
+loss of work.
+
+ When you make the first modification in an Emacs buffer that is
+visiting a file, Emacs records that you have locked the file. (It does
+this by writing another file in a directory reserved for this purpose.)
+The lock is removed when you save the changes. The idea is that the
+file is locked whenever the buffer is modified. If you begin to modify
+the buffer while the visited file is locked by someone else, this
+constitutes a collision, and Emacs asks you what to do. It does this
+by calling the Lisp function `ask-user-about-lock', which you can
+redefine to customize what it does. The standard definition of this
+function asks you a question and accepts three possible answers:
+
+`s'
+ Steal the lock. Whoever was already changing the file loses the
+ lock, and you get the lock.
+
+`p'
+ Proceed. Go ahead and edit the file despite its being locked by
+ someone else.
+
+`q'
+ Quit. This causes an error (`file-locked') and the modification
+ you were trying to make in the buffer does not actually take place.
+
+ Note that locking works on the basis of a file name; if a file has
+multiple names, Emacs does not realize that the two names are the same
+file and cannot prevent two users from editing it simultaneously under
+different names. However, basing locking on names means that Emacs can
+interlock the editing of new files that do not really exist until they
+are saved.
+
+ Some systems are not configured to allow Emacs to make locks. On
+these systems, Emacs cannot detect trouble in advance, but it can still
+detect it in time to prevent you from overwriting someone else's
+changes.
+
+ Every time Emacs saves a buffer, it first checks the
+last-modification date of the existing file on disk to see that it has
+not changed since the file was last visited or saved. If the date does
+not match, it implies that changes were made in the file in some other
+way, and these changes are about to be lost if Emacs actually does
+save. To prevent this, Emacs prints a warning message and asks for
+confirmation before saving. Occasionally you will know why the file
+was changed and know that it does not matter; then you can answer `yes'
+and proceed. Otherwise, you should cancel the save with `C-g' and
+investigate the situation.
+
+ The first thing you should do when notified that simultaneous editing
+has already taken place is to list the directory with `C-u C-x C-d'
+(*note Directory Listing: ListDir.). This will show the file's current
+author. You should attempt to contact that person and ask him not to
+continue editing. Often the next step is to save the contents of your
+Emacs buffer under a different name, and use `diff' to compare the two
+files.
+
+ Simultaneous editing checks are also made when you visit a file that
+is already visited with `C-x C-f' and when you start to modify a file.
+This is not strictly necessary, but it is useful to find out about such
+a problem as early as possible, when corrective action takes less work.
+
+ Another way to protect your file is to set the read, write, and
+executable permissions for the file. Use the function
+`set-default-file-modes' to set the UNIX `umask' value to the NMASK
+argument. The `umask' value is the default protection mode for new
+files.
+
+\1f
+File: xemacs.info, Node: Reverting, Next: Auto Save, Prev: Saving, Up: Files
+
+Reverting a Buffer
+==================
+
+ If you have made extensive changes to a file and then change your
+mind about them, you can get rid of all changes by reading in the
+previous version of the file. To do this, use `M-x revert-buffer',
+which operates on the current buffer. Since reverting a buffer can
+result in very extensive changes, you must confirm it with `yes'.
+
+ If the current buffer has been auto-saved more recently than it has
+been saved explicitly, `revert-buffer' offers to read the auto save file
+instead of the visited file (*note Auto Save::). Emacs asks you about
+the auto-save file before the request for confirmation of the
+`revert-buffer' operation, and demands `y' or `n' as an answer. If you
+have started to type `yes' for confirmation without realizing that the
+auto-save question was going to be asked, the `y' will answer that
+question, but the `es' will not be valid confirmation. This gives you
+a chance to cancel the operation with `C-g' and try again with the
+answers you really intend.
+
+ `revert-buffer' keeps point at the same distance (measured in
+characters) from the beginning of the file. If the file was edited only
+slightly, you will be at approximately the same piece of text after
+reverting as before. If you have made more extensive changes, the
+value of point in the old file may bring you to a totally different
+piece of text than your last editing point.
+
+ A buffer reverted from its visited file is marked "not modified"
+until you make a change.
+
+ Some kinds of buffers whose contents reflect data bases other than
+files, such as Dired buffers, can also be reverted. For them,
+reverting means recalculating their contents from the appropriate data.
+Buffers created randomly with `C-x b' cannot be reverted;
+`revert-buffer' reports an error when asked to do so.
+
+\1f
+File: xemacs.info, Node: Auto Save, Next: Version Control, Prev: Reverting, Up: Files
+
+Auto-Saving: Protection Against Disasters
+=========================================
+
+ Emacs saves all the visited files from time to time (based on
+counting your keystrokes) without being asked. This is called
+"auto-saving". It prevents you from losing more than a limited amount
+of work if the system crashes.
+
+ When Emacs determines it is time for auto-saving, each buffer is
+considered and is auto-saved if auto-saving is turned on for it and it
+has changed since the last time it was auto-saved. If any auto-saving
+is done, the message `Auto-saving...' is displayed in the echo area
+until auto-saving is finished. Errors occurring during auto-saving are
+caught so that they do not interfere with the execution of commands you
+have been typing.
+
+* Menu:
+
+* Files: Auto Save Files.
+* Control: Auto Save Control.
+* Recover:: Recovering text from auto-save files.
+
+\1f
+File: xemacs.info, Node: Auto Save Files, Next: Auto Save Control, Prev: Auto Save, Up: Auto Save
+
+Auto-Save Files
+---------------
+
+ Auto-saving does not normally write to the files you visited, because
+it can be undesirable to save a program that is in an inconsistent
+state when you have made only half of a planned change. Instead,
+auto-saving is done in a different file called the "auto-save file",
+and the visited file is changed only when you save explicitly, for
+example, with `C-x C-s'.
+
+ Normally, the name of the auto-save file is generated by appending
+`#' to the front and back of the visited file name. Thus, a buffer
+visiting file `foo.c' would be auto-saved in a file `#foo.c#'. Most
+buffers that are not visiting files are auto-saved only if you request
+it explicitly; when they are auto-saved, the auto-save file name is
+generated by appending `#%' to the front and `#' to the back of buffer
+name. For example, the `*mail*' buffer in which you compose messages
+to be sent is auto-saved in a file named `#%*mail*#'. Names of
+auto-save files are generated this way unless you customize the
+functions `make-auto-save-file-name' and `auto-save-file-name-p' to do
+something different. The file name to be used for auto-saving a buffer
+is calculated at the time auto-saving is turned on in that buffer.
+
+ If you want auto-saving to be done in the visited file, set the
+variable `auto-save-visited-file-name' to be non-`nil'. In this mode,
+there is really no difference between auto-saving and explicit saving.
+
+ Emacs deletes a buffer's auto-save file when you explicitly save the
+buffer. To inhibit the deletion, set the variable
+`delete-auto-save-files' to `nil'. Changing the visited file name with
+`C-x C-w' or `set-visited-file-name' renames any auto-save file to
+correspond to the new visited name.
+
+\1f
+File: xemacs.info, Node: Auto Save Control, Next: Recover, Prev: Auto Save Files, Up: Auto Save
+
+Controlling Auto-Saving
+-----------------------
+
+ Each time you visit a file, auto-saving is turned on for that file's
+buffer if the variable `auto-save-default' is non-`nil' (but not in
+batch mode; *note Entering Emacs::). The default for this variable is
+`t', so Emacs auto-saves buffers that visit files by default. You can
+use the command `M-x auto-save-mode' to turn auto-saving for a buffer
+on or off. Like other minor mode commands, `M-x auto-save-mode' turns
+auto-saving on with a positive argument, off with a zero or negative
+argument; with no argument, it toggles.
+
+ Emacs performs auto-saving periodically based on counting how many
+characters you have typed since the last time auto-saving happened. The
+variable `auto-save-interval' specifies the number of characters
+between auto-saves. By default, it is 300. Emacs also auto-saves
+whenever you call the function `do-auto-save'.
+
+ Emacs also does auto-saving whenever it gets a fatal error. This
+includes killing the Emacs job with a shell command such as `kill
+-emacs', or disconnecting a phone line or network connection.
+
+ You can set the number of seconds of idle time before an auto-save is
+done. Setting the value of the variable `auto-save-timeout' to zero or
+`nil' will disable auto-saving due to idleness.
+
+ The actual amount of idle time between auto-saves is logarithmically
+related to the size of the current buffer. This variable is the number
+of seconds after which an auto-save will happen when the current buffer
+is 50k or less; the timeout will be 2 1/4 times this in a 200k buffer, 3
+3/4 times this in a 1000k buffer, and 4 1/2 times this in a 2000k
+buffer.
+
+ For this variable to have any effect, you must do `(require 'timer)'.
+
+\1f
+File: xemacs.info, Node: Recover, Prev: Auto Save Control, Up: Auto Save
+
+Recovering Data from Auto-Saves
+-------------------------------
+
+ If you want to use the contents of an auto-save file to recover from
+a loss of data, use the command `M-x recover-file <RET> FILE <RET>'.
+Emacs visits FILE and then (after your confirmation) restores the
+contents from the auto-save file `#FILE#'. You can then save the file
+with `C-x C-s' to put the recovered text into FILE itself. For
+example, to recover file `foo.c' from its auto-save file `#foo.c#', do:
+
+ M-x recover-file <RET> foo.c <RET>
+ C-x C-s
+
+ Before asking for confirmation, `M-x recover-file' displays a
+directory listing describing the specified file and the auto-save file,
+so you can compare their sizes and dates. If the auto-save file is
+older, `M-x recover-file' does not offer to read it.
+
+ Auto-saving is disabled by `M-x recover-file' because using this
+command implies that the auto-save file contains valuable data from a
+past session. If you save the data in the visited file and then go on
+to make new changes, turn auto-saving back on with `M-x auto-save-mode'.
+
+\1f
+File: xemacs.info, Node: Version Control, Next: ListDir, Prev: Auto Save, Up: Files
+
+Version Control
+===============
+
+ "Version control systems" are packages that can record multiple
+versions of a source file, usually storing the unchanged parts of the
+file just once. Version control systems also record history information
+such as the creation time of each version, who created it, and a
+description of what was changed in that version.
+
+ The GNU project recommends the version control system known as RCS,
+which is free software and available from the Free Software Foundation.
+Emacs supports use of either RCS or SCCS (a proprietary, but widely
+used, version control system that is not quite as powerful as RCS)
+through a facility called VC. The same Emacs commands work with either
+RCS or SCCS, so you hardly have to know which one of them you are using.
+
+* Menu:
+
+* Concepts of VC:: Basic version control information;
+ checking files in and out.
+* Editing with VC:: Commands for editing a file maintained
+ with version control.
+* Variables for Check-in/out:: Variables that affect the commands used
+ to check files in or out.
+* Log Entries:: Logging your changes.
+* Change Logs and VC:: Generating a change log file from log
+ entries.
+* Old Versions:: Examining and comparing old versions.
+* VC Status:: Commands to view the VC status of files and
+ look at log entries.
+* Renaming and VC:: A command to rename both the source and
+ master file correctly.
+* Snapshots:: How to make and use snapshots, a set of
+ file versions that can be treated as a unit.
+* Version Headers:: Inserting version control headers into
+ working files.
+
+\1f
+File: xemacs.info, Node: Concepts of VC, Next: Editing with VC, Prev: Version Control, Up: Version Control
+
+Concepts of Version Control
+---------------------------
+
+ When a file is under version control, we also say that it is
+"registered" in the version control system. Each registered file has a
+corresponding "master file" which represents the file's present state
+plus its change history, so that you can reconstruct from it either the
+current version or any specified earlier version. Usually the master
+file also records a "log entry" for each version describing what was
+changed in that version.
+
+ The file that is maintained under version control is sometimes called
+the "work file" corresponding to its master file.
+
+ To examine a file, you "check it out". This extracts a version of
+the source file (typically, the most recent) from the master file. If
+you want to edit the file, you must check it out "locked". Only one
+user can do this at a time for any given source file. (This kind of
+locking is completely unrelated to the locking that Emacs uses to
+detect simultaneous editing of a file.)
+
+ When you are done with your editing, you must "check in" the new
+version. This records the new version in the master file, and unlocks
+the source file so that other people can lock it and thus modify it.
+
+ Checkin and checkout are the basic operations of version control.
+You can do both of them with a single Emacs command: `C-x C-q'
+(`vc-toggle-read-only').
+
+ A "snapshot" is a coherent collection of versions of the various
+files that make up a program. *Note Snapshots::.
+
+\1f
+File: xemacs.info, Node: Editing with VC, Next: Variables for Check-in/out, Prev: Concepts of VC, Up: Version Control
+
+Editing with Version Control
+----------------------------
+
+ When you visit a file that is maintained using version control, the
+mode line displays `RCS' or `SCCS' to inform you that version control
+is in use, and also (in case you care) which low-level system the file
+is actually stored in. Normally, such a source file is read-only, and
+the mode line indicates this with `%%'. With RCS, the mode line also
+indicates the number of the head version, which is normally also the
+version you are looking at.
+
+ These are the commands for editing a file maintained with version
+control:
+
+`C-x C-q'
+ Check the visited file in or out.
+
+`C-x v u'
+ Revert the buffer and the file to the last checked in version.
+
+`C-x v c'
+ Remove the last-entered change from the master for the visited
+ file. This undoes your last check-in.
+
+`C-x v i'
+ Register the visited file in version control.
+
+(`C-x v' is the prefix key for version control commands; all of these
+commands except for `C-x C-q' start with `C-x v'.)
+
+ When you want to modify a file maintained with version control, type
+`C-x C-q' (`vc-toggle-read-only'). This "checks out" the file, and
+tells RCS or SCCS to lock the file. This means making the file
+writable for you (but not for anyone else).
+
+ When you are finished editing the file, type `C-x C-q' again. When
+used on a file that is checked out, this command checks the file in.
+But check-in does not start immediately; first, you must enter the "log
+entry"--a description of the changes in the new version. `C-x C-q'
+pops up a buffer for you to enter this in. When you are finished
+typing in the log entry, type `C-c C-c' to terminate it; this is when
+actual check-in takes place.
+
+ Once you have checked in your changes, the file is unlocked, so that
+other users can lock it and modify it.
+
+ Emacs does not save backup files for source files that are maintained
+with version control. If you want to make backup files despite version
+control, set the variable `vc-make-backup-files' to a non-`nil' value.
+
+ Normally the work file exists all the time, whether it is locked or
+not. If you set `vc-keep-workfiles' to `nil', then checking in a new
+version with `C-x C-q' deletes the work file; but any attempt to visit
+the file with Emacs creates it again.
+
+ It is not impossible to lock a file that someone else has locked. If
+you try to check out a file that is locked, `C-x C-q' asks you whether
+you want to "steal the lock." If you say yes, the file becomes locked
+by you, but a message is sent to the person who had formerly locked the
+file, to inform him of what has happened. The mode line indicates that
+a file is locked by someone else by displaying the login name of that
+person, before the version number.
+
+ If you want to discard your current set of changes and revert to the
+last version checked in, use `C-x v u' (`vc-revert-buffer'). This
+cancels your last check-out, leaving the file unlocked. If you want to
+make a different set of changes, you must first check the file out
+again. `C-x v u' requires confirmation, unless it sees that you
+haven't made any changes since the last checked-in version.
+
+ `C-x v u' is also the command to use if you lock a file and then
+don't actually change it.
+
+ You can cancel a change after checking it in, with `C-x v c'
+(`vc-cancel-version'). This command discards all record of the most
+recent checked in version, so be careful about using it. It requires
+confirmation with `yes'. By default, `C-x v c' reverts your workfile
+and buffer to the previous version (the one that precedes the version
+that is deleted), but you can prevent the reversion by giving the
+command a prefix argument. Then the buffer does not change.
+
+ This command with a prefix argument is useful when you have checked
+in a change and then discover a trivial error in it; you can cancel the
+erroneous check-in, fix the error, and repeat the check-in.
+
+ Be careful when invoking `C-x v c', as it is easy to throw away a
+lot of work with it. To help you be careful, this command always
+requires confirmation with `yes'.
+
+ You can register the visited file for version control using
+`C-x v i' (`vc-register'). If the variable `vc-default-back-end' is
+non-`nil', it specifies which version control system to use; otherwise,
+this uses RCS if it is installed on your system and SCCS if not. After
+`C-x v i', the file is unlocked and read-only. Type `C-x C-q' if you
+wish to edit it.
+
+ By default, the initial version number is 1.1. If you want to use a
+different number, give `C-x v i' a prefix argument; then it reads the
+initial version number using the minibuffer.
+
+ If `vc-initial-comment' is non-`nil', `C-x v i' reads an initial
+comment (much like a log entry) to describe the purpose of this source
+file.
+
+ To specify the version number for a subsequent checkin, use the
+command `C-u C-x v v'. `C-x v v' (`vc-next-action') is the command
+that `C-x C-q' uses to do the "real work" when the visited file uses
+version control. When used for checkin, and given a prefix argument,
+it reads the version number with the minibuffer.
+
+\1f
File: xemacs.info, Node: Variables for Check-in/out, Next: Log Entries, Prev: Editing with VC, Up: Version Control
Variables Affecting Check-in and Check-out
directory by programs other than Dired. All deletion flags in the Dired
buffer are lost when this is done.
-\1f
-File: xemacs.info, Node: Dired Deletion, Next: Dired Immed, Prev: Dired Edit, Up: Dired
-
-Deleting Files With Dired
--------------------------
-
- The primary use of Dired is to flag files for deletion and then
-delete them.
-
-`d'
- Flag this file for deletion.
-
-`u'
- Remove deletion-flag on this line.
-
-`<DEL>'
- Remove deletion-flag on previous line, moving point to that line.
-
-`x'
- Delete the files that are flagged for deletion.
-
-`#'
- Flag all auto-save files (files whose names start and end with `#')
- for deletion (*note Auto Save::).
-
-`~'
- Flag all backup files (files whose names end with `~') for deletion
- (*note Backup::).
-
-`. (Period)'
- Flag excess numeric backup files for deletion. The oldest and
- newest few backup files of any one file are exempt; the middle
- ones are flagged.
-
- You can flag a file for deletion by moving to the line describing the
-file and typing `d' or `C-d'. The deletion flag is visible as a `D' at
-the beginning of the line. Point is moved to the beginning of the next
-line, so that repeated `d' commands flag successive files.
-
- The files are flagged for deletion rather than deleted immediately to
-avoid the danger of deleting a file accidentally. Until you direct
-Dired to delete the flagged files, you can remove deletion flags using
-the commands `u' and <DEL>. `u' works just like `d', but removes flags
-rather than making flags. <DEL> moves upward, removing flags; it is
-like `u' with numeric argument automatically negated.
-
- To delete the flagged files, type `x'. This command first displays a
-list of all the file names flagged for deletion, and requests
-confirmation with `yes'. Once you confirm, all the flagged files are
-deleted, and their lines are deleted from the text of the Dired buffer.
-The shortened Dired buffer remains selected. If you answer `no' or
-quit with `C-g', you return immediately to Dired, with the deletion
-flags still present and no files actually deleted.
-
- The `#', `~', and `.' commands flag many files for deletion, based
-on their names. These commands are useful precisely because they do
-not actually delete any files; you can remove the deletion flags from
-any flagged files that you really wish to keep.
-
- `#' flags for deletion all files that appear to have been made by
-auto-saving (that is, files whose names begin and end with `#'). `~'
-flags for deletion all files that appear to have been made as backups
-for files that were edited (that is, files whose names end with `~').
-
- `.' (Period) flags just some of the backup files for deletion: only
-numeric backups that are not among the oldest few nor the newest few
-backups of any one file. Normally `dired-kept-versions' (not
-`kept-new-versions'; that applies only when saving) specifies the
-number of newest versions of each file to keep, and `kept-old-versions'
-specifies the number of oldest versions to keep. Period with a
-positive numeric argument, as in `C-u 3 .', specifies the number of
-newest versions to keep, overriding `dired-kept-versions'. A negative
-numeric argument overrides `kept-old-versions', using minus the value
-of the argument to specify the number of oldest versions of each file
-to keep.
-
-\1f
-File: xemacs.info, Node: Dired Immed, Prev: Dired Deletion, Up: Dired
-
-Immediate File Operations in Dired
-----------------------------------
-
- Some file operations in Dired take place immediately when they are
-requested.
-
-`C'
- Copies the file described on the current line. You must supply a
- file name to copy to, using the minibuffer.
-
-`f'
- Visits the file described on the current line. It is just like
- typing `C-x C-f' and supplying that file name. If the file on
- this line is a subdirectory, `f' actually causes Dired to be
- invoked on that subdirectory. *Note Visiting::.
-
-`o'
- Like `f', but uses another window to display the file's buffer.
- The Dired buffer remains visible in the first window. This is
- like using `C-x 4 C-f' to visit the file. *Note Windows::.
-
-`R'
- Renames the file described on the current line. You must supply a
- file name to rename to, using the minibuffer.
-
-`v'
- Views the file described on this line using `M-x view-file'.
- Viewing a file is like visiting it, but is slanted toward moving
- around in the file conveniently and does not allow changing the
- file. *Note View File: Misc File Ops. Viewing a file that is a
- directory runs Dired on that directory.
-
-\1f
-File: xemacs.info, Node: Misc File Ops, Prev: Dired, Up: Files
-
-Miscellaneous File Operations
-=============================
-
- Emacs has commands for performing many other operations on files.
-All operate on one file; they do not accept wildcard file names.
-
- You can use the command `M-x add-name-to-file' to add a name to an
-existing file without removing the old name. The new name must belong
-on the file system that the file is on.
-
- `M-x append-to-file' adds the text of the region to the end of the
-specified file.
-
- `M-x copy-file' reads the file OLD and writes a new file named NEW
-with the same contents. Confirmation is required if a file named NEW
-already exists, because copying overwrites the old contents of the file
-NEW.
-
- `M-x delete-file' deletes a specified file, like the `rm' command in
-the shell. If you are deleting many files in one directory, it may be
-more convenient to use Dired (*note Dired::).
-
- `M-x insert-file' inserts a copy of the contents of a specified file
-into the current buffer at point, leaving point unchanged before the
-contents and the mark after them. *Note Mark::.
-
- `M-x make-symbolic-link' reads two file names OLD and LINKNAME, and
-then creates a symbolic link named LINKNAME and pointing at OLD.
-Future attempts to open file LINKNAME will then refer to the file named
-OLD at the time the opening is done, or will result in an error if the
-name OLD is not in use at that time. Confirmation is required if you
-create the link while LINKNAME is in use. Note that not all systems
-support symbolic links.
-
- `M-x rename-file' reads two file names OLD and NEW using the
-minibuffer, then renames file OLD as NEW. If a file named NEW already
-exists, you must confirm with `yes' or renaming is not done; this is
-because renaming causes the previous meaning of the name NEW to be
-lost. If OLD and NEW are on different file systems, the file OLD is
-copied and deleted.
-
- `M-x view-file' allows you to scan or read a file by sequential
-screenfuls. It reads a file name argument using the minibuffer. After
-reading the file into an Emacs buffer, `view-file' reads and displays
-one windowful. You can then type <SPC> to scroll forward one window,
-or <DEL> to scroll backward. Various other commands are provided for
-moving around in the file, but none for changing it; type `C-h' while
-viewing a file for a list of them. Most commands are the default Emacs
-cursor motion commands. To exit from viewing, type `C-c'.
-
-\1f
-File: xemacs.info, Node: Buffers, Next: Windows, Prev: Files, Up: Top
-
-Using Multiple Buffers
-**********************
-
- Text you are editing in Emacs resides in an object called a
-"buffer". Each time you visit a file, Emacs creates a buffer to hold
-the file's text. Each time you invoke Dired, Emacs creates a buffer to
-hold the directory listing. If you send a message with `C-x m', a
-buffer named `*mail*' is used to hold the text of the message. When
-you ask for a command's documentation, it appears in a buffer called
-`*Help*'.
-
- At any time, one and only one buffer is "selected". It is also
-called the "current buffer". Saying a command operates on "the buffer"
-really means that the command operates on the selected buffer, as most
-commands do.
-
- When Emacs creates multiple windows, each window has a chosen buffer
-which is displayed there, but at any time only one of the windows is
-selected and its chosen buffer is the selected buffer. Each window's
-mode line displays the name of the buffer the window is displaying
-(*note Windows::).
-
- Each buffer has a name which can be of any length but is
-case-sensitive. You can select a buffer using its name. Most buffers
-are created when you visit files; their names are derived from the
-files' names. You can also create an empty buffer with any name you
-want. A newly started Emacs has a buffer named `*scratch*' which you
-can use for evaluating Lisp expressions in Emacs.
-
- Each buffer records what file it is visiting, whether it is
-modified, and what major mode and minor modes are in effect in it
-(*note Major Modes::). Any Emacs variable can be made "local to" a
-particular buffer, meaning its value in that buffer can be different
-from the value in other buffers. *Note Locals::.
-
-* Menu:
-
-* Select Buffer:: Creating a new buffer or reselecting an old one.
-* List Buffers:: Getting a list of buffers that exist.
-* Misc Buffer:: Renaming; changing read-onliness; copying text.
-* Kill Buffer:: Killing buffers you no longer need.
-* Several Buffers:: How to go through the list of all buffers
- and operate variously on several of them.
-
-\1f
-File: xemacs.info, Node: Select Buffer, Next: List Buffers, Prev: Buffers, Up: Buffers
-
-Creating and Selecting Buffers
-==============================
-
-`C-x b BUFFER <RET>'
- Select or create a buffer named BUFFER (`switch-to-buffer').
-
-`C-x 4 b BUFFER <RET>'
- Similar, but select a buffer named BUFFER in another window
- (`switch-to-buffer-other-window').
-
-`M-x switch-to-other-buffer N'
- Switch to the previous buffer.
-
- To select a buffer named BUFNAME, type `C-x b BUFNAME <RET>'. This
-is the command `switch-to-buffer' with argument BUFNAME. You can use
-completion on an abbreviation for the buffer name you want (*note
-Completion::). An empty argument to `C-x b' specifies the most
-recently selected buffer that is not displayed in any window.
-
- Most buffers are created when you visit files, or use Emacs commands
-that display text. You can also create a buffer explicitly by typing
-`C-x b BUFNAME <RET>', which creates a new, empty buffer that is not
-visiting any file, and selects it for editing. The new buffer's major
-mode is determined by the value of `default-major-mode' (*note Major
-Modes::). Buffers not visiting files are usually used for making notes
-to yourself. If you try to save one, you are asked for the file name
-to use.
-
- The function `switch-to-buffer-other-frame' is similar to
-`switch-to-buffer' except that it creates a new frame in which to
-display the selected buffer.
-
- Use `M-x switch-to-other-buffer' to visit the previous buffer. If
-you supply a positive integer N, the Nth most recent buffer is
-displayed. If you supply an argument of 0, the current buffer is moved
-to the bottom of the buffer stack.
-
- Note that you can also use `C-x C-f' and any other command for
-visiting a file to switch buffers. *Note Visiting::.
-
-\1f
-File: xemacs.info, Node: List Buffers, Next: Misc Buffer, Prev: Select Buffer, Up: Buffers
-
-Listing Existing Buffers
-========================
-
-`C-x C-b'
- List the existing buffers (`list-buffers').
-
- To print a list of all existing buffers, type `C-x C-b'. Each line
-in the list shows one buffer's name, major mode, and visited file. A
-`*' at the beginning of a line indicates the buffer has been
-"modified". If several buffers are modified, it may be time to save
-some with `C-x s' (*note Saving::). A `%' indicates a read-only
-buffer. A `.' marks the selected buffer. Here is an example of a
-buffer list:
-
- MR Buffer Size Mode File
- -- ------ ---- ---- ----
- .* emacs.tex 383402 Texinfo /u2/emacs/man/emacs.tex
- *Help* 1287 Fundamental
- files.el 23076 Emacs-Lisp /u2/emacs/lisp/files.el
- % RMAIL 64042 RMAIL /u/rms/RMAIL
- *% man 747 Dired /u2/emacs/man/
- net.emacs 343885 Fundamental /u/rms/net.emacs
- fileio.c 27691 C /u2/emacs/src/fileio.c
- NEWS 67340 Text /u2/emacs/etc/NEWS
- *scratch* 0 Lisp Interaction
-
-Note that the buffer `*Help*' was made by a help request; it is not
-visiting any file. The buffer `man' was made by Dired on the directory
-`/u2/emacs/man/'.
-
- As you move the mouse over the `*Buffer List*' buffer, the lines are
-highlighted. This visual cue indicates that clicking the right mouse
-button (`button3') will pop up a menu of commands on the buffer
-represented by this line. This menu duplicates most of those commands
-which are bound to keys in the `*Buffer List*' buffer.
-
-\1f
-File: xemacs.info, Node: Misc Buffer, Next: Kill Buffer, Prev: List Buffers, Up: Buffers
-
-Miscellaneous Buffer Operations
-===============================
-
-`C-x C-q'
- Toggle read-only status of buffer (`toggle-read-only').
-
-`M-x rename-buffer'
- Change the name of the current buffer.
-
-`M-x view-buffer'
- Scroll through a buffer.
-
- A buffer can be "read-only", which means that commands to change its
-text are not allowed. Normally, read-only buffers are created by
-subsystems such as Dired and Rmail that have special commands to operate
-on the text. Emacs also creates a read-only buffer if you visit a file
-that is protected. To make changes in a read-only buffer, use the
-command `C-x C-q' (`toggle-read-only'). It makes a read-only buffer
-writable, and makes a writable buffer read-only. This works by setting
-the variable `buffer-read-only', which has a local value in each buffer
-and makes a buffer read-only if its value is non-`nil'.
-
- `M-x rename-buffer' changes the name of the current buffer,
-prompting for the new name in the minibuffer. There is no default. If
-you specify a name that is used by a different buffer, an error is
-signalled and renaming is not done.
-
- `M-x view-buffer' is similar to `M-x view-file' (*note Misc File
-Ops::), but it examines an already existing Emacs buffer. View mode
-provides convenient commands for scrolling through the buffer but not
-for changing it. When you exit View mode, the resulting value of point
-remains in effect.
-
- To copy text from one buffer to another, use the commands `M-x
-append-to-buffer' and `M-x insert-buffer'. *Note Accumulating Text::.
-
-\1f
-File: xemacs.info, Node: Kill Buffer, Next: Several Buffers, Prev: Misc Buffer, Up: Buffers
-
-Killing Buffers
-===============
-
- After using Emacs for a while, you may accumulate a large number of
-buffers and may want to eliminate the ones you no longer need. There
-are several commands for doing this.
-
-`C-x k'
- Kill a buffer, specified by name (`kill-buffer').
-
-`M-x kill-some-buffers'
- Offer to kill each buffer, one by one.
-
- `C-x k' (`kill-buffer') kills one buffer, whose name you specify in
-the minibuffer. If you type just <RET> in the minibuffer, the default,
-killing the current buffer, is used. If the current buffer is killed,
-the buffer that has been selected recently but does not appear in any
-window now is selected. If the buffer being killed contains unsaved
-changes, you are asked to confirm with `yes' before the buffer is
-killed.
-
- The command `M-x kill-some-buffers' asks about each buffer, one by
-one. An answer of `y' means to kill the buffer. Killing the current
-buffer or a buffer containing unsaved changes selects a new buffer or
-asks for confirmation just like `kill-buffer'.
-
-\1f
-File: xemacs.info, Node: Several Buffers, Prev: Kill Buffer, Up: Buffers
-
-Operating on Several Buffers
-============================
-
- The "buffer-menu" facility is like a "Dired for buffers"; it allows
-you to request operations on various Emacs buffers by editing a buffer
-containing a list of them. You can save buffers, kill them (here
-called "deleting" them, for consistency with Dired), or display them.
-
-`M-x buffer-menu'
- Begin editing a buffer listing all Emacs buffers.
-
- The command `buffer-menu' writes a list of all Emacs buffers into
-the buffer `*Buffer List*', and selects that buffer in Buffer Menu
-mode. The buffer is read-only. You can only change it using the
-special commands described in this section. Most of the commands are
-graphic characters. You can use Emacs cursor motion commands in the
-`*Buffer List*' buffer. If the cursor is on a line describing a
-buffer, the following special commands apply to that buffer:
-
-`d'
- Request to delete (kill) the buffer, then move down. A `D' before
- the buffer name on a line indicates a deletion request. Requested
- deletions actually take place when you use the `x' command.
-
-`k'
- Synonym for `d'.
-
-`C-d'
- Like `d' but move up afterwards instead of down.
-
-`s'
- Request to save the buffer. An `S' before the buffer name on a
- line indicates the request. Requested saves actually take place
- when you use the `x' command. You can request both saving and
- deletion for the same buffer.
-
-`~'
- Mark buffer "unmodified". The command `~' does this immediately
- when typed.
-
-`x'
- Perform previously requested deletions and saves.
-
-`u'
- Remove any request made for the current line, and move down.
-
-`<DEL>'
- Move to previous line and remove any request made for that line.
-
- All commands that add or remove flags to request later operations
-also move down a line. They accept a numeric argument as a repeat
-count, unless otherwise specified.
-
- There are also special commands to use the buffer list to select
-another buffer, and to specify one or more other buffers for display in
-additional windows.
-
-`1'
- Select the buffer in a full-frame window. This command takes
- effect immediately.
-
-`2'
- Immediately set up two windows, with this buffer in one and the
- buffer selected before `*Buffer List*' in the other.
-
-`f'
- Immediately select the buffer in place of the `*Buffer List*'
- buffer.
-
-`o'
- Immediately select the buffer in another window as if by `C-x 4 b',
- leaving `*Buffer List*' visible.
-
-`q'
- Immediately select this buffer, and display any buffers previously
- flagged with the `m' command in other windows. If there are no
- buffers flagged with `m', this command is equivalent to `1'.
-
-`m'
- Flag this buffer to be displayed in another window if the `q'
- command is used. The request shows as a `>' at the beginning of
- the line. The same buffer may not have both a delete request and a
- display request.
-
- Going back between a `buffer-menu' buffer and other Emacs buffers is
-easy. You can, for example, switch from the `*Buffer List*' buffer to
-another Emacs buffer, and edit there. You can then reselect the
-`buffer-menu' buffer and perform operations already requested, or you
-can kill that buffer or pay no further attention to it. All that
-`buffer-menu' does directly is create and select a suitable buffer, and
-turn on Buffer Menu mode. All the other capabilities of the buffer
-menu are implemented by special commands provided in Buffer Menu mode.
-
- The only difference between `buffer-menu' and `list-buffers' is that
-`buffer-menu' selects the `*Buffer List*' buffer and `list-buffers'
-does not. If you run `list-buffers' (that is, type `C-x C-b') and
-select the buffer list manually, you can use all the commands described
-here.
-
-\1f
-File: xemacs.info, Node: Windows, Next: Mule, Prev: Buffers, Up: Top
-
-Multiple Windows
-****************
-
- Emacs can split the frame into two or many windows, which can display
-parts of different buffers or different parts of one buffer. If you are
-running XEmacs under X, that means you can have the X window that
-contains the Emacs frame have multiple subwindows.
-
-* Menu:
-
-* Basic Window:: Introduction to Emacs windows.
-* Split Window:: New windows are made by splitting existing windows.
-* Other Window:: Moving to another window or doing something to it.
-* Pop Up Window:: Finding a file or buffer in another window.
-* Change Window:: Deleting windows and changing their sizes.
-
-\1f
-File: xemacs.info, Node: Basic Window, Next: Split Window, Prev: Windows, Up: Windows
-
-Concepts of Emacs Windows
-=========================
-
- When Emacs displays multiple windows, each window has one Emacs
-buffer designated for display. The same buffer may appear in more than
-one window; if it does, any changes in its text are displayed in all
-the windows that display it. Windows showing the same buffer can show
-different parts of it, because each window has its own value of point.
-
- At any time, one window is the "selected window"; the buffer
-displayed by that window is the current buffer. The cursor shows the
-location of point in that window. Each other window has a location of
-point as well, but since the terminal has only one cursor, it cannot
-show the location of point in the other windows.
-
- Commands to move point affect the value of point for the selected
-Emacs window only. They do not change the value of point in any other
-Emacs window, including those showing the same buffer. The same is
-true for commands such as `C-x b' to change the selected buffer in the
-selected window; they do not affect other windows at all. However,
-there are other commands such as `C-x 4 b' that select a different
-window and switch buffers in it. Also, all commands that display
-information in a window, including (for example) `C-h f'
-(`describe-function') and `C-x C-b' (`list-buffers'), work by switching
-buffers in a non-selected window without affecting the selected window.
-
- Each window has its own mode line, which displays the buffer name,
-modification status, and major and minor modes of the buffer that is
-displayed in the window. *Note Mode Line::, for details on the mode
-line.
-
-\1f
-File: xemacs.info, Node: Split Window, Next: Other Window, Prev: Basic Window, Up: Windows
-
-Splitting Windows
-=================
-
-`C-x 2'
- Split the selected window into two windows, one above the other
- (`split-window-vertically').
-
-`C-x 3'
- Split the selected window into two windows positioned side by side
- (`split-window-horizontally').
-
-`C-x 6'
- Save the current window configuration in register REG (a letter).
-
-`C-x 7'
- Restore (make current) the window configuration in register REG (a
- letter). Use with a register previously set with `C-x 6'.
-
- The command `C-x 2' (`split-window-vertically') breaks the selected
-window into two windows, one above the other. Both windows start out
-displaying the same buffer, with the same value of point. By default
-each of the two windows gets half the height of the window that was
-split. A numeric argument specifies how many lines to give to the top
-window.
-
- `C-x 3' (`split-window-horizontally') breaks the selected window
-into two side-by-side windows. A numeric argument specifies how many
-columns to give the one on the left. A line of vertical bars separates
-the two windows. Windows that are not the full width of the frame have
-truncated mode lines which do not always appear in inverse video,
-because Emacs display routines cannot display a region of inverse video
-that is only part of a line on the screen.
-
- When a window is less than the full width, many text lines are too
-long to fit. Continuing all those lines might be confusing. Set the
-variable `truncate-partial-width-windows' to non-`nil' to force
-truncation in all windows less than the full width of the frame,
-independent of the buffer and its value for `truncate-lines'. *Note
-Continuation Lines::.
-
- Horizontal scrolling is often used in side-by-side windows. *Note
-Display::.
-
- You can resize a window and store that configuration in a register by
-supplying a REGISTER argument to `window-configuration-to-register'
-(`C-x 6'). To return to the window configuration established with
-`window-configuration-to-register', use `jump-to-register' (`C-x j').
-
-This is ../info/xemacs.info, produced by makeinfo version 4.0 from
+This is ../info/xemacs.info, produced by makeinfo version 4.0b from
xemacs/xemacs.texi.
INFO-DIR-SECTION XEmacs Editor
translation approved by the author instead of in the original English.
\1f
+File: xemacs.info, Node: Dired Deletion, Next: Dired Immed, Prev: Dired Edit, Up: Dired
+
+Deleting Files With Dired
+-------------------------
+
+ The primary use of Dired is to flag files for deletion and then
+delete them.
+
+`d'
+ Flag this file for deletion.
+
+`u'
+ Remove deletion-flag on this line.
+
+`<DEL>'
+ Remove deletion-flag on previous line, moving point to that line.
+
+`x'
+ Delete the files that are flagged for deletion.
+
+`#'
+ Flag all auto-save files (files whose names start and end with `#')
+ for deletion (*note Auto Save::).
+
+`~'
+ Flag all backup files (files whose names end with `~') for deletion
+ (*note Backup::).
+
+`. (Period)'
+ Flag excess numeric backup files for deletion. The oldest and
+ newest few backup files of any one file are exempt; the middle
+ ones are flagged.
+
+ You can flag a file for deletion by moving to the line describing the
+file and typing `d' or `C-d'. The deletion flag is visible as a `D' at
+the beginning of the line. Point is moved to the beginning of the next
+line, so that repeated `d' commands flag successive files.
+
+ The files are flagged for deletion rather than deleted immediately to
+avoid the danger of deleting a file accidentally. Until you direct
+Dired to delete the flagged files, you can remove deletion flags using
+the commands `u' and <DEL>. `u' works just like `d', but removes flags
+rather than making flags. <DEL> moves upward, removing flags; it is
+like `u' with numeric argument automatically negated.
+
+ To delete the flagged files, type `x'. This command first displays a
+list of all the file names flagged for deletion, and requests
+confirmation with `yes'. Once you confirm, all the flagged files are
+deleted, and their lines are deleted from the text of the Dired buffer.
+The shortened Dired buffer remains selected. If you answer `no' or
+quit with `C-g', you return immediately to Dired, with the deletion
+flags still present and no files actually deleted.
+
+ The `#', `~', and `.' commands flag many files for deletion, based
+on their names. These commands are useful precisely because they do
+not actually delete any files; you can remove the deletion flags from
+any flagged files that you really wish to keep.
+
+ `#' flags for deletion all files that appear to have been made by
+auto-saving (that is, files whose names begin and end with `#'). `~'
+flags for deletion all files that appear to have been made as backups
+for files that were edited (that is, files whose names end with `~').
+
+ `.' (Period) flags just some of the backup files for deletion: only
+numeric backups that are not among the oldest few nor the newest few
+backups of any one file. Normally `dired-kept-versions' (not
+`kept-new-versions'; that applies only when saving) specifies the
+number of newest versions of each file to keep, and `kept-old-versions'
+specifies the number of oldest versions to keep. Period with a
+positive numeric argument, as in `C-u 3 .', specifies the number of
+newest versions to keep, overriding `dired-kept-versions'. A negative
+numeric argument overrides `kept-old-versions', using minus the value
+of the argument to specify the number of oldest versions of each file
+to keep.
+
+\1f
+File: xemacs.info, Node: Dired Immed, Prev: Dired Deletion, Up: Dired
+
+Immediate File Operations in Dired
+----------------------------------
+
+ Some file operations in Dired take place immediately when they are
+requested.
+
+`C'
+ Copies the file described on the current line. You must supply a
+ file name to copy to, using the minibuffer.
+
+`f'
+ Visits the file described on the current line. It is just like
+ typing `C-x C-f' and supplying that file name. If the file on
+ this line is a subdirectory, `f' actually causes Dired to be
+ invoked on that subdirectory. *Note Visiting::.
+
+`o'
+ Like `f', but uses another window to display the file's buffer.
+ The Dired buffer remains visible in the first window. This is
+ like using `C-x 4 C-f' to visit the file. *Note Windows::.
+
+`R'
+ Renames the file described on the current line. You must supply a
+ file name to rename to, using the minibuffer.
+
+`v'
+ Views the file described on this line using `M-x view-file'.
+ Viewing a file is like visiting it, but is slanted toward moving
+ around in the file conveniently and does not allow changing the
+ file. *Note View File: Misc File Ops. Viewing a file that is a
+ directory runs Dired on that directory.
+
+\1f
+File: xemacs.info, Node: Misc File Ops, Prev: Dired, Up: Files
+
+Miscellaneous File Operations
+=============================
+
+ Emacs has commands for performing many other operations on files.
+All operate on one file; they do not accept wildcard file names.
+
+ You can use the command `M-x add-name-to-file' to add a name to an
+existing file without removing the old name. The new name must belong
+on the file system that the file is on.
+
+ `M-x append-to-file' adds the text of the region to the end of the
+specified file.
+
+ `M-x copy-file' reads the file OLD and writes a new file named NEW
+with the same contents. Confirmation is required if a file named NEW
+already exists, because copying overwrites the old contents of the file
+NEW.
+
+ `M-x delete-file' deletes a specified file, like the `rm' command in
+the shell. If you are deleting many files in one directory, it may be
+more convenient to use Dired (*note Dired::).
+
+ `M-x insert-file' inserts a copy of the contents of a specified file
+into the current buffer at point, leaving point unchanged before the
+contents and the mark after them. *Note Mark::.
+
+ `M-x make-symbolic-link' reads two file names OLD and LINKNAME, and
+then creates a symbolic link named LINKNAME and pointing at OLD.
+Future attempts to open file LINKNAME will then refer to the file named
+OLD at the time the opening is done, or will result in an error if the
+name OLD is not in use at that time. Confirmation is required if you
+create the link while LINKNAME is in use. Note that not all systems
+support symbolic links.
+
+ `M-x rename-file' reads two file names OLD and NEW using the
+minibuffer, then renames file OLD as NEW. If a file named NEW already
+exists, you must confirm with `yes' or renaming is not done; this is
+because renaming causes the previous meaning of the name NEW to be
+lost. If OLD and NEW are on different file systems, the file OLD is
+copied and deleted.
+
+ `M-x view-file' allows you to scan or read a file by sequential
+screenfuls. It reads a file name argument using the minibuffer. After
+reading the file into an Emacs buffer, `view-file' reads and displays
+one windowful. You can then type <SPC> to scroll forward one window,
+or <DEL> to scroll backward. Various other commands are provided for
+moving around in the file, but none for changing it; type `C-h' while
+viewing a file for a list of them. Most commands are the default Emacs
+cursor motion commands. To exit from viewing, type `C-c'.
+
+\1f
+File: xemacs.info, Node: Buffers, Next: Windows, Prev: Files, Up: Top
+
+Using Multiple Buffers
+**********************
+
+ Text you are editing in Emacs resides in an object called a
+"buffer". Each time you visit a file, Emacs creates a buffer to hold
+the file's text. Each time you invoke Dired, Emacs creates a buffer to
+hold the directory listing. If you send a message with `C-x m', a
+buffer named `*mail*' is used to hold the text of the message. When
+you ask for a command's documentation, it appears in a buffer called
+`*Help*'.
+
+ At any time, one and only one buffer is "selected". It is also
+called the "current buffer". Saying a command operates on "the buffer"
+really means that the command operates on the selected buffer, as most
+commands do.
+
+ When Emacs creates multiple windows, each window has a chosen buffer
+which is displayed there, but at any time only one of the windows is
+selected and its chosen buffer is the selected buffer. Each window's
+mode line displays the name of the buffer the window is displaying
+(*note Windows::).
+
+ Each buffer has a name which can be of any length but is
+case-sensitive. You can select a buffer using its name. Most buffers
+are created when you visit files; their names are derived from the
+files' names. You can also create an empty buffer with any name you
+want. A newly started Emacs has a buffer named `*scratch*' which you
+can use for evaluating Lisp expressions in Emacs.
+
+ Each buffer records what file it is visiting, whether it is
+modified, and what major mode and minor modes are in effect in it
+(*note Major Modes::). Any Emacs variable can be made "local to" a
+particular buffer, meaning its value in that buffer can be different
+from the value in other buffers. *Note Locals::.
+
+* Menu:
+
+* Select Buffer:: Creating a new buffer or reselecting an old one.
+* List Buffers:: Getting a list of buffers that exist.
+* Misc Buffer:: Renaming; changing read-onliness; copying text.
+* Kill Buffer:: Killing buffers you no longer need.
+* Several Buffers:: How to go through the list of all buffers
+ and operate variously on several of them.
+
+\1f
+File: xemacs.info, Node: Select Buffer, Next: List Buffers, Prev: Buffers, Up: Buffers
+
+Creating and Selecting Buffers
+==============================
+
+`C-x b BUFFER <RET>'
+ Select or create a buffer named BUFFER (`switch-to-buffer').
+
+`C-x 4 b BUFFER <RET>'
+ Similar, but select a buffer named BUFFER in another window
+ (`switch-to-buffer-other-window').
+
+`M-x switch-to-other-buffer N'
+ Switch to the previous buffer.
+
+ To select a buffer named BUFNAME, type `C-x b BUFNAME <RET>'. This
+is the command `switch-to-buffer' with argument BUFNAME. You can use
+completion on an abbreviation for the buffer name you want (*note
+Completion::). An empty argument to `C-x b' specifies the most
+recently selected buffer that is not displayed in any window.
+
+ Most buffers are created when you visit files, or use Emacs commands
+that display text. You can also create a buffer explicitly by typing
+`C-x b BUFNAME <RET>', which creates a new, empty buffer that is not
+visiting any file, and selects it for editing. The new buffer's major
+mode is determined by the value of `default-major-mode' (*note Major
+Modes::). Buffers not visiting files are usually used for making notes
+to yourself. If you try to save one, you are asked for the file name
+to use.
+
+ The function `switch-to-buffer-other-frame' is similar to
+`switch-to-buffer' except that it creates a new frame in which to
+display the selected buffer.
+
+ Use `M-x switch-to-other-buffer' to visit the previous buffer. If
+you supply a positive integer N, the Nth most recent buffer is
+displayed. If you supply an argument of 0, the current buffer is moved
+to the bottom of the buffer stack.
+
+ Note that you can also use `C-x C-f' and any other command for
+visiting a file to switch buffers. *Note Visiting::.
+
+\1f
+File: xemacs.info, Node: List Buffers, Next: Misc Buffer, Prev: Select Buffer, Up: Buffers
+
+Listing Existing Buffers
+========================
+
+`C-x C-b'
+ List the existing buffers (`list-buffers').
+
+ To print a list of all existing buffers, type `C-x C-b'. Each line
+in the list shows one buffer's name, major mode, and visited file. A
+`*' at the beginning of a line indicates the buffer has been
+"modified". If several buffers are modified, it may be time to save
+some with `C-x s' (*note Saving::). A `%' indicates a read-only
+buffer. A `.' marks the selected buffer. Here is an example of a
+buffer list:
+
+ MR Buffer Size Mode File
+ -- ------ ---- ---- ----
+ .* emacs.tex 383402 Texinfo /u2/emacs/man/emacs.tex
+ *Help* 1287 Fundamental
+ files.el 23076 Emacs-Lisp /u2/emacs/lisp/files.el
+ % RMAIL 64042 RMAIL /u/rms/RMAIL
+ *% man 747 Dired /u2/emacs/man/
+ net.emacs 343885 Fundamental /u/rms/net.emacs
+ fileio.c 27691 C /u2/emacs/src/fileio.c
+ NEWS 67340 Text /u2/emacs/etc/NEWS
+ *scratch* 0 Lisp Interaction
+
+Note that the buffer `*Help*' was made by a help request; it is not
+visiting any file. The buffer `man' was made by Dired on the directory
+`/u2/emacs/man/'.
+
+ As you move the mouse over the `*Buffer List*' buffer, the lines are
+highlighted. This visual cue indicates that clicking the right mouse
+button (`button3') will pop up a menu of commands on the buffer
+represented by this line. This menu duplicates most of those commands
+which are bound to keys in the `*Buffer List*' buffer.
+
+\1f
+File: xemacs.info, Node: Misc Buffer, Next: Kill Buffer, Prev: List Buffers, Up: Buffers
+
+Miscellaneous Buffer Operations
+===============================
+
+`C-x C-q'
+ Toggle read-only status of buffer (`toggle-read-only').
+
+`M-x rename-buffer'
+ Change the name of the current buffer.
+
+`M-x view-buffer'
+ Scroll through a buffer.
+
+ A buffer can be "read-only", which means that commands to change its
+text are not allowed. Normally, read-only buffers are created by
+subsystems such as Dired and Rmail that have special commands to operate
+on the text. Emacs also creates a read-only buffer if you visit a file
+that is protected. To make changes in a read-only buffer, use the
+command `C-x C-q' (`toggle-read-only'). It makes a read-only buffer
+writable, and makes a writable buffer read-only. This works by setting
+the variable `buffer-read-only', which has a local value in each buffer
+and makes a buffer read-only if its value is non-`nil'.
+
+ `M-x rename-buffer' changes the name of the current buffer,
+prompting for the new name in the minibuffer. There is no default. If
+you specify a name that is used by a different buffer, an error is
+signalled and renaming is not done.
+
+ `M-x view-buffer' is similar to `M-x view-file' (*note Misc File
+Ops::), but it examines an already existing Emacs buffer. View mode
+provides convenient commands for scrolling through the buffer but not
+for changing it. When you exit View mode, the resulting value of point
+remains in effect.
+
+ To copy text from one buffer to another, use the commands `M-x
+append-to-buffer' and `M-x insert-buffer'. *Note Accumulating Text::.
+
+\1f
+File: xemacs.info, Node: Kill Buffer, Next: Several Buffers, Prev: Misc Buffer, Up: Buffers
+
+Killing Buffers
+===============
+
+ After using Emacs for a while, you may accumulate a large number of
+buffers and may want to eliminate the ones you no longer need. There
+are several commands for doing this.
+
+`C-x k'
+ Kill a buffer, specified by name (`kill-buffer').
+
+`M-x kill-some-buffers'
+ Offer to kill each buffer, one by one.
+
+ `C-x k' (`kill-buffer') kills one buffer, whose name you specify in
+the minibuffer. If you type just <RET> in the minibuffer, the default,
+killing the current buffer, is used. If the current buffer is killed,
+the buffer that has been selected recently but does not appear in any
+window now is selected. If the buffer being killed contains unsaved
+changes, you are asked to confirm with `yes' before the buffer is
+killed.
+
+ The command `M-x kill-some-buffers' asks about each buffer, one by
+one. An answer of `y' means to kill the buffer. Killing the current
+buffer or a buffer containing unsaved changes selects a new buffer or
+asks for confirmation just like `kill-buffer'.
+
+\1f
+File: xemacs.info, Node: Several Buffers, Prev: Kill Buffer, Up: Buffers
+
+Operating on Several Buffers
+============================
+
+ The "buffer-menu" facility is like a "Dired for buffers"; it allows
+you to request operations on various Emacs buffers by editing a buffer
+containing a list of them. You can save buffers, kill them (here
+called "deleting" them, for consistency with Dired), or display them.
+
+`M-x buffer-menu'
+ Begin editing a buffer listing all Emacs buffers.
+
+ The command `buffer-menu' writes a list of all Emacs buffers into
+the buffer `*Buffer List*', and selects that buffer in Buffer Menu
+mode. The buffer is read-only. You can only change it using the
+special commands described in this section. Most of the commands are
+graphic characters. You can use Emacs cursor motion commands in the
+`*Buffer List*' buffer. If the cursor is on a line describing a
+buffer, the following special commands apply to that buffer:
+
+`d'
+ Request to delete (kill) the buffer, then move down. A `D' before
+ the buffer name on a line indicates a deletion request. Requested
+ deletions actually take place when you use the `x' command.
+
+`k'
+ Synonym for `d'.
+
+`C-d'
+ Like `d' but move up afterwards instead of down.
+
+`s'
+ Request to save the buffer. An `S' before the buffer name on a
+ line indicates the request. Requested saves actually take place
+ when you use the `x' command. You can request both saving and
+ deletion for the same buffer.
+
+`~'
+ Mark buffer "unmodified". The command `~' does this immediately
+ when typed.
+
+`x'
+ Perform previously requested deletions and saves.
+
+`u'
+ Remove any request made for the current line, and move down.
+
+`<DEL>'
+ Move to previous line and remove any request made for that line.
+
+ All commands that add or remove flags to request later operations
+also move down a line. They accept a numeric argument as a repeat
+count, unless otherwise specified.
+
+ There are also special commands to use the buffer list to select
+another buffer, and to specify one or more other buffers for display in
+additional windows.
+
+`1'
+ Select the buffer in a full-frame window. This command takes
+ effect immediately.
+
+`2'
+ Immediately set up two windows, with this buffer in one and the
+ buffer selected before `*Buffer List*' in the other.
+
+`f'
+ Immediately select the buffer in place of the `*Buffer List*'
+ buffer.
+
+`o'
+ Immediately select the buffer in another window as if by `C-x 4 b',
+ leaving `*Buffer List*' visible.
+
+`q'
+ Immediately select this buffer, and display any buffers previously
+ flagged with the `m' command in other windows. If there are no
+ buffers flagged with `m', this command is equivalent to `1'.
+
+`m'
+ Flag this buffer to be displayed in another window if the `q'
+ command is used. The request shows as a `>' at the beginning of
+ the line. The same buffer may not have both a delete request and a
+ display request.
+
+ Going back between a `buffer-menu' buffer and other Emacs buffers is
+easy. You can, for example, switch from the `*Buffer List*' buffer to
+another Emacs buffer, and edit there. You can then reselect the
+`buffer-menu' buffer and perform operations already requested, or you
+can kill that buffer or pay no further attention to it. All that
+`buffer-menu' does directly is create and select a suitable buffer, and
+turn on Buffer Menu mode. All the other capabilities of the buffer
+menu are implemented by special commands provided in Buffer Menu mode.
+
+ The only difference between `buffer-menu' and `list-buffers' is that
+`buffer-menu' selects the `*Buffer List*' buffer and `list-buffers'
+does not. If you run `list-buffers' (that is, type `C-x C-b') and
+select the buffer list manually, you can use all the commands described
+here.
+
+\1f
+File: xemacs.info, Node: Windows, Next: Mule, Prev: Buffers, Up: Top
+
+Multiple Windows
+****************
+
+ Emacs can split the frame into two or many windows, which can display
+parts of different buffers or different parts of one buffer. If you are
+running XEmacs under X, that means you can have the X window that
+contains the Emacs frame have multiple subwindows.
+
+* Menu:
+
+* Basic Window:: Introduction to Emacs windows.
+* Split Window:: New windows are made by splitting existing windows.
+* Other Window:: Moving to another window or doing something to it.
+* Pop Up Window:: Finding a file or buffer in another window.
+* Change Window:: Deleting windows and changing their sizes.
+
+\1f
+File: xemacs.info, Node: Basic Window, Next: Split Window, Prev: Windows, Up: Windows
+
+Concepts of Emacs Windows
+=========================
+
+ When Emacs displays multiple windows, each window has one Emacs
+buffer designated for display. The same buffer may appear in more than
+one window; if it does, any changes in its text are displayed in all
+the windows that display it. Windows showing the same buffer can show
+different parts of it, because each window has its own value of point.
+
+ At any time, one window is the "selected window"; the buffer
+displayed by that window is the current buffer. The cursor shows the
+location of point in that window. Each other window has a location of
+point as well, but since the terminal has only one cursor, it cannot
+show the location of point in the other windows.
+
+ Commands to move point affect the value of point for the selected
+Emacs window only. They do not change the value of point in any other
+Emacs window, including those showing the same buffer. The same is
+true for commands such as `C-x b' to change the selected buffer in the
+selected window; they do not affect other windows at all. However,
+there are other commands such as `C-x 4 b' that select a different
+window and switch buffers in it. Also, all commands that display
+information in a window, including (for example) `C-h f'
+(`describe-function') and `C-x C-b' (`list-buffers'), work by switching
+buffers in a non-selected window without affecting the selected window.
+
+ Each window has its own mode line, which displays the buffer name,
+modification status, and major and minor modes of the buffer that is
+displayed in the window. *Note Mode Line::, for details on the mode
+line.
+
+\1f
+File: xemacs.info, Node: Split Window, Next: Other Window, Prev: Basic Window, Up: Windows
+
+Splitting Windows
+=================
+
+`C-x 2'
+ Split the selected window into two windows, one above the other
+ (`split-window-vertically').
+
+`C-x 3'
+ Split the selected window into two windows positioned side by side
+ (`split-window-horizontally').
+
+`C-x 6'
+ Save the current window configuration in register REG (a letter).
+
+`C-x 7'
+ Restore (make current) the window configuration in register REG (a
+ letter). Use with a register previously set with `C-x 6'.
+
+ The command `C-x 2' (`split-window-vertically') breaks the selected
+window into two windows, one above the other. Both windows start out
+displaying the same buffer, with the same value of point. By default
+each of the two windows gets half the height of the window that was
+split. A numeric argument specifies how many lines to give to the top
+window.
+
+ `C-x 3' (`split-window-horizontally') breaks the selected window
+into two side-by-side windows. A numeric argument specifies how many
+columns to give the one on the left. A line of vertical bars separates
+the two windows. Windows that are not the full width of the frame have
+truncated mode lines which do not always appear in inverse video,
+because Emacs display routines cannot display a region of inverse video
+that is only part of a line on the screen.
+
+ When a window is less than the full width, many text lines are too
+long to fit. Continuing all those lines might be confusing. Set the
+variable `truncate-partial-width-windows' to non-`nil' to force
+truncation in all windows less than the full width of the frame,
+independent of the buffer and its value for `truncate-lines'. *Note
+Continuation Lines::.
+
+ Horizontal scrolling is often used in side-by-side windows. *Note
+Display::.
+
+ You can resize a window and store that configuration in a register by
+supplying a REGISTER argument to `window-configuration-to-register'
+(`C-x 6'). To return to the window configuration established with
+`window-configuration-to-register', use `jump-to-register' (`C-x j').
+
+\1f
File: xemacs.info, Node: Other Window, Next: Pop Up Window, Prev: Split Window, Up: Windows
Using Other Windows
system, you can specify a different coding system for the buffer using
`set-buffer-file-coding-system' (*note Specify Coding::).
-\1f
-File: xemacs.info, Node: Specify Coding, Prev: Recognize Coding, Up: Mule
-
-Specifying a Coding System
-==========================
-
- In cases where XEmacs does not automatically choose the right coding
-system, you can use these commands to specify one:
-
-`C-x <RET> f CODING <RET>'
- Use coding system CODING for the visited file in the current
- buffer.
-
-`C-x <RET> c CODING <RET>'
- Specify coding system CODING for the immediately following command.
-
-`C-x <RET> k CODING <RET>'
- Use coding system CODING for keyboard input.
-
-`C-x <RET> t CODING <RET>'
- Use coding system CODING for terminal output.
-
-`C-x <RET> p CODING <RET>'
- Use coding system CODING for subprocess input and output in the
- current buffer.
-
- The command `C-x RET f' (`set-buffer-file-coding-system') specifies
-the file coding system for the current buffer--in other words, which
-coding system to use when saving or rereading the visited file. You
-specify which coding system using the minibuffer. Since this command
-applies to a file you have already visited, it affects only the way the
-file is saved.
-
- Another way to specify the coding system for a file is when you visit
-the file. First use the command `C-x <RET> c'
-(`universal-coding-system-argument'); this command uses the minibuffer
-to read a coding system name. After you exit the minibuffer, the
-specified coding system is used for _the immediately following command_.
-
- So if the immediately following command is `C-x C-f', for example,
-it reads the file using that coding system (and records the coding
-system for when the file is saved). Or if the immediately following
-command is `C-x C-w', it writes the file using that coding system.
-Other file commands affected by a specified coding system include `C-x
-C-i' and `C-x C-v', as well as the other-window variants of `C-x C-f'.
-
- In addition, if you run some file input commands with the precedent
-`C-u', you can specify coding system to read from minibuffer. So if
-the immediately following command is `C-x C-f', for example, it reads
-the file using that coding system (and records the coding system for
-when the file is saved). Other file commands affected by a specified
-coding system include `C-x C-i' and `C-x C-v', as well as the
-other-window variants of `C-x C-f'.
-
- The variable `default-buffer-file-coding-system' specifies the
-choice of coding system to use when you create a new file. It applies
-when you find a new file, and when you create a buffer and then save it
-in a file. Selecting a language environment typically sets this
-variable to a good choice of default coding system for that language
-environment.
-
- The command `C-x <RET> t' (`set-terminal-coding-system') specifies
-the coding system for terminal output. If you specify a character code
-for terminal output, all characters output to the terminal are
-translated into that coding system.
-
- This feature is useful for certain character-only terminals built to
-support specific languages or character sets--for example, European
-terminals that support one of the ISO Latin character sets.
-
- By default, output to the terminal is not translated at all.
-
- The command `C-x <RET> k' (`set-keyboard-coding-system') specifies
-the coding system for keyboard input. Character-code translation of
-keyboard input is useful for terminals with keys that send non-ASCII
-graphic characters--for example, some terminals designed for ISO
-Latin-1 or subsets of it.
-
- By default, keyboard input is not translated at all.
-
- There is a similarity between using a coding system translation for
-keyboard input, and using an input method: both define sequences of
-keyboard input that translate into single characters. However, input
-methods are designed to be convenient for interactive use by humans, and
-the sequences that are translated are typically sequences of ASCII
-printing characters. Coding systems typically translate sequences of
-non-graphic characters.
-
- The command `C-x <RET> p' (`set-buffer-process-coding-system')
-specifies the coding system for input and output to a subprocess. This
-command applies to the current buffer; normally, each subprocess has its
-own buffer, and thus you can use this command to specify translation to
-and from a particular subprocess by giving the command in the
-corresponding buffer.
-
- By default, process input and output are not translated at all.
-
- The variable `file-name-coding-system' specifies a coding system to
-use for encoding file names. If you set the variable to a coding
-system name (as a Lisp symbol or a string), XEmacs encodes file names
-using that coding system for all file operations. This makes it
-possible to use non-Latin-1 characters in file names--or, at least,
-those non-Latin-1 characters which the specified coding system can
-encode. By default, this variable is `nil', which implies that you
-cannot use non-Latin-1 characters in file names.
-
-\1f
-File: xemacs.info, Node: Major Modes, Next: Indentation, Prev: Mule, Up: Top
-
-Major Modes
-***********
-
- Emacs has many different "major modes", each of which customizes
-Emacs for editing text of a particular sort. The major modes are
-mutually exclusive; at any time, each buffer has one major mode. The
-mode line normally contains the name of the current major mode in
-parentheses. *Note Mode Line::.
-
- The least specialized major mode is called "Fundamental mode". This
-mode has no mode-specific redefinitions or variable settings. Each
-Emacs command behaves in its most general manner, and each option is in
-its default state. For editing any specific type of text, such as Lisp
-code or English text, you should switch to the appropriate major mode,
-such as Lisp mode or Text mode.
-
- Selecting a major mode changes the meanings of a few keys to become
-more specifically adapted to the language being edited. <TAB>, <DEL>,
-and <LFD> are changed frequently. In addition, commands which handle
-comments use the mode to determine how to delimit comments. Many major
-modes redefine the syntactical properties of characters appearing in
-the buffer. *Note Syntax::.
-
- The major modes fall into three major groups. Lisp mode (which has
-several variants), C mode, and Muddle mode are for specific programming
-languages. Text mode, Nroff mode, TeX mode, and Outline mode are for
-editing English text. The remaining major modes are not intended for
-use on users' files; they are used in buffers created by Emacs for
-specific purposes and include Dired mode for buffers made by Dired
-(*note Dired::), Mail mode for buffers made by `C-x m' (*note Sending
-Mail::), and Shell mode for buffers used for communicating with an
-inferior shell process (*note Interactive Shell::).
-
- Most programming language major modes specify that only blank lines
-separate paragraphs. This is so that the paragraph commands remain
-useful. *Note Paragraphs::. They also cause Auto Fill mode to use the
-definition of <TAB> to indent the new lines it creates. This is
-because most lines in a program are usually indented. *Note
-Indentation::.
-
-* Menu:
-
-* Choosing Modes:: How major modes are specified or chosen.
-
-\1f
-File: xemacs.info, Node: Choosing Modes, Prev: Major Modes, Up: Major Modes
-
-Choosing Major Modes
-====================
-
- You can select a major mode explicitly for the current buffer, but
-most of the time Emacs determines which mode to use based on the file
-name or some text in the file.
-
- Use a `M-x' command to explicitly select a new major mode. Add
-`-mode' to the name of a major mode to get the name of a command to
-select that mode. For example, to enter Lisp mode, execute `M-x
-lisp-mode'.
-
- When you visit a file, Emacs usually chooses the right major mode
-based on the file's name. For example, files whose names end in `.c'
-are edited in C mode. The variable `auto-mode-alist' controls the
-correspondence between file names and major mode. Its value is a list
-in which each element has the form:
-
- (REGEXP . MODE-FUNCTION)
-
-For example, one element normally found in the list has the form
-`("\\.c$" . c-mode)'. It is responsible for selecting C mode for files
-whose names end in `.c'. (Note that `\\' is needed in Lisp syntax to
-include a `\' in the string, which is needed to suppress the special
-meaning of `.' in regexps.) The only practical way to change this
-variable is with Lisp code.
-
- You can specify which major mode should be used for editing a certain
-file by a special sort of text in the first non-blank line of the file.
-The mode name should appear in this line both preceded and followed by
-`-*-'. Other text may appear on the line as well. For example,
-
- ;-*-Lisp-*-
-
-tells Emacs to use Lisp mode. Note how the semicolon is used to make
-Lisp treat this line as a comment. Such an explicit specification
-overrides any default mode based on the file name.
-
- Another format of mode specification is:
-
- -*-Mode: MODENAME;-*-
-
-which allows other things besides the major mode name to be specified.
-However, Emacs does not look for anything except the mode name.
-
- The major mode can also be specified in a local variables list.
-*Note File Variables::.
-
- When you visit a file that does not specify a major mode to use, or
-when you create a new buffer with `C-x b', Emacs uses the major mode
-specified by the variable `default-major-mode'. Normally this value is
-the symbol `fundamental-mode', which specifies Fundamental mode. If
-`default-major-mode' is `nil', the major mode is taken from the
-previously selected buffer.
-
-\1f
-File: xemacs.info, Node: Indentation, Next: Text, Prev: Major Modes, Up: Top
-
-Indentation
-***********
-
-`<TAB>'
- Indent current line "appropriately" in a mode-dependent fashion.
-
-`<LFD>'
- Perform <RET> followed by <TAB> (`newline-and-indent').
-
-`M-^'
- Merge two lines (`delete-indentation'). This would cancel out the
- effect of <LFD>.
-
-`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
- (`split-line').
-
-`M-m'
- Move (forward or back) to the first non-blank character on the
- current line (`back-to-indentation').
-
-`C-M-\'
- Indent several lines to same column (`indent-region').
-
-`C-x <TAB>'
- Shift block of lines rigidly right or left (`indent-rigidly').
-
-`M-i'
- Indent from point to the next prespecified tab stop column
- (`tab-to-tab-stop').
-
-`M-x indent-relative'
- Indent from point to under an indentation point in the previous
- line.
-
- 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 <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, <TAB> aligns a line according
-to its depth in parentheses. No matter where in the line you are when
-you type <TAB>, it aligns the line as a whole. In C mode, <TAB>
-implements a subtle and sophisticated indentation style that knows
-about many aspects of C syntax.
-
- In Text mode, <TAB> runs the command `tab-to-tab-stop', which
-indents to the next tab stop column. You can set the tab stops with
-`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.
-
-\1f
-File: xemacs.info, Node: Indentation Commands, Next: Tab Stops, Prev: Indentation, Up: Indentation
-
-Indentation Commands and Techniques
-===================================
-
- If you just want to insert a tab character in the buffer, you can
-type `C-q <TAB>'.
-
- To move over the indentation on a line, type `Meta-m'
-(`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 `C-a C-o
-<TAB>'. To make an indented line after the current line, use `C-e
-<LFD>'.
-
- `C-M-o' (`split-line') moves the text from point to the end of the
-line vertically down, so that the current line becomes two lines.
-`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, `C-M-o' resembles `C-o'.
-
- To join two lines cleanly, use the `Meta-^' (`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 `Meta-\'
-(`delete-horizontal-space'), which deletes all spaces and tabs around
-the cursor.
-
- There are also commands for changing the indentation of several
-lines at once. `Control-Meta-\' (`indent-region') gives each line which
-begins in the region the "usual" indentation by invoking <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. `C-x <TAB>'
-(`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.
-
- `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, `tab-to-tab-stop' is run
-(see next section).
-
- `indent-relative' is the definition of <TAB> in Indented Text mode.
-*Note Text::.
-
-\1f
-File: xemacs.info, Node: Tab Stops, Next: Just Spaces, Prev: Indentation Commands, Up: Indentation
-
-Tab Stops
-=========
-
- For typing in tables, you can use Text mode's definition of <TAB>,
-`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 `M-i' anyway.
-
- You can arbitrarily set the tab stops used by `M-i'. They are
-stored as a list of column-numbers in increasing order in the variable
-`tab-stop-list'.
-
- The convenient way to set the tab stops is using `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 `C-c C-c' to make those new
-tab stops take effect. In the tab stop buffer, `C-c C-c' runs the
-function `edit-tab-stops-note-changes' rather than the default
-`save-buffer'. `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 `tab-stop-list' local in one buffer
-`edit-tab-stops' in that buffer edits only the local settings.
-
- Below is the text representing ordinary tab stops every eight
-columns:
-
- : : : : : :
- 0 1 2 3 4
- 0123456789012345678901234567890123456789012345678
- To install changes, type C-c C-c
-
- 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 `tab-to-tab-stop' have nothing
-to do with displaying tab characters in the buffer. *Note Display
-Vars::, for more information on that.
-
-\1f
-File: xemacs.info, Node: Just Spaces, Prev: Tab Stops, Up: Indentation
-
-Tabs vs. Spaces
-===============
-
- 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 `indent-tabs-mode' to `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. *Note Locals::.
-
- There are also commands to convert tabs to spaces or vice versa,
-always preserving the columns of all non-blank text. `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. `M-x untabify' changes all tabs in the region to
-corresponding numbers of spaces.
-
-\1f
-File: xemacs.info, Node: Text, Next: Programs, Prev: Indentation, Up: Top
-
-Commands for Human Languages
-****************************
-
- The term "text" has two widespread meanings in our area of the
-computer field. One is data that is a sequence of characters. In this
-sense of the word any file that you edit with Emacs is text. The other
-meaning is more restrictive: a sequence of characters in a human
-language for humans to read (possibly after processing by a text
-formatter), as opposed to a program or commands for a program.
-
- Human languages have syntactic and stylistic conventions that editor
-commands should support or use to advantage: conventions involving
-words, sentences, paragraphs, and capital letters. This chapter
-describes Emacs commands for all these things. There are also commands
-for "filling", or rearranging paragraphs into lines of approximately
-equal length. The commands for moving over and killing words,
-sentences, and paragraphs, while intended primarily for editing text,
-are also often useful for editing programs.
-
- Emacs has several major modes for editing human language text. If a
-file contains plain text, use Text mode, which customizes Emacs in
-small ways for the syntactic conventions of text. For text which
-contains embedded commands for text formatters, Emacs has other major
-modes, each for a particular text formatter. Thus, for input to TeX,
-you can use TeX mode; for input to nroff, Nroff mode.
-
-* Menu:
-
-* Text Mode:: The major modes for editing text files.
-* Nroff Mode:: The major mode for editing input to the formatter nroff.
-* TeX Mode:: The major modes for editing input to the formatter TeX.
-* Outline Mode:: The major mode for editing outlines.
-* Words:: Moving over and killing words.
-* Sentences:: Moving over and killing sentences.
-* Paragraphs:: Moving over paragraphs.
-* Pages:: Moving over pages.
-* Filling:: Filling or justifying text
-* Case:: Changing the case of text
-
-\1f
-File: xemacs.info, Node: Text Mode, Next: Words, Prev: Text, Up: Text
-
-Text Mode
-=========
-
- You should use Text mode--rather than Fundamental or Lisp mode--to
-edit files of text in a human language. Invoke `M-x text-mode' to
-enter Text mode. In Text mode, <TAB> runs the function
-`tab-to-tab-stop', which allows you to use arbitrary tab stops set with
-`M-x edit-tab-stops' (*note Tab Stops::). Features concerned with
-comments in programs are turned off unless they are explicitly invoked.
-The syntax table is changed so that periods are not considered part of a
-word, while apostrophes, backspaces and underlines are.
-
- A similar variant mode is Indented Text mode, intended for editing
-text in which most lines are indented. This mode defines <TAB> to run
-`indent-relative' (*note Indentation::), and makes Auto Fill indent the
-lines it creates. As a result, a line made by Auto Filling, or by
-<LFD>, is normally indented just like the previous line. Use `M-x
-indented-text-mode' to select this mode.
-
- Entering Text mode or Indented Text mode calls the value of the
-variable `text-mode-hook' with no arguments, if that value exists and
-is not `nil'. This value is also called when modes related to Text
-mode are entered; this includes Nroff mode, TeX mode, Outline mode, and
-Mail mode. Your hook can look at the value of `major-mode' to see
-which of these modes is actually being entered.
-
- Two modes similar to Text mode are of use for editing text that is to
-be passed through a text formatter before achieving its final readable
-form.
-
-* Menu:
-
-* Nroff Mode:: The major mode for editing input to the formatter nroff.
-* TeX Mode:: The major modes for editing input to the formatter TeX.
-
-
- Another similar mode is used for editing outlines. It allows you
-to view the text at various levels of detail. You can view either
-the outline headings alone or both headings and text; you can also
-hide some of the headings at lower levels from view to make the high
-level structure more visible.
-
-
-* Outline Mode:: The major mode for editing outlines.
-
-\1f
-File: xemacs.info, Node: Nroff Mode, Next: TeX Mode, Prev: Text Mode, Up: Text Mode
-
-Nroff Mode
-----------
-
- Nroff mode is a mode like Text mode but modified to handle nroff
-commands present in the text. Invoke `M-x nroff-mode' to enter this
-mode. Nroff mode differs from Text mode in only a few ways. All nroff
-command lines are considered paragraph separators, so that filling never
-garbles the nroff commands. Pages are separated by `.bp' commands.
-Comments start with backslash-doublequote. There are also three special
-commands that are not available in Text mode:
-
-`M-n'
- Move to the beginning of the next line that isn't an nroff command
- (`forward-text-line'). An argument is a repeat count.
-
-`M-p'
- Like `M-n' but move up (`backward-text-line').
-
-`M-?'
- Prints in the echo area the number of text lines (lines that are
- not nroff commands) in the region (`count-text-lines').
-
- The other feature of Nroff mode is Electric Nroff newline mode.
-This is a minor mode that you can turn on or off with `M-x
-electric-nroff-mode' (*note Minor Modes::). When the mode is on and
-you use <RET> to end a line containing an nroff command that opens a
-kind of grouping, Emacs automatically inserts the matching nroff
-command to close that grouping on the following line. For example, if
-you are at the beginning of a line and type `.(b <RET>', the matching
-command `.)b' will be inserted on a new line following point.
-
- Entering Nroff mode calls the value of the variable `text-mode-hook'
-with no arguments, if that value exists and is not `nil'; then it does
-the same with the variable `nroff-mode-hook'.
-
-\1f
-File: xemacs.info, Node: TeX Mode, Next: Outline Mode, Prev: Nroff Mode, Up: Text Mode
-
-TeX Mode
---------
-
- TeX is a powerful text formatter written by Donald Knuth; like GNU
-Emacs, it is free. LaTeX is a simplified input format for TeX,
-implemented by TeX macros. It is part of TeX.
-
- Emacs has a special TeX mode for editing TeX input files. It
-provides facilities for checking the balance of delimiters and for
-invoking TeX on all or part of the file.
-
- TeX mode has two variants, Plain TeX mode and LaTeX mode, which are
-two distinct major modes that differ only slightly. These modes are
-designed for editing the two different input formats. The command `M-x
-tex-mode' looks at the contents of a buffer to determine whether it
-appears to be LaTeX input or not; it then selects the appropriate mode.
-If it can't tell which is right (e.g., the buffer is empty), the
-variable `tex-default-mode' controls which mode is used.
-
- The commands `M-x plain-tex-mode' and `M-x latex-mode' explicitly
-select one of the variants of TeX mode. Use these commands when `M-x
-tex-mode' does not guess right.
-
-* Menu:
-
-* Editing: TeX Editing. Special commands for editing in TeX mode.
-* Printing: TeX Print. Commands for printing part of a file with TeX.
-
- TeX for Unix systems can be obtained from the University of
-Washington for a distribution fee.
-
- To order a full distribution, send $140.00 for a 1/2 inch 9-track
-tape, $165.00 for two 4-track 1/4 inch cartridge tapes (foreign sites
-$150.00, for 1/2 inch, $175.00 for 1/4 inch, to cover the extra
-postage) payable to the University of Washington to:
-
- The Director
- Northwest Computer Support Group, DW-10
- University of Washington
- Seattle, Washington 98195
-
-Purchase orders are acceptable, but there is an extra charge of $10.00
-to pay for processing charges. (The total cost comes to $150 for
-domestic sites, $175 for foreign sites).
-
- The normal distribution is a tar tape, blocked 20, 1600 bpi, on an
-industry standard 2400 foot half-inch reel. The physical format for
-the 1/4 inch streamer cartridges uses QIC-11, 8000 bpi, 4-track
-serpentine recording for the SUN. Also, SystemV tapes can be written
-in cpio format, blocked 5120 bytes, ASCII headers.
-
* update-elc.sh (ignore_dirs): Ignore lisp/utf-2000 subdirectory.
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
* files.el (insert-file-contents-literally): Treat file as binary;
call file-name-handlers. [sync with Emacs 20.3.10]
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
+2000-12-27 Martin Buchholz <martin@xemacs.org>
+
+ * byte-optimize.el (byte-optimize-cond):
+ (byte-optimize-cond-1): New.
+ Rewrite `cond' in terms of `if' and `or', which are easier to optimize.
+ Optimizes (cond (x nil)) ==> nil.
+ Provide better diagnostic on malformed expr like (cond foo).
+
+2000-12-20 Stephen J. Turnbull <stephen@xemacs.org>
+
+ * mule/mule-coding.el:
+ mule/mule-cmds.el (reset-language-environment,
+ set-language-environment-coding-systems):
+ Safer default coding-priority-list, corresponding to src/file-coding.h.
+
+2000-12-03 Jorma Laaksonen <jorma.laaksonen@hut.fi>
+
+ * package-admin.el: Allow package removal from
+ early-package-load-path.
+
+2000-12-15 Andreas Jaeger <aj@suse.de>
+
+ * about.el (about-maintainer-info): Update my entry.
+
+2000-12-11 Matt Tucker <tuck@whistlingfish.net>
+
+ * packages.el (locate-library): Add support for bzip2
+ compressed .el files.
+
+2000-12-12 Andy Piper <andy@xemacs.org>
+
+ * package-net.el: new file.
+
+2000-12-01 Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
+
+ * font-lock.el: Add missing C++ keywords.
+
+2000-12-08 Adrian Aichner <adrian@xemacs.org>
+
+ * simple.el (indent-for-comment): Preserve indentation of comments
+ starting in column 0, as documented in (Info-goto-node
+ "(xemacs)Comments"). Update docstring accordingly.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
(widget-insert ".\n"))
(aj
(widget-insert "\
-In the XEmacs team I'm responsible for the packages which means mainly
-applying patches and packaging the packages.
-
I'm a software developer working for the SuSE Labs of the Linux
distributor SuSE. My main task is to improve the GNU C library.")
(widget-insert ".\n"))
(about-show-linked-info 'chr "\
Maintainer of the XEmacs FAQ and proud author of `zap-up-to-char'.\n")
(about-show-linked-info 'aj "\
-`Package Patch Tender', beta tester and GNU libc developer.\n")
+Former `Package Patch Tender', beta tester and GNU libc developer.\n")
(flet ((print-short (name addr &optional shortinfo)
(concat (about-with-face name 'italic)
(byte-optimize-predicate form)
(nth 1 form))))
+;;; For the byte optimizer, `cond' is just overly sweet syntactic sugar.
+;;; So we rewrite (cond ...) in terms of `if' and `or',
+;;; which are easier to optimize.
(defun byte-optimize-cond (form)
- ;; if any clauses have a literal nil as their test, throw them away.
- ;; if any clause has a literal non-nil constant as its test, throw
- ;; away all following clauses.
- (let (rest)
- ;; This must be first, to reduce (cond (t ...) (nil)) to (progn t ...)
- (while (setq rest (assq nil (cdr form)))
- (setq form (delq rest (copy-sequence form))))
- (if (memq nil (cdr form))
- (setq form (delq nil (copy-sequence form))))
- (setq rest form)
- (while (setq rest (cdr rest))
- (cond ((byte-compile-trueconstp (car-safe (car rest)))
- (cond ((eq rest (cdr form))
- (setq form
- (if (cdr (car rest))
- (if (cdr (cdr (car rest)))
- (cons 'progn (cdr (car rest)))
- (nth 1 (car rest)))
- (car (car rest)))))
- ((cdr rest)
- (setq form (copy-sequence form))
- (setcdr (memq (car rest) form) nil)))
- (setq rest nil)))))
- ;;
- ;; Turn (cond (( <x> )) ... ) into (or <x> (cond ... ))
- (if (eq 'cond (car-safe form))
- (let ((clauses (cdr form)))
- (if (and (consp (car clauses))
- (null (cdr (car clauses))))
- (list 'or (car (car clauses))
- (byte-optimize-cond
- (cons (car form) (cdr (cdr form)))))
- form))
- form))
+ (byte-optimize-cond-1 (cdr form)))
+
+(defun byte-optimize-cond-1 (clauses)
+ (cond
+ ((null clauses) nil)
+ ((consp (car clauses))
+ (nconc
+ (case (length (car clauses))
+ (1 `(or ,(nth 0 (car clauses))))
+ (2 `(if ,(nth 0 (car clauses)) ,(nth 1 (car clauses))))
+ (t `(if ,(nth 0 (car clauses)) (progn ,@(cdr (car clauses))))))
+ (when (cdr clauses) (list (byte-optimize-cond-1 (cdr clauses))))))
+ (t (error "malformed cond clause %s" (car clauses)))))
(defun byte-optimize-if (form)
;; (if <true-constant> <then> <else...>) ==> <then>
(c++-keywords
; ("break" "continue" "do" "else" "for" "if" "return" "switch" "while"
; "asm" "catch" "delete" "new" "operator" "sizeof" "this" "throw" "try"
-; "protected" "private" "public")
- (concat "asm\\|break\\|c\\(atch\\|ontinue\\)\\|d\\(elete\\|o\\)\\|"
- "else\\|for\\|if\\|new\\|"
- "p\\(r\\(ivate\\|otected\\)\\|ublic\\)\\|return\\|"
- "s\\(izeof\\|witch\\)\\|t\\(h\\(is\\|row\\)\\|ry\\)\\|while"))
+; "protected" "private" "public" "const_cast" "dynamic_cast" "reinterpret_cast"
+; "static_cast" "and" "bitor" "or" "xor" "compl" "bitand" "and_eq"
+; "or_eq" "xor_eq" "not" "not_eq" "typeid" "false" "true")
+ (concat "a\\(nd\\(\\|_eq\\)\\|sm\\)\\|"
+ "b\\(it\\(or\\|and\\)\\|reak\\)\\|"
+ "c\\(atch\\|o\\(mpl\\|n\\(tinue\\|st_cast\\)\\)\\)\\|"
+ "d\\(elete\\|o\\|ynamic_cast\\)\\|"
+ "else\\|"
+ "f\\(alse\\|or\\)\\|if\\|"
+ "n\\(ew\\|ot\\(\\|_eq\\)\\)\\|"
+ "p\\(r\\(ivate\\|otected\\)\\|ublic\\)\\|"
+ "or\\(\\|_eq\\)\\|"
+ "re\\(interpret_cast\\|turn\\)\\|"
+ "s\\(izeof\\|tatic_cast\\|witch\\)\\|"
+ "t\\(h\\(is\\|row\\)\\|r\\(ue\\|y\\)\\|ypeid\\)\\|"
+ "xor\\(\\|_eq\\)\\|while"))
(c++-type-types
; ("auto" "extern" "register" "static" "typedef" "struct" "union" "enum"
; "signed" "unsigned" "short" "long" "int" "char" "float" "double"
; "void" "volatile" "const" "class" "inline" "friend" "bool"
-; "virtual" "complex" "template")
+; "virtual" "complex" "template" "explicit" "mutable" "export" "namespace"
+; "using" "typename" "wchar_t")
(concat "auto\\|bool\\|c\\(har\\|lass\\|o\\(mplex\\|nst\\)\\)\\|"
- "double\\|e\\(num\\|xtern\\)\\|f\\(loat\\|riend\\)\\|"
- "in\\(line\\|t\\)\\|long\\|register\\|"
+ "double\\|"
+ "e\\(num\\|x\\(p\\(licit\\|ort\\)\\|tern\\)\\)\\|"
+ "f\\(loat\\|riend\\)\\|"
+ "in\\(line\\|t\\)\\|long\\|mutable\\|namespace\\|register\\|"
"s\\(hort\\|igned\\|t\\(atic\\|ruct\\)\\)\\|"
- "t\\(emplate\\|ypedef\\)\\|un\\(ion\\|signed\\)\\|"
- "v\\(irtual\\|o\\(id\\|latile\\)\\)")) ; 11 ()s deep.
+ "t\\(emplate\\|ype\\(def\\|name\\)\\)\\|"
+ "u\\(\\(n\\(ion\\|signed\\)\\|sing\\)\\)\\|"
+ "v\\(irtual\\|o\\(id\\|latile\\)\\)\\|"
+ "wchar_t")) ; 11 ()s deep.
(ctoken "\\(\\sw\\|\\s_\\|[:~*&]\\)+")
)
(setq c-font-lock-keywords-1
(defun lm-version (&optional file)
"Return the version listed in file FILE, or current buffer if FILE is nil.
-This can befound in an RCS or SCCS header to crack it out of."
+This can be found in an RCS or SCCS header to crack it out of."
(save-excursion
(if file
(find-file file))
cyrillic-iso8859-5
greek-iso8859-7
thai-tis620
+ chinese-big5-cdp
japanese-jisx0208
japanese-jisx0208-1990
japanese-jisx0212
chinese-cns11643-5
chinese-cns11643-6
chinese-cns11643-7
- chinese-big5-cdp
chinese-big5
chinese-isoir165
katakana-jisx0201
bound to each category are as follows
coding category coding system
--------------------------------------------------
- iso-8-2 iso-8859-1
- iso-8-1 iso-8859-1
iso-7 iso-2022-7bit
- iso-lock-shift iso-2022-lock
- iso-8-designate iso-2022-8bit-ss2
no-conversion raw-text
+ utf-8 utf-8
+ iso-8-1 iso-8859-1
+ iso-8-2 ctext (iso-8859-1 alias)
+ iso-8-designate ctext (iso-8859-1 alias)
+ iso-lock-shift iso-2022-lock
shift-jis shift_jis
big5 big5
- ucs-4 ----
- utf-8 ----
+ ucs-4 iso-10646-ucs-4
"
+;; The old table (from FSF synch?) was not what we use (cf mule-coding.el),
+;; and as documented iso-8-designate is inconsistent with iso-2022-8bit-ss2.
+;; The order of priorities of coding categories and the coding system
+;; bound to each category are as follows
+;; coding category coding system
+;; --------------------------------------------------
+;; iso-8-2 iso-8859-1
+;; iso-8-1 iso-8859-1
+;; iso-7 iso-2022-7bit
+;; iso-lock-shift iso-2022-lock
+;; iso-8-designate iso-2022-8bit-ss2
+;; no-conversion raw-text
+;; shift-jis shift_jis
+;; big5 big5
+;; ucs-4 ----
+;; utf-8 ----
(interactive)
- ;; This function formerly set default-enable-multibyte-characters to t,
- ;; but that is incorrect. It should not alter the unibyte/multibyte choice.
- (set-coding-category-system 'iso-7 'iso-2022-7bit)
+ (set-coding-category-system 'iso-7 'iso-2022-7)
(set-coding-category-system 'iso-8-1 'iso-8859-1)
- (set-coding-category-system 'iso-8-2 'iso-8859-1)
+ (set-coding-category-system 'iso-8-2 'ctext)
(set-coding-category-system 'iso-lock-shift 'iso-2022-lock)
- (set-coding-category-system 'iso-8-designate 'iso-2022-8bit-ss2)
+ (set-coding-category-system 'iso-8-designate 'ctext)
(set-coding-category-system 'no-conversion 'raw-text)
(set-coding-category-system 'shift-jis 'shift_jis)
(set-coding-category-system 'big5 'big5)
+ ;; #### Can we now assume the existence of the 10646 coding systems?
+ ;; #### These lists need to be synched with the ones in mule-coding.el.
(cond ((eq (coding-system-type (coding-category-system 'utf-8)) 'utf-8)
(set-coding-category-system 'utf-8 'utf-8)
(cond ((eq (coding-system-type (coding-category-system 'ucs-4))
'iso-10646-ucs-4)
(set-coding-category-system 'ucs-4 'iso-10646-ucs-4)
(set-coding-priority-list
- '(iso-8-1
+ '(iso-7
+ no-conversion
+ utf-8
+ iso-8-1
iso-8-2
- iso-7
- iso-lock-shift
iso-8-designate
- utf-8
- ucs-4
- no-conversion
+ iso-lock-shift
shift-jis
- big5))
+ big5
+ ucs-4))
)
(t
(set-coding-priority-list
- '(iso-8-1
+ '(iso-7
+ no-conversion
+ utf-8
+ iso-8-1
iso-8-2
- iso-7
- iso-lock-shift
iso-8-designate
- utf-8
- no-conversion
+ iso-lock-shift
shift-jis
big5))
))
)
(t
(set-coding-priority-list
- '(iso-8-1
+ '(iso-7
+ no-conversion
+ iso-8-1
iso-8-2
- iso-7
- iso-lock-shift
iso-8-designate
- no-conversion
+ iso-lock-shift
shift-jis
big5))
))
"Do various coding system setups for language environment LANGUAGE-NAME.
The optional arg EOL-TYPE specifies the eol-type of the default value
-of buffer-file-coding-system set by this function."
+of buffer-file-coding-system set by this function.
+
+Note that `coding-priority-list' is not reset first; thus changing language
+environment allows recognition of coding systems from previously set language
+environments. (This will not work if the desired coding systems are from the
+same category. E.g., starting with a Hebrew language environment, ISO 8859-8
+will be recognized. If you shift to Russian, ISO 8859-8 will be shadowed by
+ISO 8859-5, and cannot be automatically recognized without resetting the
+language environment to Hebrew. However, if you shift from Japanese to
+Russian, ISO-2022-JP will continue to be automatically recognized, since
+ISO-8859-5 and ISO-2022-JP are different coding categories.)"
(let* ((priority (get-language-info language-name 'coding-priority))
(default-coding (car priority)))
(if priority
;; initialize the coding categories to something semi-reasonable
;; so that the remaining Lisp files can contain extended characters.
;; (They will be in ISO-7 format)
+;; #### This list needs to be synched with the ones in mule-cmds.el.
(if (featurep 'utf-2000)
- (set-coding-priority-list '(iso-8-2 iso-8-designate iso-8-1
- iso-7 iso-lock-shift utf-8 no-conversion))
- (set-coding-priority-list '(iso-8-2 iso-8-designate iso-8-1
- iso-7 iso-lock-shift no-conversion)))
+ (set-coding-priority-list '(iso-7
+ no-conversion
+ utf-8
+ iso-8-1
+ iso-8-2
+ iso-8-designate
+ iso-lock-shift
+ shift-jis
+ big5
+ ucs-4))
+ (set-coding-priority-list '(iso-7
+ no-conversion
+ ;; utf-8
+ iso-8-1
+ iso-8-2
+ iso-8-designate
+ iso-lock-shift
+ shift-jis
+ big5
+ ;; ucs-4
+ )))
(set-coding-category-system 'iso-7 'iso-2022-7)
(set-coding-category-system 'iso-8-designate 'ctext)
(featurep package-feature)
(setq autoload-dir (feature-file package-feature))
(setq autoload-dir (file-name-directory autoload-dir))
- (member autoload-dir late-package-load-path))
+ (member autoload-dir (append early-package-load-path late-package-load-path)))
;; Find the corresponding entry in late-package
(setq pkg-dir
(car-safe (member-if (lambda (h)
(string-match (concat "^" (regexp-quote h))
autoload-dir))
- late-packages))))
+ (append (cdr early-packages) late-packages)))))
(if pkg-dir
pkg-dir
;; Ok we need to guess
(member 'crypt-find-file-hook find-file-hooks)))
;; Compression involved.
(if nosuffix
- '("" ".gz" ".Z")
- '(".elc" ".elc.gz" "elc.Z" ".el" ".el.gz" ".el.Z" "" ".gz" ".Z")))
+ '("" ".gz" ".Z" ".bz2")
+ '(".elc" ".elc.gz" "elc.Z" ".elc.bz2"
+ ".el" ".el.gz" ".el.Z" ".el.bz2"
+ "" ".gz" ".Z" ".bz2")))
(t
;; No compression.
(if nosuffix
If a match spreads across multiple lines, all those lines are shown.
-If variable `list-matching-lines-whole-buffer' is non-nil, the entire buffer is
-searched, otherwise search begins at point.
+If variable `list-matching-lines-whole-buffer' is non-nil, the entire
+buffer is searched, otherwise search begins at point.
Each line is displayed with NLINES lines before and after, or -NLINES
before if NLINES is negative.
:group 'fill-comments)
(defun indent-for-comment ()
- "Indent this line's comment to comment column, or insert an empty comment."
+ "Indent this line's comment to comment column, or insert an empty
+comment. Comments starting in column 0 are not moved."
(interactive "*")
(let* ((empty (save-excursion (beginning-of-line)
(looking-at "[ \t]*$")))
(skip-syntax-backward "^ " (match-beginning 0)))))
(setq begpos (point))
;; Compute desired indent.
- (if (= (current-column)
- (setq indent (funcall comment-indent-function)))
- (goto-char begpos)
+ ;; XEmacs change: Preserve indentation of comments starting in
+ ;; column 0, as documented.
+ (cond
+ ((= (current-column) 0)
+ (goto-char begpos))
+ ((= (current-column)
+ (setq indent (funcall comment-indent-function)))
+ (goto-char begpos))
+ (t
;; If that's different from current, change it.
(skip-chars-backward " \t")
(delete-region (point) begpos)
- (indent-to indent))
+ (indent-to indent)))
;; An existing comment?
(if cpos
(progn (goto-char cpos)
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
+2000-12-30 Andy Piper <andy@xemacs.org>
+
+ * xlwtabs.c: remove assertion definitions and put them in
+ lwlib-internal.h. This has the effect of enabling assertions which
+ should have been done from the very start.
+ (TabsShuffleRows): fix duff assertion.
+ (PreferredSize3): use dimensions throughout.
+ (PreferredSize2): ditto.
+ (TabLayout): ditto.
+ (DrawFrame): be clever about the enclosing frame if the child
+ height is 0.
+ (TabsResize): don't configure children that are no visible
+ anyway. Make sure geometry calculations don't end up negative.
+
+ * lwlib-internal.h: put in assertion definitions.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
#include "lwlib.h"
+#ifdef USE_ASSERTIONS
+/* Highly dubious kludge */
+/* (thanks, Jamie, I feel better now -- ben) */
+void assert_failed (const char *, int, const char *);
+# define abort() (assert_failed (__FILE__, __LINE__, "abort()"))
+# define assert(x) ((x) ? (void) 0 : assert_failed (__FILE__, __LINE__, #x))
+#else
+# ifdef DEBUG_XEMACS
+# define assert(x) ((x) ? (void) 0 : (void) abort ())
+# else
+# define assert(x)
+# endif
+#endif
+
/* This represents a single widget within a widget tree. All the
widgets in a widget tree are chained through the `next' field.
`info' is a back pointer to the widget tree. */
#include <X11/Xlib.h>
#include <X11/IntrinsicP.h>
#include <X11/StringDefs.h>
+
+#include "lwlib-internal.h"
#include "../src/xmu.h"
#include "xlwtabsP.h"
#include "xlwgcs.h"
static void UndrawTab( TabsWidget tw, Widget child) ;
static void TabWidth( Widget w) ;
-static int TabLayout( TabsWidget, int wid, int hgt, Dimension *r_hgt,
+static int TabLayout( TabsWidget, Dimension wid, Dimension hgt, Dimension *r_hgt,
Bool query_only) ;
static void GetPreferredSizes(TabsWidget) ;
static void MaxChild(TabsWidget, Widget except, Dimension, Dimension) ;
static int PreferredSize( TabsWidget,
Dimension *reply_width, Dimension *reply_height,
Dimension *reply_cw, Dimension *reply_ch) ;
-static int PreferredSize2( TabsWidget, int cw, int ch,
+static int PreferredSize2( TabsWidget, Dimension cw, Dimension ch,
Dimension *rw, Dimension *rh) ;
-static int PreferredSize3( TabsWidget, int wid, int hgt,
+static int PreferredSize3( TabsWidget, Dimension wid, Dimension hgt,
Dimension *rw, Dimension *rh) ;
static void MakeSizeRequest(TabsWidget) ;
WidgetClass tabsWidgetClass = (WidgetClass)&tabsClassRec;
-
-
-#ifdef DEBUG
-#ifdef __STDC__
-#define assert(e) \
- if(!(e)) fprintf(stderr,"yak! %s at %s:%d\n",#e,__FILE__,__LINE__)
-#else
-#define assert(e) \
- if(!(e)) fprintf(stderr,"yak! e at %s:%d\n",__FILE__,__LINE__)
-#endif
-#else
-#define assert(e)
-#endif
-
#define TabsNumChildren(tw) (((TabsWidget)tw)->composite.num_children)
#define TabVisible(tab) \
(XtIsManaged(tab) && \
tw->tabs.child_width = cw = tw->core.width - 2 * SHADWID ;
tw->tabs.child_height = ch =
- tw->core.height - tw->tabs.tab_total - 2 * SHADWID ;
-
+ tw->core.height < (tw->tabs.tab_total + 2 * SHADWID) ? 0 :
+ tw->core.height - tw->tabs.tab_total - 2 * SHADWID ;
for(i=0, childP=tw->composite.children;
i < num_children;
++i, ++childP)
- if( TabVisible(*childP) )
+ if( XtIsManaged(*childP) )
{
tab = (TabsConstraints) (*childP)->core.constraints ;
bw = (*childP)->core.border_width ;
- XtConfigureWidget(*childP, SHADWID,tw->tabs.tab_total+SHADWID,
- cw-bw*2,ch-bw*2, bw) ;
+ /* Don't do anything if we can't see any of the child. */
+ if (ch >= bw*2 && ch > 0 && cw >= bw*2 && cw > 0)
+ XtConfigureWidget(*childP, SHADWID,tw->tabs.tab_total+SHADWID,
+ cw-bw*2,ch-bw*2, bw) ;
}
if( XtIsRealized(w) ) {
XClearWindow(XtDisplay((Widget)tw), XtWindow((Widget)tw)) ;
myrequest.width = wid ;
myrequest.height = hgt ;
myrequest.request_mode = CWWidth | CWHeight ;
-
+
+ assert (wid > 0 && hgt > 0);
/* If child is only querying, or if we're going to have to
* offer the child a compromise, then make this a query only.
*/
GC botgc = tw->tabs.botGC ;
Dimension s = SHADWID ;
Dimension ch = tw->tabs.child_height ;
- Draw3dBox((Widget)tw, 0,tw->tabs.tab_total,
- tw->core.width, ch+2*s, s, topgc, botgc) ;
+ if (ch > 0)
+ Draw3dBox((Widget)tw, 0,tw->tabs.tab_total,
+ tw->core.width, ch+2*s, s, topgc, botgc) ;
+ else
+ {
+ Widget w = tw->tabs.topWidget ;
+ if (w != NULL)
+ {
+ TabsConstraints tab = (TabsConstraints) w->core.constraints ;
+ Draw3dBox((Widget)tw, 0,tw->core.height - 2*s,
+ tab->tabs.x, 2*s, s, topgc, botgc);
+ Draw3dBox((Widget)tw, tab->tabs.x + tab->tabs.width,
+ tw->core.height - 2*s,
+ tw->core.width - tab->tabs.x - tab->tabs.width, 2*s, s,
+ topgc, botgc);
+ }
+ else
+ Draw3dBox((Widget)tw, 0,tw->core.height - 2*s,
+ tw->core.width, 2*s, s, topgc, botgc) ;
+ }
}
*/
static int
-TabLayout(TabsWidget tw, int wid, int hgt, Dimension *reply_height, Bool query_only)
+TabLayout(TabsWidget tw,
+ Dimension wid,
+ Dimension hgt,
+ Dimension *reply_height, Bool query_only)
{
int i, row, done = 0, display_rows = 0 ;
int num_children = tw->composite.num_children ;
XtWidgetGeometry preferred ;
for(i=tw->composite.num_children; --i >=0; ++childP)
- if( XtIsManaged(*childP) && *childP != except )
+ if( TabVisible (*childP) /*XtIsManaged(*childP)*/ && *childP != except )
{
(void) XtQueryGeometry(*childP, NULL, &preferred) ;
cw = Max(cw, preferred.width + preferred.border_width * 2 ) ;
{
display_rows = tw->tabs.numRows ;
real_rows = tw->tabs.realRows ;
- assert( display_rows >= real_rows ) ;
+ assert( display_rows <= real_rows ) ;
if( real_rows > 1 )
{
static int
PreferredSize2(
TabsWidget tw,
- int cw, /* child width, height */
- int ch,
+ Dimension cw, /* child width, height */
+ Dimension ch,
Dimension *reply_width, /* total widget size */
Dimension *reply_height)
{
Dimension s = SHADWID ;
+ int ret;
/* make room for shadow frame */
cw += s*2 ;
ch += s*2 ;
- return PreferredSize3(tw, cw, ch, reply_width, reply_height) ;
+ ret = PreferredSize3(tw, cw, ch, reply_width, reply_height) ;
+
+ assert (*reply_width > 0 && *reply_height > 0);
+ return ret;
}
static int
PreferredSize3(
TabsWidget tw,
- int wid, /* child width, height */
- int hgt,
+ Dimension wid, /* child width, height */
+ Dimension hgt,
Dimension *reply_width, /* total widget size */
Dimension *reply_height)
{
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
+2000-12-05 Stephen J. Turnbull <stephen@xemacs.org>
+
+ * internals/internals.texi (General Coding Rules): further document
+ usage of symsinit.h. Reorder slightly.
+
+2000-11-29 Stephen J. Turnbull <stephen@xemacs.org>
+
+ * xemacs/packages.texi (Creating Packages): new node.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
tools means that a greater variety of development tools are available to
the developer.
-Almost every module contains a @code{syms_of_*()} function and a
-@code{vars_of_*()} function. The former declares any Lisp primitives
-you have defined and defines any symbols you will be using. The latter
-declares any global Lisp variables you have added and initializes global
-C variables in the module. For each such function, declare it in
-@file{symsinit.h} and make sure it's called in the appropriate place in
-@file{emacs.c}. @strong{Important}: There are stringent requirements on
-exactly what can go into these functions. See the comment in
-@file{emacs.c}. The reason for this is to avoid obscure unwanted
-interactions during initialization. If you don't follow these rules,
-you'll be sorry! If you want to do anything that isn't allowed, create
-a @code{complex_vars_of_*()} function for it. Doing this is tricky,
-though: You have to make sure your function is called at the right time
-so that all the initialization dependencies work out.
-
Every module includes @file{<config.h>} (angle brackets so that
@samp{--srcdir} works correctly; @file{config.h} may or may not be in
the same directory as the C sources) and @file{lisp.h}. @file{config.h}
@file{config.h} files. Which one will be used if you @samp{#include
"config.h"}?
+Almost every module contains a @code{syms_of_*()} function and a
+@code{vars_of_*()} function. The former declares any Lisp primitives
+you have defined and defines any symbols you will be using. The latter
+declares any global Lisp variables you have added and initializes global
+C variables in the module. @strong{Important}: There are stringent
+requirements on exactly what can go into these functions. See the
+comment in @file{emacs.c}. The reason for this is to avoid obscure
+unwanted interactions during initialization. If you don't follow these
+rules, you'll be sorry! If you want to do anything that isn't allowed,
+create a @code{complex_vars_of_*()} function for it. Doing this is
+tricky, though: you have to make sure your function is called at the
+right time so that all the initialization dependencies work out.
+
+Declare each function of these kinds in @file{symsinit.h}. Make sure
+it's called in the appropriate place in @file{emacs.c}. You never need
+to include @file{symsinit.h} directly, because it is included by
+@file{lisp.h}.
+
@strong{All global and static variables that are to be modifiable must
be declared uninitialized.} This means that you may not use the
``declare with initializer'' form for these variables, such as @code{int
@enumerate
@item
We do not use the mark bit (which does not exist for C structures
-anyway), we use a big hash table instead.
+anyway); we use a big hash table instead.
@item
We do not use the mark function of lrecords but instead rely on the
allows us to look up a pdump_entry_list_elmt with the object it points
to). Entries are added with @code{pdump_add_entry()} and looked up with
@code{pdump_get_entry()}. There is no need for entry removal. The hash
-value is computed quite basically from the object pointer by
+value is computed quite simply from the object pointer by
@code{pdump_make_hash()}.
The roots for the marking are:
call for protected variables we do not want to dump).
@item
-the @code{pdump_wire}'d variables (@code{staticpro} is equivalent to
+the @code{pdump_wire}'d variables (@code{staticpro()} is equivalent to
@code{staticpro_nodump()} + @code{pdump_wire()}).
@item
@item
the C compiler is required to adjust the size of a struct so that you
-can have an array of them next to each other. This means you can have a
+can have an array of them next to each other. This means you can have an
upper bound of the alignment requirements of a given structure by
looking at which power of two its size is a multiple.
The maximum alignment requirement we take into account is 2^8.
@code{pdump_allocate_offset()} only has to do a linear allocation,
-starting at offset 256 (this leaves room for the header and keep the
+starting at offset 256 (this leaves room for the header and keeps the
alignments happy).
@node The header, Data dumping, Address allocation, Dumping phase
@subsection The header
The next step creates the file and writes a header with a signature and
-some random informations in it (number of staticpro, number of assigned
+some random information in it (number of staticpro, number of assigned
lrecord types, etc...). The reloc_address field, which indicates at
which address the file should be loaded if we want to avoid post-reload
relocation, is set to 0. It then seeks to offset 256 (base offset for
a vector of all the offsets to the objects in the file that include a
description (for faster relocation at reload time)
@item
-the pdump_wired and pdump_wired_list arrays
+the pdump_wire and pdump_wire_list arrays
@end enumerate
For each of the arrays we write both the pointer to the variables and
are global, the pointers are still valid when restarting the program and
are used to regenerate the global pointers.
-The @code{pdump_wired_list} array is a special case. The variables it
+The @code{pdump_wire_list} array is a special case. The variables it
points to are the head of weak linked lists of lisp objects of the same
type. Not all objects of this list are dumped so the relocated pointer
we associate with them points to the first dumped object of the list, or
* Package Terminology:: Understanding different kinds of packages.
* Using Packages:: How to install and use packages.
* Building Packages:: Building packages from sources.
+* Creating Packages:: The basics.
* Available Packages:: A brief, out-of-date, directory of packaged LISP.
@end menu
@end enumerate
-@node Building Packages, Available Packages, Using Packages, Packages
+@node Building Packages, Creating Packages, Using Packages, Packages
@comment node-name, next, previous, up
Source packages are available from the @file{packages/source-packages}
of TeXinfo documentation if present.
@item srckit
-Usually aliased to @code{make srckit-std}. This does a @code{make
+Usually aliased to @code{srckit-std}. This does a @code{make
distclean} and creates a package source tarball in the staging
directory. This is generally only of use for package maintainers.
@end table
-@node Available Packages, , Building Packages, Packages
+@node Creating Packages, Available Packages, Building Packages, Packages
+@comment node-name, next, previous, up
+
+Creating a package from an existing Lisp library is not very difficult.
+
+In addition to the Lisp libraries themselves, you need a
+@file{package-info.in} file and a simple @file{Makefile}. The rest is
+done by @file{XEmacs.rules}, part of the packaging system
+infrastructure.
+
+@file{package-info.in} contains a single Lisp form like this:
+
+@example
+(name ; your package's name
+ (standards-version 1.1
+ version VERSION
+ author-version AUTHOR_VERSION
+ date DATE
+ build-date BUILD_DATE
+ maintainer MAINTAINER
+ distribution xemacs ; change to "mule" if MULE is needed
+ priority high
+ category CATEGORY
+ dump nil
+ description "description" ; a one-line description string
+ filename FILENAME
+ md5sum MD5SUM
+ size SIZE
+ provides (feature1 feature2) ; one for every `provides' form
+ requires (REQUIRES)
+ type regular
+))
+@end example
+
+You must fill in the four commented lines. The value of @code{name} is
+the name of your package as an unquoted symbol. Normally it is the name
+of the main Lisp file or principal feature provided. The allowed values
+for distribution are @code{xemacs} and @code{mule}. Write them as
+unquoted symbols. The @code{description} is a quoted Lisp string; use
+the usual conventions. The value for @code{provides} is a list of
+feature symbols (written unquoted). All of the features provided by
+libraries in your package should be elements of this list. Implementing
+an automatic method for generating the @file{provides} line is
+desirable, but as yet undone.
+
+The variables in upper-case are references to variables set in the
+@file{Makefile} or automatically generated. Do not change them; they
+are automatically filled in by the build process.
+
+The remaining lines refer to implementation constants
+(@code{standards-version}), or features that are unimplemented or have
+been removed (@code{priority} and @code{dump}). The @code{type} line is
+not normally relevant to external maintainers; the alternate value is
+@code{single-file}, which refers to packages consed up out of a number
+of single-file libraries that are more or less thematically related. An
+example is @code{prog-modes}. Single-file packages are basically for
+administrative convenience, and new packages should generally be created
+as regular packages.
+
+The @file{Makefile} is quite stylized. The idea is similar to an
+@file{Imakefile} or an @code{automake} file: the complexity is hidden in
+generic rules files, in this case the @file{XEmacs.rules} include file
+in the top directory of the packages hierarchy. Although a number of
+facilities are available for complex libraries, most simple packages'
+@file{Makefile}s contain a copyright notice, a few variable definitions,
+an include for @file{XEmacs.rules}, and a couple of standard targets.
+
+The first few @code{make} variables defined are @code{VERSION},
+@code{AUTHOR_VERSION}, @code{MAINTAINER}, @code{PACKAGE},
+@code{PKG_TYPE}, @code{REQUIRES}, and @code{CATEGORY}. All but one were
+described in the description of @file{package-info.in}. The last is an
+admistrative grouping. Current categories include @code{comm},
+@code{games}, @code{libs}, @code{mule}, @code{oa}, @code{os},
+@code{prog}, and @code{wp}. @ref{Available Packages}, for a list of
+categories.
+
+Next, define the variable @code{ELCS}. This contains the list of the
+byte-compiled Lisp files used by the package. These files and their
+@file{.el} versions will be included in the binary package. If there
+are other files (such as extra Lisp sources or an upstream
+@file{Makefile}) that are normally placed in the installed Lisp
+directory, but not byte-compiled, they can be listed as the value of
+@code{EXTRA_SOURCES}.
+
+The include is simply
+@example
+include ../../XEmacs.rules
+@end example
+
+The standard targets follow. These are
+
+@example
+all:: $(ELCS) auto-autoloads.elc
+
+srckit: srckit-alias
+
+binkit: binkit-alias
+@end example
+
+Other targets (such as Texinfo sources) may need to be added as
+dependencies for the @code{all} target. Dependencies for @code{srckit}
+and @code{binkit} (that is, values for @var{srckit-alias} and
+@var{binkit-alias}) are defined in @file{XEmacs.rules}. The most useful
+of these values are given in the following table.
+
+@table @var
+@item srckit-alias
+Usually set to @code{srckit-std}.
+
+@item binkit-alias
+May be set to @code{binkit-sourceonly}, @code{binkit-sourceinfo},
+@code{binkit-sourcedata}, or
+@code{binkit-sourcedatainfo}. @code{sourceonly} indicates there is
+nothing to install in a data directory or info directory.
+@code{sourceinfo} indicates that source and info files are to be
+installed. @code{sourcedata} indicates that source and etc (data) files
+are to be installed. @code{sourcedatainfo} indicates source, etc
+(data), and info files are to be installed.
+@end table
+
+Data files include things like pixmaps for a package-specific toolbar,
+and are normally installed in @file{etc/@var{PACKAGE_NAME}}. A few
+packages have needs beyond the basic templates. See @file{XEmacs.rules}
+or a future revision of this manual for details.
+
+@node Available Packages, , Creating Packages, Packages
@comment node-name, next, previous, up
This section is surely out-of-date. If you're sure that XEmacs is
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
(Vcharset_thai_tis620): Likewise.
(Vcharset_katakana_jisx0201): Likewise.
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
+2000-12-29 Andy Piper <andy@xemacs.org>
+
+ * menubar.c (menubar_visible_p_changed): signal the frame changed.
+
+ * glyphs-x.c (x_redisplay_widget): Re-calculate widget offsets if
+ the frame has changed so that we pick up geometry changes such as
+ menubar visibility.
+
+2000-12-28 Andy Piper <andy@xemacs.org>
+
+ * lastfile.c (my_ebss): make a char array so we can pad the
+ bss. Fixes cygwin unexec.
+
+ * unexcw.c: invert BROKEN_GDB to NO_DEBUG.
+
+2000-12-26 Andy Piper <andy@xemacs.org>
+
+ * event-Xt.c (emacs_Xt_force_event_pending): add some verbose
+ comments and try and be more precise about a non-/SIGIO world.
+ (emacs_Xt_event_pending_p): use XtAppPending under cygwin and non
+ SIGIO.
+
+ * redisplay-output.c (redisplay_normalize_glyph_area): make sure
+ we don't normalize to zero width or height.
+
+2000-12-24 Andy Piper <andy@xemacs.org>
+
+ * Makefile.in.in (ldflags): add -mwindows when appropriate.
+
+2000-08-18 Golubev I. N. <gin@mo.msk.ru>
+
+ * s/sco5.h: SCO 5 has pty support.
+
+2000-07-20 Kazuyuki IENAGA <ienaga@xemacs.org>
+
+ * input-method-xlib.c: supports both XIM_XLIB and USE_XFONTSET.
+ input-method-xlib.c contains whole contents of input-method-xfs.c,
+ so we can use input-method-xlib.c's code for USE_XFONTSET
+ using #ifdefs.
+ * input-method-xfs.c: removed.
+
+2000-12-20 Stephen Turnbull <stephen@xemacs.org>
+
+ * file-coding.h (enum coding_category_type): reorder enumerators to
+ make autodetection safer. Make CODING_CATEGORY_LAST an enumerator
+ (now one greater than largest real coding_category_type enumerator).
+ * file-coding.c (coding_category_symbol, coding_category_by_priority,
+ coding_category_system, fcd_descriptihon_1, decode_coding_category,
+ Fcoding_category_list, Fset_coding_priority_list,
+ Fcoding_priority_list, coding_system_from_mask, Fdetect_coding_region,
+ vars_of_file_coding): adjust for change in CODING_CATEGORY_LAST.
+
+2000-12-18 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * redisplay-output.c (redisplay_clear_top_of_window): Remove static.
+ * redisplay-output.c (redisplay_output_window): Clear top of window
+ when face is changed.
+ * redisplay-x.c (x_redraw_exposed_window): Call
+ redisplay_clear_top_of_window.
+ * redisplay.h: Publish redisplay_clear_top_of_window.
+
+2000-12-18 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * buffer.c (Fkill_buffer): Map over all devices.
+ * window.c (window_loop): Remove UNSHOW_BUFFER code.
+ (list_windows): New function.
+ (list_all_windows): Ditto.
+ (Freplace_buffer_in_windows): Use them.
+
+2000-02-02 Daiki Ueno <ueno@ueda.info.waseda.ac.jp>
+
+ * database.c (berkdb_subtype): Recognize new subtype `queue'.
+ (Fopen_database): Use `db_create' instead of `db_open'.
+ (syms_of_database): Initialize Qqueue.
+
+2000-12-13 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * buffer.c (common_init_complex_vars_of_buffer): Initialize
+ buffer_local_face_property.
+ * buffer.h (struct buffer): New member buffer_local_face_property.
+ * window.c (Fset_window_buffer): Mark window's face as changed
+ when buffer has buffer local face.
+ * window.h (MARK_WINDOW_FACES_CHANGED): New macro.
+ * objects.c (color_after_change): Set buffer_local_face_property
+ when locale of face specifier is buffer.
+ * objects.c (font_after_change): Ditto.
+ * objects.c (face_boolean_after_change): Ditto.
+ * glyphs.c (image_after_change): Ditto.
+
+2000-12-09 Dan Holmsand <dan@eyebee.com>
+
+ * nt.c (mswindows_fstat): Report file permissions, volume serial
+ number, etc. Code adapted from FSF Emacs 20.7.
+
+2000-12-09 Dan Holmsand <dan@eyebee.com>
+
+ * sysfile.h (lstat): Make lstat an alias for xemacs_stat instead
+ of stat when we don't have symbolic links, to make sure
+ mswindows_stat is called on mswindows.
+
+2000-12-12 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * alloca.c: Define malloc to xmalloc only when built with XEmacs.
+
+2000-12-12 Martin Buchholz <martin@xemacs.org>
+
+ * doprnt.c (emacs_doprnt_1): More printing fixes.
+ Make printing of numbers compatible with libc and FSF Emacs.
+ BUG was: (format "%6.3f" 1.2) ==>"1.200000"
+ Use the system printf to do most of the hard work of formatting,
+ instead of doprnt_1().
+ Calculate memory to allocate for format string.
+ Remove arbitrary limit on precision, e.g. (format "%.1000f" 3.14)
+ (doprnt_1): Cleaner code and documentation.
+
+2000-12-01 Jerry James <james@eecs.ukans.edu>
+
+ * Makefile.in.in: Use the loop variable to install headers.
+
+2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * window.c (Fsplit_window): Don't invalidate face cache.
+
+2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * minibuf.c (Fall_completions): Undo the previous change
+ which removed checking elements start with space.
+
+2000-12-06 Stephen Turnbull <stephen@xemacs.org>
+
+ * mule-canna.c: Didier suppression.
+
+2000-12-06 Stephen Turnbull <stephen@xemacs.org>
+
+ * mule-canna.c: rename static unsigned char buf[] to key_buffer
+ (warning suppression). Add English comment translations.
+
+2000-12-05 Martin Buchholz <martin@xemacs.org>
+
+ * unexelfsgi.c (unexec): Better test for mmap failure.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
2000-12-05 Martin Buchholz <martin@xemacs.org>
+ * redisplay.c (bar-cursor): Make a user variable.
+
* symsinit.h: Add init_postgresql_from_environment.
2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
cppflags = $(CPPFLAGS) -Demacs -I. $(c_switch_all)
cflags = $(CFLAGS) $(cppflags)
+#if defined (WIN32_NATIVE) || defined (CYGWIN)
+ldflags = $(LDFLAGS) -mwindows $(ld_switch_all) $(ld_dynamic_link_flags)
+#else
ldflags = $(LDFLAGS) $(ld_switch_all) $(ld_dynamic_link_flags)
+#endif
#ifdef SOLARIS2
%.o : %.c
cd ${srcdir}; hdrdir2=`pwd`; cd $$hdir; \
test "$$hdrdir2" != "$$hdir" && hdir="$$hdir $$hdrdir2"; \
(for thisdir in $$hdir; do \
- cd $$hdir && \
+ cd $$thisdir && \
(hdrtars=; \
for hdrfile in *.h; do \
hdrtars="$$hdrtars $$hdrfile"; \
Callers below should use malloc. */
-#ifndef emacs
+#ifdef emacs
#define malloc xmalloc
#endif
#ifndef WIN32_NATIVE
/* #### This is a problem if this buffer is in a dedicated window.
Need to undedicate any windows of this buffer first (and delete them?)
*/
- Freplace_buffer_in_windows (buf, Qnil, Qnil);
+ GCPRO1 (buf);
+ Freplace_buffer_in_windows (buf, Qnil, Qall);
+ UNGCPRO;
font_lock_buffer_was_killed (b);
defs->auto_save_modified = 0;
defs->auto_save_failure_time = -1;
defs->invisibility_spec = Qt;
+ defs->buffer_local_face_property = 0;
defs->indirect_children = Qnil;
syms->indirect_children = Qnil;
int face_change; /* This is set when a change in how the text should
be displayed (e.g., font, color) is made. */
+ /* Whether buffer specific face is specified. */
+ int buffer_local_face_property;
+
/* change data indicating what portion of the text has changed
since the last time this was reset. Used by redisplay.
Logically we should keep this with the text structure, but
#endif /* DB_VERSION_MAJOR */
Lisp_Object Qberkeley_db;
Lisp_Object Qhash, Qbtree, Qrecno, Qunknown;
+#if DB_VERSION_MAJOR > 2
+Lisp_Object Qqueue;
+#endif
#endif /* HAVE_BERKELEY_DB */
#ifdef HAVE_DBM
case DB_BTREE: return Qbtree;
case DB_HASH: return Qhash;
case DB_RECNO: return Qrecno;
+#if DB_VERSION_MAJOR > 2
+ case DB_QUEUE: return Qqueue;
+#endif
default: return Qunknown;
}
}
real_subtype = DB_BTREE;
else if (EQ (subtype, Qrecno))
real_subtype = DB_RECNO;
+#if DB_VERSION_MAJOR > 2
+ else if (EQ (subtype, Qqueue))
+ real_subtype = DB_QUEUE;
+#endif
else
signal_simple_error ("Unsupported subtype", subtype);
if (strchr (acc, 'r') && !strchr (acc, 'w'))
accessmask |= DB_RDONLY;
}
+#if DB_VERSION_MAJOR == 2
status = db_open (filename, real_subtype, accessmask,
modemask, NULL , NULL, &dbase);
if (status)
return Qnil;
+#else
+ status = db_create (&dbase, NULL, 0);
+ if (status)
+ return Qnil;
+ status = dbase->open (dbase, filename, NULL,
+ real_subtype, accessmask, modemask);
+ if (status)
+ {
+ dbase->close (dbase, 0);
+ return Qnil;
+ }
+#endif /* DB_VERSION_MAJOR > 2 */
+ /* Normalize into system specific file modes. Only for printing */
+ accessmask = accessmask & DB_RDONLY ? O_RDONLY : O_RDWR;
#endif /* DB_VERSION_MAJOR */
db = allocate_database ();
defsymbol (&Qhash, "hash");
defsymbol (&Qbtree, "btree");
defsymbol (&Qrecno, "recno");
+#if DB_VERSION_MAJOR > 2
+ defsymbol (&Qqueue, "queue");
+#endif
defsymbol (&Qunknown, "unknown");
#endif
indent.o: $(LISP_H) buffer.h bufslots.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console.h device.h extents.h faces.h frame.h frameslots.h glyphs.h gui.h insdel.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h redisplay.h scrollbar.h specifier.h toolbar.h window.h winslots.h
inline.o: $(LISP_H) $(LWLIB_SRCDIR)/lwlib.h buffer.h bufslots.h bytecode.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console-msw.h console.h database.h device.h eldap.h elhash.h events.h extents.h faces.h file-coding.h frame.h frameslots.h glyphs-x.h glyphs.h gui-x.h gui.h keymap.h lstream.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h objects.h opaque.h postgresql.h process.h rangetab.h redisplay.h scrollbar.h specifier.h syntax.h syscommctrl.h systime.h syswindows.h toolbar.h tooltalk.h window.h winslots.h xintrinsic.h
input-method-motif.o: $(LISP_H) EmacsFrame.h char-1byte.h char-lb.h char-ucs.h character.h conslots.h console-x.h console.h device.h frame.h frameslots.h glyphs.h gui.h mule-charset.h redisplay.h scrollbar.h specifier.h toolbar.h window.h winslots.h xintrinsic.h
-input-method-xfs.o: $(LISP_H) EmacsFrame.h buffer.h bufslots.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console-x.h console.h device.h events.h frame.h frameslots.h glyphs.h gui.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h redisplay.h scrollbar.h specifier.h systime.h toolbar.h window.h winslots.h xintrinsic.h
input-method-xlib.o: $(LISP_H) EmacsFrame.h buffer.h bufslots.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console-x.h console.h device.h events.h frame.h frameslots.h glyphs.h gui.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h redisplay.h scrollbar.h specifier.h systime.h toolbar.h window.h winslots.h xintrinsic.h
insdel.o: $(LISP_H) buffer.h bufslots.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console.h device.h extents.h frame.h frameslots.h glyphs.h gui.h insdel.h line-number.h lstream.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h redisplay.h scrollbar.h specifier.h toolbar.h window.h winslots.h
intl.o: $(LISP_H) bytecode.h char-1byte.h char-lb.h char-ucs.h character.h conslots.h console.h device.h mule-charset.h
keymap.o: $(LISP_H) buffer.h bufslots.h bytecode.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h conslots.h console.h device.h elhash.h events-mod.h events.h frame.h frameslots.h glyphs.h gui.h insdel.h keymap.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h redisplay.h scrollbar.h specifier.h systime.h toolbar.h window.h winslots.h
+lastfile.o: config.h
libsst.o: $(LISP_H) libsst.h
line-number.o: $(LISP_H) buffer.h bufslots.h casetab.h char-1byte.h char-lb.h char-ucs.h character.h chartab.h line-number.h mb-1byte.h mb-lb.h mb-multibyte.h mb-utf-8.h mule-charset.h multibyte.h
linuxplay.o: $(LISP_H) miscplay.h nativesound.h sysfile.h syssignal.h
unexalpha.o: config.h
unexapollo.o: config.h
unexconvex.o: config.h getpagesize.h
-unexcw.o: config.h sysfile.h
+unexcw.o: $(LISP_H) sysfile.h
unexec.o: $(LISP_H) getpagesize.h
unexelf.o: config.h
unexelfsgi.o: config.h
Dynarr_declare (union printf_arg);
} printf_arg_dynarr;
-/* Append STRING (of length LEN) to STREAM. MINLEN is the minimum field
- width. If MINUS_FLAG is set, left-justify the string in its field;
- otherwise, right-justify. If ZERO_FLAG is set, pad with 0's; otherwise
- pad with spaces. If MAXLEN is non-negative, the string is first
- truncated to that many character.
+/* Append STRING (of length LEN bytes) to STREAM.
+ MINLEN is the minimum field width.
+ If MINUS_FLAG is set, left-justify the string in its field;
+ otherwise, right-justify.
+ If ZERO_FLAG is set, pad with 0's; otherwise pad with spaces.
+ If MAXLEN is non-negative, the string is first truncated on the
+ right to that many characters.
Note that MINLEN and MAXLEN are Charcounts but LEN is a Bytecount. */
doprnt_1 (Lisp_Object stream, const Bufbyte *string, Bytecount len,
Charcount minlen, Charcount maxlen, int minus_flag, int zero_flag)
{
- Charcount cclen;
- Bufbyte pad;
Lstream *lstr = XLSTREAM (stream);
-
- cclen = bytecount_to_charcount (string, len);
-
- if (zero_flag)
- pad = '0';
- else
- pad = ' ';
+ Charcount cclen = bytecount_to_charcount (string, len);
+ int to_add = minlen - cclen;
/* Padding at beginning to right-justify ... */
- if (minlen > cclen && !minus_flag)
- {
- int to_add = minlen - cclen;
- while (to_add > 0)
- {
- Lstream_putc (lstr, pad);
- to_add--;
- }
- }
+ if (!minus_flag)
+ while (to_add-- > 0)
+ Lstream_putc (lstr, zero_flag ? '0' : ' ');
- if (maxlen >= 0)
- len = charcount_to_bytecount (string, min (maxlen, cclen));
+ if (0 <= maxlen && maxlen < cclen)
+ len = charcount_to_bytecount (string, maxlen);
Lstream_write (lstr, string, len);
/* Padding at end to left-justify ... */
- if (minlen > cclen && minus_flag)
- {
- int to_add = minlen - cclen;
- while (to_add > 0)
- {
- Lstream_putc (lstr, pad);
- to_add--;
- }
- }
+ if (minus_flag)
+ while (to_add-- > 0)
+ Lstream_putc (lstr, zero_flag ? '0' : ' ');
}
static const Bufbyte *
}
else
{
- char text_to_print[500];
+ /* ASCII Decimal representation uses 2.4 times as many
+ bits as machine binary. */
+ char *text_to_print =
+ alloca_array (char, 32 +
+ max (spec->minwidth,
+ max (sizeof (double), sizeof (long)) * 3 +
+ max (spec->precision, 0)));
char constructed_spec[100];
char *p = constructed_spec;
- /* Partially reconstruct the spec and use sprintf() to
+ /* Mostly reconstruct the spec and use sprintf() to
format the string. */
- /* Make sure nothing stupid happens */
- /* DO NOT REMOVE THE (int) CAST! Incorrect results will
- follow! */
- spec->precision = min (spec->precision,
- (int) (sizeof (text_to_print) - 50));
-
*p++ = '%';
if (spec->plus_flag) *p++ = '+';
if (spec->space_flag) *p++ = ' ';
if (spec->number_flag) *p++ = '#';
+ if (spec->minus_flag) *p++ = '-';
+ if (spec->zero_flag) *p++ = '0';
- if (spec->precision >= 0 && !spec->minwidth)
+ if (spec->minwidth >= 0)
+ p = long_to_string (p, spec->minwidth);
+ if (spec->precision >= 0)
{
*p++ = '.';
p = long_to_string (p, spec->precision);
}
-
- /* sprintf the mofo */
- /* we have to use separate calls to sprintf(), rather than
- a single big conditional, because of the different types
- of the arguments */
+
if (strchr (double_converters, ch))
{
*p++ = ch;
}
else
{
- if (spec->zero_flag && spec->minwidth)
- sprintf (p, "0%dl%c", spec->minwidth, ch);
- else
- sprintf (p, "l%c", ch);
+ *p++ = 'l'; /* Always use longs with sprintf() */
+ *p++ = ch;
+ *p++ = '\0';
if (strchr (unsigned_int_converters, ch))
sprintf (text_to_print, constructed_spec, arg.ul);
}
doprnt_1 (stream, (Bufbyte *) text_to_print,
- strlen (text_to_print),
- spec->minwidth, -1, spec->minus_flag, spec->zero_flag);
+ strlen (text_to_print), 0, -1, 0, 0);
}
}
}
}
}
+/* #### I'm struggling to understand how the X event loop really works.
+ Here is the problem:
+
+ When widgets get mapped / changed etc the actual display updates
+ are done asynchronously via X events being processed - this
+ normally happens when XtAppProcessEvent() gets called. However, if
+ we are executing lisp code or even doing redisplay we won't
+ necessarily process X events for a very long time. This has the
+ effect of widgets only getting updated when XEmacs only goes into
+ idle, or some other event causes processing of the X event queue.
+
+ XtAppProcessEvent can get called from the following places:
+
+ emacs_Xt_next_event () - this is normal event processing, almost
+ any non-X event will take precedence and this means that we
+ cannot rely on it to do the right thing at the right time for
+ widget display.
+
+ drain_X_queue () - this happens when SIGIO gets tripped,
+ processing the event queue allows C-g to be checked for. It gets
+ called from emacs_Xt_event_pending_p ().
+
+ In order to solve this I have tried introducing a list primitive -
+ dispatch-non-command-events - which forces processing of X events
+ related to display. Unfortunately this has a number of problems,
+ one is that it is possible for event_stream_event_pending_p to
+ block for ever if there isn't actually an event. I guess this can
+ happen if we drop the synthetic event for reason. It also relies on
+ SIGIO processing which makes things rather fragile.
+
+ People have seen behaviour whereby XEmacs blocks until you move the
+ mouse. This seems to indicate that dispatch-non-command-events is
+ blocking. It may be that in a SIGIO world forcing SIGIO processing
+ does the wrong thing.
+*/
static void
emacs_Xt_force_event_pending (struct frame* f)
{
/* Send the drop message */
XSendEvent(dpy, XtWindow (FRAME_X_SHELL_WIDGET (f)),
True, NoEventMask, &event);
- /* Force event pending to check the X queue. */
- quit_check_signal_tick_count++;
+ /* We rely on SIGIO and friends to realise we have generated an
+ event. */
}
static void
/* quit_check_signal_tick_count is volatile so try to avoid race conditions
by using a temporary variable */
tick_count_val = quit_check_signal_tick_count;
- if (last_quit_check_signal_tick_count != tick_count_val)
+ if (last_quit_check_signal_tick_count != tick_count_val
+#if !defined (SIGIO) || defined (CYGWIN)
+ || (XtIMXEvent & XtAppPending (Xt_app_con))
+#endif
+ )
{
last_quit_check_signal_tick_count = tick_count_val;
Lisp_Object Vfile_name_coding_system;
/* Table of symbols identifying each coding category. */
-Lisp_Object coding_category_symbol[CODING_CATEGORY_LAST + 1];
+Lisp_Object coding_category_symbol[CODING_CATEGORY_LAST];
struct file_coding_dump {
/* Coding system currently associated with each coding category. */
- Lisp_Object coding_category_system[CODING_CATEGORY_LAST + 1];
+ Lisp_Object coding_category_system[CODING_CATEGORY_LAST];
/* Table of all coding categories in decreasing order of priority.
This describes a permutation of the possible coding categories. */
- int coding_category_by_priority[CODING_CATEGORY_LAST + 1];
+ int coding_category_by_priority[CODING_CATEGORY_LAST];
#if defined(MULE) && !defined(UTF2000)
Lisp_Object ucs_to_mule_table[65536];
} *fcd;
static const struct lrecord_description fcd_description_1[] = {
- { XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, coding_category_system), CODING_CATEGORY_LAST + 1 },
+ { XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, coding_category_system), CODING_CATEGORY_LAST },
#if defined(MULE) && !defined(UTF2000)
{ XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, ucs_to_mule_table), countof (fcd->ucs_to_mule_table) },
#endif
int i;
CHECK_SYMBOL (symbol);
- for (i = 0; i <= CODING_CATEGORY_LAST; i++)
+ for (i = 0; i < CODING_CATEGORY_LAST; i++)
if (EQ (coding_category_symbol[i], symbol))
return i;
int i;
Lisp_Object list = Qnil;
- for (i = CODING_CATEGORY_LAST; i >= 0; i--)
+ for (i = CODING_CATEGORY_LAST - 1; i >= 0; i--)
list = Fcons (coding_category_symbol[i], list);
return list;
}
*/
(list))
{
- int category_to_priority[CODING_CATEGORY_LAST + 1];
+ int category_to_priority[CODING_CATEGORY_LAST];
int i, j;
Lisp_Object rest;
/* First generate a list that maps coding categories to priorities. */
- for (i = 0; i <= CODING_CATEGORY_LAST; i++)
+ for (i = 0; i < CODING_CATEGORY_LAST; i++)
category_to_priority[i] = -1;
/* Highest priority comes from the specified list. */
/* Now go through the existing categories by priority to retrieve
the categories not yet specified and preserve their priority
order. */
- for (j = 0; j <= CODING_CATEGORY_LAST; j++)
+ for (j = 0; j < CODING_CATEGORY_LAST; j++)
{
int cat = fcd->coding_category_by_priority[j];
if (category_to_priority[cat] < 0)
/* Now we need to construct the inverse of the mapping we just
constructed. */
- for (i = 0; i <= CODING_CATEGORY_LAST; i++)
+ for (i = 0; i < CODING_CATEGORY_LAST; i++)
fcd->coding_category_by_priority[category_to_priority[i]] = i;
/* Phew! That was confusing. */
int i;
Lisp_Object list = Qnil;
- for (i = CODING_CATEGORY_LAST; i >= 0; i--)
+ for (i = CODING_CATEGORY_LAST - 1; i >= 0; i--)
list = Fcons (coding_category_symbol[fcd->coding_category_by_priority[i]],
list);
return list;
#endif
/* Look through the coding categories by priority and find
the first one that is allowed. */
- for (i = 0; i <= CODING_CATEGORY_LAST; i++)
+ for (i = 0; i < CODING_CATEGORY_LAST; i++)
{
cat = fcd->coding_category_by_priority[i];
if ((mask & (1 << cat)) &&
#ifdef MULE
decst.mask = postprocess_iso2022_mask (decst.mask);
#endif
- for (i = CODING_CATEGORY_LAST; i >= 0; i--)
+ for (i = CODING_CATEGORY_LAST - 1; i >= 0; i--)
{
int sys = fcd->coding_category_by_priority[i];
if (decst.mask & (1 << sys))
If CHECK_INVALID_CHARSETS is non-zero, check for designation
or invocation of an invalid character set and treat that as
- an unrecognized escape sequence. */
+ an unrecognized escape sequence.
+
+ ********************************************************************
+
+ #### Strategies for error annotation and coding orthogonalization
+
+ We really want to separate out a number of things. Conceptually,
+ there is a nested syntax.
+
+ At the top level is the ISO 2022 extension syntax, including charset
+ designation and invocation, and certain auxiliary controls such as the
+ ISO 6429 direction specification. These are octet-oriented, with the
+ single exception (AFAIK) of the "exit Unicode" sequence which uses the
+ UTF's natural width (1 byte for UTF-7 and UTF-8, 2 bytes for UCS-2 and
+ UTF-16, and 4 bytes for UCS-4 and UTF-32). This will be treated as a
+ (deprecated) special case in Unicode processing.
+
+ The middle layer is ISO 2022 character interpretation. This will depend
+ on the current state of the ISO 2022 registers, and assembles octets
+ into the character's internal representation.
+
+ The lowest level is translating system control conventions. At present
+ this is restricted to newline translation, but one could imagine doing
+ tab conversion or line wrapping here. "Escape from Unicode" processing
+ would be done at this level.
+
+ At each level the parser will verify the syntax. In the case of a
+ syntax error or warning (such as a redundant escape sequence that affects
+ no characters), the parser will take some action, typically inserting the
+ erroneous octets directly into the output and creating an annotation
+ which can be used by higher level I/O to mark the affected region.
+
+ This should make it possible to do something sensible about separating
+ newline convention processing from character construction, and about
+ preventing ISO 2022 escape sequences from being recognized
+ inappropriately.
+
+ The basic strategy will be to have octet classification tables, and
+ switch processing according to the table entry.
+
+ It's possible that, by doing the processing with tables of functions or
+ the like, the parser can be used for both detection and translation. */
static int
parse_iso2022_esc (Lisp_Object codesys, struct iso2022_decoder *iso,
dumpstruct (&fcd, &fcd_description);
/* Initialize to something reasonable ... */
- for (i = 0; i <= CODING_CATEGORY_LAST; i++)
+ for (i = 0; i < CODING_CATEGORY_LAST; i++)
{
fcd->coding_category_system[i] = Qnil;
fcd->coding_category_by_priority[i] = i;
#define ISO_CODE_CSI 0x9B /* control-sequence-introduce */
#endif /* MULE */
-/* For detecting the encoding of text */
+/* Distinguishable categories of encodings.
+
+ This list determines the initial priority of the categories.
+
+ For better or worse, currently Mule files are encoded in 7-bit ISO 2022.
+ For this reason, under Mule ISO_7 gets highest priority.
+
+ Putting NO_CONVERSION second prevents "binary corruption" in the
+ default case in all but the (presumably) extremely rare case of a
+ binary file which contains redundant escape sequences but no 8-bit
+ characters.
+
+ The remaining priorities are based on perceived "internationalization
+ political correctness." An exception is UCS-4 at the bottom, since
+ basically everything is compatible with UCS-4, but it is likely to
+ be very rare as an external encoding. */
+
enum coding_category_type
{
+ /* must be a contiguous range of values 0 -- CODING_CATEGORY_LAST - 1 */
#ifdef MULE
- CODING_CATEGORY_SHIFT_JIS,
CODING_CATEGORY_ISO_7, /* ISO2022 system using only seven-bit bytes,
no locking shift */
- CODING_CATEGORY_ISO_8_DESIGNATE, /* ISO2022 system using eight-bit bytes,
- no locking shift, no single shift,
- using designation to switch charsets */
+ CODING_CATEGORY_NO_CONVERSION,
+ CODING_CATEGORY_UTF8,
CODING_CATEGORY_ISO_8_1, /* ISO2022 system using eight-bit bytes,
no locking shift, no designation sequences,
one-dimension characters in the upper half. */
CODING_CATEGORY_ISO_8_2, /* ISO2022 system using eight-bit bytes,
no locking shift, no designation sequences,
two-dimension characters in the upper half. */
+ CODING_CATEGORY_ISO_8_DESIGNATE, /* ISO2022 system using eight-bit bytes,
+ no locking shift, no single shift,
+ using designation to switch charsets */
CODING_CATEGORY_ISO_LOCK_SHIFT, /* ISO2022 system using locking shift */
+ CODING_CATEGORY_SHIFT_JIS,
CODING_CATEGORY_BIG5,
CODING_CATEGORY_UCS4,
- CODING_CATEGORY_UTF8,
+#else /* not MULE */
+ CODING_CATEGORY_NO_CONVERSION,
#endif /* MULE */
- CODING_CATEGORY_NO_CONVERSION
+ CODING_CATEGORY_LAST /* not a real coding category */
};
-#define CODING_CATEGORY_LAST CODING_CATEGORY_NO_CONVERSION
-
#ifdef MULE
#define CODING_CATEGORY_SHIFT_JIS_MASK \
(1 << CODING_CATEGORY_SHIFT_JIS)
x_map_subwindow (Lisp_Image_Instance *p, int x, int y,
struct display_glyph_area* dga)
{
+ assert (dga->width > 0 && dga->height > 0);
if (IMAGE_INSTANCE_TYPE (p) == IMAGE_SUBWINDOW)
{
Window subwindow = IMAGE_INSTANCE_X_SUBWINDOW_ID (p);
(Dimension)IMAGE_INSTANCE_HEIGHT (p));
}
+ /* Adjust offsets within the frame. */
+ if (XFRAME (IMAGE_INSTANCE_FRAME (p))->frame_changed)
+ {
+ Arg al[2];
+ XtSetArg (al [0], XtNx, &IMAGE_INSTANCE_X_WIDGET_XOFFSET (p));
+ XtSetArg (al [1], XtNy, &IMAGE_INSTANCE_X_WIDGET_YOFFSET (p));
+ XtGetValues (FRAME_X_TEXT_WIDGET
+ (XFRAME (IMAGE_INSTANCE_FRAME (p))), al, 2);
+ }
+
/* now modify the widget */
lw_modify_all_widgets (IMAGE_INSTANCE_X_WIDGET_LWID (p),
wv, True);
Lisp_Object property =
IMAGE_SPECIFIER_ATTACHEE_PROPERTY (XIMAGE_SPECIFIER (specifier));
if (FACEP (attachee))
- face_property_was_changed (attachee, property, locale);
+ {
+ face_property_was_changed (attachee, property, locale);
+ if (BUFFERP (locale))
+ XBUFFER (locale)->buffer_local_face_property = 1;
+ }
else if (GLYPHP (attachee))
glyph_property_was_changed (attachee, property, locale);
}
+++ /dev/null
-/* input-method-xfs.c provides just only locale initialize
- for non Motif people. (stoled from input-method-xlib.c)
- Why I made this code is to initialize X locale environment for
- the purpose of use XFontSet correctly in lwlib/xlwmenu.c.
- And this code donot provides input methods under Xlib while they
- prefer to use Canna, Wnn, skk or something like that.
- This code has been tested on FreeBSD 2.2.1 and Solaris2.5.
-
- Copyright (C) 1997 Kazuyuki IENAGA.
-
-This file is a part of XEmacs.
-
-XEmacs is free software; you can redistribute it and/or modify it
-under the terms of the GNU General Public License as published by the
-Free Software Foundation; either version 2, or (at your option) any
-later version.
-
-XEmacs is distributed in the hope that it will be useful, but WITHOUT
-ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
-for more details.
-
-You should have received a copy of the GNU General Public License
-along with XEmacs; see the file COPYING. If not, write to
-the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
-Boston, MA 02111-1307, USA. */
-
-#include <config.h>
-#include <X11/Xlocale.h> /* More portable than <locale.h> ? */
-#include "lisp.h"
-#include "frame.h"
-#include "device.h"
-#include "window.h"
-#include "buffer.h"
-#include "console-x.h"
-#include "EmacsFrame.h"
-#include "events.h"
-
-#ifdef USE_XFONTSET
-void
-Initialize_Locale (void)
-{
- char *locale;
-
- /* dverna - Nov. 98: #### DON'T DO THIS !!! The default XtLanguageProc
- routine calls setlocale(LC_ALL, lang) which fucks up our lower-level
- locale management, and especially the value of LC_NUMERIC. Anyway, since
- at this point, we don't know yet whether we're gonna need an X11 frame,
- we should really do it manually and not use Xlib's dumb default routine */
- /*XtSetLanguageProc (NULL, (XtLanguageProc) NULL, NULL);*/
- if ((locale = setlocale (LC_ALL, "")) == NULL)
- {
- stderr_out ("Can't set locale.\n");
- stderr_out ("Using C locale instead.\n");
- putenv ("LANG=C");
- putenv ("LC_ALL=C");
- if ((locale = setlocale (LC_ALL, "C")) == NULL)
- {
- stderr_out ("Can't even set locale to `C'!\n");
- return;
- }
- }
-
- if (!XSupportsLocale ())
- {
- stderr_out ("X Windows does not support locale `%s'\n", locale);
- stderr_out ("Using C Locale instead\n");
- putenv ("LANG=C");
- putenv ("LC_ALL=C");
- if ((locale = setlocale (LC_ALL, "C")) == NULL)
- {
- stderr_out ("Can't even set locale to `C'!\n");
- return;
- }
- if (!XSupportsLocale ())
- {
- stderr_out ("X Windows does not even support locale `C'!\n");
- return;
- }
- }
-
- setlocale(LC_NUMERIC, "C");
- setlocale(LC_CTYPE, ""); /* take back CTYPE to previous state */
-
- if (XSetLocaleModifiers ("") == NULL)
- {
- stderr_out ("XSetLocaleModifiers(\"\") failed\n");
- stderr_out ("Check the value of the XMODIFIERS environment variable.\n");
- }
-}
-#endif /* USE_XFONTSET */
#include "EmacsFrame.h"
#include "events.h"
-#ifndef XIM_XLIB
-#error XIM_XLIB is not defined??
+#if !defined (XIM_XLIB) && !defined (USE_XFONTSET)
+#error neither XIM_XLIB nor USE_XFONTSET is defined??
#endif
Lisp_Object Qxim_xlib;
#define xim_warn1(fmt, str) warn_when_safe (Qxim_xlib, Qwarning, fmt, str);
#define xim_info(str) warn_when_safe (Qxim_xlib, Qinfo, str);
+#ifdef XIM_XLIB /* XIM_XLIB specific */
/* Get/Set IC values for just one attribute */
#ifdef DEBUG_XEMACS
#define XIC_Value(Get_Set, xic, name, attr, value) \
"XIMPreeditNone|XIMStatusNone";
static XIMStyle best_style (XIMStyles *user, XIMStyles *xim);
+#endif /* XIM_XLIB only */
/* This function is documented, but no prototype in the header files */
EXTERN_C char * XSetIMValues(XIM, ...);
}
}
+#ifdef XIM_XLIB /* starting XIM specific codes */
+
/* Callbacks for IM are supported from X11R6 or later. */
#ifdef HAVE_XREGISTERIMINSTANTIATECALLBACK
}
}
#endif
+#endif /* XIM_XLIB only */
#if 0
/* Get a fontset for IM to use */
coming from libraries.
*/
+#include <config.h>
+
char my_edata[] = "End of Emacs initialized data";
-int my_ebss;
+/* Ensure there is enough slack in the .bss to pad with. */
+#ifdef HEAP_IN_DATA
+#define BSS_PADDING 0x1000
+#else
+#define BSS_PADDING 1
+#endif
+
+char my_ebss [BSS_PADDING];
+
Lisp_Object oldval)
{
MARK_MENUBAR_CHANGED;
+ /* This is to force subwindow offsets to be recalculated - see
+ x_redisplay_widget (). */
+ MARK_FRAME_CHANGED (WINDOW_XFRAME (w));
}
static void
if (STRINGP (eltstring)
&& (slength <= XSTRING_CHAR_LENGTH (eltstring))
- && (0 > scmp (XSTRING_DATA (eltstring),
+ /* Reject alternatives that start with space
+ unless the input starts with space. */
+ && ((XSTRING_CHAR_LENGTH (string) > 0 &&
+ string_char (XSTRING (string), 0) == ' ')
+ || string_char (XSTRING (eltstring), 0) != ' ')
+ && (0 > scmp (XSTRING_DATA (eltstring),
XSTRING_DATA (string),
slength)))
{
/* Synched up with: Mule 2.3. Not in FSF. */
-/* #### The comments in this file are mostly in EUC-formatted Japanese.
- It would be ***soooo*** much nicer if someone could translate
- them ... */
+/* Japanese comments were translated 2000-12-06 by Stephen Turnbull
+ <stephen@xemacs.org>. I haven't verified that the Japanese comments
+ were correct. YMMV, NO WARRANTY, not even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (^^;;; as the
+ Japanese say. */
/*
#endif /* !CANNA2 */
extern char *jrKanjiError;
+/* #### is this global really necessary? */
#define KEYTOSTRSIZE 2048
-static unsigned char buf[KEYTOSTRSIZE];
+static unsigned char key_buffer[KEYTOSTRSIZE];
static char **warning;
static int canna_empty_info, canna_through_info;
int len;
CHECK_CHAR_COERCE_INT (ch);
- len = jrKanjiString (0, XCHAR (ch), buf, KEYTOSTRSIZE, &ks);
- return storeResults (buf, len, &ks);
+ len = jrKanjiString (0, XCHAR (ch), key_buffer, KEYTOSTRSIZE, &ks);
+ return storeResults (key_buffer, len, &ks);
}
static Lisp_Object
}
else
{
- /* ³ÎÄꤷ¤¿Ê¸»úÎó */
+ /* ³ÎÄꤷ¤¿Ê¸»úÎó (the confirmed string) */
Vcanna_kakutei_string = make_string (buf, len);
val = make_int (len);
- /* ³ÎÄꤷ¤¿Ê¸»úÎó¤ÎÆɤߤξðÊó... */
+ /* ³ÎÄꤷ¤¿Ê¸»úÎó¤ÎÆɤߤξðÊó...
+ (info about the reading of the confirmed string) */
Vcanna_kakutei_yomi = Vcanna_kakutei_romaji = Qnil;
if (ks->info & KanjiYomiInfo)
{
{
int yomilen2;
- Vcanna_kakutei_yomi = make_string (p, yomilen); /* ÆÉ¤ß */
+ Vcanna_kakutei_yomi = make_string (p, yomilen); /* Æɤß
+ (reading) */
p += yomilen + 1;
yomilen2 = strlen (p);
if (len + yomilen + yomilen2 + 2 < KEYTOSTRSIZE)
{
- Vcanna_kakutei_romaji = make_string (p, yomilen2); /* ¥í¡¼¥Þ»ú */
+ Vcanna_kakutei_romaji = make_string (p, yomilen2);
+ /* ¥í¡¼¥Þ»ú (romanization) */
}
}
}
- /* ¸õÊäɽ¼¨¤Îʸ»úÎó¤Ç¤¹¡£*/
+ /* ¸õÊäɽ¼¨¤Îʸ»úÎó¤Ç¤¹¡£
+ (string for displaying candidate translations) */
Vcanna_henkan_string = Qnil;
if (ks->length >= 0)
{
{
canna_henkan_length = mule_strlen (ks->echoStr,ks->length);
canna_henkan_revPos = mule_strlen (ks->echoStr,ks->revPos);
- canna_henkan_revLen = mule_strlen (ks->echoStr+ks->revPos,ks->revLen);
+ canna_henkan_revLen = mule_strlen (ks->echoStr+ks->revPos,
+ ks->revLen);
}
else
{
#endif /* CANNA_MULE */
}
- /* °ìÍ÷¤Î¾ðÊó */
+ /* °ìÍ÷¤Î¾ðÊó (information about the echo area menu) */
Vcanna_ichiran_string = Qnil;
if (ks->info & KanjiGLineInfo && ks->gline.length >= 0)
{
- Vcanna_ichiran_string = make_string (ks->gline.line, ks->gline.length);
+ Vcanna_ichiran_string = make_string (ks->gline.line,
+ ks->gline.length);
#ifndef CANNA_MULE
canna_ichiran_length = ks->gline.length;
canna_ichiran_revPos = ks->gline.revPos;
canna_ichiran_revLen = ks->gline.revLen;
#else /* CANNA_MULE */
count_char (ks->gline.line, ks->gline.length,
- ks->gline.revPos, ks->gline.revLen, &canna_ichiran_length,
+ ks->gline.revPos, ks->gline.revLen,
+ &canna_ichiran_length,
&canna_ichiran_revPos, &canna_ichiran_revLen);
#endif /* CANNA_MULE */
}
- /* ¥â¡¼¥É¤Î¾ðÊó */
+ /* ¥â¡¼¥É¤Î¾ðÊó (mode information) */
Vcanna_mode_string = Qnil;
if (ks->info & KanjiModeInfo)
{
Vcanna_mode_string = make_string (ks->mode, strlen (ks->mode));
}
- /* ¤½¤Î¾¤Î¾ðÊó */
+ /* ¤½¤Î¾¤Î¾ðÊó (other information) */
canna_empty_info = (ks->info & KanjiEmptyInfo) ? 1 : 0;
canna_through_info = (ks->info & KanjiThroughInfo) ? 1 : 0;
}
*/
(num))
{
- int kugiri; /* ʸÀá¶èÀÚ¤ê¤ò¤¹¤ë¤«¡© */
+ int kugiri; /* ʸÀá¶èÀÚ¤ê¤ò¤¹¤ë¤«¡© (display clause separator?) */
kugiri = NILP (num) ? 0 : 1;
int res;
unsigned char **p, **q;
- int kugiri; /* ʸÀá¶èÀÚ¤ê¤ò¤¹¤ë¤«¡© */
+ int kugiri; /* ʸÀá¶èÀÚ¤ê¤ò¤¹¤ë¤«¡© (display clause separator?) */
IRCP_context = -1;
{
val = Fcons (make_string ((unsigned char*) jrKanjiError,
strlen (jrKanjiError)), val);
- /* ¥¤¥Ë¥·¥ã¥é¥¤¥º¤Ç¼ºÇÔ¤·¤¿¾ì¹ç¡£ */
+ /* ¥¤¥Ë¥·¥ã¥é¥¤¥º¤Ç¼ºÇÔ¤·¤¿¾ì¹ç¡£ (on initialization failure) */
return Fcons (Qnil, val);
}
else
#ifndef CANNA_MULE
jrKanjiControl (0, KC_INHIBITHANKAKUKANA, (char *) 1);
#else
- /* mule ¤À¤Ã¤¿¤éȾ³Ñ¥«¥¿¥«¥Ê¤â»È¤¨¤ë */
+ /* mule ¤À¤Ã¤¿¤éȾ³Ñ¥«¥¿¥«¥Ê¤â»È¤¨¤ë
+ (Mule can use half-width katakana) */
if (canna_inhibit_hankakukana)
jrKanjiControl (0, KC_INHIBITHANKAKUKANA, (char *) 1);
#endif
- jrKanjiControl (0, KC_YOMIINFO, (char *) 2); /* ¢¨£²: ¥í¡¼¥Þ»ú¤Þ¤ÇÊÖ¤¹ */
+ jrKanjiControl (0, KC_YOMIINFO, (char *) 2); /* ¢¨£²: ¥í¡¼¥Þ»ú¤Þ¤ÇÊÖ¤¹
+ (*2: return to
+ romanized form) */
val = Fcons (Qnil, val);
return Fcons (CANNA_mode_keys (), val);
}
#endif
CHECK_STRING (str);
- ksv.buffer = (unsigned char *) buf;
+ ksv.buffer = (unsigned char *) key_buffer;
ksv.bytes_buffer = KEYTOSTRSIZE;
#ifndef CANNA_MULE
ks.echoStr = XSTRING_DATA (str);
#endif /* CANNA_MULE */
ksv.ks = &ks;
len = jrKanjiControl (0, KC_DEFINEKANJI, (char *)&ksv);
- val = storeResults (buf, ksv.val, ksv.ks);
+ val = storeResults (key_buffer, ksv.val, ksv.ks);
return val;
}
CHECK_INT (num);
- ksv.buffer = (unsigned char *) buf;
+ ksv.buffer = (unsigned char *) key_buffer;
ksv.bytes_buffer = KEYTOSTRSIZE;
ksv.ks = &ks;
ksv.val = XINT (num);
jrKanjiControl (0, KC_CHANGEMODE, (char *)&ksv);
- val = storeResults (buf, ksv.val, ksv.ks);
+ val = storeResults (key_buffer, ksv.val, ksv.ks);
return val;
}
CHECK_STRING (yomi);
#ifndef CANNA_MULE
- strncpy (buf, XSTRING_DATA (yomi), XSTRING_LENGTH (yomi));
+ strncpy (key_buffer, XSTRING_DATA (yomi), XSTRING_LENGTH (yomi));
ks.length = XSTRING_LENGTH (yomi);
- buf[ks.length] = '\0';
+ key_buffer[ks.length] = '\0';
#else /* CANNA_MULE */
- m2c (XSTRING_DATA (yomi), XSTRING_LENGTH (yomi), buf);
- ks.length = strlen (buf);
+ m2c (XSTRING_DATA (yomi), XSTRING_LENGTH (yomi), key_buffer);
+ ks.length = strlen (key_buffer);
#endif /* CANNA_MULE */
if (NILP (roma))
CHECK_STRING (roma);
#ifndef CANNA_MULE
- strncpy (buf + XSTRING_LENGTH (yomi) + 1, XSTRING_DATA (roma),
+ strncpy (key_buffer + XSTRING_LENGTH (yomi) + 1, XSTRING_DATA (roma),
XSTRING_LENGTH (roma));
- buf[XSTRING_LENGTH (yomi) + 1 + XSTRING_LENGTH (roma)] = '\0';
- ks.mode = (unsigned char *)(buf + XSTRING_LENGTH (yomi) + 1);
+ key_buffer[XSTRING_LENGTH (yomi) + 1 + XSTRING_LENGTH (roma)] = '\0';
+ ks.mode = (unsigned char *)(key_buffer + XSTRING_LENGTH (yomi) + 1);
#else /* CANNA_MULE */
- ks.mode = (unsigned char *)(buf + ks.length + 1);
+ ks.mode = (unsigned char *)(key_buffer + ks.length + 1);
m2c (XSTRING_DATA (roma), XSTRING_LENGTH (roma), ks.mode);
#endif /* CANNA_MULE */
}
- ks.echoStr = (unsigned char *) buf;
- ksv.buffer = (unsigned char *) buf; /* ÊÖÃÍÍÑ */
+ ks.echoStr = (unsigned char *) key_buffer;
+ ksv.buffer = (unsigned char *) key_buffer; /* ÊÖÃÍÍÑ (return value) */
ksv.bytes_buffer = KEYTOSTRSIZE;
ksv.ks = &ks;
jrKanjiControl (0, KC_STOREYOMI, (char *)&ksv);
- return storeResults (buf, ksv.val, ksv.ks);
+ return storeResults (key_buffer, ksv.val, ksv.ks);
}
DEFUN ("canna-do-function", Fcanna_do_function, 1, 2, 0, /*
if (NILP (ch))
{
- *buf = '@';
+ *key_buffer = '@';
}
else
{
CHECK_CHAR (ch);
- *buf = XCHAR (ch);
+ *key_buffer = XCHAR (ch);
}
- ksv.buffer = (unsigned char *) buf;
+ ksv.buffer = (unsigned char *) key_buffer;
ksv.bytes_buffer = KEYTOSTRSIZE;
ksv.ks = &ks;
ksv.val = XINT (num);
jrKanjiControl (0, KC_DO, (char *) &ksv);
- val = storeResults (buf, ksv.val, ksv.ks);
+ val = storeResults (key_buffer, ksv.val, ksv.ks);
return val;
}
CHECK_STRING (str);
#ifndef CANNA_MULE
- strncpy (buf, XSTRING_DATA (str), XSTRING_LENGTH (str));
- buf[XSTRING_LENGTH (str)] = '\0';
+ strncpy (key_buffer, XSTRING_DATA (str), XSTRING_LENGTH (str));
+ key_buffer[XSTRING_LENGTH (str)] = '\0';
#else /* CANNA_MULE */
- m2c (XSTRING_DATA (str), XSTRING_LENGTH (str), buf);
+ m2c (XSTRING_DATA (str), XSTRING_LENGTH (str), key_buffer);
#endif /* CANNA_MULE */
- p = (unsigned char**) buf;
+ p = (unsigned char**) key_buffer;
n = jrKanjiControl (0, KC_PARSE, (char *) &p);
val = Qnil;
while (n > 0)
{
return Qnil;
}
- RkEndBun (IRCP_context, 1); /* ³Ø½¬¤Ï¤¤¤Ä¤Ç¤â¹Ô¤Ã¤ÆÎɤ¤¤â¤Î¤Ê¤Î¤«¡© */
+ RkEndBun (IRCP_context, 1); /* ³Ø½¬¤Ï¤¤¤Ä¤Ç¤â¹Ô¤Ã¤ÆÎɤ¤¤â¤Î¤Ê¤Î¤«¡©
+ (is it OK to invoke learning function
+ at arbitrary times?) */
return Qt;
}
a compatibility test. --kkm */
/* Since stat is encapsulated on Windows NT, we need to encapsulate
- the equally broken fstat as well. */
+ the equally broken fstat as well. FSFmacs also provides its own
+ utime. Is that necessary here too? */
int
-mswindows_fstat (int handle, struct stat *buffer)
+mswindows_fstat (int desc, struct stat * buf)
{
- int ret;
- BY_HANDLE_FILE_INFORMATION lpFileInfo;
- /* Initialize values */
- buffer->st_mode = 0;
- buffer->st_size = 0;
- buffer->st_dev = 0;
- buffer->st_rdev = 0;
- buffer->st_atime = 0;
- buffer->st_ctime = 0;
- buffer->st_mtime = 0;
- buffer->st_nlink = 0;
- ret = GetFileInformationByHandle((HANDLE) _get_osfhandle(handle), &lpFileInfo);
- if (!ret)
+ HANDLE fh = (HANDLE) _get_osfhandle (desc);
+ BY_HANDLE_FILE_INFORMATION info;
+ DWORD fake_inode;
+ int permission;
+
+ switch (GetFileType (fh) & ~FILE_TYPE_REMOTE)
{
- return -1;
+ case FILE_TYPE_DISK:
+ buf->st_mode = _S_IFREG;
+ if (!GetFileInformationByHandle (fh, &info))
+ {
+ errno = EACCES;
+ return -1;
+ }
+ break;
+ case FILE_TYPE_PIPE:
+ buf->st_mode = _S_IFIFO;
+ goto non_disk;
+ case FILE_TYPE_CHAR:
+ case FILE_TYPE_UNKNOWN:
+ default:
+ buf->st_mode = _S_IFCHR;
+ non_disk:
+ memset (&info, 0, sizeof (info));
+ info.dwFileAttributes = 0;
+ info.ftCreationTime = utc_base_ft;
+ info.ftLastAccessTime = utc_base_ft;
+ info.ftLastWriteTime = utc_base_ft;
+ }
+
+ if (info.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY)
+ {
+ buf->st_mode = _S_IFDIR;
+ buf->st_nlink = 2; /* doesn't really matter */
+ fake_inode = 0; /* this doesn't either I think */
}
else
{
- buffer->st_mtime = convert_time (lpFileInfo.ftLastWriteTime);
- buffer->st_atime = convert_time (lpFileInfo.ftLastAccessTime);
- if (buffer->st_atime == 0) buffer->st_atime = buffer->st_mtime;
- buffer->st_ctime = convert_time (lpFileInfo.ftCreationTime);
- if (buffer->st_ctime == 0) buffer->st_ctime = buffer->st_mtime;
- buffer->st_size = lpFileInfo.nFileSizeLow;
- buffer->st_nlink = (short) lpFileInfo.nNumberOfLinks;
- return 0;
+ buf->st_nlink = info.nNumberOfLinks;
+ /* Might as well use file index to fake inode values, but this
+ is not guaranteed to be unique unless we keep a handle open
+ all the time (even then there are situations where it is
+ not unique). Reputedly, there are at most 48 bits of info
+ (on NTFS, presumably less on FAT). */
+ fake_inode = info.nFileIndexLow ^ info.nFileIndexHigh;
}
+
+ /* MSVC defines _ino_t to be short; other libc's might not. */
+ if (sizeof (buf->st_ino) == 2)
+ buf->st_ino = fake_inode ^ (fake_inode >> 16);
+ else
+ buf->st_ino = fake_inode;
+
+ /* consider files to belong to current user */
+ buf->st_uid = 0;
+ buf->st_gid = 0;
+
+ buf->st_dev = info.dwVolumeSerialNumber;
+ buf->st_rdev = info.dwVolumeSerialNumber;
+
+ buf->st_size = info.nFileSizeLow;
+
+ /* Convert timestamps to Unix format. */
+ buf->st_mtime = convert_time (info.ftLastWriteTime);
+ buf->st_atime = convert_time (info.ftLastAccessTime);
+ if (buf->st_atime == 0) buf->st_atime = buf->st_mtime;
+ buf->st_ctime = convert_time (info.ftCreationTime);
+ if (buf->st_ctime == 0) buf->st_ctime = buf->st_mtime;
+
+ /* determine rwx permissions */
+ if (info.dwFileAttributes & FILE_ATTRIBUTE_READONLY)
+ permission = _S_IREAD;
+ else
+ permission = _S_IREAD | _S_IWRITE;
+
+ if (info.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY)
+ permission |= _S_IEXEC;
+
+ buf->st_mode |= permission | (permission >> 3) | (permission >> 6);
+
+ return 0;
}
/* MSVC stat function can't cope with UNC names and has other bugs, so
Lisp_Object property =
COLOR_SPECIFIER_FACE_PROPERTY (XCOLOR_SPECIFIER (specifier));
if (!NILP (face))
- face_property_was_changed (face, property, locale);
+ {
+ face_property_was_changed (face, property, locale);
+ if (BUFFERP (locale))
+ XBUFFER (locale)->buffer_local_face_property = 1;
+ }
}
void
Lisp_Object property =
FONT_SPECIFIER_FACE_PROPERTY (XFONT_SPECIFIER (specifier));
if (!NILP (face))
- face_property_was_changed (face, property, locale);
+ {
+ face_property_was_changed (face, property, locale);
+ if (BUFFERP (locale))
+ XBUFFER (locale)->buffer_local_face_property = 1;
+ }
}
void
Lisp_Object property =
FACE_BOOLEAN_SPECIFIER_FACE_PROPERTY (XFACE_BOOLEAN_SPECIFIER (specifier));
if (!NILP (face))
- face_property_was_changed (face, property, locale);
+ {
+ face_property_was_changed (face, property, locale);
+ if (BUFFERP (locale))
+ XBUFFER (locale)->buffer_local_face_property = 1;
+ }
}
void
/*****************************************************************************
compare_runes
- Compare to runes to see if each of their fields is equal. If so,
+ Compare two runes to see if each of their fields is equal. If so,
return true otherwise return false.
****************************************************************************/
static int
Remove subwindows from the area in the box defined by the given
parameters.
****************************************************************************/
-static void redisplay_unmap_subwindows (struct frame* f, int x, int y, int width, int height,
- Lisp_Object ignored_window)
+static void
+redisplay_unmap_subwindows (struct frame* f, int x, int y, int width, int height,
+ Lisp_Object ignored_window)
{
Lisp_Object rest;
||
-glyphsrc->xoffset >= glyphsrc->width
||
- -glyphsrc->yoffset >= glyphsrc->height)
+ -glyphsrc->yoffset >= glyphsrc->height
+ ||
+ /* #### Not sure why this wasn't coped with before but normalizing
+ to zero width or height is definitely wrong. */
+ (dest->xpos + glyphsrc->xoffset + glyphsrc->width > dest->xpos + dest->width
+ &&
+ dest->width - glyphsrc->xoffset <= 0)
+ ||
+ (dest->ypos + glyphsrc->yoffset + glyphsrc->height > dest->ypos + dest->height
+ &&
+ dest->height - glyphsrc->yoffset <= 0))
{
/* It's all clipped out */
return 0;
If window is topmost, clear the internal border above it.
****************************************************************************/
-static void
+void
redisplay_clear_top_of_window (struct window *w)
{
Lisp_Object window;
/* If the window's structure has changed clear the internal border
above it if it is topmost (the function will check). */
- if (f->windows_structure_changed)
+ if (f->windows_structure_changed || f->faces_changed)
redisplay_clear_top_of_window (w);
/* Output each line. */
f->windows_structure_changed = 1;
}
+ redisplay_clear_top_of_window (w);
if (window_needs_vertical_divider (w))
{
x_output_vertical_divider (w, 0);
maybe a caret cursor, etc. */
DEFVAR_LISP ("bar-cursor", &Vbar_cursor /*
-Use vertical bar cursor if non-nil. If t width is 1 pixel, otherwise 2.
+*Use vertical bar cursor if non-nil. If t width is 1 pixel, otherwise 2.
*/ );
Vbar_cursor = Qnil;
void redisplay_clear_to_window_end (struct window *w, int ypos1, int ypos2);
void redisplay_clear_region (Lisp_Object window, face_index findex, int x,
int y, int width, int height);
+void redisplay_clear_top_of_window (struct window *w);
void redisplay_clear_bottom_of_window (struct window *w,
display_line_dynarr *ddla,
int min_start, int max_end);
#define SYSTEM_TYPE "SCO 3.2v5"
/* SCO has ptys, but with weird names */
+#define HAVE_PTYS
#define PTY_ITERATION \
for (i = 0; ; i++)
#define PTY_NAME_SPRINTF \
In that case, use ordinary stat instead. */
#ifndef S_IFLNK
-#define lstat stat
+#define lstat xemacs_stat
#endif
#if !S_IRUSR
} *fcd;
static const struct lrecord_description fcd_description_1[] = {
- { XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, coding_category_system), CODING_CATEGORY_LAST + 1 },
+ { XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, coding_category_system), CODING_CATEGORY_LAST },
#if defined(MULE) && !defined(UTF2000)
{ XD_LISP_OBJECT_ARRAY, offsetof (struct file_coding_dump, ucs_to_mule_table), countof (fcd->ucs_to_mule_table) },
#endif
/* This is a complete rewrite, some code snarfed from unexnt.c and
unexec.c, Andy Piper (andy@xemacs.org) 13-1-98 */
+#include <config.h>
+#include "lisp.h"
+
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
-#include <config.h>
#include <string.h>
#define DONT_ENCAPSULATE /* filenames are external in unex*.c */
((((unsigned long)addr) + ALLOC_UNIT) & ALLOC_MASK)
/* Note that all sections must be aligned on a 0x1000 boundary so
this is the minimum size that our dummy bss can be. */
-#ifdef BROKEN_GDB
+#ifndef NO_DEBUG
#define BSS_PAD_SIZE 0x1000
#else
#define BSS_PAD_SIZE 0
exit(-1); \
}
-void
-unexec (char *out_name, char *in_name, void *start_data,
- void * d1, void * d2);
/* Dump out .data and .bss sections into a new executable. */
-void unexec (char *out_name, char *in_name, void *start_data,
- void * d1, void * d2)
+int
+unexec (char *out_name, char *in_name, uintptr_t start_data,
+ uintptr_t d1, uintptr_t d2)
{
/* ugly nt hack - should be in lisp */
int a_new, a_out = -1;
close(a_out);
close(a_new);
+ return 0;
}
/* Flip through the executable and cache the info necessary for dumping. */
static void get_section_info (int a_out, char* a_name)
{
- extern int my_ebss;
+ extern char my_ebss[];
/* From lastfile.c */
extern char my_edata[];
data_padding = (f_bss.s_vaddr - f_data.s_vaddr) - f_data.s_size;
}
+ if ((new_bss_size - bss_size) < BSS_PAD_SIZE)
+ {
+ PERROR (".bss free space too small");
+ }
+
file_sz_change=(new_bss_size + data_padding) - BSS_PAD_SIZE;
new_data_size=f_ohdr.dsize + file_sz_change;
lseek (a_new, 0, SEEK_SET);
/* write file header */
f_hdr.f_symptr += file_sz_change;
-#ifndef BROKEN_GDB
+#ifdef NO_DEBUG
f_hdr.f_nscns--;
#endif
{
PERROR("failed to write text header");
}
-#ifdef BROKEN_GDB
+#ifndef NO_DEBUG
/* Write small bss section. */
if (!sections_reversed)
{
{
PERROR("failed to write data header");
}
-#ifdef BROKEN_GDB
+#ifndef NO_DEBUG
/* Write small bss section. */
if (sections_reversed)
{
PERROR("failed to write data header");
}
}
-#ifndef BROKEN_GDB
+#ifdef NO_DEBUG
/* dump bss to maintain offsets */
memset(&f_bss, 0, sizeof(f_bss));
if (write(a_new, &f_bss, sizeof(f_bss)) != sizeof(f_bss))
fatal ("Can't fstat (%s): errno %d\n", old_name, errno);
/* map old file into the address space. */
- if ( (old_base = (caddr_t) mmap ((caddr_t) 0, stat_buf.st_size,
- PROT_READ, MAP_SHARED, old_file, 0)) < 0 )
- fatal ("Can't mmap (%s): errno %d\n", old_name, errno);
+ old_base = (caddr_t) mmap ((caddr_t) 0, stat_buf.st_size,
+ PROT_READ, MAP_SHARED, old_file, 0);
+ if (old_base == (caddr_t) MAP_FAILED)
+ fatal ("Can't mmap (%s): errno %d\n", old_name, errno);
old_file_h = (ElfW(Ehdr) *) old_base;
old_program_h = (ElfW(Phdr) *) ((byte *) old_base + old_file_h->e_phoff);
By default, only the windows in the selected frame are considered.
The optional argument WHICH-FRAMES changes this behavior:
WHICH-FRAMES = `visible' means search windows on all visible frames.
-WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
+WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
WHICH-FRAMES = t means search windows on all frames including invisible frames.
WHICH-FRAMES = a frame means search only windows on that frame.
Anything else means restrict to the selected frame.
By default, only the windows in the selected frame are considered.
The optional argument WHICH-FRAMES changes this behavior:
WHICH-FRAMES = `visible' means search windows on all visible frames.
-WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
+WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
WHICH-FRAMES = t means search windows on all frames including invisible frames.
WHICH-FRAMES = a frame means search only windows on that frame.
Anything else means restrict to the selected frame.
By default, only the windows in the selected frame are considered.
The optional argument WHICH-FRAMES changes this behavior:
WHICH-FRAMES = `visible' means search windows on all visible frames.
-WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
+WHICH-FRAMES = 0 means search windows on all visible and iconified frames.
WHICH-FRAMES = t means search windows on all frames including invisible frames.
WHICH-FRAMES = a frame means search only windows on that frame.
Anything else means restrict to the selected frame.
DELETE_OTHER_WINDOWS, /* Arg is window not to delete */
DELETE_BUFFER_WINDOWS, /* Arg is buffer */
GET_LARGEST_WINDOW,
- UNSHOW_BUFFER, /* Arg is buffer */
GET_BUFFER_WINDOW_COUNT, /* Arg is buffer */
GET_BUFFER_MRU_WINDOW /* Arg is buffer */
};
int dedicated_too,
Lisp_Object which_devices)
{
- /* This function can GC if type == DELETE_BUFFER_WINDOWS or UNSHOW_BUFFER */
+ /* This function can GC if type == DELETE_BUFFER_WINDOWS */
Lisp_Object w;
Lisp_Object best_window = Qnil;
Lisp_Object next_window;
for (;;)
{
struct window *p = XWINDOW (w);
- struct frame *w_frame = XFRAME (WINDOW_FRAME (p));
/* Pick the next window now, since some operations will delete
the current window. */
break;
}
- case UNSHOW_BUFFER:
- {
- if (EQ (p->buffer, obj))
- {
- /* Find another buffer to show in this window. */
- Lisp_Object another_buffer =
- Fother_buffer (obj, Qnil, Qnil);
- if (NILP (another_buffer))
- another_buffer
- = Fget_buffer_create (QSscratch);
- /* If this window is dedicated, and in a frame
- of its own, kill the frame. */
- if (EQ (w, FRAME_ROOT_WINDOW (w_frame))
- && !NILP (p->dedicated)
- && other_visible_frames (w_frame))
- {
- /* Skip the other windows on this frame.
- There might be one, the minibuffer! */
- if (! EQ (w, last_window))
- while (w_frame == XFRAME (WINDOW_FRAME
- (XWINDOW (next_window))))
- {
- /* As we go, check for the end of the
- loop. We mustn't start going
- around a second time. */
- if (EQ (next_window, last_window))
- {
- last_window = w;
- break;
- }
- next_window = Fnext_window (next_window,
- mini ? Qt : Qnil,
- frame_arg, Qt);
- }
- /* Now we can safely delete the frame. */
- delete_frame_internal (XFRAME (WINDOW_FRAME (p)),
- 0, 0, 0);
- }
- else
- {
- /* Otherwise show a different buffer in the
- window. */
- p->dedicated = Qnil;
- Fset_window_buffer (w, another_buffer, Qnil);
- if (EQ (w, Fselected_window (Qnil)))
- Fset_buffer (p->buffer);
- }
- }
- break;
- }
-
default:
abort ();
}
return Qnil;
}
+static Lisp_Object
+list_windows (struct window *w, Lisp_Object value)
+{
+ for (;;)
+ {
+ if (!NILP (w->hchild))
+ value = list_windows (XWINDOW (w->hchild), value);
+ else if (!NILP (w->vchild))
+ value = list_windows (XWINDOW (w->vchild), value);
+ else
+ {
+ Lisp_Object window;
+ XSETWINDOW (window, w);
+ value = Fcons (window, value);
+ }
+ if (NILP (w->next))
+ break;
+ w = XWINDOW (w->next);
+ }
+ return value;
+}
+
+static Lisp_Object
+list_all_windows (Lisp_Object frame_spec, Lisp_Object device_spec)
+{
+ Lisp_Object devcons, concons;
+ Lisp_Object retval = Qnil;
+
+ DEVICE_LOOP_NO_BREAK (devcons, concons)
+ {
+ Lisp_Object frame_list, the_window;
+ Lisp_Object device, tail;
+
+ device = XCAR (devcons);
+ frame_list = DEVICE_FRAME_LIST (XDEVICE (device));
+
+ LIST_LOOP (tail, frame_list)
+ {
+ if ((NILP (frame_spec)
+ && !EQ (XCAR (tail), DEVICE_SELECTED_FRAME (XDEVICE (device))))
+ || (EQ (frame_spec, Qvisible)
+ && !FRAME_VISIBLE_P (XFRAME (XCAR (tail))))
+ || (FRAMEP (frame_spec)
+ && !EQ (frame_spec, XCAR (tail)))
+ || (!NILP (frame_spec)
+ && !device_matches_device_spec (device,
+ NILP (device_spec) ?
+ Vselected_console :
+ device_spec)))
+ continue;
+ the_window = FRAME_ROOT_WINDOW (XFRAME (XCAR (tail)));
+ retval = list_windows (XWINDOW (the_window), retval);
+ }
+ }
+ return Fnreverse (retval);
+}
+
DEFUN ("replace-buffer-in-windows", Freplace_buffer_in_windows, 1, 3,
"bReplace buffer in windows: ", /*
Replace BUFFER with some other buffer in all windows showing it.
(buffer, which_frames, which_devices))
{
/* This function can GC */
- buffer = Fget_buffer (buffer);
- CHECK_BUFFER (buffer);
+ Lisp_Object window_list;
+ Lisp_Object tail;
+ struct gcpro gcpro1, gcpro2;
- /* WHICH-FRAMES values t and nil mean the opposite of what
- window_loop expects. */
if (EQ (which_frames, Qnil))
which_frames = Qt;
else if (EQ (which_frames, Qt))
which_frames = Qnil;
+ window_list = list_all_windows (which_frames, which_devices);
- /* Ignore dedicated windows. */
- window_loop (UNSHOW_BUFFER, buffer, 0, which_frames, 0, which_devices);
+ buffer = Fget_buffer (buffer);
+ CHECK_BUFFER (buffer);
+
+ GCPRO2 (window_list, buffer);
+ LIST_LOOP (tail, window_list)
+ {
+ Lisp_Object window = XCAR (tail);
+ if (!MINI_WINDOW_P (XWINDOW (window))
+ && EQ (XWINDOW (window)->buffer, buffer))
+ {
+ Lisp_Object another_buffer = Fother_buffer (buffer, Qnil, Qnil);
+ Lisp_Object frame = WINDOW_FRAME (XWINDOW (window));
+ if (NILP (another_buffer))
+ another_buffer = Fget_buffer_create (QSscratch);
+ if (!NILP (XWINDOW (window)->dedicated)
+ && EQ (window,
+ FRAME_ROOT_WINDOW (XFRAME (frame)))
+ && other_visible_frames (XFRAME (frame)))
+ {
+ delete_frame_internal (XFRAME (frame), 0, 0, 0); /* GC */
+ }
+ else
+ {
+ Fset_window_buffer (window, another_buffer, Qnil);
+ if (EQ (window, Fselected_window (Qnil)))
+ Fset_buffer (XWINDOW (window)->buffer);
+ }
+ }
+ }
+ UNGCPRO;
return Qnil;
}
\f
{
Lisp_Object tem;
struct window *w = decode_window (window);
+ int old_buffer_local_face_property = 0;
buffer = Fget_buffer (buffer);
CHECK_BUFFER (buffer);
error ("Window is dedicated to buffer %s",
XSTRING_DATA (XBUFFER (tem)->name));
+ old_buffer_local_face_property =
+ XBUFFER (w->buffer)->buffer_local_face_property;
unshow_buffer (w);
}
SET_LAST_MODIFIED (w, 1);
SET_LAST_FACECHANGE (w);
MARK_WINDOWS_CHANGED (w);
+ {
+ int new_buffer_local_face_property =
+ XBUFFER (w->buffer)->buffer_local_face_property;
+
+ if (new_buffer_local_face_property
+ || new_buffer_local_face_property != old_buffer_local_face_property)
+ MARK_WINDOW_FACES_CHANGED (w);
+ }
recompute_all_cached_specifiers_in_window (w);
if (EQ (window, Fselected_window (Qnil)))
{
|| NILP (XWINDOW (o->parent)->vchild))
{
make_dummy_parent (window);
+#if 0
+ /* #### I can't understand why you have to reset face
+ cachels here. This can cause crash so let's disable it
+ and see the difference. See redisplay-tests.el --yh */
reset_face_cachels (XWINDOW (window));
+#endif
new = o->parent;
XWINDOW (new)->vchild = window;
XFRAME (o->frame)->mirror_dirty = 1;
|| NILP (XWINDOW (o->parent)->hchild))
{
make_dummy_parent (window);
+#if 0
+ /* #### See above. */
reset_face_cachels (XWINDOW (window));
+#endif
new = o->parent;
XWINDOW (new)->hchild = window;
XFRAME (o->frame)->mirror_dirty = 1;
windows_changed = 1; \
} while (0)
+/* #### This should be fixed not to call MARK_FRAME_CHANGED because
+ faces are cached per window. Also, other code which changes window's
+ face should use this macro.
+*/
+#define MARK_WINDOW_FACES_CHANGED(w) \
+ MARK_FRAME_FACES_CHANGED (XFRAME ((w)->frame))
+
#define WINDOW_TTY_P(w) FRAME_TTY_P (XFRAME ((w)->frame))
#define WINDOW_X_P(w) FRAME_X_P (XFRAME ((w)->frame))
#define WINDOW_NS_P(w) FRAME_NS_P (XFRAME ((w)->frame))
+2000-12-31 Martin Buchholz <martin@xemacs.org>
+
+ * XEmacs 21.2.39 is released.
+
+2000-12-28 Martin Buchholz <martin@xemacs.org>
+
+ * automated/lisp-tests.el:
+ Avoid triggering Solaris printf buffer overflow from (format).
+
+2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * redisplay-tests.el: New file.
+
+2000-12-12 Martin Buchholz <martin@xemacs.org>
+
+ * automated/lisp-tests.el: Add/Change (format) tests.
+
+2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * automated/lisp-test.el: Test if all-completions ignore
+ elements start with space.
+
+2000-12-04 Yoshiki Hayashi <yoshiki@xemacs.org>
+
+ * automated/regexp-tests.el: Test unmatched search doesn't
+ alter match-string.
+
2000-12-05 Martin Buchholz <martin@xemacs.org>
* XEmacs 21.2.38 is released.
(Assert (string= (format "%e" 100) "1.000000e+02"))
(Assert (string= (format "%E" 100) "1.000000E+02"))
(Assert (string= (format "%f" 100) "100.000000"))
+(Assert (string= (format "%7.3f" 12.12345) " 12.123"))
+(Assert (string= (format "%07.3f" 12.12345) "012.123"))
+(Assert (string= (format "%-7.3f" 12.12345) "12.123 "))
+(Assert (string= (format "%-07.3f" 12.12345) "12.123 "))
(Assert (string= (format "%g" 100.0) "100"))
(Assert (string= (format "%g" 0.000001) "1e-06"))
(Assert (string= (format "%g" 0.0001) "0.0001"))
(Assert (string= (format "%.1d" 10) "10"))
(Assert (string= (format "%.4d" 10) "0010"))
;; Combination of `-', `+', ` ', `0', `#', `.', `*'
-(Assert (string= (format "%-04d" 10) "0010"))
+(Assert (string= (format "%-04d" 10) "10 "))
(Assert (string= (format "%-*d" 4 10) "10 "))
;; #### Correctness of this behavior is questionable.
;; It might be better to signal error.
;; (format "%-.1d" 10)
(Assert (string= (format "%01.1d" 10) "10"))
-(Assert (string= (format "%03.1d" 10) "010"))
-(Assert (string= (format "%01.3d" 10) "10"))
-(Assert (string= (format "%1.3d" 10) "10"))
+(Assert (string= (format "%03.1d" 10) " 10"))
+(Assert (string= (format "%01.3d" 10) "010"))
+(Assert (string= (format "%1.3d" 10) "010"))
(Assert (string= (format "%3.1d" 10) " 10"))
+;;; The following two tests used to use 1000 instead of 100,
+;;; but that merely found buffer overflow bugs in Solaris sprintf().
+(Assert (= 102 (length (format "%.100f" 3.14))))
+(Assert (= 100 (length (format "%100f" 3.14))))
+
;;; Check for 64-bit cleanness on LP64 platforms.
(Assert (= (read (format "%d" most-positive-fixnum)) most-positive-fixnum))
(Assert (= (read (format "%ld" most-positive-fixnum)) most-positive-fixnum))
;;; The printed value might be useful to a human, if not to Emacs Lisp.
(Check-Error invalid-read-syntax (read (format "%u" most-negative-fixnum)))
(Check-Error invalid-read-syntax (read (format "%u" -1)))
+
+;; Check all-completions ignore element start with space.
+(Assert (not (all-completions "" '((" hidden" . "object")))))
+(Assert (all-completions " " '((" hidden" . "object"))))
(setq i (1+ i))))))
;; (test-regex-charset-mule-paranoid)
+
+;; Test replace-match
+(with-temp-buffer
+ (insert "This is a test buffer.")
+ (goto-char (point-min))
+ (search-forward "this is a test ")
+ (looking-at "Unmatchable text")
+ (replace-match "")
+ (Assert (looking-at "^buffer.$")))
projects / chise / xemacs-chise.git- / commitdiff