Re: Patch 7.4.570

2015-01-14 Fir de Conversatie Cesar Romani
On 14/01/2015 05:52 p.m., Ken Takata wrote: > Hi Cesar, > > 2015/1/15 Thu 0:40:05 UTC+9 Cesar wrote: >> [...] >> gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb6c): undefined reference to >> `rb_gc_writebarrier_unprotect_promoted' >> gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb7c): undefined reference to >>

Re: Patch 7.4.570

2015-01-14 Fir de Conversatie tux.
Ken Takata schrob am Mittwoch, 14. Januar 2015 um 23:52 Zeit: > Did you set RUBY_VER and RUBY_VER_LONG properly? MSVC 2010, RUBY_VER = 22, RUBY_VER_LONG = 2.2.0: I can reproduce Cesar's error. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below

Re: Patch 7.4.570

2015-01-14 Fir de Conversatie Ken Takata
Hi Cesar, 2015/1/15 Thu 0:40:05 UTC+9 Cesar wrote: > [...] > gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb6c): undefined reference to > `rb_gc_writebarrier_unprotect_promoted' > gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb7c): undefined reference to > `rb_gc_writebarrier_unprotect_promoted' > gobjZi386/i

Re: Issue 314 in vim: Netrw problem with Vexplore (actually a :wincmd range checking problem)

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #5 on issue 314 by drc...@campbellfamily.biz: Netrw problem with Vexplore (actually a :wincmd range checking problem) https://code.google.com/p/vim/issues/detail?id=314 Looks like patches 577 and 580 fixed this problem. -- You received this message beca

Re: Issue 232 in vim: AWK syntax highliting slash operator turns into regexp

2015-01-14 Fir de Conversatie vim
Comment #4 on issue 232 by azc...@gmail.com: AWK syntax highliting slash operator turns into regexp https://code.google.com/p/vim/issues/detail?id=232 I agree, I will send the file to Bram. -- You received this message because this project is configured to send all issue notifications to t

Re: Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Marcin Szamotulski
On 13:06 Wed 14 Jan , Gary Johnson wrote: > On 2015-01-14, Bram Moolenaar wrote: > > Gary Johnson wrote: > > > > > I just updated to 7.4.579 on one of my Linux systems. With the > > > cursor over "printf" in a C file, typing K results in the following > > > error message. > > > > > > Err

Re: Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Gary Johnson
On 2015-01-14, Bram Moolenaar wrote: > Gary Johnson wrote: > > > I just updated to 7.4.579 on one of my Linux systems. With the > > cursor over "printf" in a C file, typing K results in the following > > error message. > > > > Error detected while processing function > > manpageview#KMap..m

Re: Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Bram Moolenaar
Gary Johnson wrote: > I just updated to 7.4.579 on one of my Linux systems. With the > cursor over "printf" in a C file, typing K results in the following > error message. > > Error detected while processing function > manpageview#KMap..manpageview#ManPageView:

Patch 7.4.580

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.580 Problem:":52wincmd v" still gives an invalid range error. (Charles Campbell) Solution: Skip over white space. Files: src/ex_docmd.c *** ../vim-7.4.579/src/ex_docmd.c 2015-01-14 15:47:33.076036876 +0100 --- src/ex_docmd.c 2015-01-14 21:17:20.8318132

Re: Issue 314 in vim: Netrw problem with Vexplore (actually a :wincmd range checking problem)

2015-01-14 Fir de Conversatie vim
Comment #4 on issue 314 by brammool...@gmail.com: Netrw problem with Vexplore (actually a :wincmd range checking problem) https://code.google.com/p/vim/issues/detail?id=314 I forgot to skip over white space. 7.4.580 will fix it. -- You received this message because this project is configure

Re: Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Marcin Szamotulski
On 14:40 Wed 14 Jan , Charles Campbell wrote: > Gary Johnson wrote: > > I just updated to 7.4.579 on one of my Linux systems. With the > > cursor over "printf" in a C file, typing K results in the following > > error message. > > > > Error detected while processing function > > manpagevie

