[Gregg Bell]

Originally Posted by avantman42

I'd have expected the apostrophe to cause a problem, rather than the comma. Either way, wrapping the file name in speech marks, or adding a backslash immediately before the problem character, will solve the problem:

"Bell,Gregg.-.Jamie's.Gamble[06.18.2013].epub"
Bell\,Gregg.-.Jamie's.Gamble[06.18.2013].epub

Russ

Thanks, Russ. Did the quotation marks. Works great. Appreciate it. (REALLY glad there was a way out of this without re-naming.)

Originally Posted by eschwartz

You can also begin the filename, then press TAB to autocomplete. (This works for all filepaths, as well as commands. If there is only one possible choice based on what you have filled in, it will fill in the rest. If there are multiple options, one TAB will fill in to the first point where you have a choice between 2 characters, then double TABbing will print a list of possible completion values, then bring you back to your in-progress command.)

http://whylovelinux.wordpress.com/20...auto-complete/

Thanks eschwartz. And thanks for the link. This is an awesome feature. It will be my next project to learn. And thanks for the example. I could see what you were talking about.

Originally Posted by avantman42

Short answer: no, don't worry about it.

Longer answer:

Extended file attributes are metadata associated with the file. They can contain virtually anything - author name, URL where the file was downloaded from, a hash or checksum of the file. Some programs might use that metadata (I think Dropbox uses them). There is a Wikipedia article on extended file attributes.

Flash drives usually use a file system called FAT32, which doesn't support them, hence the message.

Cool. Thanks Russ. As long as it's copying properly, that's my major concern. Thanks for both explanations and the link.