Thread: Gregg's Nearly Interminable Adventures in Linux Land
View Single Post
Old 04-02-2014, 07:08 AM   #83
avantman42
Wizard
avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.avantman42 ought to be getting tired of karma fortunes by now.
 
avantman42's Avatar
 
Posts: 1,090
Karma: 6058305
Join Date: Sep 2010
Location: UK
Device: Kindle Paperwhite
Quote:
Originally Posted by Gregg Bell View Post
So it seems Linux doesn't like commas. Would that be accurate?

And any ideas for overcoming this or should I just get to work changing over all the commas to periods?

Thanks.
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:

Code:
"Bell,Gregg.-.Jamie's.Gamble[06.18.2013].epub"
Bell\,Gregg.-.Jamie's.Gamble[06.18.2013].epub
Russ
avantman42 is offline   Reply With Quote