Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.wizards
Subject: Re: Ugly file name
Message-ID: <8474@chinet.chi.il.us>
Date: 17 May 89 17:31:02 GMT
References: <105096@sun.Eng.Sun.COM> <9001@csli.Stanford.EDU>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 18

In article <9001@csli.Stanford.EDU> gandalf@csli.stanford.edu (Juergen Wagner) writes:
>Several alternatives have been suggested to uniquely identify the file
>to be removed. However, there are cases in which `rm' won't do the job
>of deleting the file because the shell which is used to run `rm' may
>strip the eighth bit off characters [some shells do]. In such cases, it
>is impossible to remove the file with `rm'. You could do a clri and fsck
>but that is a little bit of overkill. A short C program will do (see my
>other posting).

On at least some machines (e.g 3B1), even rm -i * won't work to
delete a file where the name has a character with the high bit set.
The easiest way is to use dired in GNU emacs if you happen to have it.
Emacs is what created the file in the first place - the 3B1 has a key
labeled <break> which happens to generate x'FF' (which doesn't
work as a break unless you happen to be cu'd through a 7-bit link to
something else), and emacs rightly accepted it like any other key.

Les Mikesell