Python version checking for OS X is wrong

2015-01-13 Fir de Conversatie Francisco Lopes
Hi, the following test from configure scripts is not allowing me to set a custom python installation. if test x$MACOSX = xyes ${vi_cv_path_python} -c \ import sys; sys.exit(${vi_cv_var_python_version} 2.3); then This is because sys.exit(false) is being considered as success by the test and

Re: Issue 313 in vim: pedit changes cursor position when BufReadPre autocmd defined

2015-01-13 Fir de Conversatie vim
Updates: Labels: patch Comment #4 on issue 313 by chrisbr...@googlemail.com: pedit changes cursor position when BufReadPre autocmd defined https://code.google.com/p/vim/issues/detail?id=313 I am not sure, why this happens only when an autocommand is defined, but this patch saves

Interaction with VNC clipboard causing vim to crash (linux)

2015-01-13 Fir de Conversatie 'Charles' via vim_dev
Hello. I use a Unix/Linux build of vim inside a VNC session on a Windows PC. I've been getting crashes when yanking a large amount of text to the clipboard (~1500 lines or more). I'm hoping someone can help me find a work-around, or at least help me narrow down the problem. Here is how I can

vim truncating line inserted by clicking middle mouse button on Linux

2015-01-13 Fir de Conversatie Peter Mattern
Hello. If the following three lines AAABAAEAczVrNGVjAADOJwAAAQAB AG92NTY1MF9tdjkzMzUAzycAAAEAAQBzaXYx MjFkANAnAAABAAEAY3NpX3VzZWQA (from a UUencoded binary file) are inserted into a vim document by dragging

great idea for a new feature - mouse scroll

2015-01-13 Fir de Conversatie Mikhail V
Very often I use mouse in gvim when I select text for copying/pasting/deleting, so my right hand is on the mouse or tablet (which I also use extensively) and left hand is on the keyboard. Now to scroll through a file I always click or drag the scrollbar area. So I've just thought out a way how

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

2015-01-13 Fir de Conversatie Enno
Le lundi 12 janvier 2015 22:57:56 UTC+1, Marcin Szamotulski a écrit : 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

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

2015-01-13 Fir de Conversatie Jan Larres
Enno enno.na...@gmail.com: When I use gt to switch tabs (or click on a different tab) the TagBar plugin (http://vim.sourceforge.net/script.php?script_id=3465) reports this error: Error detected while processing function SNR99_QuitIfOnlyWindow..SNR99_goto_win: line8: E16: Invalid

Re: Issue 208 in vim: 'make' loops forever during normal compilation

2015-01-13 Fir de Conversatie vim
Comment #3 on issue 208 by jonathan...@gmail.com: 'make' loops forever during normal compilation https://code.google.com/p/vim/issues/detail?id=208 I encountered the same problem (Scientific Linux). Stable 7.4 compiled fine as well. -- You received this message because this project is

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

2015-01-13 Fir de Conversatie vim
Comment #5 on issue 310 by chrisbr...@googlemail.com: Vim hangs with matchadd('...', '\%78v') and nowrap on large/long lines https://code.google.com/p/vim/issues/detail?id=310 That patch is wrong. Please use this new patch Attachments: slow_matchadd_vcol_v2.diff 760 bytes -- You

Re: Regression: CTRL-C mapping ignored after 7.4.468

2015-01-13 Fir de Conversatie Christian Brabandt
Hi Bram! 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/patches/7.4/README) addressed Issue 26: CTRL-C

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

2015-01-13 Fir de Conversatie vim
Updates: Labels: patch Comment #6 on issue 310 by chrisbr...@googlemail.com: Vim hangs with matchadd('...', '\%78v') and nowrap on large/long lines https://code.google.com/p/vim/issues/detail?id=310 (No comment was entered for this change.) -- You received this message because this

Re: Issue 313 in vim: pedit changes cursor position when BufReadPre autocmd defined

2015-01-13 Fir de Conversatie vim
Comment #5 on issue 313 by fritzoph...@gmail.com: pedit changes cursor position when BufReadPre autocmd defined https://code.google.com/p/vim/issues/detail?id=313 Confirmed, this seems to fix the issue. It sounds like it's more of a band-aid than a fix, though? Oh well, a band-aid is

Issue 314 in vim: Netrw problem with Vexplore

2015-01-13 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 314 by cotko...@gmail.com: Netrw problem with Vexplore https://code.google.com/p/vim/issues/detail?id=314 What steps will reproduce the problem? 1. run :Vexplore a:dir What is the expected output? What do you see instead?