Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: TERM setting influences `case' reserved word

X-seq: zsh-workers 508
From: hzoli@xxxxxxxxxx (Zoltan Hidvegi)
To: rl@xxxxxxxxxxxxxxxxxxxx
Subject: Re: TERM setting influences `case' reserved word
Date: Sun, 29 Oct 1995 01:01:56 +0100 (MET)
Cc: zsh-workers@xxxxxxxxxxxxxxx (zsh-workers)
In-reply-to: <199510281943.VAA17570@xxxxxxxxxxxxxxxxxxxx> from "Zvi Har'El" at Oct 28, 95 09:43:21 pm

Zvi Har'El wrote:
> 
> Hi there, 
> I am using zsh 2.6-beta10, with history patches in archive/337 and 376.
> I compiled it with gnu termcap 1.3 and gcc 2.7.0 on a sparcstation running
> SunOS 4.1.3. I have a very surprizing problem. Certain settings of the TERM 
> environment variable make the `case' reserved word change its behaviour, and a 
> statment lime `case $i in' yields `command not found: case'. For example, 
> TERM=xterms produces the problem, while TERM=xterm and TERM=xterm24 do not! 

A while ago someone reported that some systems has a bug in the termcap
library which causes problems when a termcap entry is longer that 1024 bytes.
It may be possible that you have such a problem.  I tried this on a SunOS
4.1.3 machine and I was unable to reproduce it.

Cheers,

   Zoltan

Follow-Ups:
- Re: TERM setting influences `case' reserved word
  - From: Zvi Har'El

References:
- TERM setting influences `case' reserved word
  - From: Zvi Har'El

Messages sorted by: Reverse Date, Date, Thread, Author