Date: Wed, 17 Apr 1996 15:56:26 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: richardc@CSUA.Berkeley.EDU (Richard Chang) Cc: terry@lambert.org, questions@FreeBSD.ORG Subject: Re: Keyboard bindings Message-ID: <199604172256.PAA02902@phaeton.artisoft.com> In-Reply-To: <Pine.PTX.3.91.960417151144.2439l-100000@soda.CSUA.Berkeley.EDU> from "Richard Chang" at Apr 17, 96 03:13:21 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I had a question for the longest time. I notice on the console, > > > CTRL-O would work for things you are running locally but not on > > > telnet/rlogin connections but it does work when you connect from anywhere > > > else besides a FreeBSD machine, any ideas? Thanks! > > > > Consider 4.3 vs. 4.2 OOB data propagation and supported signals > > for the rlogin and telnet protocols in the RFC's. > > Hmmm, now why did every other CTRL combination work except for CTRL-O? > Isn't pine/pico developed on Ultrix which is BSD 4.3 based but they still > supported CTRL-O? Discard is a cannonical processing capability, not a transported (ie: capable of being sent out of band) signal. Only transported signals work like you want ^O to work... you need to get a faster link or reduce time between packet reception and output buffer flushing to make it work. It's not done by default because (a) it would slow down average throughput, and (b) no one but VMS/.TOPS-20 hold-overs use ^O. ;-). Alternately, you could reabstract the ^O implementation to make it into a signal... lotta work, that. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604172256.PAA02902>