Re: Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Charles Campbell
Gary Johnson wrote: > I just updated to 7.4.579 on one of my Linux systems. With the > cursor over "printf" in a C file, typing K results in the following > error message. > > Error detected while processing function > manpageview#KMap..manpageview#ManPageView:

Re: Issue 314 in vim: Netrw problem with Vexplore (actually a :wincmd range checking problem)

2015-01-14 Fir de Conversatie vim
Updates: Status: Accepted Comment #3 on issue 314 by drc...@campbellfamily.biz: Netrw problem with Vexplore (actually a :wincmd range checking problem) https://code.google.com/p/vim/issues/detail?id=314 Unfortunately the following still produces an error message about invalid range:

Vim 7.4.579: wincmd range problem with manpageview plugin

2015-01-14 Fir de Conversatie Gary Johnson
I just updated to 7.4.579 on one of my Linux systems. With the cursor over "printf" in a C file, typing K results in the following error message. Error detected while processing function manpageview#KMap..manpageview#ManPageView:

Re: Issue 184 in vim: Setting (paste) input mode after setting ruler causes ruler to hide

2015-01-14 Fir de Conversatie vim
Comment #7 on issue 184 by josh.end...@gmail.com: Setting (paste) input mode after setting ruler causes ruler to hide https://code.google.com/p/vim/issues/detail?id=184 Makes sense. Thanks for the follow up! -- You received this message because this project is configured to send all issue

Re: Issue 184 in vim: Setting (paste) input mode after setting ruler causes ruler to hide

2015-01-14 Fir de Conversatie vim
Comment #6 on issue 184 by jend...@pinterest.com: Setting (paste) input mode after setting ruler causes ruler to hide https://code.google.com/p/vim/issues/detail?id=184 Makes sense. Thanks for the quick follow up! -- You received this message because this project is configured to send all

Re: Issue 232 in vim: AWK syntax highliting slash operator turns into regexp

2015-01-14 Fir de Conversatie vim
Comment #3 on issue 232 by chrisbr...@googlemail.com: AWK syntax highliting slash operator turns into regexp https://code.google.com/p/vim/issues/detail?id=232 Since no one complained, I think this new awk syntax file should be included with vim. -- You received this message because this

Re: Issue 314 in vim: Netrw problem with Vexplore (actually a :wincmd range checking problem)

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #2 on issue 314 by chrisbr...@googlemail.com: Netrw problem with Vexplore (actually a :wincmd range checking problem) https://code.google.com/p/vim/issues/detail?id=314 I think, this should be fixed by patch 7.4.572. Please verify. -- You received this

Re: Issue 312 in vim: word wrapping messed up when entering Insert mode with 'c' or 's'

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #3 on issue 312 by chrisbr...@googlemail.com: word wrapping messed up when entering Insert mode with 'c' or 's' https://code.google.com/p/vim/issues/detail?id=312 Fixed by 7.4.576 https://code.google.com/p/vim/source/detail?r=749fc929da45d07efc5352dd8a

Patch 7.4.579

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.579 Problem:Wrong cursor positioning when 'linebreak' is set and lines wrap. Solution: (Christian Brabandt) Files: src/charset.c, src/screen.c *** ../vim-7.4.578/src/charset.c2014-10-31 12:41:57.427319153 +0100 --- src/charset.c 2015-01-14 19:34:38.916109031 +

Patch 7.4.578

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.578 Problem:Using getcurpos() after "$" in an empty line returns a negative number. Solution: Don't add one when this would overflow. (Hirohito Higashi) Files: src/eval.c *** ../vim-7.4.577/src/eval.c 2015-01-14 17:14:57.351424263 +0100 --- src/eval.c 2015-01-

Patch 7.4.577

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.577 Problem:Matching with a virtual column has a lot of overhead on very long lines. (Issue 310) Solution: Bail out early if there can't be a match. (Christian Brabandt) Also check for CTRL-C at every position. Files: src/regexp_nfa.c *** ../vim-7.4.5

