Zsh Mailing List Archive
Messages sorted by:
Re: typeahead fix
- X-seq: zsh-workers 90
- From: Richard Coleman <coleman@xxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: typeahead fix
- Date: Thu, 08 Jun 1995 14:59:54 -0400
- In-reply-to: Your message of "Thu, 08 Jun 1995 12:17:34 BST." <12218.9506081117@xxxxxxxxxxxxxxx>
> In fact, the code is there already, #ifdef'd behind a test for
> CLOBBERS_TYPEAHEAD (actually, that was a bit of a giveaway). This is
> one of the old buildzsh definitions that hasn't made it into configure
> yet. The problem is that it's not that easy to test. I've therefore
> just added an ad hoc test for Ultrix to configure.in.
> By the way, there's another phantom preprocessor definition:
> TTY_NEEDS_DRAINING. Someone, somewhere may find this coming back to
> haunt them.
I've looked through the configuration scripts for zsh 2.5.03 and it
defines CLOBBERS_TYPEAHEAD for ultrix and dgux. It defines
TTY_NEEDS_DRAINING for ultrix. People on these machines should check
whether either of these are needed.
What is the relationship/lineage between ultrix and dgux?
I've changed the patch around a little. Test this and make sure it is
*** configure.in 1995/05/23 03:50:13 1.23
--- configure.in 1995/06/08 18:36:36 1.25
*** 414,419 ****
--- 414,433 ----
+ dnl Some systems clobber typeahead when you go from canonical input
+ dnl processing to non-canonical, so we need a FIONREAD ioctl.
+ dnl I don't know how to check this with configure, so I am using the
+ dnl system names directly.
+ dnl The doubled square brackets are necessary because autoconf uses m4.
+ AC_MSG_CHECKING(if typeahead needs FIONREAD)
+ [test `echo $host_os | sed 's/^\([[a-z]]*\).*/\1/'` = ultrix &&
+ zsh_cv_clobbers_typeahead=yes || zsh_cv_clobbers_typeahead=no])
+ if test $zsh_cv_clobbers_typeahead = yes; then
AC_OUTPUT(Makefile Src/Makefile Doc/Makefile Etc/Makefile Misc/Makefile \
Util/Makefile Functions/Makefile Startup_Files/Makefile, \
Messages sorted by: