[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/compile.texi
From: |
Romain Francoise |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/compile.texi |
Date: |
Sun, 07 May 2006 16:02:27 +0000 |
Index: emacs/lispref/compile.texi
diff -u emacs/lispref/compile.texi:1.26 emacs/lispref/compile.texi:1.27
--- emacs/lispref/compile.texi:1.26 Mon Feb 6 11:55:09 2006
+++ emacs/lispref/compile.texi Sun May 7 16:02:26 2006
@@ -412,7 +412,7 @@
compiling and executing.
@code{autoload} is also effectively @code{eval-and-compile} too. It's
-recognised when compiling, so uses of such a function don't produce
+recognized when compiling, so uses of such a function don't produce
``not known to be defined'' warnings.
Most uses of @code{eval-and-compile} are fairly sophisticated.
@@ -456,7 +456,7 @@
The same sort of thing goes for macros or @code{defalias}es defined
locally and only for use within the file. They can be defined while
compiling, but then not needed when executing. This is good for code
-that's only a fallback for compability with other versions of Emacs.
+that's only a fallback for compatibility with other versions of Emacs.
For example.
@lisp
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/lispref/compile.texi,
Romain Francoise <=