On Sun, 6 Dec 2020 19:35:18 -0000 (UTC), bob prohaska 
declaimed the following:

>What's with the whitespace in filenames? It seems a pointless complication.
>
 You'd have to ask Google... Though before graphical file managers
embedded spaces were rarely found, since they have to be escaped on the
command line. Graphical systems that use text boxes can take almost
anything and once you have that "anything" the OS functions for
creating/opening files don't care. The normal escape for Linux appears to
be a \ before the space. Windows, instead requires the entire path to be
inside " marks if any component has a space.

 Tab-completion on the command line does help. One just types enough of
the path to identify the start of the file name, then hits  and the OS
fills in the name with any escapes (or shows a list of names with similar
starts -- so those could require including the escape to isolate).

 FYI: The Xerox CP/V OS allowed for other non-printable characters in
file names -- like BEL, which would cause the terminal to beep when the
name is displayed. Trick was, on anything faster than a 300baud terminal,
one could not tell /where/ the BEL was while the name was spewed to the
screen. One could have two files that "looked" like the same name on screen
with non-printing characters at various locations...

 example
 example


>Anyway, that makes sense, at least more than putting user-specific date in
>places other than home directories.
>

 I haven't used Chromium on Windows but seem to have a

   C:\Users\Wulfraed\AppData\Local\Chromium\User Data

directory, so that would be in the Windows equivalent of "home directory"


--
 Wulfraed                 Dennis Lee Bieber         AF6VN
 wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/

--- SoupGate-Win32 v1.05