|
|
| Author |
Message |
matthew
|
|
Text scrolling
| 
Jun 2 00:12 UTC 1993 |
How do I go about activating whatever system it is that makes text
stop scrolling when the screen is full ?
Thanks in advance for any help provided.
|
| 32 responses total. |
danr
|
|
response 1 of 32:
|
Jun 2 01:16 UTC 1993 |
You create a file named .cfonce in your home directory with the line:
define pager more
This will cause the output of the bbs to go through the more pager,
which will stop the output every 24 lines. To look at the next 24 lines
you just hit the space bar. To quit, you hit "q".
If you'd like I'll create this file for you.
|
kentn
|
|
response 2 of 32:
|
Jun 2 02:20 UTC 1993 |
Will 'define pager less' work, too?
|
popcorn
|
|
response 3 of 32:
|
Jun 2 02:38 UTC 1993 |
This response has been erased.
|
tsty
|
|
response 4 of 32:
|
Jun 2 07:38 UTC 1993 |
Ummm, must be a new, newuser program running, cause the .cfonce file
is already created, and has a single line that says:
# here is where you can put PicoSpan customization
and so it only needs to be edited with either of the above suggestions,
but not both .......
|
mta
|
|
response 5 of 32:
|
Jun 2 08:51 UTC 1993 |
If the "more" pager drives you nuts like it does me, you can also
use the <ctrl-q> <ctrl-s> function.
When you want to stop the text, type <ctrl-q>, then, to make it start scrolling
again, type <ctrl-s>
(Or do I have it backwards? My keyboard has a <pause> key...
|
davel
|
|
response 6 of 32:
|
Jun 2 10:48 UTC 1993 |
You do have it backwards. ctl-s is xoff, tells the other end to stop sending.
ctl-q is xon, says it's OK to send again.
|
jared
|
|
response 7 of 32:
|
Jun 3 03:21 UTC 1993 |
That's what I do. because picospan takes the extra time to pipe it
through your pager, that creates so much overhead time, if you've got more
than one or two responses, you'll just sit there forever before you can hit
interrupt or such, and type forget if you don't want to read that item.
|
matthew
|
|
response 8 of 32:
|
Jun 3 04:24 UTC 1993 |
Thanks to all. I've been using Ctr-S and Ctr-Q and it's driving me buggy
since I don.t always stop the scrolling in time and then have to go
back through my screen buffer, usually just to get a couple of lines I
missed.
|
tsty
|
|
response 9 of 32:
|
Jun 3 17:37 UTC 1993 |
Sounds like the pager is just right then - do it.
|
popcorn
|
|
response 10 of 32:
|
Jun 4 03:29 UTC 1993 |
This response has been erased.
|
tsty
|
|
response 11 of 32:
|
Jun 4 08:35 UTC 1993 |
Ummmmmmm, what if you don't have a PageUp key? I can't find the scrollback
facility in the Kermit I'm using, Kermit 387, btw.
|
davel
|
|
response 12 of 32:
|
Jun 4 10:40 UTC 1993 |
Hm. I don't find Procomm's page-back buffer slow or clunky. The only
thing is that sometimes things like elm get confused & overwrite lines
before I get them read; with the shareware version of Procomm, the
read-back buffer display shows me the written-over version.
|
rcurl
|
|
response 13 of 32:
|
Jun 4 14:37 UTC 1993 |
I agree with popcorn - the ProComm buffer scrollback is "clunky and slow".
Also, as far as I can tell, one can't capture selections from it, as
one can do with PCTIE (to MTS), or with Mac comm apps. I do most of my
communication with the Mac, as a result. ProComm (shareware) doesn't
even support a mouse. With respect to !elm (and !pine, for that matter),
I find that I can't scroll back at all to see what came before, unless
I include the message I am answering in my reply, and use the editor.
That's a nuisance.
|
kentn
|
|
response 14 of 32:
|
Jun 4 22:49 UTC 1993 |
What happened to pg?
|
davel
|
|
response 15 of 32:
|
Jun 4 23:32 UTC 1993 |
The non-shareware Procomm (PCPLUS) supports several more scrollback buffer
functions, including writing sections to file, FWIW.
|
rcurl
|
|
response 16 of 32:
|
Jun 5 05:30 UTC 1993 |
I should have paid the extra for PLUS, instead of just registering
2.4.2 (or whatever it was). I suppose I could upgrade for not much.
|
popcorn
|
|
response 17 of 32:
|
Jun 6 00:01 UTC 1993 |
This response has been erased.
|
kaplan
|
|
response 18 of 32:
|
Feb 4 14:55 UTC 1994 |
I use procomm 2.4.2 (shareware) and you can use alt-G to save a screen-
full of stuff in the scrollback buffer to procomm.img
|
rcurl
|
|
response 19 of 32:
|
Feb 5 06:13 UTC 1994 |
That's been upgraded to 2.4.3 (in 1989 - cutting edge!). They added
Ymodem-G.
|
davel
|
|
response 20 of 32:
|
Feb 5 12:01 UTC 1994 |
2.4.2 was intended to be the last shareware release, I think, when they
decided to create Procomm Plus and market it in other ways. They
eventually added ymodem-G and maybe cleaned up a couple more minor things,
calling it 2.4.3, but I believe that once Plus came out there was never any
intention of doing further enhancements of the shareware version. So it's
not cutting-edge, but it's pretty cheap & pretty good, as far as it goes.
|
toking
|
|
response 21 of 32:
|
May 23 23:20 UTC 1995 |
helppppppp!!!!!! I'm on an old tandy 1000hx now and the program (bitcom)
seems to like to double space everything!!@ does anyone know how to stop mit
????????????????
|
davel
|
|
response 22 of 32:
|
May 24 00:36 UTC 1995 |
What you typed looks fine here, to me anyway. When you say "double space"
do you mean:
- empty lines between lines you type?
- blank spaces between letters you type?
- duplicates of letters you type?
If the first, you may be sending a carriage return AND a newline as your
line terminator. This is normal for DOS but not for most of the rest of
the world. Depending on what terminal you're emulating, it would be one
or the other (but I'd say a carriage return is the likely one).
If the third, you're set to HDX (half duplex) instead of FDX (full duplex).
Change that & you should be OK.
If the second, I have no idea. Sorry.
|
toking
|
|
response 23 of 32:
|
May 26 21:34 UTC 1995 |
ok...how do I change between HDX and FDX????
|
popcorn
|
|
response 24 of 32:
|
May 28 13:34 UTC 1995 |
This response has been erased.
|