Hi Bram and Nobuhiro,
2014/05/28(Wed) 20:42:17 UTC+9 Bram Moolenaar:
Nobuhiro Takasaki wrote:
It is a test that is an error in the patch before.
It does not result in an error in the patch after.
The correctness of meaning, there is no confidence.
If there is a better
Hirohito Higashi wrote:
Hi Bram and Nobuhiro,
2014/05/28(Wed) 20:42:17 UTC+9 Bram Moolenaar:
Nobuhiro Takasaki wrote:
It is a test that is an error in the patch before.
It does not result in an error in the patch after.
The correctness of meaning, there is no
Patch 7.4.315 (after 7.4.309)
Problem:Fixes for computation of topline not tested.
Solution: Add test. (Hirohito Higashi)
Files: src/testdir/Make_amiga.mak, src/testdir/Make_dos.mak,
src/testdir/Make_ming.mak, src/testdir/Make_os2.mak,
src/testdir/Make_vms.mms,
Could anyone explain why does Vim still have vi-compatibility mode? Why
would one use it?
As a consequence, we have to keep set nocompatible in our .vimrc; there is
much noise in docs like {not in Vi}, {Vi: no ++opt}, etc.
and I can't really understand why developers keep it so carefully.
--
Christian wrote:
On Mi, 28 Mai 2014, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 12 Mai 2014, Christian Brabandt wrote:
Thanks, I enhanced it further. You can adjust the behaviour now using
:set breakindentopt
For now, I put the patch here:
On May 29, 2014, at 4:50 AM, Dmitry Frank dimon.fr...@gmail.com wrote:
Could anyone explain why does Vim still have vi-compatibility mode? Why would
one use it?
As a consequence, we have to keep set nocompatible in our .vimrc; there is
much noise in docs like {not in Vi}, {Vi: no ++opt},
Dmitry Frank schrob am Donnerstag, 29. Mai 2014 um 11:50 Zeit:
and I can't really understand why developers keep it so carefully.
What's wrong with that?
If you don't want that, use NeoVim or something.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
Hi,
On Thursday, May 29, 2014 11:50:47 AM UTC+2, Dmitry Frank wrote:
Could anyone explain why does Vim still have vi-compatibility mode? Why would
one use it?
As a consequence, we have to keep set nocompatible in our .vimrc; there is
much noise in docs like {not in Vi}, {Vi: no ++opt},
I recently discovered 'cdpath', and noticed VIM is doing a good job at it,
except :cd doesn't autocomplete the valid paths from the 'cdpath'. I wrote this
script as a hack to work around it :
function! s:CdComplete(ArgLead, CmdLine, CursorPos)
let pattern = empty(a:ArgLead) ? '*/' : '*' .
On Do, 29 Mai 2014, Dmitry Frank wrote:
Could anyone explain why does Vim still have vi-compatibility mode? Why
would one use it?
As a consequence, we have to keep set nocompatible in our .vimrc; there is
No:
,[ :h 'cp' ]-
| When a |vimrc| or |gvimrc| file is found while Vim is
On 2014-05-29 01:46 PM, Christian Brabandt wrote:
On Do, 29 Mai 2014, Dmitry Frank wrote:
Could anyone explain why does Vim still have vi-compatibility mode? Why
would one use it?
never forget your roots
nor your humble beginnings.
nor your grandpa! :p
As a consequence, we have to
Patch 7.4.316
Problem:Warning from 64-bit compiler.
Solution: Add type cast. (Mike Williams)
Files: src/ex_getln.c
*** ../vim-7.4.315/src/ex_getln.c 2014-05-07 18:35:25.665216052 +0200
--- src/ex_getln.c 2014-05-29 14:32:53.584860716 +0200
***
*** 5202,5208
On Thursday, May 29, 2014 11:52:29 AM UTC+2, Dhruva Sagar wrote:
I recently discovered 'cdpath', and noticed VIM is doing a good job at it,
except :cd doesn't autocomplete the valid paths from the 'cdpath'. I wrote
this script as a hack to work around it :
function! s:CdComplete(ArgLead,
I am aware of the fact that it's set from $CDPATH and it is doing that
correctly. At least in ZSH (which I use), it does complete directory names from
the $CDPATH.
On Thursday, May 29, 2014 7:50:21 PM UTC+5:30, glts wrote:
On Thursday, May 29, 2014 11:52:29 AM UTC+2, Dhruva Sagar wrote:
I
I have had an annoying issue with gvim 7.4, with patches 1-307. If I open a
large file (e.g. containing 200,000 lines) and use the global command to delete
lines, the operation takes a very long time on Windows if clipboard has been
set to unnamed. I'm assuming it's the constant copying of
Hello
Recently I had experienced a segmentation fault
at the last mch_memmove() call in the function
clip_x11_convert_selection_cb() of ui.c.
This fault happens under the conditions:
*target == utf8_atom
*length == 0
enc_utf8 == false.
In fact, if clip_x11_convert_selection_cb() is called
under
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On May 29, 2014 9:25:05 PM GMT+03:00, Praful Kapadia praful...@gmail.com
wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307. If I
open a large file (e.g. containing 200,000 lines) and use the global
command to delete lines, the
It's a bit hard to see the excellent advice in that last post,
so here it is:
To delete (not cut) all lines matching pattern use:
:g/pattern/d_
John
--
--
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
18 matches
Mail list logo
