Re: Issue 85 in vim: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators

On 2012-10-17, v...@googlecode.com wrote: Status: New Owner: Labels: Type-Defect Priority-Medium New issue 85 by shlo...@gmail.com: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators http://code.google.com/p/vim/issues/detail?id=85

Re: Issue 85 in vim: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators

Comment #1 on issue 85 by shlo...@gmail.com: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators http://code.google.com/p/vim/issues/detail?id=85 On the mailing list (not here on the bug report) Gary Johnson replied and said: «« I'm not

Issue 86 in vim: Minor bug in autoload/syntaxcomplete.vim line 459

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 86 by karl.yn...@gmail.com: Minor bug in autoload/syntaxcomplete.vim line 459 http://code.google.com/p/vim/issues/detail?id=86 Minor error in version 7.3.692 in autoload/syntaxcomplete.vim line 459: let accept_chars =

Issue 87 in vim: Patch for /runtime/autoload/syntaxcomplete.vim

Status: New Owner: Labels: Type-Patch New issue 87 by karl.yn...@gmail.com: Patch for /runtime/autoload/syntaxcomplete.vim http://code.google.com/p/vim/issues/detail?id=87 Added '-' to line 459, since '-' must also be escaped in regexp brackets. This addresses issue 86. Attachments:

Re: Issue 86 in vim: Minor bug in autoload/syntaxcomplete.vim line 459

Comment #1 on issue 86 by ben...@benizi.com: Minor bug in autoload/syntaxcomplete.vim line 459 http://code.google.com/p/vim/issues/detail?id=86 Attaching patch from issue 87 -- not sure why it was a separate issue. Attachments: syntaxcomplete.vim.patch 574 bytes -- You received

Re: Issue 87 in vim: Patch for /runtime/autoload/syntaxcomplete.vim

Comment #1 on issue 87 by ben...@benizi.com: Patch for /runtime/autoload/syntaxcomplete.vim http://code.google.com/p/vim/issues/detail?id=87 Added this patch directly to issue 86. This should be closed. -- You received this message from the vim_dev maillist. Do not top-post! Type your

Re: Issue 84 in vim: [PATCH] Missing the in documentation.

Comment #2 on issue 84 by shlo...@gmail.com: [PATCH] Missing the in documentation. http://code.google.com/p/vim/issues/detail?id=84 This issue is still present in «hg clone https://code.google.com/p/vim/» in revision «changeset: 3872:1001f417a37182832612cde6d11fb321907e49ea». Why was

Re: Issue 84 in vim: [PATCH] Missing the in documentation.

(Sorry, currently have no login for googlecode.com, so only replying on the list, hope you also read it): On Thu, October 18, 2012 16:26, v...@googlecode.com wrote: Comment #2 on issue 84 by shlo...@gmail.com: [PATCH] Missing the in documentation.

Re: Issue 84 in vim: [PATCH] Missing the in documentation.

Comment #3 on issue 84 by brammool...@gmail.com: [PATCH] Missing the in documentation. http://code.google.com/p/vim/issues/detail?id=84 Runtime file changes go out at irregular intervals. I mark items as fixed when I updated the master copy (that's on my harddisk, nobody else sees it

[patch] fix parsing of functions arguments

Bram, this patch fixes this issue from the todo list: , | Space before comma in function definition not allowed: function x(a , b) | Give a more appropriate error message. Add a remark to the docs. ` regards, Christian -- Aus Lügen, die wir glauben, werden Wahrheiten, mit denen wir

Re: [patch] Unsetting undofile calculates the undo_hash

Hi James! On Di, 16 Okt 2012, James McCoy wrote: On Oct 16, 2012 1:14 PM, Christian Brabandt cbli...@256bit.org wrote: Hi vim_dev! On Di, 16 Okt 2012, Christian Brabandt wrote: […] BTW: Any comments on whether unsetting the 'undofile' option should delete the undofile? I've

[patch] Fix filename-escaping for input() function

Bram, this patch fixes this issue from the todo list: , | Unwanted file name escaping: :echo input('file:' , '', 'file') | And use file name completion on a file with spaces. (Frederic Hardy, 2009 Mar | 23) ` regards Christian -- Geschichte schreiben ist eine Art, sich das Vergangene

Re: Sorry for no subject; HIGHLIGHT stops working around 144000th time

Hi, 2010/10/12 Tue 15:46:39 UTC+9 Sergey Khorev: Christian Brabandt cblists at 256bit.org writes: I see that on Windows XP with Vim 7.2.284 after approximately 2 iterations. But what is really weird is, that the whole gui is broken afterwards. The window is not redrawn correctly

Re: Sorry for no subject; HIGHLIGHT stops working around 144000th time

On 18/10/12 23:13, Ken Takata wrote: Hi, 2010/10/12 Tue 15:46:39 UTC+9 Sergey Khorev: Christian Brabandt cblists at 256bit.org writes: I see that on Windows XP with Vim 7.2.284 after approximately 2 iterations. But what is really weird is, that the whole gui is broken afterwards. The

Re: Issue 85 in vim: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators

On 2012-10-18, v...@googlecode.com wrote: Comment #1 on issue 85 by shlo...@gmail.com: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators http://code.google.com/p/vim/issues/detail?id=85 On the mailing list (not here on the bug report) Gary

Re: Issue 85 in vim: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators

Gary Johnson wrote: On 2012-10-18, v...@googlecode.com wrote: Comment #1 on issue 85 by shlo...@gmail.com: :grep in gvim on Linux is much slower than the same :grep in vim in the various terminal emulators http://code.google.com/p/vim/issues/detail?id=85 On the mailing list (not

Re: Sorry for no subject; HIGHLIGHT stops working around 144000th time

Ken Takata wrote: 2010/10/12 Tue 15:46:39 UTC+9 Sergey Khorev: Christian Brabandt cblists at 256bit.org writes: I see that on Windows XP with Vim 7.2.284 after approximately 2 iterations. But what is really weird is, that the whole gui is broken afterwards. The window is not

Re: [patch] Fix filename-escaping for input() function

Christian Brabandt wrote: Bram, this patch fixes this issue from the todo list: , | Unwanted file name escaping: :echo input('file:' , '', 'file') | And use file name completion on a file with spaces. (Frederic Hardy, 2009 Mar | 23) ` Thanks, I'll put it in the todo list. --

Re: [patch] fix parsing of functions arguments

Christian Brabandt wrote: Bram, this patch fixes this issue from the todo list: , | Space before comma in function definition not allowed: function x(a , b)= | Give a more appropriate error message. Add a remark to the docs. ` Looks like this will allow the white space,

Re: (BUG) pastetoggle and f{char}

On Oct 15, 8:01 am, Marcin Szamotulski msza...@gmail.com wrote: On 07:45 Mon 15 Oct     , Bee wrote: I need to add: It is only necessary to 'define' set pastetoggle=,, in .vimrc to get this effect. Bill -- You received this message from the vim_dev maillist. Do not

Re: [patch] fix parsing of functions arguments

Hi Bram! On Fr, 19 Okt 2012, Bram Moolenaar wrote: Christian Brabandt wrote: Bram, this patch fixes this issue from the todo list: , | Space before comma in function definition not allowed: function x(a , b)= | Give a more appropriate error message. Add a remark to the

Re: [patch] Fix filename-escaping for input() function

Hi Bram! On Fr, 19 Okt 2012, Bram Moolenaar wrote: Christian Brabandt wrote: Bram, this patch fixes this issue from the todo list: , | Unwanted file name escaping: :echo input('file:' , '', 'file') | And use file name completion on a file with spaces. (Frederic Hardy, 2009