Hello, The problem I described is indeed related to how vim handles it's files. It looks like vim moves the file, which invalidates the Factor monitor on it. Later vim will recreate the file when you do an explcit save from within vim.
One way to handle this situation is to recursively monitor the directory containing the file. Then you'd only act on events such as +modify-file+ with the particular path you're interested in. So it looks like this is not a bug in Factor's inotify code. Ed On Thursday 23 October 2008 15:55:05 Eduardo Cavazos wrote: > Hello, > > I'm noticing some strange behaviour with file monitors on 32-bit Ubuntu > Linux. If anybody else can reproduce this let me know. > > Open a couple of terminals. In the first one do: > > $ vim ~/test-xyz > > Then do a ':w' in vim to write the file. > > In the other terminal start up Factor: > > $ ./factor -run=listener > > and monitor that test file: > > [ home "test-xyz" append-path f <monitor> next-change 2drop ] > with-monitors > > Back in the first terminal (still in vim), insert some text write the file > (via ':w'). > > At this point, on my system, the monitor still hasn't budged. > > This might sound strage, but it seems to only happen with I use 'vim' to > edit the file. If I use the shell (e.g. "echo 10 >> test-xyz") or emacs, > the monitor works. > > Ed ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
