From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: losing nnml .overview files
Date: 20 Feb 1996 00:30:34 +0100 [thread overview]
Message-ID: <w8sn36e7v1h.fsf@eistla.ifi.uio.no> (raw)
In-Reply-To: gsstark@MIT.EDU's message of 19 Feb 1996 16:42:35 -0500
gsstark@MIT.EDU (Greg Stark) writes:
> hmm, the problem seems to have gone away, i think the only thing that changed
> was my fixing a hook that was globally setting auto-save-visited-file-name to
> T. Is it possible something is trying to clean up by removing any auto-save
> files? I can't find any place in the code where such a thing might be
> happening, but maybe you'll know what's going on.
No, I don't see why that should affect anything, really. Hmn. nnml
uses `find-file-noselect' to load the .overview files, and
`write-region' to save those files. Is that a bad idea?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1996-02-19 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-15 17:39 Greg Stark
1996-02-15 21:00 ` Lars Magne Ingebrigtsen
1996-02-19 21:42 ` Greg Stark
1996-02-19 23:30 ` 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=w8sn36e7v1h.fsf@eistla.ifi.uio.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).