Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!bbn!jr@bbn.com From: jr@bbn.com (John Robinson) Newsgroups: gnu.bash.bug Subject: Re: Bash-1.04 and modems Message-ID: <51045@bbn.COM> Date: 17 Jan 90 18:37:58 GMT References: <50659@bbn.COM> Sender: news@bbn.COM Reply-To: jr@bbn.com (John Robinson) Distribution: gnu Organization: BBN Systems and Technologies Corporation, Cambridge MA Lines: 26 In-reply-to: news@bbn.COM (News system owner ID) In article <50659@bbn.COM>, pplacewa@antares.bbn.com (Paul W Placeway) writes: >brian@radio.astro.utoronto.ca (Brian Glendenning) writes: >< >< I have been using bash-1.02 instead of 1.04 for a while because when I >< use bash-1.04 over a modem something weird happens. In particular, >< about every other character forces a beep from the shell using the >< default e71, they all echo ok at n81, but escape codes get fouled up. > >Bash 1.04 seems to be ignoring the parity setting (and resetting it). >(Hint: this is unwise...) It looks like 1.02 was doing the right >thing; that behaviour should probably be restored. Yeah, I am seeing something like this too. Worked okay in 1.03 as best I can recall. Passing through a telnet connection seems to insulate the modem/terminal from bash, as a workaround. I will test this against a Vax-Ultrix bash-1.04 tonight or tomorrow night. Possibly related, in an xterm (X11R4) window I find that bash is forcing the stty pass8 bit (Sun OS3.5; 3/50M) off on me; for a workaround I put a "stty pass8" in my PROMPT_COMMAND (kludgy). Anyone understand this? Is there some way to tell bash to leave the tty modes alone? -- /jr, nee John Robinson Life did not take over the globe by combat, jr@bbn.com or bbn!jr but by networking -- Lynn Margulis