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
