Am Dienstag, 28.01.03 um 03:29 Uhr schrieb Wayne O. Cochran:
> > Quoting "Pierre R. Mai" <[EMAIL PROTECTED]>: > >> This should work, and it does for me, at least using an OS X >> terminal.app to log into one of my Linux boxen. <snip> > > Actually, when I use xterm on a linux box all is well. > The problem is when I used the "OS X terminal.app" and I > am ssh'ed into a Linux box. > >> Also, this isn't >> really a CMUCL-specific problem, as CMUCL just uses normal I/O, and >> doesn't meddle with tty settings. �I.e. anything that works for you >> with e.g. cat, should also work for CMUCL... > > So I see, backspace just echoes ^? > > $ cat > crap > asdf^?^?^?^? > ^d > $ stty > speed 38400 baud; line = 0; > erase = ^H; > -brkint -imaxbel > > hmmm.... obviously a deeper issue... When backspace echoes ^? (i.e. delete), setting the erase character to this should definitely work, i.e.: bash$ stty speed 38400 baud; line = 0; erase = ^H; -brkint -imaxbel bash$ stty erase ^? bash$ stty speed 38400 baud; line = 0; -brkint -imaxbel bash$ cat > /dev/null a (i.e. the last line showed correct operations of backspace). This definitely works for me going from Apple's Terminal.app via openssh to various Linux boxen (where in fact, the erase character defaults to ^?, hence no playing around with stty required). You might also want to check that the first option on Terminal.app's Emulation setting isn't checked, or, when it is checked, that you've made ^H the erase char with stty. Hope this helps a bit, Regs, Pierre. -- Pierre R. Mai <[EMAIL PROTECTED]> http://www.pmsf.de/pmai/ The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents. -- Nathaniel Borenstein
