That's *precisely* the point I tried to make. .desktop files are just
plain text files, as far as Unix is concerned. They do not map neatly
to Windows .lnk files because the kernel's file system layer does
not handle them specially, as it does symlinks. God and Bill Gates
alone know how Windows handles .lnk files, but it does seem that Windows
imputes to them special semantics, rather like a shell script.
> > GNOME and the window managers I use do not know how to interpret
> > them, except as plain vanilla text files.
>
> Yes, and...? From what I've seen in this thread that's precisely what
> these .lnk files are in Windows. You would have a point if Windows
> kernel would handle them as Unix kernel handles symlinks. It doesn't.
Again, that was my point, which I rather muddled. I was coming at it from
the other direction, though. Windows doesn't handle .lnks as the Unix kernel
handles symlinks, true, but the kernel doesn't handle .desktop files as
Windows handles .lnks, either.
> Some libraries know how to parse them. Which means "plain files", no
> matter how you turn it.
Quite so: the kernel sees .desktop and sees a plain old file; Windows sees
.lnk and does something that resembles interpreting them. Again, my point
was that .desktop files do not map cleanly .lnk files.
As for who "wins" in this thread, I could care less because I don't need
or want to display Windows shortcuts.
Kurt
-- Pity the meek, for they shall inherit the earth. -- Don Marquis - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/