Friday, June 20, 2014

Re: way to force vim to do a read (already in 'autoread')

Conner McDaniel wrote:
> You could also pair this with a program like [entr] or [guard] to
> monitor file changes and update vim remotely.
>
> [entr]: http://entrproject.org/
> [guard]: http://guardgem.org/
Not sure what you meant by update vim 'remotely'?

About 50% of the time, the problem I am seeing is that vim will
update as soon as it sees the 1st change, but since it's the output of
of a makefile, it isn't done yet -- and vim won't autoupdate
so I can see the final changes.

Lately I'm nearly giving up on on vim being able to
monitor the latest state of a file and just manually
refreshing it with 'e'.... That's a pain because 'w'
is right next to it... but it's a short rebuild, fortunately.

I think I'd end up with similar problems if I used any sort of
monitoring protocol -- as it will detect early changes -- but
might not detect an update at file close (?)....

Thanks for the suggestions...


--
--
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: