[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSHK 1.1 Problems -- line length
- Subject: Re: GSHK 1.1 Problems -- line length
- From: johnlb@primenet.com (John Bowling)
- Date: 1996/05/29
- Newsgroups: comp.sys.apple2
- Organization: Primenet (602)416-7000
- References: <4ofhl2$bpl@news.ysu.edu> <4oganh$sjk@seeker.the-hermes.net> <4oh31q$rva@gap.cco.caltech.edu>
- Sender: root@primenet.com
In article <4oh31q$rva@gap.cco.caltech.edu>,
Nathan Mates <nathan@cco.caltech.edu> wrote:
>In article <4oganh$sjk@seeker.the-hermes.net>,
>Geoff Weiss <geoff@seeker.the-hermes.net> wrote:
>>(heh..actually I'm breaking the rules too by having a 76 column line,
>>so flame me :).
>
> When you write stuff worth being quoted four times, then I'll get
>around to flaming you for line length. :)
>
> Also, my normal line length message reads something like this:
>
> [Hint: press return every 70 characters or so. Makes it much easier
>to quote you]
>
> It's not an order, or even really a flame. Just a helpful
>suggestion that _most_ people catch on to rather quickly. By using
>lines of a nonexcessive length, everyone is much happer in the long
>run. Unfortunately, some people that insist on being old farts still
>haven't gotten the message yet.
>
>Nathan Mates
Actually, it seems strange to me that this problem even comes up, unless
people are editing off line and then transferring the message to
internet. I am using 'trn' with a shell account (which I assume the vast
majority of A2 users use) to read mail and to enter/edit new mail. I
have entered this as one continuous long line without pressing return and
the software handles ling length very well.
I have to really work at making lines too long.
John
--
--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--
- John Bowling -- Nothing worthwhile came to mind, so this
- johnlb@primenet.com -- is a big blank. Ignore it!
--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--