From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gmail-like mail backend?
Date: 10 Feb 2005 12:48:56 -0500 [thread overview]
Message-ID: <4n7jlgcnlj.fsf@lifelogs.com> (raw)
In-Reply-To: <buo3bw6dul1.fsf@mctpc71.ucom.lsi.nec.co.jp> (Miles Bader's message of "Wed, 09 Feb 2005 17:08:10 +0900")
On Wed, 09 Feb 2005, miles@lsi.nec.co.jp wrote:
> I've come to really like the gmail notion of "groups" (really called
> "labels") actually just being views into a big pool of messages, so that
> a single message can easily exist in many groups, and things that happen
> to that message (mark it as read, delete it) are immediately visible in
> all relevant groups. Another nice thing (in general) is that it ends to
> operate on threads as a whole, rather than individual messages; e.g., if
> you add a particular "label" to a thread, subsequent replies that arrive
> in that same thread show up in all relevant labels/groups, without the
> need to add classify them. Moving threads around is very lightweight.
>
> I wonder how hard would it be to have somethings niceness in gnus?
>
> Gnus already has the notion of crossposts from news, but the pervasive
> use of group-specific article-number ranges seems somewhat problematic.
>
> Anyway just food for thought. I like using Emacs to read email a lot
> more than using a web-browser, but Gnus is seeming a bit clunky at the
> moment compared to gmail...
Look at my previous posts in ding on "message labels" that someone was
going to implement. This can be done with the registry - just
associate the labels as extra data with the message ID, and you can
find the message by the message ID.
Ted
next prev parent reply other threads:[~2005-02-10 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 8:08 Miles Bader
2005-02-09 16:15 ` David Abrahams
2005-02-10 17:48 ` Ted Zlatanov [this message]
2005-02-10 23:15 ` Adam Sjøgren
2005-02-11 18:10 ` Ted Zlatanov
2005-02-15 18:03 ` Ian Soboroff
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=4n7jlgcnlj.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).