On 27/01/2014, at 9:01 PM, spamwax wrote: > > OK, it seems Sublime Text has a role in this issue. > When I modify a text file using vim and do a 'tup upd', it works as expected. > However when I modify the same file using Sublime Text, even though "ls" > shows that size and date/time of the file have been modified, but 'tup upd' > doesn't pick up the change and hence no command is run:
AFAIK, Vim rewrites the whole file. In other words, it creates the file from scratch. This is quite different from writing a file opened I/O. On OSX (at least 10.6.8 which I'm running) you can save a file on top of a running program, no problem. That's because the old inode is still intact, and the directory entry is just set to a fresh inode for the new file. But if you open the file output, you'd be writing on the file identified by the SAME inode. I don't think that's allowed (if the file is "busy" i.e. mapped into memory). So I am guessing, Vim is using old fashioned load/save. Whereas Sublime is using memory mapping. Tup is detecting the gross change to the directory, but it isn't detecting a mere changed file size/time stamp. [Just guessing .. :] -- john skaller [email protected] http://felix-lang.org -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
