9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] more userfriendly mailer like exmh on Plan 9?
Date: Mon,  7 Sep 1998 10:54:53 +0100	[thread overview]
Message-ID: <19980907095453.m5J-8I57mSRmCryfL1gE9htuZYVgEeaF1NopfWK6Jfw@z> (raw)

> How can I cook acme for naive users' initiallization?

>>Set up the window the way you want it, type "Dump" somewhere
>>and execute it.  That creates an acme.dump file that you can
>>squirrel off somewhere (like $home/lib) and use as an argument
>>to acme's -l option.  See acme(1) for more.

	acme /acme/*/guide
quickly provides a starting point (you can eliminate the bits you don't need);
then Dump as suggested above.

you can put an entry in the file named in 8.5's -i option (in lib/profile)
to start acme with -l:

window '0 71 1024 760' acme -l acme.dump

acme is very nice for programmers who also read email
(or people who read email who also program), but it can
and is used by people who aren't computer scientists to read email.

the main limitation i'd note in the Plan9 version is the clumsiness of
manipulating MIME attachments (MIME itself is clumsy, but what can you do?).
it's possibly worth adding Undo to the Reply windows it creates (though i haven't
yet -- when i need it i type it in the tag myself).

there are some convenient features that follow from general
Acme mouse button rules (eg, click in the string 9fans with button 1,
then click Save with chord button2,button1 to save a given message
in /mail/box/$user/9fans).  thus it's probably worth the effort
to teach the mousing rules well.




             reply	other threads:[~1998-09-07  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-07  9:54 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-09-07  2:57 Russ
1998-09-07  2:23 Kenji
1998-09-07  1:05 Scott
1998-09-07  0:58 okamoto%plan9

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=19980907095453.m5J-8I57mSRmCryfL1gE9htuZYVgEeaF1NopfWK6Jfw@z \
    --to=forsyth@caldo.demon.co.uk \
    /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).