From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56291@debbugs.gnu.org, larsi@gnus.org
Subject: bug#56291: 29.0.50; version-control versus gnus-backup-startup-file
Date: Wed, 29 Jun 2022 09:17:35 -0700 [thread overview]
Message-ID: <10477.1656519455@alto> (raw)
In-Reply-To: Your message of "Wed, 29 Jun 2022 19:05:38 +0300." <83zghv5ub1.fsf@gnu.org>
Eli Zaretskii wrote:
> > Cc: 56291@debbugs.gnu.org
> > From: Mike Kupfer <mkupfer@alum.berkeley.edu>
> > Date: Wed, 29 Jun 2022 07:38:28 -0700
> >
> > Fair enough. How about
> >
> > The usual way to set this variable is globally, through your init
> > file or the customization buffer. However, you can set
> > ‘version-control’ locally in an individual buffer to control the
> > making of backups for that buffer’s file (*note Locals::). Some
> > packages, such as Rmail, override the global setting of
> > ‘version-control’ this way. You can also have Emacs set
> > ‘version-control’ locally whenever you visit a given file (*note File
> > Variables::).
> >
> > ?
>
> The point of the example is to illustrate the local setting of the
> variable, so talking about packages that set the global value misses
> the point, and shouldn't be there. If Rmail is a bad example, then we
> should find a better one, and mention only those.
Okay, I guess "override the global setting" is too confusing. Rmail
only sets it locally. Does this work better:
The usual way to set this variable is globally, through your init
file or the customization buffer. However, you can set
‘version-control’ locally in an individual buffer to control the
making of backups for that buffer’s file (*note Locals::). Some
packages, such as Rmail, do this. You can also have Emacs set
‘version-control’ locally whenever you visit a given file (*note
File Variables::).
?
mike
next prev parent reply other threads:[~2022-06-29 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:00 bug#56291: 29.0.50; version-control versus gnus-backup-startup-file Mike Kupfer
2022-06-29 10:22 ` Lars Ingebrigtsen
2022-06-29 14:38 ` Mike Kupfer
2022-06-29 14:44 ` Mike Kupfer
2022-06-29 16:05 ` Eli Zaretskii
2022-06-29 16:17 ` Mike Kupfer [this message]
2022-06-29 17:21 ` Eli Zaretskii
2022-06-30 9:21 ` Lars Ingebrigtsen
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=10477.1656519455@alto \
--to=mkupfer@alum.berkeley.edu \
--cc=56291@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).