9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme mail "feature"
Date: Fri,  1 Oct 2004 14:19:39 +0100	[thread overview]
Message-ID: <a3074f4709c06e0207d1d7859b6f2cc5@vitanuova.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0410010858120.14170@athena>

> Does anyone find it useful that acme mail highlights the
> incoming mail, deselecting whatever was previously
> highlighted?
[...]
> It's happened enough times that I'm pretty sick of
> this "feature."  I'll hunt it down and squash it
> if others agree.

it's probably an automatic consequence of inserting new text.  if you
want to avoid it, you'll have to add code to set the selection back to
what it was, but i'm not sure how easy that'll be when the user might
be changing the text too.

personally, this hasn't bitten me much.  what i would like though is
some way of tagging messages.  it'd be nice to know which messages i
haven't read, for example (i've missed important emails in the past
when receiving lots of mail), and i'd like to be able to tag mail
items as "needs further attention"/"must reply".

but the thing that most needs fixing (for my usage pattern anyway) is
the way that upas/fs reads the entire mailbox into RAM. i get around
this by periodically archiving my mailbox, deleting all but the most
recent 6 month's worth of messages, but i'd prefer not to do this.

all that said, i think the combination of acme mail and upas/fs
is excellent, and i wouldn't use anything else!



  reply	other threads:[~2004-10-01 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 14:03 Sam
2004-10-01 13:19 ` rog [this message]
2004-10-01 13:56   ` andrey mirtchovski
2004-10-01 14:45     ` rog
2004-10-01 14:42       ` Fco. J. Ballesteros
2004-10-01 14:51         ` Axel Belinfante
2004-10-01 14:58           ` Fco. J. Ballesteros
2004-10-01 15:18             ` boyd, rounin
2004-10-01 16:27               ` C H Forsyth
2004-10-02 22:28                 ` Skip Tavakkolian
2004-10-02 22:55                   ` George Michaelson
2004-10-02 23:22                     ` andrey mirtchovski
2004-10-01 14:54         ` rog
2004-10-01 16:59           ` Richard Miller
2004-10-01 15:01     ` Russ Cox
2004-10-01 14:49   ` Brantley Coile
2004-10-01 14:56     ` Axel Belinfante
2004-10-01 14:56     ` Fco. J. Ballesteros
2004-10-01 14:59       ` Brantley Coile
2004-10-01 15:07         ` Fco. J. Ballesteros
2004-10-01 15:16       ` rog
2004-10-01 15:24         ` boyd, rounin
2004-10-04 12:33 Caerwyn B Jones
2004-10-04 12:39 ` Russ Cox
2004-10-04 14:13 Caerwyn B Jones

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=a3074f4709c06e0207d1d7859b6f2cc5@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.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).