From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: saving nnfolders
Date: 19 Mar 2001 14:12:46 -0500 [thread overview]
Message-ID: <87vgp5y3m9.fsf@home.com> (raw)
In-Reply-To: <87r8zxpdy6.fsf@home.com> (Dmitry Yaitskov's message of "16 Mar 2001 17:05:21 -0500")
Sorry to followup to my own post - but... I wonder why nobody replied
- is it because I'm asking a completely stupid question and missing
something bloody obvious? The problem is (or at least seems) serious
enough to me (esp the non-saving of nnfolders - if my emacs crashes -
which happens - I will get asked about restoring the "dribble" buffer
but I have no idea how if at all I'll get asked about the nnfolder
autosaved buffers - will I?), and I'm tempted to try and hack
something up myself to fix that - but before I do - maybe I'm missing
something? Gnus gurus, what do you say? Thx.
Dmitry Yaitskov <dimas@home.com> wrote:
> Hi,
>
> I have (finally :) succeeded in setting up the expired articles to be
> moved to nnfolders. What I don't like with the way it works now is,
> after this expiration process I end up with all those updated nnfolder
> groups as changed (and unsaved) buffers in my XEmacs. I'd like to
>
> 1. Have nnfolders save themselves each time a message is added (disk
> access if fast; losing articles - or having to restore them from
> auto saves - is bad).
>
> 2. Have these nnfolder buffers delete themselves at some point
> auto-magically (or perhaps just have them delete themselves after
> each article is added, after saving).
>
> Any ideas or pointers to the relevant places in the docs would be
> appreciated. Thanks.
--
Cheers,
-Dima.
next prev parent reply other threads:[~2001-03-19 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 22:05 Dmitry Yaitskov
2001-03-19 19:12 ` Dmitry Yaitskov [this message]
2001-03-19 19:35 ` Alan Shutko
2001-03-19 23:46 ` Dmitry Yaitskov
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=87vgp5y3m9.fsf@home.com \
--to=dimas@home.com \
/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).