kans wrote:
> Zyx,
>
> Thanks for the help. Intervals are no longer run if they error of any
> sort (apart from a user interrupt which will likely happen
> accidentally). I was also forced to change configure.in as the
> monotonic timer on Linux needs to sometimes link against rt. I ran
> autoconf and also dumped those changes into auto/configure file. They
> run in both Linux and OsX.
>
>
> Originally, I had hopped that this patch will be 100 lines tops, but
> it is closer to 600. A good chunk of that is documentation and
> touching the various make files. I think we have addressed all the
> concerns (apart from changing the name). What would it take to get
> this merged?
I still have several problems with including this functionality.
I would prefer this to be called timed events instead of async, since
it's not really asynchronous. A timeout is for when you do something
and it takes too long. What this is doing is setting a timer or a
repeated timer.
There is no need for 'ticktime', one can compute the time until the next
event and use that. It's also more accurate and has less overhead.
Like others I'm worried that some plugin creates a timer with a problem,
and it keeps triggering over and over. The user must have a way to stop
it. Also, there will be plugins that have interference with what some
timer is doing, there needs to be a way to temporary disable them.
It might be required to give the timers a name instead of an ID, so that
specific timers can be disabled by name, instead of having to lookup
their ID (how would one do that anyway?).
What happens with timers when at a prompt, e.g. for ":s/pat/repl/gc"?
This is the kind of functionality where we may need to fix many bugs
that are uncovered over time, like with the conceal feature. I am not
going to include it before I'm convinced it works properly.
--
hundred-and-one symptoms of being an internet addict:
250. You've given up the search for the "perfect woman" and instead,
sit in front of the PC until you're just too tired to care.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
