|
|
| Author |
Message |
| 25 new of 283 responses total. |
janc
|
|
response 131 of 283:
| 
Feb 5 00:20 UTC 1999 |
A vandal filled up /a. I found him and nuked him. All in a days work.
|
cmcgee
|
|
response 132 of 283:
|
Feb 5 03:53 UTC 1999 |
I'm only getting a Respond or pass? prompt at the end of each item. And when I
reached the end of the last new item, I typed read 4, to come back herel When
I did that, I got the whole item, with no page breaks, just line after line
scrolling up and off my screen. Where should I start looking for the problem?
|
cmcgee
|
|
response 133 of 283:
|
Feb 5 04:11 UTC 1999 |
Ok, I quit PicoSpan, got to a shell prompt, typed menu, then b.
I'm now back in PicoSpan, getting full prompts (respond, pass, forget, etc)
and word wrap is working. Twice before when I tried that, it didn't work.
Any clues here?
|
aruba
|
|
response 134 of 283:
|
Feb 5 15:11 UTC 1999 |
In sounds to me like picospan couldn't find your .cfonce file, because that's
where your editor gets set to 'gate' (which inserts line breaks when
you're typing a response) and your pager to 'more -d' (which keeps the
text from scrolling off the screen without pausing) and your prompts to
what you expect.
Maybe this was related to /a being filled up?
|
janc
|
|
response 135 of 283:
|
Feb 5 18:28 UTC 1999 |
Failure to read the .cfonce makes sense, but I can't imagine how /a
being full would relate.
|
scott
|
|
response 136 of 283:
|
Feb 5 23:38 UTC 1999 |
Most of the modems were offline from when Grex was down until just a few
minutes ago (victims of the reboot).
|
keesan
|
|
response 137 of 283:
|
Feb 6 02:34 UTC 1999 |
That explains why I did not even get a busy signal. I sent email via arbornet
instead. Nice that one system is always operative.
|
janc
|
|
response 138 of 283:
|
Feb 6 15:08 UTC 1999 |
Yeah, I'd screwed up one of Grex's configuration files, so it refused to
reboot right. STeve had just stopped in to do a quick reboot on his way
to work. But the time he managed to fix things, he was running rather
late, and took off in a hurry, forgetting to turn the modeii back on.
My fault at least as much as STeve's. Scott went by later and powered
the modeii back up.
|
steve
|
|
response 139 of 283:
|
Feb 6 16:40 UTC 1999 |
Sorry, all. It once again proves that no good deep goes unpunished.
|
hhsrat
|
|
response 140 of 283:
|
Feb 6 21:27 UTC 1999 |
trying to look at the item list for hangout using Backtalk, I get a
backtalk error
"ERROR: could not open /bbs/hangout /config
executing "open_conf" on line 19 of pistachio/openconf.bt included by
"stopped" on line 44 of pistachio/confhome.bt"
Using telnet and then running bbs, it works fine
|
mdw
|
|
response 141 of 283:
|
Feb 7 04:10 UTC 1999 |
That is because backtalk has a "different" interpretation of /bbs/conflist
lines 183-184 than PicoSpan.
|
hhsrat
|
|
response 142 of 283:
|
Feb 7 04:40 UTC 1999 |
Is there a way to fix this problem?
|
mdw
|
|
response 143 of 283:
|
Feb 7 07:24 UTC 1999 |
There are many ways to fix this problem.
|
hhsrat
|
|
response 144 of 283:
|
Feb 7 19:44 UTC 1999 |
This problem has been fixed. According to (login-name) i, there were
extranaeous blanks in some file that Backtalk didn't like
|
valerie
|
|
response 145 of 283:
|
Feb 7 21:52 UTC 1999 |
This response has been erased.
|
i
|
|
response 146 of 283:
|
Feb 7 22:56 UTC 1999 |
Re#144 -
Extra spaces in /bbs/conflist that *i* put there....but i was just
uh, testing...that's it!...i was just testing!....
<i hides the ball & remains of the vase behind the sofa and goes
back to playing with his Legos>
|
valerie
|
|
response 147 of 283:
|
Feb 8 02:52 UTC 1999 |
This response has been erased.
|
mdw
|
|
response 148 of 283:
|
Feb 8 02:58 UTC 1999 |
(doesn't everyone use 90 cols by now?)
|
janc
|
|
response 149 of 283:
|
Feb 8 03:28 UTC 1999 |
Yeah, Backtalk should be smart enough to ignore extra spaces, but it
apparantly isn't.
|
rtg
|
|
response 150 of 283:
|
Feb 8 10:22 UTC 1999 |
WHy is 80 columns such a standard? A terminal could be made with just
about any line width, why did 80 evolve to be so common?
Possibly?
) mechanical teletypes which printed on 8.5 inch paper, at 10CPI?
) legacy Hollerith cards from the mainframe days of batch jobs?
WHy do we stick with the habit?
|
davel
|
|
response 151 of 283:
|
Feb 8 12:50 UTC 1999 |
Legacy systems.
|
cmcgee
|
|
response 152 of 283:
|
Feb 8 13:21 UTC 1999 |
*grin*
|
aruba
|
|
response 153 of 283:
|
Feb 8 15:15 UTC 1999 |
I always thought it was because of punch cards.
|
steve
|
|
response 154 of 283:
|
Feb 8 15:49 UTC 1999 |
It is.
Most terminal emulation software these days defaults to 80
characters. Probably the single most popular program used to
get to Grex these days, Windows 9x telnet, isn't very good about
changing its screen size.
|
mcnally
|
|
response 155 of 283:
|
Feb 8 18:26 UTC 1999 |
According to references I've seen to cognitive psychology studies
there's an effect that results in diminishing readability when line-length
gets too long (though that limit is somewhat more than 80 characters..)
I can't recall offhand at what point readability starts degrading
substantially but there *are* decent empirical reasons for not having
ultra-wide display terminals..
|
