Hi, this topic has already been discussed in 2008, and became dead.
Time to make it born again.
I was talking with Bram about the limitations of libcall: the load/unload
of a library at every invocation and the arguments limitations.
I talked about a small change on it to avoid the load/unload pr
Hi, this topic has already been discussed in 2008, and became dead.
Time to make it born again.
I was talking with Bram about the limitations of libcall: the load/unload
of a library at every invocation and the arguments limitations.
I talked about a small change on it to avoid the load/unload pr
I noticed that if Vim is in Hit-enter mode when a command gets run in the
background via vim.command(), vim officially stays in Hit-enter mode
("vim.eval('mode()')" continues to return 'r'), but the Hit-enter display
disappears. A similar problem occurs if you're using the "list" wildmode
when vim.
On Tuesday, August 28, 2012 1:05:01 AM UTC-4, Sergey Khorev wrote:
> > link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
>
> ...
>
> > advapi32.lib shell32.lib /machine:i386 /no
>
>
>
> Ok, the problem is in /machine:i386 which should be AMD64 for x64
>
> builds. Either something
Charles Campbell wrote:
Simon Ruderich wrote:
On Wed, Sep 05, 2012 at 03:46:00PM +0200, Bram Moolenaar wrote:
Thanks for pointing me to this patch. It fixes a few tab related
issues I just noticed (and tried to fix - you saved me some time,
thanks).
Which patch is that, who sent it?
It's Domi
Simon Ruderich wrote:
On Wed, Sep 05, 2012 at 03:46:00PM +0200, Bram Moolenaar wrote:
Thanks for pointing me to this patch. It fixes a few tab related
issues I just noticed (and tried to fix - you saved me some time,
thanks).
Which patch is that, who sent it?
It's Dominique P
> I tried to add the functions (patch attached - as I'm new to Vim
> internals, please tell me if that's the correct way to do it),
> but there is one major problem. screen_cur_col and screen_cur_row
> report the current cursor position - which is of course the
> command line where the current comm
Patch 7.3.659
Problem:Recent Python changes are not tested.
Solution: Add tests for Python bindings. (ZyX)
Files: src/testdir/test86.in, src/testdir/test86.ok,
src/testdir/test87.in, src/testdir/test87.ok
*** ../vim-7.3.658/src/testdir/test86.in2012-06-29 12:54:32.
Patch 7.3.658
Problem:NUL bytes truncate strings when converted from Python.
Solution: Handle truncation as an error. (ZyX)
Files: src/if_py_both.h, src/if_python3.c
*** ../vim-7.3.657/src/if_py_both.h 2012-09-05 18:45:24.0 +0200
--- src/if_py_both.h2012-09-05 19:05:27
Patch 7.3.657
Problem:Python bindings silently truncate string values containing NUL.
Solution: Fail when a string contains NUL. (ZyX)
Files: src/if_python.c, src/if_python3.c
*** ../vim-7.3.656/src/if_python.c 2012-09-05 18:54:37.0 +0200
--- src/if_python.c 2012-09-0
On Wed, Sep 05, 2012 at 03:46:00PM +0200, Bram Moolenaar wrote:
>> Thanks for pointing me to this patch. It fixes a few tab related
>> issues I just noticed (and tried to fix - you saved me some time,
>> thanks).
>
> Which patch is that, who sent it?
It's Dominique Pellé's patch:
http://comments.g
Note: the patch probably doesn't work, since this is a binary file.
Get the file from Mercurial instead, or get the patch file from the ftp
server.
Patch 7.3.655
Problem:64 bit MingW xpm .a file is missing.
Solution: Add the file. (Sergey Khorev)
Files: src/xpm/x64/lib/libXpm.a
*** .
Patch 7.3.656
Problem:Internal error in :pyeval.
Solution: Handle failed object conversion. (ZyX)
Files: src/if_python.c, src/if_python3.c
*** ../vim-7.3.655/src/if_python.c 2012-06-30 13:34:29.0 +0200
--- src/if_python.c 2012-09-05 18:52:50.0 +0200
**
Patch 7.3.654
Problem:When creating a Vim dictionary from Python objects an empty key
might be used.
Solution: Do not use empty keys, throw an IndexError. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.653/src/if_py_both.h 2012-09-05 17:28:08.0 +0200
--- src/if_p
Patch 7.3.653
Problem:MingW needs build rule for included XPM files. Object directory
for 32 and 64 builds is the same, also for MSVC.
Solution: Add MingW build rule to use included XPM files. Add the CPU or
architecture to the object directory name. (Sergey Khorev)
Patch 7.3.652
Problem:Workaround for Python crash isn't perfect.
Solution: Change the type of the length argument. (Sean Estabrooks)
Files: src/if_py_both.h
*** ../vim-7.3.651/src/if_py_both.h 2012-08-08 16:05:03.0 +0200
--- src/if_py_both.h2012-09-05 17:15:31.
Ingo Karkat wrote:
> In a plugin, I want to avoid that a :put =var command clobbers the expression
> register, so I save this via getreg('=', 1). I realized that I couldn't use
> setreg() to restore the expression register, but assignment via :let @= = var
> works just fine. Is this disallowed fo
Simon Ruderich wrote:
> diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
> index 7a5fa04..fe77265 100644
> --- a/runtime/doc/autocmd.txt
> +++ b/runtime/doc/autocmd.txt
> @@ -203,7 +203,7 @@ Name triggered by ~
> Reading
> |BufNewFile| starting to
Simon Ruderich wrote:
[...]
> > There is a patch pending which fixes those alignment issues among other
> > problems (whether Vim uses conceal feature or not).
>
> Thanks for pointing me to this patch. It fixes a few tab related
> issues I just noticed (and tried to fix - you saved me some time
Simon Ruderich wrote:
> diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
> index a8bff07..7a5fa04 100644
> --- a/runtime/doc/autocmd.txt
> +++ b/runtime/doc/autocmd.txt
> @@ -263,8 +263,11 @@ Name triggered by ~
> Startup and exit
> |VimEnter| af
Patch 7.3.651
Problem:Completion after ":help \{-" gives an error message.
Solution: Prepend a backslash.
Files: src/ex_cmds.c
*** ../vim-7.3.650/src/ex_cmds.c2012-08-08 16:50:40.0 +0200
--- src/ex_cmds.c 2012-09-05 15:10:13.0 +0200
***
*** 48
Patch 7.3.650
Problem:Completion after ":help \{-" gives an error message and messes up
the command line.
Solution: Cancel the tag search if the pattern can't be compiled. (Yasuhiro
Matsumoto)
Files: src/tag.c
*** ../vim-7.3.649/src/tag.c2012-01-10 22:26:12
Yasuhiro Matsumoto wrote:
> Try to type following into command line.
>
> :help \{-
>
> And type . You'll see error message, and you'll see broken command line.
>
> :help E64
>
> The words should be kept on the command line after displaying E64.
> Below is a patch.
>
> https://gist.github.com
Simon Ruderich wrote:
> Patch 7.3.504 and the following runtime update changed (some of)
> the ".." notation to `..` with a different highlighting.
>
> I'm not entirely sure what counts as a command. Should `..` be
> used for all commands which can be entered, e.g. even `3dw` or
> `v`, but also
Christian Brabandt wrote:
> On Di, 04 Sep 2012, Ingo Karkat wrote:
>
> > this does indeed fix the problem, but now (with empty 'clipboard'),
> > when I "dd" a single line, I get "cannot yank; delete anyway (y/n)?"
> > and then a "E470: Command aborted" when I press "n".
>
> Oh yes, sorry.
> Thi
Patch 7.3.649
Problem:When 'clipboard' is set to "unnamed" small deletes end up in the
numbered registers. (Ingo Karkat)
Solution: Use the original register name to decide whether to put a delete
in a numbered register. (Christian Brabandt)
Files: src/ops.c
***
ZyX wrote:
> Consider the following script:
>
> autocmd BufReadCmd read://* call setline('.', split(expand(''),
> '/')[1:])
> edit `='read://'.join(range(100), '/')`
> file
> . Being launched with “vim -u NONE -S longfnamebug.vim -s <(<<<
> $'\n')” it causes vim to crash with SI
Patch 7.3.648
Problem:Crash when using a very long file name. (ZyX)
Solution: Properly check length of buffer space.
Files: src/buffer.c
*** ../vim-7.3.647/src/buffer.c 2012-07-16 17:31:48.0 +0200
--- src/buffer.c2012-09-05 13:17:38.0 +0200
***
***
Patch 7.3.647
Problem:"gnd" doesn't work correctly in Visual mode.
Solution: Handle Visual mode differently in "gn". (Christian Brabandt)
Files: src/search.c, src/testdir/test53.in, src/testdir/test53.ok
*** ../vim-7.3.646/src/search.c 2012-08-23 15:53:00.0 +0200
--- src/searc
29 matches
Mail list logo
