Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: various nnml questions, many about cross-posted mail messages
Date: 20 Jun 1996 10:32:22 +0200	[thread overview]
Message-ID: <x6n31yswo9.fsf@eyesore.no> (raw)
In-Reply-To: jbw@cs.bu.edu's message of Sun, 9 Jun 1996 23:39:21 -0400

jbw@cs.bu.edu (Joe Wells) writes:

> I also believe that a newsreader, to the greatest extent practically
> possible, should treat a message cross posted to several groups as a
> single entity.  When I receive a message that gets put in groups A, B, and
> C, I do not want it to make a difference in which group I deal with the
> message first.  If, while in group B, I read the message, tick it, and
> reply to it, I expect it to be annotated with "!A".  If a week later I am
> viewing the same message in group C, I want to see the same annotation
> there too.

I don't agree.  I feel that the Xref header should be used for one
thing and one thing only -- it should ensure that a reader never has
to read a crossposted article more than once.  That's all.

> First, I disagree about the usefulness of Xref.  Second, the lack of mark
> propagation in Gnus prevents achieving the goal of not reading articles
> more than once.  Suppose, while in group A, I read an article which was
> cross posted to group B and then I tick the article.  Then I go to group
> B.  I will see the same article and it will be unmarked (not marked as
> read).  Unless I am very careful, I will end up reading it again.

No, if you tick the article in group A it will be marked as read in
group B.  So you'll never see it in group B.

>    > 4. Question: How do people keep track of whether they have edited a
>    >    message or forwarded it?
> 
>    They have rilly good memories?
> 
> I asked this question because this is one of the features of VM which I
> like quite a bit.

Well, I could add new secondary marks for forwarding and editing, but
is it really something we need?  Well, perhaps it would be nice.  I've
added it to the Red Gnus todo list.  (Along with World Peace,
Happiness For Everybody, and Free Word For XEmacs.  :-)

(We need more smileys.  We should really have O:-) and :-=, for
instance.  Anybody feel up to going through that mam(m)ooth list of
smileys and drawing them all?  :-)  Shouldn't be much work.  :-O.)

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-06-20  8:32 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 [this message]
1996-06-10  9:16 ` Per Abrahamsen
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=x6n31yswo9.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).