Re: [vile] Detecting if vile is idle

[Chris Green]

On Fri, Mar 11, 2016 at 11:41:00AM +0000, Chris Green wrote:
> On Thu, Mar 10, 2016 at 10:03:52AM +1100, Brendan O'Dea wrote:
> > On 9 March 2016 at 22:06, Chris Green <address@hidden> wrote:
> > > On Wed, Mar 09, 2016 at 03:33:41PM +1100, Brendan O'Dea wrote:
> > >> Sure, just make some trivial change and undo it:
> > > Doesn't undo back to the start clear the modified flag?  It certainly
> > > seems to when done manually, which I think is actually rather clever!
> > 
> > I does clear the modified flag, so "exit" in the script above won't
> > complain about the contents needing to be saved.  There are however
> > two relevant bits for each buffer: has the buffer been changed since
> > last write (BFCHG) and has the buffer been recently changed (BFRCHG).
> > The first is cleared by the "undo", the second is not.  BFRCHG is used
> > to determine if the autocolor hook should run, and is only cleared
> > once it has.
> > 
> > Either way, it works.  If I open a file, source the script I posted
> > earlier, then wait patiently for fiveish minutes, vile exits.
> > 
> OK, but I still have one problem, I need to do the modify/unmodify
> automatically which means running those commands after I've loaded the
> file.  I guess I can use the -c command line option to do this though.
> 
That doesn't work either as a an insert string using the -c command
line option doesn't set the modified flag.  Grrrrr!  :-)

-- 
Chris Green