aboutsummaryrefslogtreecommitdiffstats
path: root/doc/emacs/custom.texi
diff options
context:
space:
mode:
authorPaul Eggert <[email protected]>2012-12-05 14:27:56 -0800
committerPaul Eggert <[email protected]>2012-12-05 14:27:56 -0800
commit1df7defd8040839a81909b0eb8f428f6158b2362 (patch)
tree552c1d92968fa9e15dafeaaec8649b1befba664b /doc/emacs/custom.texi
parent7c2fcf9bad2bed6c0198875384dc2bdb7cbd7e99 (diff)
Fix minor whitespace issues after "." in manual.
Be more systematic about using "@." (not ".") at end of sentence that ends in a capital letter, and about appending "@:" after non-ends of sentences that end in a lower case letter followed by "." followed by whitespace. Omit unnecessary use of "@:" and "@.". Similarly for "?" and "!". Be more consistent about putting a comma after "i.e." and "e.g."; this is the typical American style and it's easier to code in Texinfo. Fixes: debbugs:12973
Diffstat (limited to 'doc/emacs/custom.texi')
-rw-r--r--doc/emacs/custom.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 6ea1ad5535..dd8da41d0c 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -610,10 +610,10 @@ always considered safe.
@vindex custom-enabled-themes
Setting or saving Custom themes actually works by customizing the
variable @code{custom-enabled-themes}. The value of this variable is
-a list of Custom theme names (as Lisp symbols, e.g.@: @code{tango}).
+a list of Custom theme names (as Lisp symbols, e.g., @code{tango}).
Instead of using the @file{*Custom Themes*} buffer to set
@code{custom-enabled-themes}, you can customize the variable using the
-usual customization interface, e.g.@: with @kbd{M-x customize-option}.
+usual customization interface, e.g., with @kbd{M-x customize-option}.
Note that Custom themes are not allowed to set
@code{custom-enabled-themes} themselves.
@@ -2329,7 +2329,7 @@ Here a full file name is used, so no searching is done.
@cindex loading Lisp libraries automatically
@cindex autoload Lisp libraries
Tell Emacs to find the definition for the function @code{myfunction}
-by loading a Lisp library named @file{mypackage} (i.e.@: a file
+by loading a Lisp library named @file{mypackage} (i.e., a file
@file{mypackage.elc} or @file{mypackage.el}):
@example
@@ -2496,7 +2496,7 @@ editor customizations even if you are running as the super user.
More precisely, Emacs first determines which user's init file to use.
It gets your user name from the environment variables @env{LOGNAME} and
-@env{USER}; if neither of those exists, it uses effective user-ID.
+@env{USER}; if neither of those exists, it uses effective user-ID@.
If that user name matches the real user-ID, then Emacs uses @env{HOME};
otherwise, it looks up the home directory corresponding to that user
name in the system's data base of users.