Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Weird problems in Drafts.
Date: 05 Jul 1999 06:46:50 +0200	[thread overview]
Message-ID: <m3r9mn9005.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "04 Jul 1999 21:48:13 +0200"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Hm.  find-backup-file-name seems to do something hardwired when
> version-control is non-nil, and calls make-backup-file-name otherwise.

  -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76
  -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76.~1~

(find-backup-file-name "~/News/drafts/drafts/76")
=> ("~/News/drafts/drafts/76.~2~")

So it seems to do the reverse thing -- it suggests a new backup file
name; it doesn't say what the current backup file names to a given
file are.

----------
(find-backup-file-name FN)

Documentation:
Find a file name for a backup file, and suggestions for deletions.
Value is a list whose car is the name for the backup file
 and whose cdr is a list of old versions to consider deleting now.
If the value is nil, don't make a backup.
----------

But the "old versions" thing sounds good, but how does one control
what "old versions" are?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1999-07-05  4:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-13 17:22 Rui Zhu
1999-07-03  8:43 ` Lars Magne Ingebrigtsen
1999-07-03 13:09   ` Rui Zhu
1999-07-04  6:14     ` Lars Magne Ingebrigtsen
1999-07-04 19:48       ` Kai.Grossjohann
1999-07-05  4:46         ` Lars Magne Ingebrigtsen [this message]
1999-07-05  9:43           ` Kai.Grossjohann
1999-07-06  4:16             ` Lars Magne Ingebrigtsen
1999-07-05  9:44           ` Kai.Grossjohann

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=m3r9mn9005.fsf@quimbies.gnus.org \
    --to=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.
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).