Path: utzoo!attcan!uunet!mplex!ror
From: ror@mplex.UUCP (Richard O'Rourke)
Newsgroups: comp.unix.questions
Subject: Re: Need help reading a file with unusual name(s)
Keywords: help!
Message-ID: <273@mplex.UUCP>
Date: 19 Apr 89 06:57:43 GMT
References: <579@netcom.UUCP> <123@tslanpar.UUCP> <1460@auspex.auspex.com>
Reply-To: ror@.UUCP (Richard O'Rourke)
Distribution: na
Organization: RFM Microplex Systems Ltd.
Lines: 39

In article <1460@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>>	to edit "maps\033w" type "vi maps\\033w".  This interprets the
>>backslash as a literal charachter rather that the introducer to a special
>>charachter.
>
>"\033" doesn't mean "the character backslash, followed by the character

[ lots deleted ]

>"filename?" will match all files whose names consist of "filename"
>followed by any character, including CR; the "?" matches any character.

[ more deleted 
Some stuff about about creating a directory and moving the file with
funny name somewhere else to deal with it.... ]

>(Yes, this is a bit painful, and can be taken out of context and used to
>bash UNIX.  I suspect the same could be done with just about any other

Too muck work.
Why not:

vi filename[!\ -\~]

which is still not perfect, but probably eliminates any files with
names that are valid.  It even eliminates files that have a trailing
space.  If the file you are after has a trailing space do this:

vi filename[!\!-\~]     # Gets trailing non-printables

these work on my version of ksh anyway.  Assumes ASCII.

-------- Opinions expressed above are not necessarily anyone elses
                      |  Voice: 604 w 875-1461  | h 438-8249
Richard O' Rourke     |  Mail:  uunet!mplex!ror
-- 
-------- Opinions expressed above are not necessarily anyone elses
                      |  Voice: 604 w 875-1461  | h 438-8249
Richard O' Rourke     |  Mail:  uunet!mplex!ror