Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!calvin.tamu.edu
From: cnh5730@calvin.tamu.edu (Chuck Herrick)
Newsgroups: comp.sys.next
Subject: Re: Rich Text and comp.sys.next
Message-ID: <10748@helios.TAMU.EDU>
Date: 9 Dec 90 20:59:26 GMT
References: <12305@milton.u.washington.edu) <356@heaven.woodside.ca.us) <12613@milton.u.washington.edu)
Sender: news@helios.TAMU.EDU
Organization: geodynamics research institute, texas a+m univ
Lines: 58

In article <12613@milton.u.washington.edu) mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes:
). Major security holes (some fixed in 2.0, I haven't tested 2.0 yet).
it is customarily in good taste to reserve comment until you know
about what you speak.
). Lack of basic features that even text-oriented mailers have.
yeah, like voice-embedded mail?
). Limitations on the To: field of messages.
). Limitations on what may be in the Subject: field of messages.
big deal. just because it doesn't do what your Mail-app does.
). The attitude that "all the world's a NeXT" (like "all the world's a
)  VAX"), so there's no need to worry about non-NeXT users.
). The attitude that "all the world's a tiny cluster of NeXT machines"
)  so you have low-res bitmaps of everyone's picture.
NeXT has raised the lowest common denominator of computing. VAX did
this at one time and then died of cardiovascular congestion. You can't
raise the lowest common denominator of computing and not carve new
ground.
). A non-intuititive interface (how would you know that the way to
)  attach a file is to go to the directory browser and drag its icon
)  into the message?  I'm still not sure how you insert a file).
read the damn manual
). Obscure buttons with pretty icons but no immediately obvious
)  purpose.
). No internal help to explain the interface or obscure buttons (it is
)  unforgivable for an application not to have a help button for every
)  menu and every major window).
oh dear, it's a matter of personal taste after all, isn't it
). No way (that I can tell) to display more than one message at a time.
). No way (that I can tell) to have more than one mailbox open at a
)  time.
jeepers, I just can't recall your post asking how to do this.
). By default, Mail.app steals the mail from /usr/spool/mail into its
)  own Mailboxes directory, taking the messages away from other tools.
). Mail.app's non-textual formats (NX_Attachments?) are not published
)  in the RFC library, making it difficult to create compatible
)  implementations for other architectures.
go to developers camp
). Mail.app's non-textual formats are completely different from the
)  non-textual formats used in present Internet multimedia e-mail
)  research.  The world is moving towards open, common standards, not
)  closed, proprietary ones.
so I have to be subjugated by your standards? like X-windows?
can you say No.
). Mail.app periodically clobbers its mailbox.  [The victims of this
)  bug are a great source of new MailManager users.]
I, for one, have never had this happen.
But now we get down to the kernel of the issue. Little Markie has his
own Mail-app he'd like us all to use, and we're just not getting the
message, are we?
)/usr/ucb/Mail
)It is the single mail program that more Unix users use than any other
)program; particularly administrator and non-computer types.
open Terminal and type /usr/ucb/Mail. or /usr/ucb/mail. feel better?
)It was a non-goal of MailManager to dovetail with Mail.app -- the goal
)was to dovetail with other Unix mail tools.  It is Mail.app that fails
)to dovetail with anything else.
Try
verbose == off