Re: Issue 310 in vim: Vim hangs with matchadd('...', '\%78v') and nowrap on large/long lines

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #7 on issue 310 by brammool...@gmail.com: Vim hangs with matchadd('...', '\%78v') and nowrap on large/long lines https://code.google.com/p/vim/issues/detail?id=310 Patch included as 7.4.577 -- You received this message because this project is configur

Re: Issue 314 in vim: Netrw problem with Vexplore (actually a :wincmd range checking problem)

2015-01-14 Fir de Conversatie vim
Updates: Summary: Netrw problem with Vexplore (actually a :wincmd range checking problem) Comment #1 on issue 314 by drc...@campbellfamily.biz: Netrw problem with Vexplore (actually a :wincmd range checking problem) https://code.google.com/p/vim/issues/detail?id=314 This problem sounds li

Re: Issue 305 in vim: Spell check for autoconf files (configure.ac) checks whole file, not just comments

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #4 on issue 305 by brammool...@gmail.com: Spell check for autoconf files (configure.ac) checks whole file, not just comments https://code.google.com/p/vim/issues/detail?id=305 I'll include the patch, also for the AC_MSG* regions. -- You received this me

Patch 7.4.576

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.576 Problem:Redrawing problem with 'relativenumber' and 'linebreak'. Solution: Temporarily reset 'linebreak' and restore it in more places. (Christian Brabandt) Files: src/normal.c *** ../vim-7.4.575/src/normal.c 2014-10-31 13:54:21.843214469 +0100 --- src/normal

Re: Proposal: range('a', 'c') should be ['a', 'b', 'c']

2015-01-14 Fir de Conversatie 'Andy Wokula' via vim_dev
Am 13.01.2015 um 02:09 schrieb mattn: I know what i want can do with map(range(char2nr('a'), char2nr('z')), 'nr2char(v:val)'). But it's too long. I think. If you want everything builtin, then what's the purpose of user functions? -- Andy -- -- You received this message from the "vim_dev" ma

Issue 316 in vim: End and Home keys not usage after :set ttymouse=urxvt

2015-01-14 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 316 by mich...@gmail.com: End and Home keys not usage after :set ttymouse=urxvt https://code.google.com/p/vim/issues/detail?id=316 What steps will reproduce the problem? 1. Use urxvt terminal 2. open vim and :set ttymouse=u

Patch 7.4.575

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.575 Problem:Unicode character properties are outdated. Solution: Update the tables with the latest version. Files: src/mbyte.c *** ../vim-7.4.574/src/mbyte.c 2014-11-19 17:05:52.209648533 +0100 --- src/mbyte.c 2015-01-14 17:23:56.509597627 +0100 *** *** 1244,126

