zsh-workers
 help / color / mirror / code / Atom feed
From: Paul Lew <lew@ezdzit.zko.dec.com>
To: Peter Stephenson <pws@ifh.de>
Cc: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: possible 3.1.4 bug - echotc
Date: Thu, 20 Aug 1998 08:35:43 -0400	[thread overview]
Message-ID: <9808201235.AA01061@ezdzit.zko.dec.com> (raw)
In-Reply-To: <199808191354.PAA13093@hydra.ifh.de>

>>>>> "Peter" == Peter Stephenson <pws@ifh.de> writes:

    Peter> Paul Lew wrote:
    >> Just found out echotc behave differently on 3.0.[35] and 3.1.4:
    >> 
    >> $ echotc so | od -c			 3.0.3, 3.0.5, 3.1.3
    >> 0000000  033   [   7   m
    >> 0000004
    >> 
    >> $ echotc so | od -c			 3.1.4
    >> 0000000    n   o  \n
    >> 0000003
    >> 
    >> Bug or feature?

    Peter> I've had problems with AIX, here, but judging from your
    Peter> domain, that's not the problem.  If it's related... try
    Peter> searching for #ifndef NCURSES_VERSION in Src/builtin.c, and
    Peter> changing it to #if 1.  If that fixes it, we'll have to be
    Peter> more careful in testing for ncurses.

The above change fixes the echotc problem.  While doing this change, I
noticed a 'core' file in the root directory.  It is from 'conftest'.
which is generated by 'configure'.  Any trick to debug 'configure'?

I also got:

       zsh: bad math expression: unbalanced stack

when I tried the basic <TAB> on any directory.  I guess this might be
related to the conftest failure.

Thanks..

BTW, environment info:

zsh:		 3.1.4
OS:		 Digital UNIX 3.2c
Compiler:	 gcc -v
Reading specs from /usr/local/lib/gcc-lib/alpha-dec-osf3.2/egcs-2.90.29/specs
gcc version egcs-2.90.29 980515 (egcs-1.0.3 release)


  reply	other threads:[~1998-08-20 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-19 12:44 Paul Lew
1998-08-19 13:54 ` Peter Stephenson
1998-08-20 12:35   ` Paul Lew [this message]
1998-08-20 13:01     ` Zefram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9808201235.AA01061@ezdzit.zko.dec.com \
    --to=lew@ezdzit.zko.dec.com \
    --cc=pws@ifh.de \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).