9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] mail client; general question web vs command
Date: Tue,  2 Aug 2011 09:07:24 -0400	[thread overview]
Message-ID: <8645c619c7c5a25163befb2496e5eca8@ladd.quanstro.net> (raw)

> Robert Raschke coded a threaded version of Acme's News.
> But that depends on the filesystem hierarchy of messages
> in nntpfs. (n)upasfs does not thread messages at the level
> of the fs. Indeed, it would be a better approach to thread at
> the interface level, which should be possible all the same
> and could apply to Acme's News interface as well (so we
> can perhaps remove a lot of that code from nntpfs).

upas/fs has all the information it needs to do the threading,
and it's cached.  the client, otoh will need to scan the entire mail box to
determine threading.  this can be pretty slow if your mailbox
is not small.  and threading's usefulness depends on your mailbox
being not small.

what upas/fs lacks is the ability to present the same mailbox many
times.  this would allow for a single store rather than moving
messages around.  nedmail is already equiped to handle threading,
since it handles subfolders already.

(for lack of threading, i use nedmail's g/subject/h or g/sender/h.)

> If anyone does this, I also suggest using Russ' rc version
> (ported to Plan 9) of Acme Mail, instead of adapting the C
> code.

this sounds tempting, but how are you going to thread efficiently
in rc?

(russ' upas/nfs is much different in presentation than upas/fs.)

- erik



             reply	other threads:[~2011-08-02 13:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 13:07 erik quanstrom [this message]
2011-08-02 13:42 ` Russ Cox
2011-08-02 15:02   ` Charles Forsyth
2011-08-02 19:20     ` David Leimbach
2011-08-03 22:18   ` Akshat Kumar
  -- strict thread matches above, loose matches on Subject: below --
2011-07-31 20:00 Rudolf Sykora
2011-07-31 20:14 ` Jacob Todd
2011-08-02  4:36   ` Akshat Kumar
2011-08-04 15:49   ` Mathieu Lonjaret
2011-08-06 14:16     ` Rudolf Sykora
2011-08-11 10:42       ` Rudolf Sykora
2011-08-11 10:54         ` Mathieu Lonjaret
2011-08-11 10:55           ` Mathieu Lonjaret
2011-08-13 18:38           ` Rudolf Sykora
2011-08-13 23:26             ` Fazlul Shahriar
2011-08-14 14:50               ` Rudolf Sykora
2011-08-13 23:40             ` Mathieu Lonjaret
2011-08-27 17:59           ` Rudolf Sykora
2011-08-11 12:20         ` Fazlul Shahriar
2011-08-11 16:34           ` John Floren
2011-08-11 17:55             ` David du Colombier
2011-08-28 14:09               ` Rudolf Sykora
     [not found]               ` <CAOEdRO1k0X8tU+QMazETGs2rT4NmMazWPJSDN_79Wd=TbcrHzA@mail.gmail.c>
2011-08-28 15:15                 ` erik quanstrom
2011-08-28 18:22                   ` Rudolf Sykora
2011-08-31 14:22                     ` Richard Miller
2011-09-09 19:48                       ` Rudolf Sykora
2011-09-14 12:39                         ` Richard Miller
2011-09-19 13:06                           ` Rudolf Sykora
2011-09-20  7:47                             ` David du Colombier
2011-09-21 15:46                               ` Rudolf Sykora
2011-11-16 19:12                                 ` David du Colombier
     [not found]                       ` <CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.c>
2011-09-10 11:29                         ` erik quanstrom
2011-08-27 17:51     ` Rudolf Sykora
2011-07-31 21:17 ` dexen deVries
2011-08-01  4:22   ` hiro
2011-08-01 11:18 ` Ethan Grammatikidis
2011-08-02 20:32 ` Lyndon Nerenberg (VE6BBM/VE7TFX)

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=8645c619c7c5a25163befb2496e5eca8@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).