Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Kernel Hacks & Weird Filenames
Message-ID: <11204@mimsy.UUCP>
Date: 25 Apr 88 04:16:31 GMT
References: <13041@brl-adm.ARPA> <4895@chinet.UUCP> <11153@mimsy.UUCP> <4911@chinet.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 31

>In article <11153@mimsy.UUCP> I wrote:
>>First, `non-printable characters'.  Well, there are certainly numerous
>>characters that cannot be printed on the terminal I am using at the
>>moment (namely my H19).  But this is not precisely the same set as are
>>non-printable on other displays.

In article <4911@chinet.UUCP> les@chinet.UUCP (Leslie Mikesell) writes:
>How many terminals do anything reasonable with ESC in random places? 

Some of them print `EC' (in one character space, raised E, lowered C).
On those, ESC is a printing character, and if you want to use it in a
file name, that is fine with me.

>>Second: are file names to be printed?  Certainly most are.  But there
>>are some that are not---for instance, the lock files used by ....

>Would you enjoy debugging the operation of said locks if displaying
>the filenames performed random cursor motions or cleared the screen
>before you could see them.

But it does not.  (`ls' prints `?' for control characters; `ls|cat -v'
expands them; other programs have other means of displaying them.)

>It just adds another reason to place some sort of silly user agent
>between the user and the system.

There is *always* a user agent (often more than one) between the
user and the system.  I do not know what you mean here.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris