Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Overwriting files when saving instead of appending to a file?
Date: 24 Sep 1996 20:18:15 +0200	[thread overview]
Message-ID: <x6pw3bbwuw.fsf@eyesore.no> (raw)
In-Reply-To: kees_de_bruin@tasking.nl's message of 24 Sep 1996 09:00:06 +0200

kees_de_bruin@tasking.nl (Kees de Bruin) writes:

> When saving articles that use the `Archive-Name' to determine the name of
> the file used to save to, I would like to be able to overwrite any existing
> files before the current article is saved. This has its use for FAQ files
> where it is used most of the time. Is there a way of doing this or should I
> write my own save function?

I think you have to write your own save function to do this.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


      reply	other threads:[~1996-09-24 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-24  7:00 Kees de Bruin
1996-09-24 18:18 ` Lars Magne Ingebrigtsen [this message]

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=x6pw3bbwuw.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).