summaryrefslogtreecommitdiff
path: root/misc/teseq
AgeCommit message (Collapse)AuthorFilesLines
2016-07-09Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.wiz1-1/+2
2015-11-03Add SHA512 digests for distfiles for misc categoryagc1-1/+2
Problems found locating distfiles: Package colorls: missing distfile ls.tar.gz Package molden: missing distfile molden-4.6/molden4.6.tar.gz Package softmaker-office-demo: missing distfile ofl06trial.tgz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-08-21Update to 1.1.1:wiz2-15/+8
Version 1.1.1 * Updated all files to reflect new email address for maintainer: micah@addictivecode.org (previous address, micah@cowan.name, is no longer valid) * Added links in the (Texinfo) manual to playable videos that demonstrate basic teseq functionality, and how to use teseq to create _and edit_ interactive terminal demos: * https://asciinema.org/a/7443 * https://asciinema.org/a/7445 * Added example in the manual for using teseq to strip escapes out of a typescript file. * Note: a new (optional) build dependency has been introduced: pkg-config, which is now used to find whether libcheck is installed. * BUG FIX: Fixed an issue where teseq could spin indefinitely churning out \xFF bytes on no further input. Input from a command such as $ printf '\033!!\177' would produce this issue. This issue was discovered by means of american fuzzy lop, http://lcamtuf.coredump.cx/afl/ * BUG FIX: Fixed an issue with \x7F (DEL) being treated as a valid final character for control sequences, and being printed on teseq's output (which should not be printing non-whitespace control characters).
2015-06-12Recursive PKGREVISION bump for all packages mentioning 'perl',wiz1-2/+2
having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2014-05-29Bump for perl-5.20.0.wiz1-1/+2
Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2013-10-29USE_LANGUAGES=c99, fixes build on SunOS.jperkin1-1/+2
2013-08-18Update to 1.1. Changes:shattered3-9/+7
* Colorized output now supported via the --color (or --colour) option, and the TESEQ_COLORS environment variable. * Descriptions and labels for non-standard controls from DEC, Xterm, Rxvt, etc, are now always issued, without the need for the -x option. * Reseq now recognizes "halt" (@@@) lines (with --halts option), waiting for keypress before continuing. * Teseq now identifies which charset is being switched, by its ISO IR registration. * BUG FIX: Teseq could crash on the input, `\033$z'.
2013-05-31Bump all packages for perl-5.18, thatwiz1-2/+2
a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
2012-10-08Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.asau1-3/+1
2012-10-03Bump all packages that use perl, or depend on a p5-* package, orwiz1-1/+2
are called p5-*. I hope that's all of them.
2011-02-28Reset maintainer for retired developers.wiz1-2/+2
2008-08-28Import teseq-1.0.0 as pkgsrc/misc/teseq.bjs4-0/+74
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.