Date: Sat, 28 Jun 2008 20:28:32 -0400 From: Thomas Dickey <dickey@radix.net> To: freebsd-questions@freebsd.org Subject: Re: null bytes after ANSI sequences in color 'ls' output Message-ID: <20080629002831.GA26661@saltmine.radix.net> In-Reply-To: <20080628201621.GB4081@dan.emsphone.com> References: <20080628024552.81805.qmail@hyperreal.org> <20080628113957.GA25335@saltmine.radix.net> <20080628201621.GB4081@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 28, 2008 at 03:16:21PM -0500, Dan Nelson wrote: > In the last episode (Jun 28), Thomas Dickey said: > > It's possible that an application could be sending padding characters > > (nulls). The vt100-color terminal description inherits from vt100, > > which does use padding - but in the sf/sr (scroll forward/reverse). >=20 > If that's the case, then the easy fix would be to tell SecureCRT to > emulate am xterm instead, and set the terminal type to xterm-color.=20 > You would probably get better function key mappings, too. yes (xterm wouldn't have padding ;-) --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFIZtcXtIqByHxlDocRAg7GAKClZKfHD0Ej4o60B3fEwiQhd8QXzgCcCbz6 qzgXsg+jkMe2ksSCg7eM2hA= =oJSI -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080629002831.GA26661>