Message-Id: <199905181753.RAA88756@out5.ibm.net> From: "Mark E." To: djgpp-workers AT delorie DOT com Date: Tue, 18 May 1999 13:54:40 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: termios and raw mode In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.11) Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Does anybody see any harm that would be done by this change? In > particular, Mark, could you please see if Bash ever switches one of > its handles to binary mode, and if so, will this somehow affect it? > Bash does switch buffered input handles to binary if the lseek works on the handle. But since stdin is never buffered, your change should not affect Bash. In looking at the modified version of tminit.c in Bash 2.03 because of your question, I came across some code that I'm not sure is correct. The modified tminit.c hooks handles 0, 1, and 2 to call a fsext handler (__libc_termios_fsext) which in the case of __FSEXT_write always uses __libc_termios_write_raw_tty to write out the output. Does this sound correct? If you need to see the source for this tmint.c, it's available by itself from my site's Bash download menu. The site is down because of a server upgrade, so I can sent it to you directly if it's down too long. The CVS version of tminit.c gets by without a fsext hook. So I have wonder if a fsext hook is really needed? I've already stripped out the keyboard support through BIOS in the early betas, so it wouldn't suprise me if more could to be removed. --- Mark Elbrecht, snowball3 AT bigfoot DOT com http://snowball.frogspace.net/