Bram,
while investigating tests for makeing 'ul' settings global-local, I see
some problems with the undo state.
./vim -u NONE -N -c ':set ul=5'
1):for i in range(1,10)| call feedkeys(o.i.\e, 't')|endfor
(i.e. make sure echo line is a single undoable change).
2)(undo as long as it is possible,
On 6 November 2013, Bram Moolenaar b...@moolenaar.net wrote:
lcd wrote:
Hi Bram,
The patch below adds a minor clarification to the docs for
matchadd(), as discussed a few days ago on vim_use.
Thanks. I think it's also good to explicitly say that 'magic' and
'ignorecase'
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 more
On Wednesday, November 6, 2013 1:33:33 AM UTC-6, v...@googlecode.com wrote:
autocmd BufHidden * call OnBufHidden(expand(afile))
function! OnBufHidden(buffer)
[snip]
if a:buffer ==
echoerr clsing:.br
execute bw! .br
endif
endfunction
What is the
Replies here (in the mailing list) are not posted to the issue tracker
(http://code.google.com/p/vim/issues/detail?id=177). I am not sure OP will see
your reply. Likely not if he is not subscribed.
When writing replies to issues it is best to write them from web interface.
--
--
You received
Comment #1 on issue 177 by fritzoph...@gmail.com: can not wipe buffer on
bufhidden
http://code.google.com/p/vim/issues/detail?id=177
As noted by ZyX, my reply on the mailing list wasn't posted here. Sorry for
the double post on vim_dev, I'm posing using the issue tracker now.
On
Comment #2 on issue 177 by zyx@gmail.com: can not wipe buffer on
bufhidden
http://code.google.com/p/vim/issues/detail?id=177
I do not see you posting an exact sequence of commands you used to test
this behavior. When testing your code with
# vim onbufhiddenwipe.vim
paste
Comment #3 on issue 177 by liaoming...@gmail.com: can not wipe buffer on
bufhidden
http://code.google.com/p/vim/issues/detail?id=177
thank you for your reply.
here is how I reproduce it.
1) launch vim.
2) edit a file
3) tabnew opens another tab.
4) try to close the new tab by :x.
when I
Christian Brabandt wrote:
On Wed, November 6, 2013 05:26, Bram Moolenaar wrote:
Patch 7.4.073
Problem:Setting undolevels for one buffer changes undo in another.
Solution: Make 'undolevels' a global-local option. (Christian Brabandt)
Files: runtime/doc/options.txt,
Thanks to @Shougo. This issue is resolved.
https://github.com/Valloric/YouCompleteMe/pull/651
On Nov 5, 2013, at 21:58, zhaocai zhao...@gmx.com wrote:
On Nov 5, 2013, at 19:37, Shougo shougo.ma...@gmail.com wrote:
Hi, I'm the author of neocomplete.
Disable Pattern not found message
Am 06.11.2013 02:16, schrieb mattn:
When keys or values contains space letter, I wonder it works
correctly.
Keys? v:key is list index, it cannot contain spaces.
Spaces in values shouldn't matter.
Not sure what you mean.
--
Andy
--
--
You received this message from the vim_dev maillist.
Do
Comment #6 on issue 140 by jke...@connectwise.com: netrw plugin
NetrwTreeListing
http://code.google.com/p/vim/issues/detail?id=140
I can confirm this issue. Vim 7.4.26 MS-Windows 32-bit (console and gvim)
It is not related to mapleader. Necessary and sufficient steps to reproduce:
vim -u
Hi Bram!
On Mi, 06 Nov 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Wed, November 6, 2013 05:26, Bram Moolenaar wrote:
Patch 7.4.073
Problem:Setting undolevels for one buffer changes undo in another.
Solution: Make 'undolevels' a global-local option.
Leonard Ehrenfried schrob am Mittwoch, 6. November 2013 um 22:54 Zeit:
I also happen to
think that it doesn't do a very good job of explaining what vim is
and how to install it.
Sorry, but that's wrong IMO. :)
--
--
You received this message from the vim_dev maillist.
Do not top-post!
Bram Moolenaar wrote:
It appears the problem is that pum_first and pum_height are out of sync.
pum_first is corrected only after the code that causes a redraw for the
preview window.
Please verify the patch below also fixes the crash. It's better in the
sense that it corrects
On Nov 6, 2013, at 3:54 PM, Leonard Ehrenfried leonard.ehrenfr...@gmail.com
wrote:
Dear list,
I really hope I don't hurt anyones's feeling by saying that the current
vim.org website looks a little bit dated. I also happen to think that it
doesn't do a very good job of explaining what
Patch 7.4.074
Problem:When undo'ing all changes and creating a new change the undo
structure is incorrect. (Christian Brabandt)
Solution: When deleting the branch starting at the old header, delete the
whole branch, not just the first entry.
Files: src/undo.c
Christian Brabandt wrote:
Bram,
while investigating tests for makeing 'ul' settings global-local, I see
some problems with the undo state.
./vim -u NONE -N -c ':set ul=5'
1):for i in range(1,10)| call feedkeys(o.i.\e, 't')|endfor
(i.e. make sure echo line is a single undoable change).
Christian Brabandt wrote:
On Mi, 06 Nov 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Wed, November 6, 2013 05:26, Bram Moolenaar wrote:
Patch 7.4.073
Problem:Setting undolevels for one buffer changes undo in another.
Solution: Make 'undolevels' a
Patch 7.4.075
Problem:Locally setting 'undolevels' is not tested.
Solution: Add a test. (Christian Brabandt)
Files: src/testdir/test100.in, src/testdir/test100.ok,
src/testdir/Make_amiga.mak, src/testdir/Make_dos.mak,
src/testdir/Make_ming.mak,
Francisco Lopes wrote:
Bram Moolenaar wrote:
It appears the problem is that pum_first and pum_height are out of sync.
pum_first is corrected only after the code that causes a redraw for the
preview window.
Please verify the patch below also fixes the crash. It's better in the
Patch 7.4.076
Problem:cgn does not wrap around the end of the file. (Dimitrov
Dimitrov)
Solution: Restore 'wrapscan' earlier. (Christian Brabandt)
Files: src/search.c
*** ../vim-7.4.075/src/search.c 2013-10-02 21:54:57.0 +0200
--- src/search.c
Patch 7.4.077
Problem:DOS installer creates shortcut without a path, resulting in the
current directory to be C:\Windows\system32.
Solution: Use environment variables.
Files: src/dosinst.c
*** ../vim-7.4.076/src/dosinst.c2013-05-06 04:06:04.0 +0200
---
On Thu, November 7, 2013 03:04, Bram Moolenaar wrote:
Christian Brabandt wrote:
./vim -u NONE -N -c ':set ul=5'
1):for i in range(1,10)| call feedkeys(o.i.\e, 't')|endfor
(i.e. make sure echo line is a single undoable change).
2)(undo as long as it is possible, e.g. press u 6 times)
On Wed, November 6, 2013 22:54, Leonard Ehrenfried wrote:
I really hope I don't hurt anyones's feeling by saying that the current
vim.org website looks a little bit dated. I also happen to think that it
doesn't do a very good job of explaining what vim is and how to install
it. Lastly, it
25 matches
Mail list logo
