From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: acme mail
Date: Mon, 20 Feb 2006 11:51:16 +0000 [thread overview]
Message-ID: <25577ab71682957ea088d5d9c1a6644f@swtch.com> (raw)
In-Reply-To: <43F9E6C2.6060709@lanl.gov>
> So I look at a message. it is /mail/fs/mbox/9 or some such. I go to the
> tag bar and change it to /mail/fs/mbox/plan9/9.
All you have to do to save the message somewhere
is type extra text in the tag after the "Save " and then
execute it. I save spam that has made its way into
my inbox by typing spam next to Save and then executing
"Save spam".
If you want a hierarchy, create directories under
/mail/box/rminnich and then use Save a/b/c.
I'm not sure what Geoff was trying to say, but you can't
use Put usefully in any acme mail window except the
main one (to actually delete messages marked as
deleted).
> What I want is to somehow point at a message, click on something in the
> tag bar, then click on a folder in another window, and have the message
> move.
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. I'm not claiming your
approach is worse; it's just not the way things are typically
done in acme.
I note that your approach requires having some other window
with a list of folders. Typing next to Save does not.
> Acme mail is an interesting foundation for a mailer, but it won't cut it
> for people I am trying to show Plan 9. At the same time, I like its
> simplicity, and still think it has a more sensible feel than (e.g.)
> tundrabird, the Super-Mailer of the Future.
I am not convinced.
If they want Thunderbird, they know where to find it.
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 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.
Russ
next prev parent reply other threads:[~2006-02-20 11:51 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 ` Russ Cox [this message]
2006-02-20 23:19 ` [9fans] Re: acme mail Ronald G Minnich
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=25577ab71682957ea088d5d9c1a6644f@swtch.com \
--to=rsc@swtch.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).