Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: emulating mozilla's Label command
Date: Thu, 08 Apr 2004 08:59:21 -0700	[thread overview]
Message-ID: <sd65catq92.fsf@wes.hardakers.net> (raw)
In-Reply-To: <m2n05mr2iv.fsf@catbert.dok.org> (Chris Green's message of "Thu, 08 Apr 2004 10:02:32 -0400")

>>>>> On Thu, 08 Apr 2004 10:02:32 -0400, Chris Green <cmg@dok.org> said:

Chris> Important,Work,Personal,Todo,Later,etc..

Chris> Is there an easy way to emulate this with marks?  I use tick right now
Chris> to mean some set of all of those and often things get lost between
Chris> important and todo. I've tried working by copying todo's to a special
Chris> folder but I'm not trainable enough in that mode.

You know, I was thinking about something like that just yesterday.

Background: I currently use "unread" as need-to-handle-at-some-point,
and ticked as "critical".  Thus, most of my zillions of folders have
zillions of unread messages in them since I never manage to get
anything done.

What I need, though, is a sorted and combined list of all my
outstanding mail messages (preferably prioritized).  The problem is
that they're spread over a lot of groups, and it would be really slow
opening a whole ton of nnimap groups to generate one large summary
buffer full of todo items from all the groups.  The way around this,
probably, is through the use of the cache or the agent.

What I'd like would be a thread summary something like (badly drawn, sorry):

imap
 \- inbox
  \- family
    - Go to Mom's at 9
    - Help sister with her computer
  \- work
    - Write boss
    \- project1
     - submit report

But the cool thing would be if each of the topics actually came from a
group name (imap.inbox, imap.inbox.family, imap.work,
imap.work.project1), ...  And if all the data was auto-gathered from a
specified list of folders to work on.

I don't think putting something like this together would be terribly
difficult, since the support for much of it already exists (virtual
groups, todos, cache, agent, ...).  It's just a matter of a high-level
wrapper.

-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett



  reply	other threads:[~2004-04-08 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 14:02 Chris Green
2004-04-08 15:59 ` Wes Hardaker [this message]
2004-04-10 10:40   ` Sacha Chua
2004-04-10 14:14     ` Wes Hardaker
2004-04-08 21:29 ` Simon Josefsson
2004-04-12 15:03   ` Ted Zlatanov
2004-04-12 16:46     ` Kai Grossjohann
2004-04-13 15:30       ` Ted Zlatanov
2004-04-13 19:14         ` Chris Green
2004-04-15 19:40           ` Ted Zlatanov
2004-04-15 20:01             ` Chris Green
2004-04-16 14:53               ` Ted Zlatanov
2004-04-16 16:30                 ` Chris Green
2004-04-16 20:10                   ` Ted Zlatanov

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=sd65catq92.fsf@wes.hardakers.net \
    --to=wes@hardakers.net \
    --cc=ding@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).