|
|
| Author |
Message |
| 25 new of 283 responses total. |
keesan
|
|
response 175 of 283:
| 
Feb 11 21:17 UTC 1999 |
On the first option, my eye comes to rest in about three spots on the line,
in the second option, in two spots (giving me reference points at both ends
of the line), in the third option two spots with redundancy from overlap, the
last option has too many hyphens, so number two for me also. Actually the
number of times my eye rests depends somewhat on grammar, but on the average
two grammatical phrases per line of the second option.
|
scott
|
|
response 176 of 283:
|
Feb 11 21:38 UTC 1999 |
The third.
|
flem
|
|
response 177 of 283:
|
Feb 11 22:06 UTC 1999 |
The second or third for me. It's hard to tell, because I read text
differently if I already know what it says.
|
scg
|
|
response 178 of 283:
|
Feb 11 22:38 UTC 1999 |
My original thought was that the third was easiest, but after seeing the first
couple of responses here I went back and read through both the second and
third again, and decided that maybe the second was easier. I'm not sure.
|
happyboy
|
|
response 179 of 283:
|
Feb 11 22:44 UTC 1999 |
the fourth.
|
albaugh
|
|
response 180 of 283:
|
Feb 11 23:28 UTC 1999 |
the 5th :-)
|
remmers
|
|
response 181 of 283:
|
Feb 12 00:06 UTC 1999 |
The fact that more people are choosing paragraph two tends to
confirm what I've read: An average of 10 to 12 words per line
is optimum for readability.
This means that responses that use almost all of the 80 columns
on a standard terminal screen aren't as readable as they could be.
A line length between 65 and 70 characters is about right.
|
orinoco
|
|
response 182 of 283:
|
Feb 12 01:10 UTC 1999 |
The third.
|
jeff
|
|
response 183 of 283:
|
Feb 12 02:33 UTC 1999 |
The second.
|
dang
|
|
response 184 of 283:
|
Feb 12 03:30 UTC 1999 |
The first.
|
davel
|
|
response 185 of 283:
|
Feb 12 12:26 UTC 1999 |
I have a Grex system problem to report: someone has hijacked the System
Problems item.
|
cmcgee
|
|
response 186 of 283:
|
Feb 12 20:07 UTC 1999 |
The second.
|
cmcgee
|
|
response 187 of 283:
|
Feb 13 02:32 UTC 1999 |
Ok, PicoSpan just did it to me again. I logged on and using the menu,
went to bbs. I got the "all text running along the bottom line, scrolling
off to the left andout of sight" problem. Quit PicoSpan, tried again, same
thing. Quit PicoSpan, logged off, logged on, same thing. Logged off, logged
on, same thing. Went to pine from screwy bbs line, no screen problem. Back
to bbs, same problem. Logged off, logged on, went to pine from menu, went
back to bbs, finally worked. (somewhere in there I also exited to the
shell and tried to go to bbs straight from the shell prompt. Still had
the scrolling line problem).
So, any clues? I don't see anywhere in this sequence where I had a
permanent problem, like changing settings in my software, or a bad phone
line, etc. As far as the phone was concerned, I never hung up. I never
quit the software, all I did was log on and log off of Grex on the same
port. (I've been on about 33 minutes right now, if anyone wants to look
at the logs).
|
mdw
|
|
response 188 of 283:
|
Feb 13 11:12 UTC 1999 |
Could be lots of things. The first thing is that it's definitely not
PicoSpan itself that's doing that; PicoSpan has no idea how to scroll
your screen, and especially not how to make text "scroll left and out of
sight". *That* sort of behavior is something your terminal software is doing.
Now, as to why your *terminal* software is doing that, is another question. A
likely prospect is certainly telephone line noise, but if it consistently
repeats, that's not so likely. The next culprits include possible problems
with your terminal settings, pager, funny characters in items on grex, or a
memory or disk problem on your computer.
You might try:
def pager 'cat -v
on grex. With this setting, PicoSpan will no longer pause when it prints an
item out (but if your terminal sofwtare supports scoll-back, that may not be a
problem). However, if there are funn characters, "cat -v" will expand them out
into printable characters. You should be suspicious of characters like ^N, ^O,
^H, ^M, and ^[[A. Anything like these could indicate something odd going on.
|
cmcgee
|
|
response 189 of 283:
|
Feb 13 16:58 UTC 1999 |
thanks Marcus. I have been having a lot of trouble lately with the pager.
Seems like every other time I sign on, I have to reset my terminal on grex
so it knows what size I have my screen set to. And my screen size isn't
changing. (25 x 80). This must be connected to that problem.
|
janc
|
|
response 190 of 283:
|
Feb 13 19:39 UTC 1999 |
(It is somewhere between impossible and extremely difficult to enter
lines longer than 72 characters with Backtalk. I think this is mostly
good, but occasionally annoying.)
|
remmers
|
|
response 191 of 283:
|
Feb 14 13:01 UTC 1999 |
For overall response readability, limiting lines to 72 characters
is good. It's occasionally annoying when I'm trying to post a
long URL.
|
tpryan
|
|
response 192 of 283:
|
Feb 14 15:25 UTC 1999 |
Once I set my 14.4kb modem to slow down to 9600b, the closest
speed this procomm supports, I get extremly less line noise and screen
problems. McGee, have you tried anything like this?
I can't see the differnce in the speed.
|
steve
|
|
response 193 of 283:
|
Feb 14 17:48 UTC 1999 |
Yes, I've done that. The more data the modem tries to cram on
the phone line the more sensitive it is to line noise.
|
mary
|
|
response 194 of 283:
|
Feb 14 20:15 UTC 1999 |
This response has been erased.
|
mcnally
|
|
response 195 of 283:
|
Feb 14 20:33 UTC 1999 |
I haven't seen line noise since error correcting modems became common.
Do people still get honest-to-goodness garbage-character line noise on
a regular basis?
|
steve
|
|
response 196 of 283:
|
Feb 14 21:34 UTC 1999 |
Absolutely! The quality of the phone lines has deteriorated in the
last decade in Michigan. Ameritech has admitted this to the mpsc.
|
davel
|
|
response 197 of 283:
|
Feb 14 22:26 UTC 1999 |
Re 195: Even with error-correcting modems, you just don't *see* the garbage.
In calling one customer in an area where we always had huge blasts of line
noise, we now find that the connection appears to just hang for intervals of
say 10 seconds to a minute or so. Once in a while it even eventually
disconnects. If I'm simultaneously on a voice line with the customer, I can
often hear snap-crackle-pop when this stuff is occurring on the data line.
|
mcnally
|
|
response 198 of 283:
|
Feb 15 05:25 UTC 1999 |
re #196, 197: I guess I should've stressed that I'm surprised at the
*seeing* not at the noise. I have no doubt that error conditions still
occur during modem conversations but it seems like any reasonable error
correction protocol should be able to eliminate a huge fraction of the
garbage characters so that the user never sees them..
|
scott
|
|
response 199 of 283:
|
Feb 15 12:10 UTC 1999 |
The modems at both ends must be error-correcting to have an error free
connection. Grex has error-correcting modems, but not all Grexers do.
Therefore some Grexers still see line noise.
|
