The fact that the hit enter prompt is shown twice sometimes after :make when an
error is found by quickfix was asked a number of times in the user list and in
stackoverflow, but AFAIK it was just workarounded by making make silent or
cmdheight larger. Now I've found a specific situation when the
> I would definitely appreciate such an option. BTW, it would be
> good to add
> this option to $VIMRUNTIME/optwin.vim
> and having tests would also help.
Christian - thank you for the quick response.
See attachment for the updated patch.
I could not find a good test to modify, so I created a
On Sa, 20 Jun 2015, Christian Brabandt wrote:
> I just uploaded a new build 7.4.749 for analysis. There should be
> results available soon.
FWIW, I have setup a cronjob to periodically build and upload a new Vim
build when a new patchlevel is available. However, that machine only has
sporadic I
Christian Brabandt wrote:
> Am 2015-06-23 06:38, schrieb Ben Fritz:
> > Today I noticed that I can no longer compile gvimext.dll, due to the
> > code added in patch 724.
> >
> > I compile with MinGW as follows:
> >
> > make -f Make_ming.mak -j%NUMBER_OF_PROCESSORS% GUI=yes FEATURES=HUGE
> > PYT
guotuofeng wrote:
> Suppose I have the following dataļ¼
>
> 4702103 BLOB: 1.dat
> 4702103 BLOB: 3.dat
> 4702104 BLOB: 4.dat
> 4702104 BLOB: 5.dat
> 4702106 BLOB: 6.dat
>
> And I want to remove duplicate item against the first column. The dedup data
> should like:
>
> 4702103 BLOB:
On 6/23/2015 7:35 AM, Christian Brabandt wrote:
On Di, 23 Jun 2015, Ernie Rael wrote:
FYI: This just showed up on the cygwin mailing list, there is a
detailed analysis of the situation
The conclusion of the cygwin developer is
I think this is a bug in vim. The `if (!backup_copy)' is wrong.
On Di, 23 Jun 2015, Ernie Rael wrote:
> FYI: This just showed up on the cygwin mailing list, there is a
> detailed analysis of the situation
>
> The conclusion of the cygwin developer is
>
> >I think this is a bug in vim. The `if (!backup_copy)' is wrong. It
> >should always try to write the A
FYI: This just showed up on the cygwin mailing list, there is a detailed
analysis of the situation
The conclusion of the cygwin developer is
I think this is a bug in vim. The `if (!backup_copy)' is wrong. It
should always try to write the ACL on systems supporting them.
Forwarde
This would be very useful. For example, when using `cgn` and the dot operator
to repeat changes on all matches. This breaks down whenever the changed text
contains delimiters such as (,[,{, ... (and using an automatic
delimiter-completion plugin such as DelimitMate).
--
--
You received this
+1
--
Yukihiro Nakadaira - yukihiro.nakada...@gmail.com
--
--
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 s
10 matches
Mail list logo
