[guestbest]

Correct me if I’m wrong, but weren’t slashes typically reserved for flags on Unix and back slashes on dos/windows? If that’s the case then surely the vertices line, pipe symbol |, would be the most visually appropriate? Piping remote data over a network connection and through the local client program to parse seems to be the kind of thing bike shedding was intended for, in agreement but focusing on semantics. It just seems new by safe and only requires reprogramming the kernel for the shell semantics.

# gemeni:|bike.domain.com|shed

Or even better, everything is little endian to allow autocomplete from previous entries by the user in the shell so that once the user hits the domain keyword the shell history parser assumes the user wants to stay on the site

# gemeni:|shed|bike|domain|com

I’m not sure how feasible this as I’ve never written an internet or shell language

[WaitWaitWha]

> Correct me if I’m wrong, but weren’t slashes typically reserved for flags on Unix and back slashes on dos/windows?

Forward slash (/) in DOS, while dash, tack, or hyphen (-) are used for UNIX for command line flags or parameters. The / in UNIX was for the path. The backslash (\) is for DOS paths. (Caveat: I started with UNIX in the mid-80s.)

[guestbest]

Ah, thanks.