From kenm@u.washington.edu Fri Jul 1 12:57:00 PDT 1994 >From kenm@u.washington.edu Fri Jul 1 12:56:59 1994 Return-Path: Received: from homer06.u.washington.edu by wells.u.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA18110; Fri, 1 Jul 94 12:56:59 -0700 Received: by homer06.u.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA18578; Fri, 1 Jul 94 12:56:58 -0700 X-Sender: kenm@homer06.u.washington.edu Date: Fri, 1 Jul 1994 12:56:58 -0700 (PDT) From: Ken Marquess Subject: 07/06: mead* tscan enhancements To: change-l@u.washington.edu Cc: Robert Jamieson Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've made some updates to tscan. The new version can be previewed as ~kenm/newtscan/tscan. The new 'features' are: 1)The old tscan would display the data as either text (ascii or ebcdic) or in hex. Displaying binary data as text led to the obvious results when bytes corresponding to NULL, newline, etc were written to the terminal. The hex display was intended for these times. Unfortunately, we underestimated the number of hexadecimally challenged people. In an effort to cater to those people, we have added a new 'nondisp' feature. This will translate nonprintable characters to a specified character (default='.') when displaying text data. The character can be specified by the 'NonDisp c' command, or this feature can be disabled by 'NonDisp none'. 2)'SLTapeMap *' is now a synonym for 'SLTapeMap 9999999999999999'. 3)Bug fix: When scrolling using the 'Left' and 'Right' commands without specifying the number of columns, tscan scrolls the number of columns that will fit on the window (however wide that may be). The window size was not being halved when in hex mode. The display of one byte takes two columns in hex mode, so if bytes 1-20 were being displayed in a window that had 40 columns for the display, and you went 'Right', you would see columns 41-60, not 21-40. This has been fixed. .