The original question seems to be how to maintain links when the file is
moved or renamed. Perhaps the file could have a unique ID in the file
system, and the link would try the given pathname, but if it's not there,
try the unique ID. Would that work?
Daniel W Gelder daniel.w.gel...@gmail.com writes:
The original question seems to be how to maintain links when the file
is moved or renamed. Perhaps the file could have a unique ID in the
file system, and the link would try the given pathname, but if it's
not there, try the unique ID. Would
We may want a program which unfortunately has a path to a shortcut to still
work if the files they point to are moved.
On Oct 9, 2014 7:56 PM, Pascal J. Bourguignon p...@informatimago.com
wrote:
Daniel W Gelder daniel.w.gel...@gmail.com writes:
The original question seems to be how to
Josh McDonald j...@joshmcdonald.info writes:
Why should links be in the filesystem, rather than an application /
UI construct?
For a lot of reasons. But the question is justified.
- because it would be more modular and represent more code reuse, to
factorize out the management of links
