Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Labels/Annotations per message
Date: 13 Aug 2000 19:07:06 +0200	[thread overview]
Message-ID: <m34s4pccp1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3ln1ed4tj.fsf@totally-fudged-out-message-id>

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Pavel.Janik@inet.cz (Pavel Janík ml.) writes:

> So I also thought about the Real Solution (tm). We should probably invent
> another type of mark, which is associated with annotations. It can be stored
> in .newsrc.eld or somewhere else?
> 
> gnus-newsrc-alist in .newsrc.eld looks like this now:
> 
> ("Gnus" 3 ((1 . 1748)) ((dormant 1015 (1153 . 1154)) (expire (1735 . 1748)) (reply 1466 1557 1637) (tick 1734)))
> 
> What about inventing new mark annotate like this:
> 
> ("Gnus" 3 ((1 . 1748)) ((annotate (1 "This is the first message in the buffer.") (1748 "I just received this message."))))
> 
> The first message is marked as such and the last one too. If this is
> implemented, you can easily limit the summary buffer to the regexp of these
> annotations and similar.
> 
> What do you think about it?

This would be one way of doing it, but it doesn't seem to go far
enough.

[-- Attachment #2: Type: text/plain, Size: 988 bytes --]


I mean, I don't edit or annotate mail messages at all, but I know some
people who do that extensively.  (Hi, François!)  Wouldn't it be
really nice if you could edit/annotate any text in any article buffer?
You read an article in some newsgroup, and there's some useful stuff
in there, so you start editing it and inserting stuff here and there
in the article.  But you want to know which parts you wrote and which
parts were in the original article, no?

And it just now occurred to me that RCS would perhaps be the right
thing here.  The Meta-Edit command would pull the article down into
the cache, and when you edit it, you just commit your edits to the
cached version of the article.  When reading the article, Gnus would
check the latest version out, but have a special viewer that would
colorize the contributions from different people differently.  And,
and...

Er.

Anyway.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

  reply	other threads:[~2000-08-13 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13 12:20 Pavel Janík ml.
2000-08-13 17:07 ` Lars Magne Ingebrigtsen [this message]
2000-08-13 19:13   ` Karl Eichwalder
2000-08-14 15:52     ` François Pinard
2000-08-14 21:10       ` Kai Großjohann
2000-08-13 19:26   ` Kai Großjohann
2000-08-13 19:50     ` Lars Magne Ingebrigtsen
2000-08-14 21:09       ` Kai Großjohann

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=m34s4pccp1.fsf@quimbies.gnus.org \
    --to=larsi@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).