Subject: Reading WP 5.1 file into Pine

From: [email-masked] (Tom Cole)
Date: 8 Mar 1995 02:24:51 GMT

I would like to know the correct way to read this type of ASCII text file 
into the body of a email message----I use (Pine 3.91).

When I put (^R) read rather long files inside Pine it gets to be a pain 
to have to move the cursor to the beginning of the text file and do a ^J 
format (justify) all the way down to eliminate word wrap, double spaces, 
control characters, etc. 

Is there a better way to do this?
 
TIA,
Thomas S. Cole
"Life is what happens to you while you're busy making other plans"
INTERNET ADDRESS:  [email-masked]

---

From: Joe Pollock <[email-masked]>
Date: Wed, 8 Mar 1995 10:52:54 -0800 (PST)

I can think of a couple of things to try.  Format the document with 
margins narrow enough to avoid triggering the word wrap function.  Save 
the document as DOS text (this may leave you with double line spacing) 
before you insert the document into your message, and avoid the control 
and formatting characters (your message implied to me that you were 
working with the document in WP format).

After you insert the document, postpone the message.  My recollection is 
that when you resume a postponed document, you are placed at the 
beginning of the message.

Joe Pollock
The Evergreen State College

---

From: Don Sugarman <[email-masked]>
Date: Wed, 8 Mar 1995 14:01:50 -0500 (EST)

> beginning of the message.

You can skip this step.  Just use ^W^Y to position to beginning fo file 
while composing.

---

From: [email-masked] (Robert E Adams)
Date: Sun, 12 Mar 1995 11:27:55 GMT

Tom Cole ([email-masked]) wrote:
: I would like to know the correct way to read this type of ASCII text file 
: into the body of a email message----I use (Pine 3.91).

: When I put (^R) read rather long files inside Pine it gets to be a pain 
: to have to move the cursor to the beginning of the text file and do a ^J 
: format (justify) all the way down to eliminate word wrap, double spaces, 
: control characters, etc. 

: Is there a better way to do this?

--
You need to do this because the files you are retrieving
with ^R contain long lines. They have likely been created
in a word processor, which when saving as ascii or DOS text
has not put a carriage return at the end of each screen line,

Actually, I make sure all my text is less that the 79 or 80 
characters I can display on screen. If I prepare a document 
with a word processor, I save it as ascii, then finish
formatting it in a text editor (memacs) in a width like you
see here. It is also easier to read on-screen.

I make sure all files in my /home directory are formatted 
properly when I place them there. When they are retreived 
with ^R, they fit in perfectly, with no reformatting (^J)
needed. 

Bob,

%% Bob Adams [email-masked] %%%%% HRD   %%%%%%%%  PUB REL   %%%%%%
% Adams Assoc   (902) 456-0761    %    TRAINING        DACUM          %
%      [email-masked]        %    EDITING         HTML           %
%      Inexpensive services       %    GRAPHICS        GAME ANIMS ART %
%   provided over the internet    % Space LEASING  Real Est PROFORMAS %
%%%%%%%%%%% http://www.cfn.cs.dal.ca/~ac200/adams.html  %%%%%%%%%%%%%%%
            Visit my home page for CIAU Mens Basketball