I've got a slight problem with a very stubborn error during an rsync. It's caused by a file with a special character in its filename. There's been others but I could sort that out by doing some conversion in the encoding of the filename. However this one file I can't even find.

So here's what rsync says:

../.\#033OA.tex.pyD0MB" failed: No such file or directory (2)

First thing one notices is that the character code can't be hex or octal so I've googled it and only found this. So it may be a CURSOR UP character (or not). I've tried

ls -la *`printf '\033OA'`*

to no avail. I've also tried piping the output of ls of that directory to od to no avail.

ls -aq will print all file names, with a ? instead of each nonprintable character. On many unix variants, ls -AB or ls -Ab (check your man page) will print octal escapes. With ls -aq, you can use the displayed output as a shell pattern.

@luxifer There's a . at the beginning of the file name, so you need ls -Aq or ls -aq. And if you use shell wildcards, you need to make the . explicit: * won't include the file but .* will.
–
GillesSep 1 '11 at 6:31

no there wasn't! The output I posted was from rsync and it was the end of the line. Rsync first copys to $DESTINATION/.$FILENAME before it moves the file to it's correct name. Therefor at the source the file had no . at the beginning of its name. Also, as said, ls -q wouldn't have shown the file whereas ls -b did.
–
luxiferSep 5 '11 at 6:23