Commit 818f06ea authored by Paul Eggert's avatar Paul Eggert

Prefer straight quoting in some text files

Mostly this just changes ` to ' in static text.  Some exceptions:
* INSTALL.REPO: Use curved quotes, as the diagnostic in question
typically does that now.
* admin/quick-install-emacs (TRY, top level):
Use straight quoting in diagnostics.
* src/README: Fix working-directory confusion.
parent 279303ad
......@@ -42,7 +42,7 @@ subdirectories of 'lisp/', e.g., 'mh-e/' and 'calendar/') will need to be
updated to reflect new autoloaded functions. If you see errors (rather
than warnings) about undefined lisp functions during compilation, that
may be the reason. Finally, sometimes there can be build failures
related to '*loaddefs.el' (e.g., "required feature `esh-groups' was not
related to '*loaddefs.el' (e.g., "required feature ‘esh-groups’ was not
provided"). In that case, follow the instructions below.
To update loaddefs.el (and similar files), do:
......
......@@ -72,7 +72,7 @@ pages of the manuals, and even if they do, the resulting page breaks
depend on what paper and font size they use. This also means that if
you _are_ going to do this, it should be done with the paper and font
size that the GNU Press are going to use when they print the manuals.
I think this is different to what you get if you just use eg `make
I think this is different to what you get if you just use eg 'make
emacs.pdf' (e.g., enable "smallbook").
** Check the keybindings in the refcards are correct, and add any new ones.
......@@ -112,21 +112,21 @@ sk Miroslav Vaško
** Check for modes which bind M-s that conflicts with a new global binding M-s
and change key bindings where necessary. The current list of modes:
1. Gnus binds `M-s' to `gnus-summary-search-article-forward'.
1. Gnus binds 'M-s' to 'gnus-summary-search-article-forward'.
2. Minibuffer binds `M-s' to `next-matching-history-element'
2. Minibuffer binds 'M-s' to 'next-matching-history-element'
(not useful any more since C-s can now search in the history).
3. `center-line' in Text mode was already moved to the text formatting
keymap as `M-o M-s' (thus this binding is not necessary any more
in `nroff-mode-map' too and can be removed now from the nroff mode
because it can now use the global key binding `M-o M-s' `center-line').
3. 'center-line' in Text mode was already moved to the text formatting
keymap as 'M-o M-s' (thus this binding is not necessary any more
in 'nroff-mode-map' too and can be removed now from the nroff mode
because it can now use the global key binding 'M-o M-s' 'center-line').
4. PCL-CVS binds `M-s' to `cvs-status', and log-edit-mode binds it to
`log-edit-comment-search-forward'. Perhaps search commands
on the global key binding `M-s' are useless in these modes.
4. PCL-CVS binds 'M-s' to 'cvs-status', and log-edit-mode binds it to
'log-edit-comment-search-forward'. Perhaps search commands
on the global key binding 'M-s' are useless in these modes.
5. Rmail binds `\es' to `rmail-search'/`rmail-summary-search'.
5. Rmail binds '\es' to 'rmail-search'/'rmail-summary-search'.
* DOCUMENTATION
......
......@@ -37,7 +37,7 @@ Build Emacs in various ways.
** quick-install-emacs
Install emacs quickly (`incrementally').
Install emacs quickly ("incrementally").
** alloc-colors.c
......
......@@ -13,13 +13,13 @@ Steps to take before starting on the first pretest in any release sequence:
have them available for the duration of the release process.
2. Consider increasing the value of the variable
`customize-changed-options-previous-release' in cus-edit.el to
'customize-changed-options-previous-release' in cus-edit.el to
refer to a newer version of Emacs. (This is probably needed only
when preparing the first pretest for a major Emacs release.)
Commit cus-edit.el if changed.
3. Remove any old pretests from ftp://alpha.gnu.org/gnu/emacs/pretest.
You can use `gnupload --delete' (see below for more gnupload details).
You can use 'gnupload --delete' (see below for more gnupload details).
General steps (for each step, check for possible errors):
......@@ -96,12 +96,12 @@ General steps (for each step, check for possible errors):
If this is the first pretest of a major release, just comparing
with the previous release may overlook many new files. You can try
something like `find . | sort' in a clean repository, and compare the
something like 'find . | sort' in a clean repository, and compare the
results against the new tar contents.
7. tar -xf emacs-NEW.tar; cd emacs-NEW
./configure --prefix=/tmp/emacs && make && make install
Use `script' or M-x compile to save the compilation log in
Use 'script' or M-x compile to save the compilation log in
compile-NEW.log and compare it against an old one. The easiest way
to do that is to visit the old log in Emacs, change the version
number of the old Emacs to __, do the same with the new log and do
......
......@@ -334,7 +334,7 @@ http://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs;tag=calendar
*** To merge bugs:
Eg when bad replies create a bunch of new bugs for the same report.
Bugs must all be in the same state (e.g. same package(s) and severity
-- see `reassign' and `severity' below), but need not have the same
-- see 'reassign' and 'severity' below), but need not have the same
tags (tags are merged). E.g.:
merge 123 124 125 ...
......@@ -343,8 +343,8 @@ Note that merging does not affect titles. In particular, a "retitle"
of merged bugs only affects individual bugs, not all of them.
*** Forcing a merge:
Like `merge', but bugs need not be in the same state. The packages
must still match though (see `reassign' below). The first one listed
Like 'merge', but bugs need not be in the same state. The packages
must still match though (see 'reassign' below). The first one listed
is the master. E.g.:
forcemerge 123 124 125 ...
......@@ -383,7 +383,7 @@ See http://debbugs.gnu.org/Developer#severities for the meanings.
*** To set the owner of a bug:
owner 123 A Hacker <none@example.com>
The shorthand `!' means your own address.
The shorthand '!' means your own address.
*** To remove the owner of a bug:
noowner 123
......@@ -408,7 +408,7 @@ reassign 1234 emacs
Note that reassigning clears the list of found versions, even if the
new packages includes the original one.
** To remove spam from the tracker, move it to the `spam' pseudo-package:
** To remove spam from the tracker, move it to the 'spam' pseudo-package:
reassign 123 spam
(Should not be necessary any more, now that the input is moderated.)
......@@ -468,10 +468,10 @@ time, rather than by increasing bug number
*** When you fix a bug, it can be helpful to put the bug number in the
change log entry, for example:
* foo.el (foofunc): Fix the `foo' case. (Bug#123)
* lisp/menu-bar.el (menu-set-font): Doc fix. (Bug#21303)
Then the relevant bug can be found for easy reference. If it's an
obvious fix (e.g. a typo), there's no need to clutter the log with the
obvious fix (e.g., a typo), there's no need to clutter the log with the
bug number.
Similarly, when you close a bug, it can be helpful to include the
......@@ -480,7 +480,7 @@ can see exactly what the fix was.
*** bug-reference-mode
Activate `bug-reference-mode' in ChangeLogs to get clickable links to
Activate 'bug-reference-mode' in ChangeLogs to get clickable links to
the bug web-pages.
*** Debian stuff
......
......@@ -132,7 +132,7 @@ lib-src/rcs2log # Copyright
Cocoa/Emacs.base/Contents/Info.plist
Cocoa/Emacs.base/Contents/Resources/English.lproj/InfoPlist.strings
GNUstep/Emacs.base/Resources/Info-gnustep.plist
`set-copyright' in admin.el will do all the above.
'set-copyright' in admin.el will do all the above.
aclocal.m4
configure
......
......@@ -13,7 +13,7 @@ daily. This script (which is kept in elpa/admin/update-archive.sh) generates
the content visible at http://elpa.gnu.org/packages.
A new package is released as soon as the "version number" of that package is
changed. So you can use `elpa' to work on a package without fear of releasing
changed. So you can use 'elpa' to work on a package without fear of releasing
those changes prematurely. And once the code is ready, just bump the
version number to make a new release of the package.
......
......@@ -33,7 +33,7 @@ You now have both branches conveniently accessible, and you can do
Fixing bugs
===========
You edit the files in either branch, `M-x vc-dir', and check in your
You edit the files in either branch, 'M-x vc-dir', and check in your
changes. Then you need to push the data to the main repository. This
will usually fail, since somebody else has pushed other changes in the
meantime. To fix this, say
......
......@@ -16,8 +16,8 @@ http://lists.gnu.org/archive/html/hydra-users/2013-08/msg00000.html
* Mail notifications
In addition to the web interface, Hydra can send notifications by
email when the build status of a project changese.g., from
`SUCCEEDED' to `FAILED'. It sends notifications about build status in
email when the build status of a project changes, e.g., from
SUCCEEDED to FAILED. It sends notifications about build status in
Emacs trunk to emacs-buildstatus@gnu.org.
If you want to receive these notifications, please subscribe at
......@@ -25,16 +25,16 @@ http://lists.gnu.org/mailman/listinfo/emacs-buildstatus
* The Emacs jobset consists of the following jobs:
** The `tarball' job
** The 'tarball' job
which gets a checkout from the repository, and does a bootstrap followed
by running make-dist to create a tarball. If this job fails, all the
others will too (because they use the tarball as input).
** The `build' job
** The 'build' job
which starts from the tarball and does a normal build
** The 'coverage' job
does a gcov build and then runs `make check'. Fails if any test fails.
does a gcov build and then runs 'make check'. Fails if any test fails.
* Nix expressions
The recipe for GNU Emacs are available via Git:
......
This diff is collapsed.
......@@ -6,7 +6,7 @@ CHECKLIST FOR ADDING A NEW FILE TO EMACS -*- outline -*-
format, copyright and license notice, etc).
** Make sure the filename does not cause the DOS port any problems (8+3).
Run the `doschk' program like this:
Run the 'doschk' program like this:
find /path/to/emacs -print | doschk
......
......@@ -73,7 +73,7 @@ removes a file, then remove the corresponding files by hand.
You may see conflicts in autoload md5sums in comments. Strictly
speaking, the right thing to do is merge everything else, resolve the
conflict by choosing either the master or branch version, then run
`make -C lisp autoloads' to update the md5sums to the correct master
'make -C lisp autoloads' to update the md5sums to the correct master
value before committing.
* Re-adding a file that has been removed from the repository
......@@ -96,12 +96,12 @@ which is often more appropriate.
* Undoing a commit (uncommitting)
If you have not pushed the commit, you may be able to use `git reset
If you have not pushed the commit, you may be able to use 'git reset
--hard' with a hash argument to revert the your local repo copy to the
pre-commit state.
If you have pushed commit, resetting will be ineffective because it
will only vanish the commit in your local copy. Instead, use `git
will only vanish the commit in your local copy. Instead, use 'git
revert', giving it the commit ID as argument. This will create a
new commit that backs out the change. Then push that.
......@@ -115,7 +115,7 @@ again.
* Bisecting
This is a semi-automated way to find the revision that introduced a bug.
Browse `git help bisect' for technical instructions.
Browse 'git help bisect' for technical instructions.
* Maintaining ChangeLog history
......
......@@ -97,11 +97,11 @@ regard to completeness.
* iso-2022 charsets get unified on i/o.
With the change on 2003-01-06, decoding routines put `charset'
property to decoded text, and iso-2022 encoder pay attention
With the change on 2003-01-06, decoding routines put the 'charset'
property onto decoded text, and iso-2022 encoder pay attention
to it. Thus, for instance, reading and writing by
iso-2022-7bit preserve the original designation sequences.
The property name `preferred-charset' may be better?
The property name 'preferred-charset' may be better?
We may have to utilize this property to decide a font.
......
......@@ -40,7 +40,7 @@ VERBOSE=''
me="`basename $0`"
# Install commands (if the user specifies the `--verbose' option, it is
# Install commands (if the user specifies the '--verbose' option, it is
# passed to these commands, so that feature only works if these commands
# implement it too)
LINK='cp -lf'
......@@ -58,7 +58,7 @@ unset LANG LC_ALL LC_MESSAGES
# Some messages
USAGE="Usage: $me [OPTION...] BUILD_TREE [PREFIX]"
TRY="Try "\`"$me --help' for more information."
TRY="Try '$me --help' for more information."
# Parse command-line options
while :; do
......@@ -93,7 +93,7 @@ Install emacs quickly
--help display this help and exit
--version output version information and exit
$me install emacs \`incrementally,' that is, it will
$me install emacs "incrementally", that is, it will
install only those files that have changed since the last time it was
invoked, and remove any obsolete files from the installation
directories. It also uses hard-links into the source and build trees to
......@@ -104,9 +104,9 @@ and build directories reside.
Optionally, $me can also remove old versions of
automatically generated files that are version-specific (such as the
versioned emacs executables in the \`src' directory).
The latter action is called \`pruning,' and
can be enabled using the \`-p' or \`--prune' options.
versioned emacs executables in the 'src' directory).
The latter action is called "pruning", and
can be enabled using the '-p' or '--prune' options.
EOF
exit 0
;;
......@@ -124,7 +124,7 @@ EOF
set -- `echo $FIRST | sed 's/-\(.\)\(.*\)/-\1 -\2/'` "$@"
;;
-*)
echo 1>&2 "$me: unrecognized option "\`"$1'"
echo 1>&2 "$me: unrecognized option '$1'"
echo 1>&2 "$TRY"
exit 1
;;
......
......@@ -12,13 +12,13 @@ CXTERM-DIC:
This directory contains source dictionaries (TIT format) for Chinese
input method distributed with cxterm (Chinese version xterm). These
dictionaries are automatically converted to Quail packages (Emacs Lisp
source files) by `make'.
source files) by 'make'.
MISC-DIC:
This directory contains various dictionaries for Chinese input
methods. These dictionaries are automatically converted to Quail
packages (Emacs Lisp source files) by `make'.
packages (Emacs Lisp source files) by 'make'.
SKK-DIC:
......
......@@ -414,7 +414,7 @@ sort $SORT_K_OPTIONS </dev/null 2>/dev/null || SORT_K_OPTIONS='+2 -4r +4 +0'
# Get the full name of each author the logs mention, and set initialize_fullname
# to awk code that initializes the `fullname' awk associative array.
# to awk code that initializes the 'fullname' awk associative array.
# Warning: foreign authors (i.e. not known in the passwd file) are mishandled;
# you have to fix the resulting output by hand.
......@@ -546,8 +546,8 @@ esac
# Function to print a single log line.
# We don't use awk functions, to stay compatible with old awk versions.
# `Log' is the log message.
# `files' contains the affected files.
# 'Log' is the log message.
# 'files' contains the affected files.
printlogline='{
# Following the GNU coding standards, rewrite
......@@ -587,7 +587,7 @@ printlogline='{
}
}'
# Pattern to match the `revision' line of rlog output.
# Pattern to match the 'revision' line of rlog output.
rlog_revision_pattern='^revision [0-9]+\.[0-9]+(\.[0-9]+\.[0-9]+)*(['"$tab"' ]+locked by: [^'"$tab"' $,.0-9:;@]*[^'"$tab"' $,:;@][^'"$tab"' $,.0-9:;@]*;)?['"$tab"' ]*$'
case $hostname in
......
......@@ -7,22 +7,22 @@ terminal types.
When Emacs opens a new terminal, it checks the TERM environment variable
to see what type of terminal the user is running on. (If there is an entry
for TERM in the `term-file-aliases' variable, Emacs uses the associated value
for TERM in the 'term-file-aliases' variable, Emacs uses the associated value
in place of TERM in the following.) Emacs searches for an elisp file named
"term/${TERM}.el", and if one exists, loads it. If Emacs finds no
suitable file, then it strips the last hyphen and what follows it from TERM,
and tries again. If that still doesn't yield a file, then the previous hyphen
is stripped, and so on until all hyphens are gone. For example, if the
terminal type is `aaa-48-foo', Emacs will try first `term/aaa-48-foo.el', then
`term/aaa-48.el' and finally `term/aaa.el'. Emacs stops searching at the
terminal type is 'aaa-48-foo', Emacs will try first 'term/aaa-48-foo.el', then
'term/aaa-48.el' and finally 'term/aaa.el'. Emacs stops searching at the
first file found, and will not load more than one file for any terminal. Note
that it is not an error if Emacs is unable to find a terminal initialization
file; in that case, it will simply proceed with the next step without loading
any files.
Once the file has been loaded (or the search failed), Emacs tries to call a
function named `terminal-init-TERMINALNAME' (eg `terminal-init-aaa-48' for the
`aaa-48' terminal) in order to initialize the terminal. Once again, if the
function named 'terminal-init-TERMINALNAME' (eg 'terminal-init-aaa-48' for the
'aaa-48' terminal) in order to initialize the terminal. Once again, if the
function is not found, Emacs strips the last component of the name and tries
again using the shorter name. This search is independent of the previous file
search, so that you can have terminal initialization functions for a family of
......@@ -40,7 +40,7 @@ declaration. Simply loading the file should not have any side effect.
given terminal, when the first frame is created on it. The function is not
called for subsequent frames on the same terminal. Therefore, terminal-init-*
functions should only modify terminal-local variables (such as
`local-function-key-map') and terminal parameters. For example, it is not
'local-function-key-map') and terminal parameters. For example, it is not
correct to modify frame parameters, since the modifications will only be
applied for the first frame opened on the terminal.
......@@ -51,7 +51,7 @@ mind.
First, about keycap names. Your terminal package can create any keycap
cookies it likes, but there are good reasons to stick to the set recognized by
the X-windows code whenever possible. The key symbols recognized by Emacs
are listed in src/term.c; look for the string `keys' in that file.
are listed in src/term.c; look for the string 'keys' in that file.
For one thing, it means that you'll have the same Emacs key bindings on in
terminal mode as on an X console. If there are differences, you can bet
......@@ -61,7 +61,7 @@ they'll frustrate you after you've forgotten about them.
about. It tries to bind many of them to useful things at startup, before your
.emacs is read (so you can override them). In some ways, the X keysym standard
is a admittedly poor one; it's incomplete, and not well matched to the set of
`virtual keys' that UNIX terminfo(3) provides. But, trust us, the alternatives
'virtual keys' that UNIX terminfo(3) provides. But, trust us, the alternatives
were worse.
This doesn't mean that if your terminal has a "Cokebottle" key you shouldn't
......@@ -70,7 +70,7 @@ that set, try to pattern them on the standard terminfo variable names for
clarity; also, for a fighting chance that your binding may be useful to someone
else someday.
For example, if your terminal has a `find' key, observe that terminfo
For example, if your terminal has a 'find' key, observe that terminfo
supports a key_find capability and call your cookie [find].
Here is a complete list, with corresponding X keysyms.
......@@ -184,14 +184,14 @@ key_f36 FQ function key 36
key_f64 k1 function key 64
(1) The terminfo documentation says this may be the 'insert character' or
`enter insert mode' key. Accordingly, key_ic is mapped to the `insertchar'
keysym if there is also a key_dc key; otherwise it's mapped to `insert'.
The presumption is that keyboards with `insert character' keys usually
have `delete character' keys paired with them.
'enter insert mode' key. Accordingly, key_ic is mapped to the 'insertchar'
keysym if there is also a key_dc key; otherwise it's mapped to 'insert'.
The presumption is that keyboards with 'insert character' keys usually
have 'delete character' keys paired with them.
(2) If there is no key_next key but there is a key_npage key, key_npage
will be bound to the `next' keysym. If there is no key_previous key but
there is a key_ppage key, key_ppage will be bound to the `previous' keysym.
will be bound to the 'next' keysym. If there is no key_previous key but
there is a key_ppage key, key_ppage will be bound to the 'previous' keysym.
(3) Sorry, these are not exact but they're the best we can do.
......@@ -242,7 +242,7 @@ the setup code to bind anything else.
If your terminal's arrow key sequences are so funky that they conflict with
normal Emacs key bindings, the package should set up a function called
(enable-foo-arrow-keys), where `foo' becomes the terminal name, and leave
(enable-foo-arrow-keys), where 'foo' becomes the terminal name, and leave
it up to the user's .emacs file whether to call it.
Before writing a terminal-support package, it's a good idea to read the
......
......@@ -4,16 +4,15 @@ See the end of the file for license conditions.
This directory contains the source files for the C component of GNU Emacs.
Nothing in this directory is needed for using Emacs once it is built
and installed, if the dumped Emacs (on Unix systems) is copied elsewhere.
and installed, if the dumped Emacs is copied elsewhere.
See the files ../README and then ../INSTALL for installation instructions.
Under GNU and Unix systems, the file `Makefile.in' is used as a
template by the script `../configure' to produce `Makefile'. This
is the file which actually controls the compilation of Emacs.
All of this should work transparently to the user; you should only
need to run `../configure', and then type `make'.
The file 'Makefile.in' is used as a template by the script
'../configure' to produce 'Makefile'. This is the file which actually
controls the compilation of Emacs C source files. All of this should
work transparently; you should only need to change to the parent
directory, run './configure', and then run 'make'.
This file is part of GNU Emacs.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment