Bug in KURL handling(?)

[Thiago Macieira]

Andras Mantia wrote:
>I don't get it why should it work in this case? If I have the file
>called "A#B" now "file:///home/user/A#B" isn't the same as
>"/home/user/A#B"?

No. The former is file "A" in "/home/user", with protocol "file:" and 
anchor "B". The latter is file "A#B" in "/home/user".

Anchors (as well as queries - "?") are only allowed in URLs. If you type a 
pathname (i.e, without the leading "file:///"), you are not allowed 
anchors or queries.

>With the current logic this looks like the first one 
>will open file "A" and go to link "#B" and the second one would open
>file "A#B".

That's it.

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiago (AT) macieira (DOT) info
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
Hwonne seo worulde wæs geong and time_t wæs 0, God gæf þæt Unix þære 
worulde. And æfter se God logode in, lá! þæt Unix cwæð "Hello, World" and 
ǽghwilc wæs glæd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20041214/ea5f26da/attachment.sig>