On 07 Mar 2001, Kai Großjohann wrote:
> On Mon, 05 Mar 2001, Francesco Potorti` wrote:
>
>> The midnight commander uses this sort of file names:
>>
>> /#sh:[user@]machine[:options]/[remote-dir]
>
> I wonder what the beginning means? Does "/#sh:" mean it's to be
> fetched via ssh? And are there other "/#" filenames?
>
> But the (new) Tramp syntax is too different from the above, so maybe
> making the second character the same doesn't make all that much of a
> difference. The new syntax needs an unambiguous terminator for the
> hop list, due to the unification of single-hop and multi-hop methods.
Well, there isn't any /technical/ reason that the syntax mentioned above
couldn't be supported.
I have vague plans, if I had not mentioned, of writing a compatibility
module for the new TRAMP code.
It's not that hard to have a handler that accepts the old path syntax
and massages it into the new syntax.
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.
This is simple, really. Just match their paths, create a new tramp2
path string are run the operation with the new path.
2. Redefine the path parser/constructor (`tramp2-path-parse',
`tramp2-path-construct')
These are nice and modular. The path object is well defined and the
*only* places that use anything but the object are the
file-name-handler table entry (modify `tramp2-path-tag') and the
parser.
I was fairly careful to keep the parser modular. If there are several
syntaxes that people feel strongly about I can write a framework for
supporting them through option 1.
That, incidentally, is something that may well happen anyway, presuming
that I do want to support the TRAMP1 style filenames.
Daniel
--
What the caterpillar calls the end of the world,
the Master calls the butterfly
-- Richard Bach
