🚀 go-pugleaf

In article <48.260A1070@imagery.FIDONET.ORG> Philip.Craig@p27.f22.n282.z1.FIDONET.ORG (Philip Craig) writes:
|In a message to All [22 Mar 90 06:27:00] Christopher Silverberg writes:
|
| >In article <10953@bsu-cs.bsu.edu> mithomas@bsu-cs.UUCP (Michael
| >Thomas Niehaus) writes:
|
|>>> Philip Craig - via FidoNet node 1:282/33
| >>I'm really getting tired of these messages that go flying off the right hand
| >>side of my screen.  Please put a return at the end of every line (and if
| >I think it must be YOUR system, or your terminal setup causing the problems.
| >I haven't seen any messages that fly dont format appropriately across the
| >screen. If the message does not contain returns, then your terminal program
| >should autowrap appropriately. You're a mac person... you should know that.
|So which is it, UseNeters?  Do I need to do something about my setup,
|or is Chris right?

If I've got my attributions right, Mr. Niehaus is right.  There should
be no lines longer than 80 characters.  If you are reading news with
some Mac program, maybe it softwraps by word for you.  I mostly read
from a Sun, which character wraps making it hard to read.  Some
readers don't wrap at all, making it impossible.  And if I want to
print an article for later study, no wrapping is done.

Usenet guidelines for posting specify a maximum line length of 80 characters.

|I don't want your opinion of FidoNet adversely affected by such things either.

It is not just FidoNet (though often it is); sometimes people compose
articles on other systems with an editor which does soft word wrapping
for them (i.e. new lines on the screen display but not in the text
file) and don't realize it.

Thanks for fixing it.

	/JBL

=
Nets: levin@bbn.com  |  "There were sweetheart roses on Yancey Wilmerding's
 or {...}!bbn!levin  |  bureau that morning.  Wide-eyed and distraught, she
POTS: (617)873-3463  |  stood with all her faculties rooted to the floor."