Gnus development mailing list
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: ding@gnus.org
Subject: Re: Exporting/archiving nnml group?
Date: Tue, 13 Nov 2007 01:19:13 +0100	[thread overview]
Message-ID: <87pryfj8u6.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <v93avb8s36.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 12 Nov 2007 15\:18\:53 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> 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...

Ah, OK, it wasn't completely clear which part exactly you were
pointing to.

>
>>>> 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.
> `----

Oh, well, it's easy tunable after all. I see another line in my .gnus ;)

Thank you!

And in the end, pardon me from being ignorant. I really do plan to
reread the manual and relearn some stuff I've managed to forget
through years. It's just that there's so little free time for quality
stuff like that. :(

And that is also the exact reason why I'm grateful to you and
everybody else with more experience on this list that is actively
helping people (like me). Gnus can be overhelming...

Best regards,
-- 
Zlatko
happy Gnus user for a decade (slightly lost at times :))



  reply	other threads:[~2007-11-13  0:19 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
2007-11-13  0:19         ` Zlatko Calusic [this message]
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=87pryfj8u6.fsf@atlas.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --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).