Patch 7.4.574

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.574 Problem:No error for eval('$'). Solution: Check for empty name. (Yasuhiro Matsumoto) Files: src/eval.c *** ../vim-7.4.573/src/eval.c 2014-12-13 21:00:52.059036480 +0100 --- src/eval.c 2015-01-14 17:11:38.633570761 +0100 *** *** 7867,7873 if (eva

Re: Regression: Patch 7.4.569 breaks vmap

2015-01-14 Fir de Conversatie Ingo Karkat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14-Jan-2015 16:07, Bram Moolenaar wrote: > > The problem is with using State directly, should use > get_real_state(). > > I added a test, but it also passes without the fix. Same problem > that it works when using :normal or feedkeys(). Thanks,

Re: Issue 133 in vim: [syntax patch proposal] config.vim recognize AC_MSG as strings

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #4 on issue 133 by brammool...@gmail.com: [syntax patch proposal] config.vim recognize AC_MSG as strings https://code.google.com/p/vim/issues/detail?id=133 Thanks. I'll check for ([message]) and (message) separately, otherwise the end isn't recognized

Re: Issue 292 in vim: Vim misidentifies polkit rules file as hog rules files

2015-01-14 Fir de Conversatie vim
Updates: Status: Fixed Comment #5 on issue 292 by brammool...@gmail.com: Vim misidentifies polkit rules file as hog rules files https://code.google.com/p/vim/issues/detail?id=292 I'll include the change, thanks. -- You received this message because this project is configured to send

Re: Patch 7.4.570

2015-01-14 Fir de Conversatie Cesar Romani
On 14/01/2015 08:04 a.m., Bram Moolenaar wrote: > > Patch 7.4.570 > Problem:Building with dynamic library does not work for Ruby 2.2.0 > Solution: Change #ifdefs and #defines. (Ken Takata) > Files: src/if_ruby.c > > > *** ../vim-7.4.569/src/if_ruby.c 2014-11-27 17:44:05.376820913 +

Inconsistencies of CTRL-C

2015-01-14 Fir de Conversatie Ingo Karkat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Vim developers, 1. In normal mode, an unmapped CTRL-C "Interrupt[s] current (search) command." And it prints the "Type :quit to exit Vim" message. So when I :nnoremap The message is indeed gone, but commands like :sleep 30 are sti

Patch 7.4.573

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.573 (after 7.4.569) Problem:Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat) Solution: Call get_real_state() instead of using State directly. Files: src/ui.c, src/testdir/test_mapping.in, src/testdir/test_mapping.ok *** ../vim-7.4.572/src/ui.c 2015-01-14 12:44:3

Re: Regression: Patch 7.4.569 breaks vmap

