pair-edit style - desktop url argument - to-lit-path bug?
[1/2] from: anton::lexicon::net at: 27-Jun-2002 0:19
> > It's gonna be slow. The index file fo every part of the > > path must be read to determine the next piece. > > Yes, but it should be faster than clicking through by hand.
> > reb://REBOL.com/sites/anton/gui/ > > But it should be easy to work this into the desktop patch,
<<quoted lines omitted: 8>>> -- > Carl Read
Like this: x: func [n][probe n] x 'a-path/blah == a-path/blah I've decided that I wouldn't be ultimately happy with using a lit-path! anyway, so I'd check out the protocol idea. All we need to do is distinguish from url!, so we can use a string! or a block! with the path in it. But your example leads to an "interesting thing": to-lit-path %/a-path/blah == '/a-path//blah ; <- double slash and note also to-lit-path %/a-path/blah/dog == '/a-path//blah//dog ; <- two double slashes Is this a bug, or just escapism? Has anyone else reported this? Anton.
[2/2] from: rotenca:telvia:it at: 26-Jun-2002 17:23
> But your example leads to an "interesting thing": > to-lit-path %/a-path/blah
<<quoted lines omitted: 3>>> == '/a-path//blah//dog ; <- two double slashes > Is this a bug, or just escapism?
'/a-path//blah is a path which contains 2 items: 1) /a-path (refinement!) 2) /blah (refinement!) both items are refinements: length? to-lit-path %/a-path/blah ; == 2 type? first to-lit-path %/a-path/blah ;== refinement! type? second to-lit-path %/a-path/blah ;== refinement! It is not a bug, neither escape. --- Ciao Romano
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted