3 ms·
And you don’t see why Google would cater to Windows and a Mac users at the expense of Linux users?
by raw_anon_1111 6mo ago
And you don’t see why Google would cater to Windows and a Mac users at the expense of Linux users?
- kalleboo 6mo agomacOS can also handle files with any of those characters in the filename, it's only Windows that's affected.
- raw_anon_1111 6mo agoYou mean 90% of desktop users… I am surprised that the # symbol isn’t on the list.
- simondotau 6mo agoNot colon.
- kalleboo 6mo agoIt can handle files with colon in the name fine, Finder just won't let you name them like that. The files themselves work fine if you created them in the Terminal/through sync. Classic MacOS used colon as a path separator, so to support creating files that could be opened on classic MacOS the Finder disallows it.