From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: ~/#.newsrc-dribble# file
Date: 01 Dec 1999 10:57:31 +0000 [thread overview]
Message-ID: <uyabf0vz8.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Dan Mills's message of "11 Dec 1999 09:35:12 -0500"
Dan> Dan Mills <URL:mailto:dm@cs.duke.edu>
0> In article <87u2lpeean.fsf@majikthise.adsl.duke.edu>, Dan wrote:
Dan> But isn't the ~ file enough? I've only had it crash a couple of
Dan> times.. is it worth having two backups? Also- could I gell gnus
Dan> (or emacs?) to add a '.' in front of it? I wouldn't mind having
Dan> 20 backups, as long as I didn't have to see them every time I do
Dan> an 'ls'.
That's a general emacs question, not specific to ding.
(apropos "auto-?save")
In particular, look at `make-auto-save-file-name'. You should be able
to advice it (in your .emacs) so that it begins with a dot.
next prev parent reply other threads:[~1999-12-01 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 23:34 Dan Mills
1999-12-01 8:16 ` Jørgen Wahlberg
1999-12-11 14:35 ` Dan Mills
1999-12-01 10:57 ` Toby Speight [this message]
1999-12-01 13:51 ` Taso N. Devetzis
1999-12-01 22:28 ` Lars Magne Ingebrigtsen
1999-12-12 10:02 ` Dan Mills
1999-12-02 4:42 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uyabf0vz8.fsf@lanber.cam.citrix.com \
--to=toby.speight@streapadair.freeserve.co.uk \
/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).