On Wednesday, March 25, 2015 at 6:47:48 PM UTC+3, Christian Brabandt wrote:
> I don't know yet, what the process will look like. Until now, I have
> been using mercurials mq extension
> but not sure how to proceed here.
There is a stgit (http://procode.org/stgit/) with similar functionality.
--
> 'viewdir' $XDG_CACHE_HOME/vim/view
My precious views are treated as "user specific non-essential data files".
Sweet.
--
--
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.
> The new logo gives VIM the professional look it deserves!
Hmph. For me it's a work of undergraduated schoorling. Too primitive, not
simple or minimalistic.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mo
On Wed, Oct 16, 2013 at 06:49:09PM -0700, Ben Fritz wrote:
> On Wednesday, October 16, 2013 8:40:23 PM UTC-5, Anton Bobrov wrote:
> > > I like the idea for a threshold, but it would be a ton of work since it
> >
> > > would have to use threads and locking and vim
> I like the idea for a threshold, but it would be a ton of work since it
> would have to use threads and locking and vim isn't thread safe. This is
> way more work than I am willing to put in even if it means this patch
> doesn't get merged.
>
> -Matt
Er, threads, locks? We only need to decide
> You are correct that we trivially know this information. What would you
> suggest for the heuristic on not rescheduling? A timer that takes up 500ms
> out of every 1000 is also something we'd want to kill.
>
> -Matt
IMHO, any kind of bad plugin detection is useless. It's complicate, need
comp
On Wed, Oct 16, 2013 at 05:24:53PM -0700, Matthew Kaniaris wrote:
> Anton,
>
> What do you mean by long running timers? Are you suggesting we look at the
> running time of the current timer?
>
> -Matt
Yes, exactly. As far as I understand the implementation dispatcher should know
about
timer's
> It wouldn't be unreproducible, nor would it be a glitch. I'd get a prominent
> error message if I pressed CTRL-C that I had canceled timers.
Not all users have excellent error message detection skills like yours.
> In response, I'd say "whoops!", save all my work, and restart Vim.
I'd say 'bl
> I press CTRL-C very infrequently. I'd be willing to give it a try first
> without such a feature and see how often I accidentally interrupt timers.
Relying on good chance is much worse than timer plugins in stock vim.
Unreproducible glitches, fuck yeah!
--
--
You received this message from
