GNU Teseq is a tool for translating files that contain control
characters and terminal control sequences, into human-understandable
text. It is intended to aid in debugging problems in terminal
emulators, software that makes use of special terminal features, and
interactions between the two.
Teseq is primarily targeted at individuals who possess a basic
understanding of terminal control sequences, especially CSI sequences;
however, by default Teseq will try to identify and describe the
sequences that it encounters, and the behavior they might produce in a
terminal.
Teseq describes control functions as they are interpreted by
VT100-compatible terminals, and/or terminals compliant with the ECMA-48 /
ISO/IEC 6429 standard. Teseq does _not_ support describing control
functions according to terminal-specific definitions in a database such
as termcap or terminfo, though future versions may include limited
support for that (*note Future Enhancements::). Therefore, the
descriptions Teseq uses for control functions may not necessarily match
their actual interpretation by whatever terminal device the characters
were actually intended for
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
misc: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Aaron Dalton <aaron@FreeBSD.org>
* Adam Weinberger <adam@vectors.cx>
* Adam Weinberger <adamw@FreeBSD.org>
* Akinori MUSHA aka knu <knu@idaemons.org>
* Alan E <alane@FreeBSD.org>
* Alex Semenyaka <alex@rinet.ru>
* Alex Stangl <alex@stangl.us>
* Alexander Logvinov <avl@FreeBSD.org>
* Alexander Logvinov <ports@logvinov.com>
* Alexander Nusov <alexander.nusov@nfvexpress.com>
* Alexander Timoshenko <gonzo@univ.kiev.ua>
(Only the first 15 lines of the commit message are shown above )
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
GNU Teseq is a tool for translating files that contain control
characters and terminal control sequences, into human-understandable
text. It is intended to aid in debugging problems in terminal
emulators, software that makes use of special terminal features, and
interactions between the two.
Teseq is primarily targeted at individuals who possess a basic
understanding of terminal control sequences, especially CSI sequences;
however, by default Teseq will try to identify and describe the
sequences that it encounters, and the behavior they might produce in a
terminal.
Teseq describes control functions as they are interpreted by
VT100-compatible terminals, and/or terminals compliant with the ECMA-48 /
ISO/IEC 6429 standard. Teseq does _not_ support describing control
functions according to terminal-specific definitions in a database such
as termcap or terminfo, though future versions may include limited
support for that (*note Future Enhancements::). Therefore, the
descriptions Teseq uses for control functions may not necessarily match
their actual interpretation by whatever terminal device the characters
were actually intended for
WWW: http://www.gnu.org/software/teseq/