2015-01-14 Fir de Conversatie Bram Moolenaar
Ingo Karkat wrote: > First, thanks for fixing this issue with unmapping CTRL-C, Bram and > Christian! Unfortunately, after patch 7.4.569, I cannot map in > visual or select mode any more. (I have mapped this to "copy to > clipboard", similar to what's in mswin.vim.) > > Steps to reproduce: > >

Patch 7.4.572

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.572 Problem:Address type of :wincmd depends on the argument. Solution: Check the argument. Files: src/ex_docmd.c, src/window.c, src/proto/window.pro *** ../vim-7.4.571/src/ex_docmd.c 2015-01-14 11:24:51.851582151 +0100 --- src/ex_docmd.c 2015-01-14 14:48:24.586468

Issue 315 in vim: Build bug in Python version checking for OS X

2015-01-14 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 315 by obl...@gmail.com: Build bug in Python version checking for OS X https://code.google.com/p/vim/issues/detail?id=315 What steps will reproduce the problem? 1. Under OS X, build vim using -with-python-config-dir option

Regression: Patch 7.4.569 breaks vmap

2015-01-14 Fir de Conversatie Ingo Karkat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Vim developers, First, thanks for fixing this issue with unmapping CTRL-C, Bram and Christian! Unfortunately, after patch 7.4.569, I cannot map in visual or select mode any more. (I have mapped this to "copy to clipboard", similar to what's in

Re: Patch 7.4.571

2015-01-14 Fir de Conversatie Ike Devolder
On Wed, Jan 14, 2015 at 02:09:04PM +0100, Bram Moolenaar wrote: > > Patch 7.4.571 (after 7.4.569) > Problem:Can't build with tiny features. (Ike Devolder) > Solution: Add #ifdef. > Files:src/getchar.c > > > *** ../vim-7.4.570/src/getchar.c 2015-01-14 12:44:38.403422124 +01

Re: Patch 7.4.569

2015-01-14 Fir de Conversatie Bram Moolenaar
Ike Devolder wrote: > On Wed, Jan 14, 2015 at 12:44:57PM +0100, Bram Moolenaar wrote: > > > > Patch 7.4.569 (after 7.4.468) > > Problem:Having CTRL-C interrupt or not does not check the mode of the > > mapping. (Ingo Karkat) > > Solution: Use a bitmask with the map mode. (Christian

Patch 7.4.571

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.571 (after 7.4.569) Problem:Can't build with tiny features. (Ike Devolder) Solution: Add #ifdef. Files: src/getchar.c *** ../vim-7.4.570/src/getchar.c2015-01-14 12:44:38.403422124 +0100 --- src/getchar.c 2015-01-14 14:06:14.457992406 +0100 *** *** 3

Patch 7.4.570

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.570 Problem:Building with dynamic library does not work for Ruby 2.2.0 Solution: Change #ifdefs and #defines. (Ken Takata) Files: src/if_ruby.c *** ../vim-7.4.569/src/if_ruby.c2014-11-27 17:44:05.376820913 +0100 --- src/if_ruby.c 2015-01-14 14:02:59.680115042 +

Re: Patch 7.4.569

2015-01-14 Fir de Conversatie Ike Devolder
On Wed, Jan 14, 2015 at 12:44:57PM +0100, Bram Moolenaar wrote: > > Patch 7.4.569 (after 7.4.468) > Problem:Having CTRL-C interrupt or not does not check the mode of the > mapping. (Ingo Karkat) > Solution: Use a bitmask with the map mode. (Christian Brabandt) > Files:s

Patch 7.4.569

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.569 (after 7.4.468) Problem:Having CTRL-C interrupt or not does not check the mode of the mapping. (Ingo Karkat) Solution: Use a bitmask with the map mode. (Christian Brabandt) Files: src/getchar.c, src/structs.h, src/testdir/test_mapping.in, src/testdi

Re: Regression: CTRL-C mapping ignored after 7.4.468

2015-01-14 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > On So, 14 Dez 2014, Bram Moolenaar wrote: > > > > Christian Brabandt wrote: > > > > > On Fr, 12 Dez 2014, Ingo Karkat wrote: > > > > > > > Hello Vim developers, > > > > > > > > patch 7.4.468 (BTW it doesn't appear in the list on > > > > ftp://ftp.vim.org/vol/2/vim/

Re: Issue 184 in vim: Setting (paste) input mode after setting ruler causes ruler to hide

2015-01-14 Fir de Conversatie vim
Comment #5 on issue 184 by brammool...@gmail.com: Setting (paste) input mode after setting ruler causes ruler to hide https://code.google.com/p/vim/issues/detail?id=184 Pasting can involve a large amount of text (someone just complained about pasting more than 1500 lines not working). Keep

Re: Regression: CTRL-C mapping ignored after 7.4.468

2015-01-14 Fir de Conversatie Christian Brabandt
Am 2015-01-13 21:18, schrieb Christian Brabandt: Okay, how about that patch? Oh, that is not completly correct. Will post an update later. Best, Christian -- -- 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

Patch 7.4.568

2015-01-14 Fir de Conversatie Bram Moolenaar
Patch 7.4.568 Problem:Giving an error for ":0wincmd w" is a problem for some plugins. Solution: Allow the zero in the range. (Marcin Szamotulski) Files: src/ex_docmd.c, src/testdir/test_command_count.ok *** ../vim-7.4.567/src/ex_docmd.c 2015-01-07 15:57:13.145559792 +0100 --- sr

Re: 0wincmd gives E16: Invalid range: 0wincmd w

2015-01-14 Fir de Conversatie Bram Moolenaar
Marcin Szamotulski wrote: > On 22:26 Mon 12 Jan , Bram Moolenaar wrote: > > > > Enno Nagel wrote: > > > > > Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit : > > > > Enno Nagel wrote: > > > > > > > > > The command > > > > > > > > > > 0wincmd w > > > > > > > > > > throws a

Re: vim truncating line inserted by clicking middle mouse button on Linux

2015-01-14 Fir de Conversatie Jürgen Krämer
Hi. Peter Mattern schrieb am 13.01.2015 um 19:57: > > If the following three lines > AAABAAEAczVrNGVjAADOJwAAAQAB > AG92NTY1MF9tdjkzMzUAzycAAAEAAQBzaXYx > MjFkANAnAAABAAEAY3NpX3VzZWQA > (from a UUencoded bina