autoread should work, but requires you to click in the vim window to wake it up.
If it doesn't, maybe you're editing across systems, so that a discrepancy in
system times means vim thinks the file hasn't changed; used to happen a bit,
but I wouldn't expect it these days and not on /tmp.
>Is there a signal I can send to vim?
As BJP says, if your vim is compiled with +clientserver (which is likely) you
can run (at a shell prompt)
vim --servername gvim --remote-send ":checkt<cr>"
The servername will be "GVIM" for the first instance of gvim, "GVIM1" for the
second, and so on; you can run :echo v:servername in the vim that is watching
your file, or run
vim --serverlist
HTH, and regards, John Little
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" 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/d/optout.
