Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Attaching notes to messages
Date: 10 Oct 1999 11:53:31 -0700	[thread overview]
Message-ID: <m3wvsvqc7o.fsf@satellite.local.lan> (raw)
In-Reply-To: Hannu Koivisto's message of "10 Oct 1999 17:58:16 +0300"

Hannu Koivisto <azure@iki.fi> writes:

> Greetings,
> 
> Has anyone thought about or, even better, implemented some way of
> attaching arbitrary notes to messages?  Many times I mark some
> messages with important URLs or other information persistent and
> ticked, but usually their subjects don't give any indication of the
> reason why I saved them, so I can't later find them just by
> interactively searching for something in the summary buffer.

This may be too amateurish for what you are after but it is a method
I've used for some time on groups where 'gnus-edit-article' is
allowed.

Editing is also possibe in News groups with  `C-u e'

Add a "Keywords:" header where you can put brief comments or single
words that will allow you to grep that topic later.
(G for gnus)

Keywords: $TOPIC  edit articles attach notes annotate messages

Where $TOPIC is a few characters.

You can then easily scan the "Keywords" lines with grep or rgrep,
or get a file number to use in gnus summary buffer with "j".

rgrep -r "^Keywords: $TOPIC" ~/Mail
To see all keyword lines for that topic.

A more developed method is possible esp. if you don't care to save
the original form.  But even if you do, below should be getting close
to what you describe.

I have code pieced together with help from Kai and Lars (the
botchiness is all mine) That allows the user to save an edited message
from  any gnus editing mode to any group with a few key strokes. And
leaves the original in place untouched.

It also allows a way to do this:

Press "F" or "R" on a message you wish to keep and annotate

Type in your annotation between [] or similar, then save that portion
to file with M-x save-to-file.

Remove the annotation with C-w then attach it with 'C-c a'

Save the Message plus attachment (to desired group) with the code I
mentioned above then kill the edit buffer.

The result of all this is an annotation attached to a copy of original
message, saved in a special group.  While leaving the original message
untouched in its group.

I'll post the code on a web site or here if you'd like to see if its
useful to you.







  parent reply	other threads:[~1999-10-10 18:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-10 14:58 Hannu Koivisto
1999-10-09 16:36 ` François Pinard
     [not found]   ` <wtn1zb3rnq1.fsf@licia.dtek.chalmers.se>
1999-10-09 20:56     ` François Pinard
1999-10-11 10:58       ` Eric Marsden
1999-10-12  8:18         ` storing messages in DBMSes (Was: Attaching notes to messages) Steinar Bang
1999-10-12 11:16           ` Eric Marsden
1999-10-12 11:54             ` Fabrice POPINEAU
1999-10-10 20:38     ` Attaching notes to messages Kai Großjohann
1999-10-10 18:53 ` Harry Putnam [this message]
1999-10-10 23:29   ` Hannu Koivisto
1999-10-11  0:15     ` Harry Putnam

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=m3wvsvqc7o.fsf@satellite.local.lan \
    --to=reader@newsguy.com \
    /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).