Actually, I have been using filename completion in all of the examples
contained in my original email. I even tried tcsh to double check that it
wasn't a problem with bash's autocomplete.
/tom
On Tue, 27 Jul 2004, Greg Folkert wrote:
> On Tue, 2004-07-27 at 14:35, Thomas Meggs wrote:
> > Here is example output:
> >
> > # ls -i
> > ls: egotrippi_-_??l??_koskaan_ikin??.mp3: No such file or directory
> > [ output does not contain the inode/file listing ]
> >
> > /tom
> >
> > On Tue, 27 Jul 2004, Joris Huizer wrote:
> >
> > > Maybe you can try,
> > > ls -i
> > > and then,
> > > find . -inum <number of ls -i> -ok mv '{}' myfile \;
>
> Are you using BASH?
>
> If so try:
>
> rm egotrippi_-_\?\?l\?\?_koskaan_ikin\?\?.mp3
>
> or try <TAB-TAB> after every char until you get it. More than once I
> have had similar problems... I have ALWAYS been able to get either way
> to work. And yes, I have had nice names with some really nice
> conventions. scary it can be done.
>
> Luck.
> --
> greg, [EMAIL PROTECTED]
>
> The technology that is
> Stronger, better, faster: Linux
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
