From: Dan Mills <dm@cs.duke.edu>
Cc: ding@gnus.org
Subject: Re: ~/#.newsrc-dribble# file
Date: 11 Dec 1999 09:35:12 -0500 [thread overview]
Message-ID: <87u2lpeean.fsf@majikthise.adsl.duke.edu> (raw)
In-Reply-To: jw@nimrod.no's message of "01 Dec 1999 09:16:21 +0100"
jw@nimrod.no (Jørgen Wahlberg) writes:
> [ Dan Mills <dm@cs.duke.edu> ]
>
> | Hello,
> |
> | I always seem to have a ~/#.newsrc-dribble# file hanging around, in
> | addition to ~/.newsrc-dribble and ~/.newsrc-dribble~. Is there any
> | way to make it not appear? Or if it's necessary to have (or
> | recommended), then could I have it be named something else (with a
> | leading ".")?
>
> Isn't that the auto-save file for .newsrc-dribble? I believe you
> would like to have that file when recovering after a crash.
I thought that too. But isn't the ~ file enough? I've only had it
crash a couple of times.. is it worth having two backups? Also- could
I gell gnus (or emacs?) to add a '.' in front of it? I wouldn't mind
having 20 backups, as long as I didn't have to see them every time I
do an 'ls'.
-Dan
--
Dan Mills, Duke Class of 2000 -o)
email: dm(at)cs(dot)duke(dot)edu /\\
-----------------------------------\ _\_v
Damn Sill.. Sand Mill? All Minds! |_____
next prev parent reply other threads:[~1999-12-11 14:35 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 [this message]
1999-12-01 10:57 ` Toby Speight
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=87u2lpeean.fsf@majikthise.adsl.duke.edu \
--to=dm@cs.duke.edu \
--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).