I noticed, that with 1137 (or lower?) my (own) vim.vim syntax file (maybe
others too) is broken (right now I'm at 1156).
Starting with re=0 or re=2 some items don't get highlighted any more, with re=1
everything's fine.
--
--
You received this message from the vim_dev maillist.
Do not
Hi list.
When completion popup is displayed, the popup window flicker with typing
several keys.
--
asdfasdf1
asdfasdf1211
asdfasdf1
asdfasdf123222
asdfasdf123223
asdfasdf13
asdfasdf2
--
1. type c-xc-nc-p at empty line
show popup window and clear candidate.
2. type
Axel Bender wrote:
I noticed, that with 1137 (or lower?) my (own) vim.vim syntax file
(maybe others too) is broken (right now I'm at 1156).
Starting with re=0 or re=2 some items don't get highlighted any more,
with re=1 everything's fine.
1137 is already old :-). Please sync to head.
I get the following during the compilation of Vim:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
ex_cmds2.c: In function 'profile_divide':
ex_cmds2.c:985: warning: incompatible implicit declaration of built-in
function
Hi Bram,
the break is still evident in 1156; however, I was able to track the issue
back to 1138 (backup version).
Are you saying that this vim file is not highlighted properly?
No, using my own vim.vim (the one I submitted) with re=1 as both, the syntax
file and the source file, the
Christ van Willegen wrote:
I get the following during the compilation of Vim:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
ex_cmds2.c: In function 'profile_divide':
ex_cmds2.c:985: warning: incompatible
Bram Moolenaar b...@moolenaar.net wrote:
Christ van Willegen wrote:
I get the following during the compilation of Vim:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
ex_cmds2.c: In function 'profile_divide':
Hi Bram,
Whether vim exits by itself, or by a caught signal, or by an uncaught signal,
cscope exits always.
For example, when TERM is sent to vim, the following is the ‘strace –p’ on
cscope:
strace -p 4017
Process 4017 attached - interrupt to quit
read(0, q\n, 4096)=
On my work system I ran into problems when trying to build with both
Python 2 and 3.
The first error is:
vim/src/if_python3.c:87: warning: PyString_Check redefined [enabled by
default]
926 /usr/include/python2.7/stringobject.h:58: note: this is the location of
the previous definition
I
Elimar Riesebieter wrote:
* Bram Moolenaar b...@moolenaar.net [2013-05-31 20:49 +0200]:
[...]
Note that this solves it by commenting out a function that apparently
fails. I hope you can figure out why it fails, so we can re-enable the
tests.
[...]
* Jun T.
Yasuhiro Matsumoto wrote:
When completion popup is displayed, the popup window flicker with typing
several keys.
--
asdfasdf1
asdfasdf1211
asdfasdf1
asdfasdf123222
asdfasdf123223
asdfasdf13
asdfasdf2
--
1. type c-xc-nc-p at empty line
show popup
On Monday, June 10, 2013 8:21:48 PM UTC+9, Bram Moolenaar wrote:
Yasuhiro Matsumoto wrote:
snip
Have you tried a completion near the end of the line, where inserting
the completed word makes the rest of the text move down? If I remember
correctly this caused the screen to be messed up.
I can
Axel Bender wrote:
the break is still evident in 1156; however, I was able to track the
issue back to 1138 (backup version).
Are you saying that this vim file is not highlighted properly?
No, using my own vim.vim (the one I submitted) with re=1 as both, the
syntax file and the source
Ok with 1157. Thanks, Bram!
--
--
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 subscribed to the Google Groups
On 2013/06/10, at 20:21, Bram Moolenaar b...@moolenaar.net wrote:
+#define PY_SSIZE_T_CELAN
Didn't you mean PY_SSIZE_T_CLEAN ?
Of course I believe he (Elimar) means PY_SSIZE_T_CLEAN.
It's defined further down, but inside an #ifdef. Do we need that #ifdef
here as well? Or perhaps we
On Monday, June 10, 2013 5:55:16 AM UTC-5, Bram Moolenaar wrote:
configure:5467: checking if compile and link flags for Python are sane
configure:5484: gcc -o conftest -O2 -fno-strength-reduce -Wall
-I/usr/include/python2.7 -DPYTHON_HOME=\/usr\ -pthread
-I/usr/local/include
On Mon, Jun 10, 2013 at 3:12 AM, dag.odenh...@gmail.com
dag.odenh...@gmail.com wrote:
In any case it would be killer for me if :lcd used 'cdpath' for
completions!
I sent a toy patch to do this about 3 years ago:
https://groups.google.com/forum/?fromgroups#!msg/vim_dev/uKsDbqUhr4w/TEXZEDMySdQJ
On Monday, June 10, 2013 3:00:45 AM UTC-5, mattn wrote:
Hi list.
When completion popup is displayed, the popup window flicker with typing
several keys.
[snip]
So I'm thinking it don't need to call update_screen(0) while completing.
However, redrawing status_line is needed.
How do
Patch 7.3.1158
Problem:Crash when running test 86. (Jun Takimoto)
Solution: Define PY_SSIZE_T_CLEAN early. (Elimar Riesebieter)
Files: src/if_python.c, src/if_python3.c
*** ../vim-7.3.1157/src/if_python.c 2013-06-02 18:20:12.0 +0200
--- src/if_python.c 2013-06-10
After fixing the crash, I still have test 86 fail with slightly
different output. The first difference is:
--- testdir/test86.ok 2013-06-10 12:42:36.304223000 +0200
+++ testdir/test86.failed 2013-06-10 18:31:36.849765000 +0200
@@ -497,7 +497,7 @@
d[a] = {abc : Mapping({\0 : 1})}:(type
Jun Takimoto wrote:
On 2013/06/10, at 20:21, Bram Moolenaar b...@moolenaar.net wrote:
+#define PY_SSIZE_T_CELAN
Didn't you mean PY_SSIZE_T_CLEAN ?
Of course I believe he (Elimar) means PY_SSIZE_T_CLEAN.
It's defined further down, but inside an #ifdef. Do we need that #ifdef
Patch 7.3.1159
Problem:The round() function is not always available. (Christ van
Willegen)
Solution: Use the solution from f_round().
Files: src/ex_cmds2.c, src/eval.c, src/proto/eval.pro
*** ../vim-7.3.1158/src/ex_cmds2.c 2013-06-08 18:19:39.0 +0200
---
Patch 7.3.1160
Problem:Mixing long and pointer doesn't always work.
Solution: Avoid cast to pointer.
Files: src/undo.c
*** ../vim-7.3.1159/src/undo.c 2013-04-15 15:47:07.0 +0200
--- src/undo.c 2013-06-10 20:13:37.0 +0200
***
*** 1514,1521
Patch 7.3.1161
Problem:Python: PyList_SetItem() is inefficient.
Solution: Use PyList_SET_ITEM() (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1160/src/if_py_both.h2013-06-05 20:34:07.0 +0200
--- src/if_py_both.h2013-06-10 20:37:50.0 +0200
***
***
Patch 7.3.1162
Problem:Python: Memory leaks
Solution: Add more Py_DECREF(). (ZyX)
Files: src/if_py_both.h, src/if_python.c
*** ../vim-7.3.1161/src/if_py_both.h2013-06-10 20:38:58.0 +0200
--- src/if_py_both.h2013-06-10 20:43:01.0 +0200
***
***
Building 7.3.1157 on an older system
uname -s -r -v -m -- HP-UX B.11.23 U ia64
cc --version -- cc: HP C/aC++ B3910B A.06.14 [Feb 22 2007]
./configure \
--with-features=big \
--with-x\
--enable-gui=auto \
--enable-multibyte
cc -c -I.
Patch 7.3.1163
Problem:Not easy to load Python modules.
Solution: Search python2, python3 and pythonx directories in
'runtimepath' for Python modules. (ZyX)
Files: runtime/doc/if_pyth.txt, src/configure.in, src/ex_cmds2.c,
src/if_py_both.h, src/if_python.c,
ZyX wrote:
# HG changeset patch
# User ZyX kp-...@ya.ru
# Date 1370769215 -14400
# Sun Jun 09 13:13:35 2013 +0400
# Branch python-path
# Node ID b40bfa1c4ff1b7b272bc2394a2ca44fa940c75de
# Parent a40ac5f7feca2a9af9c6d1eb0f746b7e01da7d10
Implement _vim_runtimepath_, as discussed in
Hi
Using the heap memory profiler 'valgrind --tool=massif vim'
I saw 146,176 bytes allocated from here:
| | -02.03% (146,176B) 0x492B61: do_autocmd_event (fileio.c:8623)
| | | -02.03% (146,176B) 0x4925F0: do_autocmd (fileio.c:8401)
| | | -02.03% (146,176B) 0x46CFDD: ex_autocmd
On Jun 10, 2013 8:46 PM, Bram Moolenaar b...@moolenaar.net wrote:
After fixing the crash, I still have test 86 fail with slightly
different output. The first difference is:
--- testdir/test86.ok 2013-06-10 12:42:36.304223000 +0200
+++ testdir/test86.failed 2013-06-10
Sorry, forgot to hg add new files:
# HG changeset patch
# User ZyX kp-...@ya.ru
# Date 1370895106 -14400
# Tue Jun 11 00:11:46 2013 +0400
# Branch python-path
# Node ID 7fda29626053270e0a60b7ec57168b74081c5472
# Parent 88b44813388439835b147bdccba707b3bf696c72
Add missing modules for tests;
Hi
I'm the httest maintainer and wonder if I could contribute my htt.vim
syntax file to the official vim? Is there a way to contribute
or is this the wrong place to ask? If it is the wrong place could you
point me to the right direction.
Thanx in advance
Christian
--
--
You received this
On Monday, June 10, 2013 12:55:16 PM UTC+2, Bram Moolenaar wrote:
On my work system I ran into problems when trying to build with both
Python 2 and 3.
The first error is:
vim/src/if_python3.c:87: warning: PyString_Check redefined [enabled by
default]
926
Hi,
I noticed slowness with the following file with Vim 7.3.1163 regexpengine=0.
https://raw.github.com/rails/rails/v2.3.18/actionpack/lib/action_controller/session/abstract_store.rb
rubyPredefinedConstant pattern looks much slower with this file.
syntime result:
:set re=0
TOTAL COUNT
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 141 by zulolox4...@gmail.com: C-@
http://code.google.com/p/vim/issues/detail?id=141
What steps will reproduce the problem?
1. Ctrl-@ doesn't work on Windows version
What do you see instead?
In insert mode I see only @
35 matches
Mail list logo
