There are real world cultures that use general-to-specific for addresses
Imagine if file paths were expressed in reverse. You want to edit xorg.conf. As soon as you enter "vi xor" the shell would know enough to auto-complete it to "vi xorg.conf/X11/etc". As it is, organizing files into a logical structure actually makes them harder to find.
> in<TAB>
index.html@.
init.sh@..
index.html@foobar@..
...
inputrc@etc@/
The problem I see is this makes it hard to have domain-specific or optional address interpretation. Eg "foo.png=FILE?get@example.com[http]" or... something to that effect.Come to think of it, that also breaks option escaping in glob et al:
./--kill=everything
vs
--kill=everything@.