From: "Jim Blandy" <jimb@red-bean.com>
To: "Emacs Development" <emacs-devel@gnu.org>
Subject: emacs manual patch: refer to File Variables from Numbered Backups.
Date: Thu, 11 Sep 2008 12:13:44 -0700 [thread overview]
Message-ID: <8f2776cb0809111213v66a6203dv1ecf28590e7a03a5@mail.gmail.com> (raw)
A user reading about backup policies will often have a particular file
in mind whose backup policy he would like to change.
The fact that Rmail mode uses this variable seems out of place.
Perhaps a reader who has noticed Rmail's behavior with regards to
backup files could relate that to the effect of this variable, but
readers unfamiliar with Rmail won't.
* emacs.texi (Numbered Backups): reference File Variables, as well.
Remove discussion of Rmail's implementation.
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -591,9 +591,9 @@ The usual way to set this variable is gl
The usual way to set this variable is globally, through your
@file{.emacs} file or the customization buffer. However, you can set
@code{version-control} locally in an individual buffer to control the
-making of backups for that buffer's file. For example, Rmail mode
-locally sets @code{version-control} to @code{never} to make sure that
-there is only one backup for an Rmail file. @xref{Locals}.
+making of backups for that buffer's file (@pxref{Locals}). You can
+have Emacs set @code{version-control} locally whenever you visit a
+given file (@pxref{File Variables}).
@cindex @env{VERSION_CONTROL} environment variable
If you set the environment variable @env{VERSION_CONTROL}, to tell
next reply other threads:[~2008-09-11 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 19:13 Jim Blandy [this message]
2008-09-20 19:57 ` emacs manual patch: refer to File Variables from Numbered Backups Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f2776cb0809111213v66a6203dv1ecf28590e7a03a5@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).