From: "Cygwin tack Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@Cygwin.com>
Subject: Updated: tack 1.10+20240501
Date: Sat, 04 May 2024 13:33:45 -0600 [thread overview]
Message-ID: <20240504133345.63716-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
terminfo file diagnostic
The following packages have been upgraded in the Cygwin distribution:
* tack 1.10+20240501
Terminfo Action ChecKer is a diagnostic designed to create,
verify, and refine terminal information descriptions.
For more information see the project home page:
https://invisible-island.net/ncurses/tack.html
For changes please see below or read /usr/share/doc/tack/CHANGES
after installation:
https://invisible-island.net/ncurses/tack/CHANGES.html
1.10 2024-05-01
- init.c, configure.in, package/tack.spec, package/debian/changelog,
tack.h, HISTORY: bump to 1.10
- configure: regen
- configure.in: add a configure-check if terminfo functions use "const"
strings, to fix compiler warnings with NetBSD
- init.c, edit.c: gcc warning (NetBSD)
- edit.c: check to avoid printing a non-printable character, per Coverity
- tack.c: initialize variables, per Coverity
- aclocal.m4: correction for CF_ANSI_CC_CHECK, works around MacOS "c89"
confusion of "-O"
- tack.1: change limit for SGR tool to allow for aixterm's colors
- ansi.c: change the SGR tool to show up to 120 (past aixterm's 108)
- color.c: when reloading the colors 0-7, use the index for the named
color rather than just the array-index (fixing an interchanged
red/blue for instance). Also, initialize the palette using the ANSI
codes if the terminal supports setaf/setab.
- color.c, charset.c, ansi.c, edit.c, crum.c, pad.c, tack.c, tack.h:
use "const" in a few places reported by cppcheck
- tack.1: improve formatting/style
- aclocal.m4: resync with my-autoconf, fixing compiler-warnings inside
configure script
- config.sub, config.guess: update
reply other threads:[~2024-05-04 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240504133345.63716-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@Cygwin.com \
--cc=cygwin@Cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).