Gnus development mailing list
 help / color / mirror / Atom feed
From: Hannu Koivisto <azure@iki.fi>
Subject: How exactly does Gnus move mail?  77h for moving feels a bit slow
Date: 07 Dec 1999 18:01:50 +0200	[thread overview]
Message-ID: <87vh6apwnl.fsf@senstation.vvf.fi> (raw)

Greetings,

I wanted to move some of the unread articles in one of my nnml
folders to a new folder for later reading (thus separating them
clearly from the new ones), but after I marked them and hit `B m',
giving a new group name (that was created), Emacs memory
consumption raised by 10Mb and I could literally see each article
being moved.  Move of one article took ten (10) seconds, which IMHO
is a bit too much.  I calculated that moving all the marked
articles (there was about 28000 of them) would have taken 77 hours
-- not good, so I terminated the operation.

Could I move them outside Gnus?  Something like getting the list of
filenames of marked articles and then moving them simply with `mv'
and re-generating neccessary status information so that Gnus knows
the new picture of things.  Or something.  Possible?

-- 
Hannu


                 reply	other threads:[~1999-12-07 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87vh6apwnl.fsf@senstation.vvf.fi \
    --to=azure@iki.fi \
    /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).