Gnus development mailing list
 help / color / mirror / Atom feed
From: Rob Browning <rlb@cs.utexas.edu>
Subject: Re: New approach to grouping/backend/marking - good or bad idea?
Date: 05 Nov 1999 16:41:29 -0600	[thread overview]
Message-ID: <87k8nwtvc6.fsf@raven.localnet> (raw)
In-Reply-To: Karl Kleinpaste's message of "04 Nov 1999 11:22:37 -0500"

Karl Kleinpaste <karl@justresearch.com> writes:

> A lot can be done with Keywords.  But adding a neater interface for
> tweaking header content would certainly be interesting and useful; as
> it is, you can always `C-u g e' a mail message and add keywords of any
> sort that makes you feel good, including "todo" or whatnot.

All this sounds interesting.  I'll have to look in to it more
carefully...

> As to your suggestion for generalized storage...no, please don't.
> One of the benefits of per-group directory storage is that I can
> simply step into a directory and grep for something interesting.
> Yes, I have nnir.el (and use it heavily -- it has become part of my
> work here) but there is still benefit ultimately in being able to
> ask truly simple UNIX questions of my filesystem.

Well, I envisioned that there would be a shell level tool that would
allow you to generate file lists i.e.

  gnus-find -k debian-devel -a -k -debian-user -not -k debian-policy

or whatever.

So you should be able to do nearly the same things you can do with
separate directories now, including exporting all your stuff as
separate directories if you want.  However, I will certainly concede
that this isn't as straightforward as just having a set of
directories.  I'm sure it makes some things easier and some things
harder.  I just started to think that I might want my mail to be more
like a database than just a collection of files (though I'll always
want to be able to get at it as files).

In any case, I'm beginning to think that overall, for now, I may just
need to switch over to total-expire (if I plan to keep using
crossposting i.e. "&" splits), and just get used to it.  It's too
weird to have an article that's marked as expire in one group get the
read mark in all the others.

And although I'd rather use the expiry process, I suppose I can just
use 'B del' when I want to remove a crossposted article from the
current group, but not affect it elsewhere, though I'd still like to
have control over what happens to marks on crossposts.  And finally,
unless I physically renumber my articles, I think I can always use the
filesystem location as a "permanent pointer".

I'll have to think about that for a bit...

Thanks

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930


  reply	other threads:[~1999-11-05 22:41 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
1999-11-04 16:22 ` Karl Kleinpaste
1999-11-05 22:41   ` Rob Browning [this message]
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=87k8nwtvc6.fsf@raven.localnet \
    --to=rlb@cs.utexas.edu \
    /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).