>> /#sh:[user@]machine[:options]/[remote-dir]
Well, there isn't any /technical/ reason that the syntax mentioned above
couldn't be supported.
So, if Francesco really likes the mc(1) style, it's possible to:
1. Write a file-name handler for it which uses TRAMP2 internally.
I think that having different possible styles of file names is a good
thing. That way, we can experiment practically with them, and hopefully
find a sort of consensus about which one is better.
I mentioned mc because it has a similar problem as us, and it solved it.
A syntax like that is very elastic, and it can naturally express ftp
remote file names (with /#ftp:), so it could be the global syntax for
file names, encompassing tramp, ange-ftp and w3. I'd like very much to
see a unique syntax for remote file names. Having a way of
experimenting with different ones would make us in the position of
asking people outside this mailing list for suggestions and opinions,
and try them quickly.
For example we could experiment with the url-like syntax that was
proposed long ago.
The problem with all-encompassing syntaxes is that they are long and
complex, so the challenge is to find a global one which is easy to use,
for example using abbreviations, optional parts, and so on.
