From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: acme mail
Date: Mon, 20 Feb 2006 16:19:49 -0700 [thread overview]
Message-ID: <43FA4E95.8010300@lanl.gov> (raw)
In-Reply-To: <25577ab71682957ea088d5d9c1a6644f@swtch.com>
Russ Cox wrote:
> That's interesting but not how things are done in acme.
> You're trying to push the drag-and-drop metaphor into
> places where it was not intended.
hmm, I wasn't really after drag and drop.
But let me try again.
Could I sweep out a section of the main mail window, do a
|filter
in the tag line, and then end up with the messages marked with where
they will be filtered to, in ()? i.e. (9fans)- in front of a message,
(deleted)- in front of others, and so on. Then all I do is a Put and
things get filed.
Then I could build up my rules bit by bit, to the point that I can read
mail, and just file it as needed.
I would rather read and file, rather than have some filter auto-file and
then I read from lots of different places. But that's me. Lots of people
I know want it filed before they read it.
> I note that your approach requires having some other window
> with a list of folders. Typing next to Save does not.
Agreed. At the same time, I have about 100 folders, and don't always
remember them all. A list can be useful.
> I have been using acme mail again for the past week
> or so, and it's really nice to be back, especially after
> the drag-and-drop clumsiness of most mailers.
I'm pretty sick of drag and drop. But I need an interface that lets me
filter a lot of mail fast.
>
> I am running a new upas/fs and a slightly-changed
> version of acme mail. In my setup (though not in the
> standard one - yet), Save goes through upas/fs, so
> that in fact all my mail - incoming and saved - is kept
> on the mail server. It doesn't matter whether I Save on
> my laptop or on my desktop.
>
neat. I've tried to do something like this with the linux mailers and
it's a bit of a pain -- when you can do it at all.
Also, our mail allocation at LANL is ONE GB -- I can't fit there.
ron
next prev parent reply other threads:[~2006-02-20 23:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 15:56 [Fwd: [Fwd: Re: [9fans] acme + mh]] Ronald G Minnich
2006-02-20 11:51 ` [9fans] Re: acme mail Russ Cox
2006-02-20 23:19 ` Ronald G Minnich [this message]
2006-02-20 23:37 ` David Leimbach
2006-02-21 0:22 ` Dan Cross
2006-02-21 0:30 ` George Michaelson
2006-02-21 0:33 ` Steve Simon
2006-02-21 9:41 ` Charles Forsyth
2006-02-21 21:42 ` Dan Cross
2006-02-21 21:54 ` Skip Tavakkolian
2006-02-21 0:39 ` geoff
2006-02-20 19:42 ` Russ Cox
2006-02-20 17:03 Brian L.Stuart
2006-02-20 12:20 ` Russ Cox
2006-02-20 17:07 ` C H Forsyth
2006-02-20 17:13 Brian L.Stuart
2006-02-20 17:15 ` Richard Miller
2006-02-20 12:21 ` Russ Cox
2006-02-20 17:29 quanstro
2006-02-20 18:09 ` C H Forsyth
2006-02-20 18:15 quanstro
2006-02-20 14:18 ` Russ Cox
2006-02-20 19:43 ` uriel
2006-02-20 14:51 ` Russ Cox
2006-02-20 20:44 ` "Nils O. Selåsdal"
2006-02-20 20:49 ` Richard Miller
2006-02-20 16:00 ` Russ Cox
2006-02-20 21:03 ` Richard Miller
2006-02-20 21:22 quanstro
2006-02-20 16:29 ` Russ Cox
2006-02-20 23:30 quanstro
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=43FA4E95.8010300@lanl.gov \
--to=rminnich@lanl.gov \
--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).