Gap between scrollbar and window border when compiled with Visual Studio 2012

2013-07-11 Fir de Conversatie Charles
Hi, Does anyone know why when compiled with visual studio 2012, the vim gui has gap between the scrollbars and the window borders. Here's the screenshot of vim compiled with visual studio 2010 http://imgur.com/lI05rgq And here is when compiled with visual studio 2012 http://imgur.com/iLeVis1

Issue 149 in vim: Bug in history management with multiple file buffers

2013-07-11 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 149 by gu...@ascomp.ch: Bug in history management with multiple file buffers http://code.google.com/p/vim/issues/detail?id=149 What steps will reproduce the problem? Suppose I have 2 files A and B open in my vim using

Main help display issue

2013-07-11 Fir de Conversatie Dimitar DIMITROV
Hi all, 1. command vim -nNX -u NONE 2. :h 3. :on 4. :se cole=2 lbr 5. :sy on Now you can see a misaligned paragraph starting on line 36 First tought this was a tab vs space issue as you can see with :se list but 'cole is somehow also involved as setting it to 0 removes the misalignment Cheers

Re: Issue 149 in vim: Bug in history management with multiple file buffers

2013-07-11 Fir de Conversatie vim
Comment #1 on issue 149 by fritzoph...@gmail.com: Bug in history management with multiple file buffers http://code.google.com/p/vim/issues/detail?id=149 This is expected behavior. By default Vim discards undo history when you abandon a buffer. You have a few options: 1. Set the 'hidden'

Re: Breaking undo in Insert mode

2013-07-11 Fir de Conversatie Ben Fritz
On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote: Perhaps we can somehow detect that CTRL-R = had the side effect of changing the text and then split undo. When it only returns the text to be inserted, there is no need to split undo. Even though it won't fix it all the

Re: Breaking undo in Insert mode

2013-07-11 Fir de Conversatie Benjamin Fritz
On Thu, Jul 11, 2013 at 10:36 AM, Ben Fritz fritzophre...@gmail.com wrote: On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote: Perhaps we can somehow detect that CTRL-R = had the side effect of changing the text and then split undo. When it only returns the text to be

Re: Breaking undo in Insert mode

2013-07-11 Fir de Conversatie Christian Brabandt
On Thu, July 11, 2013 17:36, Ben Fritz wrote: On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote: Perhaps we can somehow detect that CTRL-R = had the side effect of changing the text and then split undo. When it only returns the text to be inserted, there is no need to split

Re: Breaking undo in Insert mode

2013-07-11 Fir de Conversatie Christian Brabandt
On Thu, July 11, 2013 17:41, Benjamin Fritz wrote: On Thu, Jul 11, 2013 at 10:36 AM, Ben Fritz fritzophre...@gmail.com wrote: On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote: Perhaps we can somehow detect that CTRL-R = had the side effect of changing the text and then split

Patch 7.3.787 performance

2013-07-11 Fir de Conversatie Travis
Hi, I noticed in the vim 7.4a beta (I believe it is the patch 7.3.787 but I'm not entirely sure), it looks like relative line number performance has greatly decreased. If I open a file with just 100 lines, scrolling via rnu is quite choppy, and if I turn it off, it's very fast again. This

Re: Breaking undo in Insert mode

2013-07-11 Fir de Conversatie Ben Fritz
On Thursday, July 11, 2013 10:45:16 AM UTC-5, Christian Brabandt wrote: On Thu, July 11, 2013 17:36, Ben Fritz wrote: On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote: Perhaps we can somehow detect that CTRL-R = had the side effect of changing the text and then

Re: Patch 7.3.787 performance

2013-07-11 Fir de Conversatie Christian Brabandt
On Do, 11 Jul 2013, Travis wrote: I noticed in the vim 7.4a beta (I believe it is the patch 7.3.787 but I'm not entirely sure), it looks like relative line number performance has greatly decreased. If I open a file with just 100 lines, scrolling via rnu is quite choppy, and if I turn it

[patch] let sign placement default to current buffer

2013-07-11 Fir de Conversatie Christian Brabandt
Bram, this small patch makes sign placement easier by defaulting to use the current buffer instead of yielding an error. Mit freundlichen Grüßen Christian -- Morgens am Frühstückstisch. Er kratzt mit dem Löffel das Eigelb von seinem Hemd und sagt: Oh Mann, ich sehe aus wie ein Schwein! Sie:

Re: Vim 7.4a ready for beta testing (test96 FAILED)

2013-07-11 Fir de Conversatie Bram Moolenaar
Raf wrote: Bram Moolenaar wrote: Announcing: Vim (Vi IMproved) version 7.4a BETA This is the first BETA release of Vim 7.4. Please check that the distribution is OK. I haven't done one for a long time. Report anything that isn't right.

Re: [patch] use correct python3 config directory when sys.abiflags is empty

2013-07-11 Fir de Conversatie Bram Moolenaar
Tim Harder wrote: I've attached a patch to fix an issue where the wrong python3 config directory is used when a system's sys.abiflags are empty. Hmm, but when adding vi_cv_var_python3_abiflags when it's not empty, might as well do:

bd closes gvim instead of the specific buffer

2013-07-11 Fir de Conversatie Sumonto Ghosh
Hi, Wondering if anyone could help me debug why bd would close gvim even if multiple buffers are open. I does not close the specific buffer. I have the following plugins installed: solarized nerdtree taglist_46 thanks. -- -- You received this message from the vim_dev maillist. Do not

Re: bd closes gvim instead of the specific buffer

2013-07-11 Fir de Conversatie Christian Brabandt
On Fri, July 12, 2013 01:10, Sumonto Ghosh wrote: Hi, Wondering if anyone could help me debug why bd would close gvim even if multiple buffers are open. I does not close the specific buffer. I have the following plugins installed: solarized nerdtree taglist_46 Well, please be a little