Gnus development mailing list
 help / color / mirror / Atom feed
From: Aharon Schkolnik <aharon@health.gov.il>
Cc: ding@gnus.org
Subject: Re: Please help me create a nnbabyl group
Date: 18 Jul 1997 10:52:13 +0300	[thread overview]
Message-ID: <nsoxc6bma.fsf@healdb.matat.health.gov.il> (raw)
In-Reply-To: Kai Grossjohann's message of 17 Jul 1997 13:57:15 +0200

>>>>> "Kai" == Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:

>>>>> Aharon Schkolnik writes:
    Aharon> I save articles using gnus-summary-save-in-rmail (I would
    Aharon> be willing to change to gnus-summary-save-in-mail if that
    Aharon> would help anything). This generates a babyl format file
    Aharon> (one per group). Later, I want to go back, look at these
    Aharon> saved messages, and delete some of them.

    Kai> Create nnfolder groups.  This is a one-file-per-group,
    Kai> many-messages-per-file, backend, and uses Unix mbox format
    Kai> for the files.

Let's see if I've got this straight:

1. I shouldn't use babyl format to save messages because there is no
backend which will read the resulting file (one file per group) and
allow message deletion (erasing from the disk - not just marking).

2. If I switch to gnus-summary-save-in-mail, I will generate mbox
format files - one per group. I can then use nnfolder to read the
resulting files, and I will be able to delete messages.


    Kai> Use "B c" to copy a message from any group (nntp groups work,
    Kai> too) into such an nnfolder group.  ("B m" moves the message,
    Kai> so it works for writable groups only.)


3. In order to transfer the messages which I have saved in babyl
format, I need to create nndoc groups, use B c to move the messages to
nnfolder groups, delete the old babyl files using the shell - not Gnus.


    Kai> But then, if you're using "B c" there is no restriction on
    Kai> the backend of the target group, so you can use nnml and
    Kai> nnmh, too.


Yeah, but my main concern is how best to save messages from gnus
(gnus-summary-save-in-*) and then to be able to delete the saved
messages - for that, I understand, the best (only ?) choice is
nnfolder.






If I understand everything correctly, it would seem strange that there
is a backend which can delete from mbox format - one group per file,
but there is no backend which can delete from babyl format - one group
per file. If this is true, is there some good reason for it ?




Thanks a lot !




-- 
  The day is short, and the work is great,     |   Aharon Schkolnik
  and the laborers are lazy, and the reward    |   Aharon@Health.Gov.IL
  is great, and the Master of the house is     |
  impatient. - Ethics Of The Fathers Ch. 2     |


  reply	other threads:[~1997-07-18  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-07-14 14:09 Aharon Schkolnik
1997-07-16 18:36 ` Lars Magne Ingebrigtsen
1997-07-17  5:29   ` Aharon Schkolnik
1997-07-17 11:57     ` Kai Grossjohann
1997-07-18  7:52       ` Aharon Schkolnik [this message]
1997-07-18  8:08         ` Kai Grossjohann
1997-07-18  8:37           ` Aharon Schkolnik

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=nsoxc6bma.fsf@healdb.matat.health.gov.il \
    --to=aharon@health.gov.il \
    --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).