On 27 Feb 2001, Kai Großjohann wrote:
> On 27 Feb 2001, Daniel Pittman wrote:
>
>> This is a description of what I have implemented and working in the
>> path parser at the moment, modulo ensuring that it all works. The
>> optional-ness of things is somewhat vague at present.
>
> This is way cool. Mouth watering. *longing look*
>
>> The path structure is: <tag> <connect>+ <path>
>>
>> A connect expression is: [ <protocol> ] [ <user> "@" ] [ <host> ]
>> ":"
>
> I'm afraid something might need to be done to allow filenames with `:'
> on them (on the remote host). Hm.
>
> Maybe `::' could be the end of the connect list?
Yup. That wouldn't be too hard to do. It also makes a certain degree of
sense...
Non-trivial with my current parser because it's vicious about
poorly-formed paths, which that currently looks like. Still, it's not
too hard to fix that by improving it...
> Another idea for `/!:' is `/tr:' which I guess also works on Windows.
> But `/!:' is also nice.
Yeah, '/tr:' would work fine. In any case, the tag is a custom variable
so if anyone felt /really/ strongly about it they could change it. :)
With luck I should have a basic version of it working within a week.
I hope. If work stays relatively quiet. :)
If not I may just check in the framework at that point, if you would
like? On a branch, of course, because a non-working version as the trunk
would be /very/ bad. :)
Daniel
--
You know you'll always be drifting
You know you'll never be found
A servant, so empty, you'll never make a sound
-- Switchblade Symphony, _Naked Birthday_
