From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: a big .newsrc.eld is *fragile*
Date: 19 Feb 1999 20:33:21 +0100 [thread overview]
Message-ID: <87ogmqgpdq.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Colin Rafferty's message of "19 Feb 1999 12:03:12 -0500"
Colin Rafferty <craffert@ms.com> writes:
> > I switched that off in 1993 ... and I rather liked that behaviour
> > so I stuck with it, even after PC-NFS stopped being an issue.
>
> You are a brave man.
I, for one, can't stand backup files. I turn them off in every editor
that I use. I have nothing against auto-saving, though -- it's just
the buggers with tidles at the end of the name that get on my nerves.
next prev parent reply other threads:[~1999-02-19 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 14:00 Steinar Bang
1999-02-19 16:16 ` Lars Magne Ingebrigtsen
1999-02-19 16:37 ` Steinar Bang
1999-02-19 17:03 ` Colin Rafferty
1999-02-19 19:10 ` Colin Rafferty
1999-02-19 19:33 ` Hrvoje Niksic [this message]
1999-02-19 17:04 ` Karl Kleinpaste
1999-02-19 17:22 ` 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=87ogmqgpdq.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).