This commit was generated by cvs2svn to compensate for changes in r6453,

[chise/xemacs-chise.git.1] / info / internals.info-1

diff --git a/info/internals.info-1 b/info/internals.info-1
index c385b18..c43d904 100644 (file)
--- a/info/internals.info-1
+++ b/info/internals.info-1
@@ -1,9 +1,9 @@
-This is ../info/internals.info, produced by makeinfo version 4.0 from
-internals/internals.texi.
+This is Info file ../../info/internals.info, produced by Makeinfo
+version 1.68 from the input file internals.texi.
 
 INFO-DIR-SECTION XEmacs Editor
 START-INFO-DIR-ENTRY
-* Internals: (internals).       XEmacs Internals Manual.
+* Internals: (internals).      XEmacs Internals Manual.
 END-INFO-DIR-ENTRY
 
    Copyright (C) 1992 - 1996 Ben Wing.  Copyright (C) 1996, 1997 Sun
@@ -73,7 +73,7 @@ File: internals.info,  Node: Top,  Next: A History of Emacs,  Prev: (dir),  Up:
 * Index::                   Index including concepts, functions, variables,
                               and other terms.
 
-      --- The Detailed Node Listing ---
+      -- The Detailed Node Listing --
 
 Here are other nodes that are inferiors of those already listed,
 mentioned here so you can get to them in one step:
@@ -595,8 +595,8 @@ Some of these objects (in particular windows and frames) have
 displayable representations, and XEmacs provides a function
 `redisplay()' that ensures that the display of all such objects matches
 their internal state.  Most of the time, a standard Lisp environment is
-in a "read-eval-print" loop--i.e. "read some Lisp code, execute it, and
-print the results".  XEmacs has a similar loop:
+in a "read-eval-print" loop - i.e. "read some Lisp code, execute it,
+and print the results".  XEmacs has a similar loop:
 
    * read an event
 
@@ -739,7 +739,7 @@ between C and Lisp:
      installed by the top-level event loop, is executed; this prints
      out the error and continues.) Routines can also specify cleanup
      code (called an "unwind-protect") that will be called when control
-     exits from a block of code, no matter how that exit occurs--i.e.
+     exits from a block of code, no matter how that exit occurs - i.e.
      even if a function deeply nested below it causes a non-local exit
      back to the top level.
 
@@ -753,8 +753,8 @@ between C and Lisp:
      "see" the local variable you declared.  This is actually
      considered a bug in Emacs Lisp and in all other early dialects of
      Lisp, and was corrected in Common Lisp. (In Common Lisp, you can
-     still declare dynamically scoped variables if you want to--they
-     are sometimes useful--but variables by default are "lexically
+     still declare dynamically scoped variables if you want to - they
+     are sometimes useful - but variables by default are "lexically
      scoped" as in C.)
 
    For those familiar with Lisp, Emacs Lisp is modelled after MacLisp,
@@ -886,7 +886,7 @@ for easy upgrading of parts of a system without upgrading the rest.  It
 would be impossible to pre-determine and pre-specify the information for
 all possible configurations.
 
-   In fact, the `s/' and `m/' files are basically _evil_, since they
+   In fact, the `s/' and `m/' files are basically *evil*, since they
 contain unmaintainable platform-specific hard-coded information.
 XEmacs has been moving in the direction of having all system-specific
 information be determined dynamically by `configure'.  Perhaps someday
@@ -897,7 +897,7 @@ we can `rm -rf src/s src/m'.
 features of your system) from template files.  You then run `make',
 which compiles the auxiliary code and programs in `lib-src/' and
 `lwlib/' and the main XEmacs executable in `src/'.  The result of
-compiling and linking is an executable called `temacs', which is _not_
+compiling and linking is an executable called `temacs', which is *not*
 the final XEmacs executable.  `temacs' by itself is not intended to
 function as an editor or even display any windows on the screen, and if
 you simply run it, it will exit immediately.  The `Makefile' runs