Ralf Reköndt wrote: > Hmm, why have all apps to know, where they are? They don't need to know where they are, but most apps I use work with files, be it source-code, spread-sheets, word-processor documents, you name it.
> If the system let them believe, they are in their root (if > necessary), they should run. Simply look at the TK3 sources, I'v > sent to you years ago. There is a mechanism for that: Yes, that is a concept known as "chroot" in Unix circles. There it is often used for security purposes. But in our context, what use is a (e.g.) text editor that can only edit files in its own directory? Having long path names is not a self-serving goal, it is only useful if applications can actually access all those deep files. Imagine not being able to use QPAC2 anymore because the directory you want to navigate to is too deeply nested in the tree. Cheers, Marcel _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
