zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Make Failure on SunOS-4.1
Date: Wed, 25 Apr 2001 14:41:52 +0000	[thread overview]
Message-ID: <1010425144152.ZM11080@candle.brasslantern.com> (raw)
In-Reply-To: <Tc0a88d015321834e70@mailsweeper01.cambridgesiliconradio.com>

On Apr 25, 10:55am, Peter Stephenson wrote:
} Subject: Re: Make Failure on SunOS-4.1
}
} I don't want to produce a `final' pre-release until the termcap problems
} have gone.  Is there something else to back out?

We could back out the `termcap' parameter entirely, and we could back out
the ability to use ${(k)terminfo} -- those were the changes that started
requiring the ncurses header files to be included even on systems that
have the old termcap as well.

Or we could change the termcap-search-order in configure.in to always try
to find ncurses first, and skip defining HAVE_TERMCAP_H when we find the
ncurses headers.  (My understanding is that in the distant past of zsh,
there were some who objected to linking the shell against curses when it
would be sufficient to link against termcap, because curses is bloated.)

Or we could add another --enable flag, which switches between the two
states described above (in which case it should probably disable the
terminfo parameter entirely rather than just crippling it).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-04-25 14:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 19:43 Vin Shelton
2001-04-25  4:13 ` Bart Schaefer
2001-04-25  9:55   ` Peter Stephenson
2001-04-25 14:41     ` Bart Schaefer [this message]
2001-04-25 14:57       ` Clint Adams
2001-04-25 14:29   ` Vin Shelton
2001-04-25 14:58     ` Bart Schaefer
2001-04-25 18:03       ` Vin Shelton
2001-04-26  4:27         ` Bart Schaefer
2001-04-26  4:35           ` Make Failure on SunOS-4.1 (correction) Bart Schaefer
2001-04-26 12:50             ` Vin Shelton
2001-04-26 13:06               ` Or on ReliantUNIX ... " Andrej Borsenkow
2001-04-26 13:15                 ` Clint Adams
2001-04-26 13:25                   ` Andrej Borsenkow
2001-04-26 13:30                     ` Clint Adams
2001-04-26 14:02                       ` Andrej Borsenkow
2001-04-26 14:20                         ` Clint Adams
2001-04-26 14:35                 ` Bart Schaefer
2001-04-26 14:52                   ` Andrej Borsenkow
2001-04-26 14:58                     ` Clint Adams
2001-04-26 15:32                       ` Bart Schaefer
2001-04-26 15:52                         ` Clint Adams

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=1010425144152.ZM11080@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).