Received: from alta.COM (root@basalt.alta.com [192.108.233.3]) by nacm.com (8.6.9/8.6.9) with SMTP id LAA19337 for <executor@nacm.com>; Wed, 16 Nov 1994 11:00:35 -0800
Received: from slate.alta.com (slate.alta.com) by alta.COM (4.1/SMI-4.1+TAS1.10)
id AA02504; Wed, 16 Nov 94 10:55:54 PST
Received: by slate.alta.com (NX5.67e/NeXT-2.0)
id AA00385; Wed, 16 Nov 94 11:01:31 -0800
Date: Wed, 16 Nov 94 11:01:31 -0800
From: tec@slate.alta.com (Tim Cushing)
Message-Id: <9411161901.AA00385@ slate.alta.com >
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
To: executor@nacm.com
Subject: Re: binhex/compact probs?
Sender: Executor-Owner@nacm.com
Precedence: bulk
maren@astron.mit.edu (Maren Leyla Cooke) writes:
> i opened Word (which you can do either by clicking on
> another Word file or on the app itself), and used
> file/open (in the menu) to open the forkless file. A new
> resource fork must be magically created at this point,
> because the file came up as happily as anything, formats
> 'n' a'.
>
Both Word and Excell files can be opened without one of those
%blah files associated. In fact, on my NeXT, I standardly use
Opener to de-binhex Eudora mail, ad the .msw or .xl to the
file name (there's a panel that tells who who created the file
so you know what it is), then just double click on it and let
Executor take it from there.
I recall it works just fine the other way, too; binhex just the
main file (ignore the %thing) then paste it into a mail window
and send it. {I always edit the line endings of the first "(This
file must be..." line to be two newlines instead of the CRLF or
whatever binhex puts there; don't know if I have to, though}.
