Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: gnus should backup .newsrc.eld
Date: Mon, 15 Dec 2008 20:40:10 +0100	[thread overview]
Message-ID: <87ljuh8bxh.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87hc55s6a9.fsf@jidanni.org> (jidanni@jidanni.org's message of "Tue, 16 Dec 2008 01:21:34 +0800")

On Mon, Dec 15 2008, jidanni@jidanni.org wrote:

> Oh, every body missed (info "(gnus)Startup Files") "If you want
> version control for this file, set `gnus-backup-startup-file'."
> Well, maybe it should be t by default.

Whether backups of ~/.newsrc.eld are created is controlled by
`make-backup-files'.  `gnus-backup-startup-file' just controls whether
Gnus makes numerical backups, like `version-control' does for other
Emacs files.  In other words, `gnus-backup-startup-file' overrides
`version-control' for .newsrc.eld, nothing more.

So with the defaults (make-backup-files == t, gnus-backup-startup-file
== never) you get a single backup file for .newsrc.eld (see the doc
string of `version-control').  One could argue that
`gnus-backup-startup-file' should default to the value of
`version-control', but as .newsrc.eld tends to become large, it might
be a good idea to create only a single backup.  But defaulting to t
(i.e., make numeric backup versions unconditionally) — independent
from the value of `version-control' — is a bad idea, IMHO.

For now, I fixed the doc string of `gnus-backup-startup-file' which
was misleading:

--8<---------------cut here---------------start------------->8---
--- gnus-start.el	4 Sep 2008 06:04:04 -0000	7.67
+++ gnus-start.el	15 Dec 2008 19:37:27 -0000
@@ -50,7 +50,7 @@
   :type 'file)
 
 (defcustom gnus-backup-startup-file 'never
-  "Whether to create backup files.
+  "Control use of version numbers for backups of `gnus-startup-file'.
 This variable takes the same values as the `version-control'
 variable."
   :version "22.1"
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2008-12-15 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12  1:15 jidanni
2008-12-12  3:04 ` Dave Goldberg
2008-12-12 11:54   ` Steinar Bang
2008-12-12 18:15     ` Andreas Schwab
2008-12-15 17:21       ` jidanni
2008-12-15 19:40         ` Reiner Steib [this message]
2008-12-15 23:34         ` Steinar Bang
2008-12-16 17:58           ` jidanni
2008-12-12  3:17 ` Katsumi Yamaoka
2008-12-12  5:17   ` jidanni
2008-12-12  6:46     ` Tassilo Horn
2008-12-12 11:57   ` Steinar Bang

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ljuh8bxh.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@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.
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 NNTP newsgroup(s).