Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Exporting/archiving nnml group?
Date: Mon, 12 Nov 2007 15:18:53 +0100	[thread overview]
Message-ID: <v93avb8s36.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87ejevlg3n.fsf@atlas.iskon.hr>

On Mon, Nov 12 2007, Zlatko Calusic wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> On Tue, Nov 06 2007, Tassilo Horn wrote:
[...]
>> This part is not necessary.
>
> Maybe (and it looks simpler), 

I tried to expres that this part (gnus-group-make-group) of Tassilo's
suggestion is not necessary.  I think you can simply...

>>> enter the nnml group, mark all messages with `M P b'
>>> and copy them to the mbox with `B c nnmbox:name RET'.

> but using 'O m' revealed 2 problems.
>
> First, it asked me to confirm the saving location for each and every
> mail it was about to append to mailbox file. Press RETURN 1879 times?
> No, thank you! :) I don't know how to stop that from happenining.

How about reading the info node that I have cited?

,----[ (info "(gnus)Saving Articles") ]
| If you save bunches of articles using these
| functions, you might get tired of being prompted for files to save each
| and every article in.  The prompting action is controlled by the
| `gnus-prompt-before-saving' variable, which is `always' by default,
| giving you that excessive prompting action you know and loathe.  If you
| set this variable to `t' instead, you'll be prompted just once for each
| series of articles you save.  If you like to really have Gnus do all
| your thinking for you, you can even set this variable to `nil', which
| means that you will never be prompted for files to save articles in.
| Gnus will simply save all the articles in the default files.
`----

> Second thing (much less problematic) it marks every article as
> saved. This might not be what people want when they're just making a
> backup copy.

Hm, I don't think we have a user interface to (un)set secondary marks.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2007-11-12 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 12:17 Zlatko Calusic
2007-11-06 14:56 ` Tassilo Horn
2007-11-06 21:15   ` Reiner Steib
2007-11-12 13:59     ` Zlatko Calusic
2007-11-12 14:18       ` Reiner Steib [this message]
2007-11-13  0:19         ` Zlatko Calusic
2007-11-12 13:54   ` Zlatko Calusic

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=v93avb8s36.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).