I'm a bit torn what the "correct" behaviour would be in this case, but when I open an existing file in TM, then move that file and save it, then it appears wherever I opened it from originally, not in the new location.
I thought TM checked the status of open files, or does that only apply for projects?
Daniel.
On 09/10/2005, at 15.01, Daniel Vollmer wrote:
I thought TM checked the status of open files, or does that only apply for projects?
Neither -- TextMate makes exclusive use of “POSIX” paths. That is, a file is identified by /path/to/file.
I'm likely to make (some) use of Apple's file alises in 1.2, which are an opaque way of handling files, and which are (currently, AFAIK) implemented by first checking the path, and if the file no longer exists at that path, use the inode (there are more cumbersome strategies for files on network mounted volumes).
I'm likely to make (some) use of Apple's file alises in 1.2, which are an opaque way of handling files, and which are (currently, AFAIK) implemented by first checking the path, and if the file no longer exists at that path, use the inode (there are more cumbersome strategies for files on network mounted volumes).
That's one of the biggest things I like with OS X vs Windows; the ability to move and throw away stuff I'm currently using. For example, trashing an mp3 I know i'll never listen to again but at least keep it running one time, or open a movie and then immediately throw it in the trash so I don't forget later on.
Andreas
On 09/10/2005, at 15.51, Andreas Wahlin wrote:
I'm likely to make (some) use of Apple's file alises in 1.2 [...]
That's one of the biggest things I like with OS X vs Windows; the ability to move and throw away stuff I'm currently using. [...]
That's not because of file aliases, but because on most non-Windows systems, a file opened for reading is not locked.