Vim slow after big count insert
There is no use case If you do something stupid by accident most vim operations can be aborted by ctrl-c (exception: python, rbuy, .. scripts) Try to abort it you will see the success you have. So there is still nothing to fix or talk about unless there is a use case. Marc Weber Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- 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.
Re: Vim slow after big count insert
On 19 July 2013, Mike Williams mike.willi...@globalgraphics.com wrote: On 19/07/2013 15:52, Mike Williams wrote: On 19/07/2013 12:18, Dimitar DIMITROV wrote: Hi, Did a search on the vim_dev archives but couldn't find anything related to this. Sorry if this is redundant. Basically vim is exponentially slow after 100iHello esc as mentionned in this link: http://www.galexander.org/vim_sucks.html A quick run over with a profiler seems to show most of the time is being spent in vim_strchr() called from has_format_option(), called from internal_format(). If I first do :set paste then it is a lot quicker - for 4000iHelloESC it goes from 16s down to 1s. [...] Textwidth. Darn sight quicker with it set to 0, wish I had remembered that. Another factor of ~2 quicker for my final times, 16000iHelloESC now takes ~4s. [...] Right, what you're seeing here is Vim backtracking to find a blank to split that N * Hello line. Since there is no such blank, you get len(Hello) * N * (N + 1) / 2 failed comparisons, which is exactly the O(N^2) behaviour claimed in the article mentioned above. If you replace your test by, say, 16000iHello ESC (with a space after Hello), you get linear behaviour, namely len(Hello) * N failed comparisons. I believe this can be fixed with a counter that means something along the lines of: this line is longer than tw, and it has no breaking point for the first X characters. Then X would be updated every time more text is appended to that line. On 19 July 2013, Marc Weber marco-owe...@gmx.de wrote: Let's discuss the use case, first. Is there one ? Yes, there is: you run through that piece of code every time you press p to paste text. It hits you particularly hard when you edit files with very long lines. If not let's forgett about it .. [...] Perhaps we should try to understand the problem before dismissing it as harmless? /lcd -- -- 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.
Re: $MYVIMRC not set
Dimitar Dimitrov wrote: After reading the docs about -u, I can't see it mentioned that in that case $MYVIMRC wouldn't be setup. But it isn't. Try with vim -u ~/.vimrc I suppose it's useful to add a remark about this in the docs. -- Contrary to popular belief, it's often your clothing that gets promoted, not you. (Scott Adams - The Dilbert principle) /// 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.
Re: regexp: \p doesn't match double width character
Yukihiro Nakadaira wrote: \p doesn't match double width character. And its behavior depends on 'ambiwidth' option. :set encoding=utf-8 :echo match(\u3042, '\p') HIRAGANA LETTER A -1 :set ambiwidth=single :echo match(\u00EC, '\p') LATIN SMALL LETTER I WITH GRAVE 0 :set ambiwidth=double :echo match(\u00EC, '\p') -1 I'll add it to the todo list. -- Often you're less important than your furniture. If you think about it, you can get fired but your furniture stays behind, gainfully employed at the company that didn't need _you_ anymore. (Scott Adams - The Dilbert principle) /// 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.
:25CR does not save cursor position to jump list
These commands perform the same function: 25G 25gg :25CR But the first two save the cursor position to the jump list, whereas the last command does not, which I feel is inconsistent and a bug. For example, with the following buffer: 1 abc 2 def 3 ghi Entering the following commands: :1CR :2CR :3CR C-O (command that moves cursor to previous line in jump list) C-O Should move you to lines 1, 2, 3, 2, 1 respectively, but at present the C-O commands do NOT move you back to lines 2 and 1. -- -- 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.
