<!--
****************************************************************************
- * Copyright 2018-2022,2023 Thomas E. Dickey *
+ * Copyright 2018-2023,2024 Thomas E. Dickey *
* Copyright 1998-2017,2018 Free Software Foundation, Inc. *
* *
* Permission is hereby granted, free of charge, to any person obtaining a *
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: curs_termcap.3x,v 1.81 2023/12/30 21:27:22 tom Exp @
- * See <https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/src/\
- * termlib/termcap.c>.
- * See https://www.oreilly.com/openbook/opensources/book/kirkmck.html
- * for much BSD release history.
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=1BSD/s7/ttycap.c
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=1BSD/man7/ttycap.7
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/src/termlib/
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/bin/etc/termcap
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/src/lib/\
- * libtermlib/
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/man/man3/\
- * termlib.3
- * ...except in the source tree...
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=4BSD/usr/src/lib/\
- * libtermlib/makefile
- * Observe the `tncktc()`, `tnamatch()`, `tskip()`, and `tdecode()`
- * entry points disappearing from termcap.c.
- * 2BSD became a branch retaining support for non-virtual memory
- * systems (such as the PDP-11) whereas most BSD development focused on
- * the VAX and other VM-enabled systems starting with 3BSD.
- * This man page previously located a termcap.h in 2BSD, but that may
- * be confusion arising from its backport to 2.9BSD (and still present
- * in surviving sources for 2.11BSD, the "end of the line" for that
- * branch's development).
- * Observe the copyright notice in
- * https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD/usr/contrib/\
- * jove/Makefile
- * --much too late for 2BSD (1979).
+ * @Id: curs_termcap.3x,v 1.85 2024/04/20 19:13:12 tom Exp @
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="generator" content="Manpage converted by man2html - see https://invisible-island.net/scripts/readme.html#others_scripts">
-<TITLE>curs_termcap 3x 2023-12-30 ncurses 6.4 Library calls</TITLE>
+<TITLE>curs_termcap 3x 2024-04-20 ncurses 6.5 Library calls</TITLE>
<link rel="author" href="mailto:bug-ncurses@gnu.org">
</HEAD>
<BODY>
-<H1 class="no-header">curs_termcap 3x 2023-12-30 ncurses 6.4 Library calls</H1>
+<H1 class="no-header">curs_termcap 3x 2024-04-20 ncurses 6.5 Library calls</H1>
<PRE>
<STRONG><A HREF="curs_termcap.3x.html">curs_termcap(3x)</A></STRONG> Library calls <STRONG><A HREF="curs_termcap.3x.html">curs_termcap(3x)</A></STRONG>
implementations conforming to portions of X/Open Curses now
withdrawn. The BSD <EM>termcap</EM> library would store a copy of the
terminal type description in the area referenced by this
- pointer. <EM>ncurses</EM> stores terminal type descriptions in compiled
+ pointer. <EM>terminfo</EM> stores terminal type descriptions in compiled
form, which is not the same thing.
<STRONG>o</STRONG> The meanings of the return values differ. The BSD <EM>termcap</EM>
parameterized string capability, be aware that it is returned in <EM>term-</EM>
<EM>info</EM> notation, not the older and not-quite-compatible <EM>termcap</EM> notation.
This does not cause problems if all you do with it is call <STRONG>tgoto</STRONG> or
- <STRONG>tparm</STRONG>, which both expand <EM>terminfo</EM>-style strings as <EM>terminfo</EM> does. (If
- <EM>ncurses</EM> is configured to support <EM>termcap,</EM> <STRONG>tgoto</STRONG> checks whether the
- string is <EM>terminfo</EM>-style by looking for "<STRONG>%p</STRONG>" parameters or "<STRONG><</STRONG>...<STRONG>></STRONG>"
- delays, and invokes a <EM>termcap</EM>-style parser if the string appears not to
- use <EM>terminfo</EM> syntax.)
+ <STRONG>tparm</STRONG>, which both parametrically expand <EM>terminfo</EM>-style string
+ capabilities as <EM>terminfo</EM> does. (If <EM>ncurses</EM> is configured to support
+ <EM>termcap,</EM> <STRONG>tgoto</STRONG> checks whether the string is <EM>terminfo</EM>-style by looking
+ for "<STRONG>%p</STRONG>" parameters or "<STRONG><</STRONG>...<STRONG>></STRONG>" delays, and invokes a <EM>termcap</EM>-style
+ parser if the string appears not to use <EM>terminfo</EM> syntax.)
Because <EM>terminfo</EM>'s syntax for padding in string capabilities differs
from <EM>termcap</EM>'s, users can be surprised.
-ncurses 6.4 2023-12-30 <STRONG><A HREF="curs_termcap.3x.html">curs_termcap(3x)</A></STRONG>
+ncurses 6.5 2024-04-20 <STRONG><A HREF="curs_termcap.3x.html">curs_termcap(3x)</A></STRONG>
</PRE>
<div class="nav">
<ul>