Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: various nnml questions, many about cross-posted mail messages
Date: 10 Jun 1996 11:16:42 +0200	[thread overview]
Message-ID: <rjg284uih1.fsf@kleene.dina.kvl.dk> (raw)
In-Reply-To: jbw@cs.bu.edu's message of Fri, 7 Jun 1996 19:16:30 -0400

>>>>> "JW" == Joe Wells <jbw@cs.bu.edu> writes:

JW> 1. An article is cross-posted to two mail groups:
   
JW>    [ a) Gnus doesn't update xref in other copies when one is deleted. ]

JW> 3. An article is cross-posted to two mail groups:

JW>    [ b) Gnus doesn't update other copies when one is moved.  
JW>      This breaks the crossposting.  c) There is no way to add to a
JW>      crosspost list. ]

The first isn't really a problem since news works this way.  However,
I use crossposting of mail extensively, it was the deciding feature
which made me switch to Gnus.  I often move mail around after they
have been split, and the fact that it breaks crossposting is a big
problem, i.e. it wastes lost of disk space.  So I really would like to
see `B m' and `B c' be crosspost aware.  I.e. `B m' should not break
the crosspost list, and `B c' should just add a new entry to the xref
list (and use a hard link).

JW> 2. In the Summary buffer, the "B m" command asks for a target group.  I
JW>    type in a name.  It complains that the group doesn't exist.  (The group
JW>    does indeed not exist yet.  I don't care.  I want the message in that
JW>    group.)

I'd like a prompt here:  Group does not exist, create it (yes/no)?

It is a good candidate for a prompt, since it is relatively rare.

JW> 4. Question: How do people keep track of whether they have edited a
JW>    message or forwarded it?

JW> 5. An article is cross-posted to multiple mail groups:

JW>   [ Propagate secondary marks to crossposted groups ]

JW> 6. I am importing some mailboxes from VM.  Question: How do I arrange that
JW>    articles to which I have replied in VM get the "A" mark?

I think all three can be solved, once the Gnus backend protocol learns
how to store marks in the server.   This is needed for proper IMAP
support, but it should also allow gnus to maintain the `Status:',
`X-VM-v5-Attribute:' headers, and the BABYL labels.  This should allow
you to do the above.


  parent reply	other threads:[~1996-06-10  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-07 23:16 Joe Wells
1996-06-09  4:06 ` Lars Magne Ingebrigtsen
1996-06-09 10:09   ` Darren/Torin/Who Ever...
1996-06-09 17:02     ` Lars Magne Ingebrigtsen
1996-06-10  2:42       ` Mark Eichin
1996-06-10 20:30         ` Sten Drescher
1996-06-09 19:57     ` Hallvard B Furuseth
1996-06-10  3:39   ` Joe Wells
1996-06-20  8:32     ` Lars Magne Ingebrigtsen
1996-06-10  9:16 ` Per Abrahamsen [this message]
1996-06-10 19:46   ` Lars Magne Ingebrigtsen
1996-06-12  3:53 ` setting marks for imported mailboxes, adding new mark types Joe Wells
1996-06-12 18:03   ` Lars Magne Ingebrigtsen
1996-06-14  1:45   ` Joe Wells

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=rjg284uih1.fsf@kleene.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).