Summary: | Dolphin cannot follow .lnk files | ||
---|---|---|---|
Product: | [Unmaintained] kde-windows | Reporter: | Charles Joseph Christie II <cchris0396> |
Component: | general | Assignee: | KDE-Windows <kde-windows> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | andriusmao, angel_blue_co2004, finex |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Charles Joseph Christie II
2008-08-11 22:44:28 UTC
There is an old bug report which could be related: bug #85348. Anyway, is the extension .ink or .lnk ? That bug report is for opening the ink files in KDE 3.3 in Linux, which doesn't really help me I don't think. The file extensions are .Ink. I don't think I've ever seen a Windows link with the extension lnk. By the way, for some reason, version up there says "unspecified." I'm runing KDE 4.1 in Windows XP if that helps any. ;) In Windows 2003 at least it is .lnk (lowercase L). Just to clarify, I mean a standard Windows "shortcut" Is this bug still valid? Windows standard links are ".lnk", it works normally for me in dolphin, a link to a folder opens that folder, a link to an executable opens that executable. In "properties" window the only difference is that links to folders are shown as "folder" while other links are shown as "Windows Link". Another thing that's different from linux is that NTFS junctions are shown as regular folders on Windows, but as links on Linux, I don't think there is a correct way in this case, because not even explorer recognises junctions, and they do not work for absolute paths when reading from linux (not a bug, just a filesystem thing). Please confirm if this bug is still valid. This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change. |