Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Marquardt <colin.marquardt@gmx.de>
Subject: Re: New approach to grouping/backend/marking - good or bad idea?
Date: 04 Nov 1999 11:09:43 +0100	[thread overview]
Message-ID: <k8zaeou36vs.fsf@alcatel.de> (raw)
In-Reply-To: Rob Browning's message of "03 Nov 1999 18:42:12 -0600"

* Rob Browning <rlb@cs.utexas.edu> writes:

> There are two bits here.  The bit that I feel pretty sure is a good
> idea is that of adding "message keywords" to Gnus.  Imagine that you
> can (either manually, or via automatic means like the split process),
> add arbitrary keywords to articles.  These keywords could then be used
> for whatever you like, but I could imeediately see a use for them in
> searches, narrows, etc.  This would easily eliminate all the arguments
> that keep me from being happy just using total-expire.

> For example, I would like to use a "todo" keyword, and attach that to
> articles that I need to do something about.  Then I could enter a
> group and do a "/ k todo" or whatever, and see all those articles.

Karl Kleinpaste has written
| ;;; messkeyw.el --- automatic keyword support during composition.
which is part of GNU Emacs (so it says).

| ;; This provides a hookable mechanism by which to have Keywords
| ;; headers automatically generated based on word frequency of the
| ;; body.  The goal is to make it possible to score on Keywords
| ;; provided, of course, that Keywords gets to the overview files.

I seem to remember that there was a HOWTO somewhere about adding the
keywords afterwards to exisiting articles.

This may be a start.

Colin


  reply	other threads:[~1999-11-04 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-04  0:42 Rob Browning
1999-11-04 10:09 ` Colin Marquardt [this message]
1999-11-04 16:22 ` Karl Kleinpaste
1999-11-05 22:41   ` Rob Browning
1999-11-05 23:07   ` Kai Großjohann
1999-11-06  0:44   ` Russ Allbery
1999-11-07  1:17 ` Lars Magne Ingebrigtsen

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=k8zaeou36vs.fsf@alcatel.de \
    --to=colin.marquardt@gmx.de \
    /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).