They've gone ahead and implemented pretty much everything that was asked for. 
Geoff and kans did a lot of work. That effort is at least worth a response in 
this thread why the patch isn't going to be accepted, even though all that was 
asked for was added to the patch. I don't understand the rational.

B

On Wednesday, October 9, 2013 3:36:24 AM UTC-7, mattn wrote:
> Bram, why you remove this patch from todo list?
> 
> https://code.google.com/p/vim/source/diff?spec=svn173c9c860e42e2af31d598aa6924b99d7e73bd1b&r=173c9c860e42e2af31d598aa6924b99d7e73bd1b&format=side&path=/runtime/doc/todo.txt
> 
> I can't assent.
> 
> On Wednesday, October 9, 2013 7:16:55 AM UTC+9, kans wrote:
> > On Wednesday, October 2, 2013 3:40:05 PM UTC-7, kans wrote:
> > > On Friday, September 27, 2013 8:04:25 AM UTC-7, Ben Fritz wrote:
> > > > On Thursday, September 26, 2013 4:53:55 PM UTC-5, kans wrote:
> > > > > 
> > > > > As Bram pointed out ctrl-c doesn't work on windows.  I'm not going to 
> > > > > try to fix that.
> > > > > 
> > > > 
> > > > CTRL-C works on Windows as long as a user doesn't source the infamous 
> > > > mswin.vim somewhere in their config. Or if they do, they need to edit 
> > > > out the mapping for CTRL-C.
> > > 
> > > 
> > > I believe we have addressed all major concerns- the last one being the 
> > > ex_timers command which shows all pending timers.  If we have missed 
> > > something, or you have other concerns, please let us know.  As I wrote 
> > > before, we'd really like to see this feature in Vim.
> > > 
> > > -Matt
> > 
> > 
> > We recently stumbled into one strange bug with timers.  Everything we've 
> > thrown at them works as expected apart from :Explore.  When run in a timer, 
> > netrw stuff slows down by about two orders of magnitude.  The commands for 
> > timers are executed like so with no other setup:
> > 
> > do_cmdline_cmd(timeouts->cmd)
> > 
> > None of the extra time is spent in self and the cpu usage doesn't spike.  
> > There isn't anything too crazy in Instruments.app (strace).  Does anyone 
> > have any idea about the cause? I've included some basis profiling info 
> > below:
> > 
> > 
> > :call settimeout(0, "Explore ~")
> > count total (s) self (s) function
> > 1 2.620059 0.027059 netrw#Explore()
> > 1 2.593000 0.000131 netrw#LocalBrowseCheck()
> > 1 2.446097 0.000347 <SNR>26_NetrwBrowse()
> > 1 1.443353 0.062179 <SNR>26_PerformListing()
> > 1 0.978938 0.000448 <SNR>26_NetrwGetBuffer()
> > 1 0.978304 0.000426 <SNR>26_NetrwEnew()
> > 3 0.957588 0.001165 <SNR>26_NetrwOptionRestore()
> > 1 0.748296 <SNR>26_NetrwSetSort()
> > 1 0.271453 <SNR>26_NetrwListHide()
> > 2 0.168370 0.042646 <SNR>13_SynSet()
> > 1 0.128560 0.128315 <SNR>26_LocalListing()
> > 1 0.126958 0.000222 <SNR>26_NetrwSafeOptions()
> > 2 0.125646 netrw#NetrwRestorePosn()
> > 1 0.083888 0.021126 netrw#NetrwSavePosn()
> > 2 0.041997 <SNR>10_LoadFTPlugin()
> > 1 0.021434 0.021221 <SNR>26_NetrwBookHistRead()
> > 68 0.001621 <SNR>26_NetrwInit()
> > 1 0.001439 0.001433 <SNR>26_NetrwMaps()
> > 2 0.000417 <SNR>26_NetrwOptionSave()
> > 1 0.000228 <SNR>26_LocalFastBrowser()
> > 
> > 
> > :Explore ~
> > count total (s) self (s) function
> > 1 0.021241 0.006975 netrw#Explore()
> > 1 0.014266 0.000074 netrw#LocalBrowseCheck()
> > 1 0.013968 0.000296 <SNR>26_NetrwBrowse()
> > 1 0.008547 0.000448 <SNR>26_PerformListing()
> > 1 0.003741 0.003255 <SNR>26_NetrwBookHistSave()
> > 1 0.003012 0.000424 <SNR>26_NetrwGetBuffer()
> > 1 0.002976 0.002806 <SNR>26_LocalListing()
> > 2 0.002871 0.000588 <SNR>26_NetrwEnew()
> > 4 0.002356 0.001092 <SNR>26_NetrwOptionRestore()
> > 1 0.001364 0.001358 <SNR>26_NetrwMaps()
> > 1 0.001356 0.000218 <SNR>26_NetrwSafeOptions()
> > 2 0.001330 0.000472 <SNR>13_SynSet()
> > 1 0.001310 <SNR>26_NetrwSetSort()
> > 68 0.001304 <SNR>26_NetrwInit()
> > 2 0.000763 <SNR>10_LoadFTPlugin()
> > 1 0.000630 0.000156 <SNR>4_mergelists()
> > 3 0.000572 <SNR>26_NetrwOptionSave()
> > 1 0.000393 0.000133 ctrlp#mrufiles#cachefile()
> > 1 0.000334 0.000008 <SNR>4_savetofile()
> > 1 0.000326 0.000313 ctrlp#utils#writecache()

-- 
-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Raspunde prin e-mail lui