> * true async support in the core.
> Remove notions of updatetime since everything will be async
I don't understand this second sentence, example?
> * remove backwards compatibility to Vi. I'm assuming that vi backwards
> compatibility is hard to maintain? At the very least make nocompatible
> the default
:-) Yeah. I agree about a lot - or make non compatible setting the
default.
> * replace cryptic one letter options like coptions
by what?
> * integrate popular plugins into the core: syntastic, ctrlp, nerdtree,
> etc
I think this would be fixed by moving vimruntime to github soon .. :)
> * ability to renumber buffer numbers. This enhancement alone I would
> pay for.
Use case? Why don't you just use aliases like b:.. and write your own
function to access buffers by alias?
Would be about 10 lines of VimL code probably ?
[1]
command
> * concept of window-local buffers and tab-local buffers
Please elaborate
Also add your ideas to this page, please:
http://vim-wiki.mawercer.de/wiki/topic/in-which-way-does-vim-suck.html
Then they won't get lost ..
Marc Weber
[1]
if !exists(g:my_buf_list)
let g:my_buf_list = {}
endif
fun SetBNr(nr)
let b:nr = a:nr
let g:my_buf_list[a:nr] = buffer_number('.')
endf
command -nargs=1 SetBufNr call SetBNr(<f-args>)
" completion missing:
command -nargs=1 GotoBuf exec '.g:my_buf_list[<f-args>]
Also see github.com/MarcWeber/vim-addon-other which implements <m-1>
<m-2> access for tabs or use :b some-chars-only which also works
reasonably well often.
Don't forgett about mA mB and access files by 'A 'B
Marc Weber
--
--
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/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment