cocoa cmake
I've adopted that code, and I have a vim build by cmake and gtk now.
However I still have to port many configuration options.
@James McCoy
http://mawercer.de/tmp/variations.py
put this into the repo directory containing src and adopt to your needs.
You can get multiple builds
I'd like to try providing patches for the following features:
- nox patch
https://code.google.com/r/yukihironakadaira-vim-cmdsrv-nox/
What is it? Allows client-server communication via sockets.
pro: only you can access your vim instances
con: you cannot connect to a vim instance running
Christian Brabandt wrote:
On Fr, 24 Mai 2013, Christian Brabandt wrote:
On Fr, 24 Mai 2013, Ein Brown wrote:
The SO question has more details:
http://stackoverflow.com/questions/16592654/in-vim-why-is-move-randomly-corrupting-my-folds
at the bottom of the SO question (under
On Wed, May 29, 2013 13:33, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Fr, 24 Mai 2013, Christian Brabandt wrote:
On Fr, 24 Mai 2013, Ein Brown wrote:
The SO question has more details:
On Saturday, May 25, 2013 8:50:56 PM UTC-5, MarcWeber wrote:
What is the future of Vim?
It looks like glib/gtk .. people have done a lot of work on providing
automatic bindings to many important scripting languages.
Would it make sense to think about porting some important code
On Sunday, May 26, 2013 5:52:49 PM UTC-5, skeept wrote:
I now understand why I claimed that my version supports -f.
If I go to the folder where gvim.exe is and run .\gvim -f it does NOT support
this option.
So I realized that when I type gvim in cmd I am actually running gvim.bat
We could also make vim inject those idomatic lines automatically. But I
don't think its important enough to worry about - unless somebody
prooves me wrong.
We don't have to forget: yzis failed.
Whatever we do, we have to make sure community follows.
For those who know it: yzis is a Vim clone
On Monday, May 27, 2013 12:50:58 PM UTC-5, franckspike wrote:
VsVim is an incomplete vim like editor with no support for scripts and
the whole Vim runtime I spent years to work on.
PLEASE INTEGRATE WITHIN VISUAL STUDIO !!!
And profit from the auto-completion, refactoring,
Patch 7.3.1037
Problem:Look-behind matching is very slow on long lines.
Solution: Add a byte limit to how far back an attempt is made.
Files: src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
src/testdir/test64.ok
*** ../vim-7.3.1036/src/regexp.c2013-05-21
I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on Windows 7
(64 bits). Python 2.7 (64 bits) works from the command line.
:py print hello gives me
E448: Could not load library function Py_InitModule4
E263: Sorry, this command is disabled, ...
Also,
:ec has(python)
returns
Patch 7.3.1038
Problem:Crash when using Cscope.
Solution: Avoid negative argument to vim_strncpy(). (Narendran
Gopalakrishnan)
Files: src/if_cscope.c
*** ../vim-7.3.1037/src/if_cscope.c 2013-05-06 04:21:35.0 +0200
--- src/if_cscope.c 2013-05-29
On Wed, May 29, 2013 at 10:11:13AM -0700, Axel Bender wrote:
I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on Windows
7 (64 bits). Python 2.7 (64 bits) works from the command line.
:py print hello gives me
E448: Could not load library function Py_InitModule4
E263:
Amadeus Demarzi wrote:
This is far from a complete JS example file, but it does trigger the
bug I mentioned in the afore-linked repo:
https://gist.github.com/amadeus/5667508
I don't see a problem with this file. The problem you refer to is that
comments continue in the next line, right?
Hiroshi Shirosaki wrote:
I noticed a syntax highlighting issue with filetype=html.
test.html contains the following one line.
script ![CDATA[]]
When opening test.html, [CDATA[]] is highlighted as error with set re=0.
But [CDATA[]] is not highlighted as error with set re=1.
It
On May 29, 2013 2:47 PM, Ingo Karkat sw...@ingo-karkat.de wrote:
On 29-May-2013 09:20 +0200, Gary Johnson wrote:
On 2013-05-29, Marc Weber wrote:
I wrote something similar initially, because
if exists('g:is_loaded')
finish
endif
let g:is_loaded = 1
is just verbose.
Patch 7.3.1039
Problem:New regexp engine does not support \%23c, \%23c and the like.
Solution: Implement them. (partly by Yasuhiro Matsumoto)
Files: src/regexp.h, src/regexp_nfa.c, src/testdir/test64.in,
src/testdir/test64.ok
*** ../vim-7.3.1038/src/regexp.h
Patch 7.3.1040
Problem:Python: Problems with debugging dynamic build.
Solution: Python patch 1. (ZyX)
Files: src/if_python.c, src/if_python3.c
*** ../vim-7.3.1039/src/if_python.c 2013-05-21 22:23:51.0 +0200
--- src/if_python.c 2013-05-29 21:32:46.0 +0200
Patch 7.3.1041
Problem:Python: Invalid read valgrind errors.
Solution: Python patch 2: defer DICTKEY_UNREF until key is no longer needed.
(ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1040/src/if_py_both.h2013-05-28 22:31:43.0 +0200
--- src/if_py_both.h
On Wed, May 29, 2013 at 09:33:54PM +0200, Bram Moolenaar wrote:
Patch 7.3.1040
Problem:Python: Problems with debugging dynamic build.
Solution: Python patch 1. (ZyX)
Files: src/if_python.c, src/if_python3.c
I had hopes this patch would solve the :py print hello doing
nothing on
Patch 7.3.1042
Problem:Python: can't assign to vim.Buffer.name.
Solution: Python patch 3. (ZyX)
Files: runtime/doc/if_pyth.txt, src/ex_cmds.c, src/if_py_both.h,
src/if_python3.c, src/if_python.c, src/proto/ex_cmds.pro,
src/testdir/test86.in,
Patch 7.3.1043
Problem:Python: Dynamic compilation with 2.3 fails.
Solution: Python patch 4. (ZyX)
Files: src/if_python.c
*** ../vim-7.3.1042/src/if_python.c 2013-05-29 22:02:18.0 +0200
--- src/if_python.c 2013-05-29 22:04:43.0 +0200
***
***
Patch 7.3.1044
Problem:Python: No {Buffer,TabPage,Window}.valid attributes.
Solution: Python patch 5: add .valid (ZyX)
Files: src/if_py_both.h, src/if_python3.c, src/if_python.c,
src/testdir/test86.in, src/testdir/test86.ok,
src/testdir/test87.in,
Patch 7.3.1045
Problem:Python: No error handling for VimToPython function.
Solution: Python patch 6. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1044/src/if_py_both.h2013-05-29 22:15:26.0 +0200
--- src/if_py_both.h2013-05-29 22:17:56.0 +0200
***
Patch 7.3.1046
Problem:Python: Using Py_BuildValue for building strings.
Solution: Python patch 7 and 7.5: Replace Py_BuildValue with
PyString_FromString. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1045/src/if_py_both.h2013-05-29 22:19:57.0 +0200
---
Patch 7.3.1047
Problem:Python: dir() does not work properly.
Solution: Python patch 8. Add __dir__ method to all objects with custom
tp_getattr supplemented by __members__ attribute for at least
python-2* versions. __members__ is not mentioned in python-3*
Patch 7.3.1048
Problem:Python: no consistent naming.
Solution: Python patch 9: Rename d to dict and lookupDict to lookup_dict.
(ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1047/src/if_py_both.h2013-05-29 22:36:06.0 +0200
--- src/if_py_both.h2013-05-29
Hello Marc,
Am Mittwoch, 29. Mai 2013 04:54:50 UTC+2 schrieb MarcWeber:
Hi Tim,
I've added your solution to
http://vim-wiki.mawercer.de/wiki/topic/vim%20plugin%20managment.html
If you additional notes about your tools edit the page.
I made some changes. Some projects seem
Patch 7.3.1049
Problem:Python: no consistent naming
Solution: Python patch 10: Rename DICTKEY_GET_NOTEMPTY to DICTKEY_GET. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1048/src/if_py_both.h2013-05-29 22:39:46.0 +0200
--- src/if_py_both.h2013-05-29 22:42:26.0
Patch 7.3.1050
Problem:Python: Typo in pyiter_to_tv.
Solution: Python patch 11. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1049/src/if_py_both.h2013-05-29 22:43:32.0 +0200
--- src/if_py_both.h2013-05-29 22:45:42.0 +0200
***
*** 4196,4202
Patch 7.3.1052
Problem:Python: possible SEGV and negative refcount.
Solution: Python patch 13: Fix IterIter function. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1051/src/if_py_both.h2013-05-29 22:49:21.0 +0200
--- src/if_py_both.h2013-05-29 22:51:59.0 +0200
Patch 7.3.1053
Problem:Python: no flag for types with tp_traverse+tp_clear.
Solution: Python patch 14: Add Py_TPFLAGS_HAVE_GC. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1052/src/if_py_both.h2013-05-29 22:52:29.0 +0200
--- src/if_py_both.h2013-05-29
On Wednesday, May 29, 2013 7:11:13 PM UTC+2, Axel Bender wrote:
I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on Windows
7 (64 bits). Python 2.7 (64 bits) works from the command line.
:py print hello gives me
E448: Could not load library function Py_InitModule4
E263:
It's very possible this issue was fixed.
But to confirm, yes, it was as if single line comments continued onto the next
line until there was an empty line.
Since I mostly just work in MacVim, I'll have to wait until these new changes
get merged in to confirm it's fixed.
Thanks!
On Wednesday,
On Thursday, May 30, 2013 2:42:26 AM UTC+9, Bram Moolenaar wrote:
Hiroshi Shirosaki wrote:
I noticed a syntax highlighting issue with filetype=html.
test.html contains the following one line.
script ![CDATA[]]
When opening test.html, [CDATA[]] is highlighted as error with set re=0.
Hello.
I developed completeselect option feature in Vim.
It determines how to select candidate in ins-completion.
The possible values are:
0 select and insert first candidate
1 select first candidate but not insert
2 no selected candidate
I think it is good change for completion.
I tested
Excerpts from Shougo's message of Thu May 30 02:30:12 +0200 2013:
How do you think about this feature?
Can you try providing use cases when which option is likely to be
preferred by users? Eg when do you want option no selecetd candidate ?
So can you talk about the use case which made you
On 2013-05-29, Shougo wrote:
Hello.
I developed completeselect option feature in Vim.
It determines how to select candidate in ins-completion.
The possible values are:
0 select and insert first candidate
1 select first candidate but not insert
2 no selected candidate
I think it
ok I just built 7.3.1053
the silence when I start vim on an empty buffer and issue :py print
hello is still silent
something I can't see tries to flash on the screen, and if I ask to
see :messages hello is in fact listed, but it never echoed
os suse 12.2 64 bit
kde 3.5.10
--
_|_ _ __|_|_ ._
On Wed, May 29, 2013 at 6:22 PM, Andrei Olsen andrei.ol...@gmail.comwrote:
On Wednesday, May 29, 2013 7:11:13 PM UTC+2, Axel Bender wrote:
I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on
Windows 7 (64 bits). Python 2.7 (64 bits) works from the command line.
:py print
On Thu, May 30, 2013 at 2:15 AM, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.3.1039
Problem:New regexp engine does not support \%23c, \%23c and the like.
Solution: Implement them. (partly by Yasuhiro Matsumoto)
Files: src/regexp.h, src/regexp_nfa.c, src/testdir/test64.in,
Charles, Thu 2013-05-30 @ 09:01:45+0700:
This patch causes compile error:
...\vim\src\regexp_nfa.c(3879) : error C2198: 'win_linetabsize' : too
few arguments for call
Are you using the breakindent patch? If so, it is the cause of this
failure.
I am working on an updated version of the patch
Here is the updated breakindent patch. Let me know if you encounter any
problems.
diff -r 44ca4bc7d747 runtime/doc/eval.txt
--- a/runtime/doc/eval.txt Wed May 29 22:58:32 2013 +0200
+++ b/runtime/doc/eval.txt Wed May 29 22:07:46 2013 -0400
@@ -6386,8 +6386,8 @@
keymap
On Thu, May 30, 2013 at 9:12 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Charles, Thu 2013-05-30 @ 09:01:45+0700:
This patch causes compile error:
...\vim\src\regexp_nfa.c(3879) : error C2198: 'win_linetabsize' : too
few arguments for call
Are you using the breakindent patch? If so, it is
On Thursday, May 30, 2013 3:59:59 AM UTC+2, David Fishburn wrote:
Windows 7 64.
:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 29 2013 18:37:51)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-1053
+python3/dyn
Python 3.3.0
I have never used
On Thu, May 30, 2013 at 9:31 AM, Taylor Hedberg tmhedb...@gmail.com wrote:
Here is the updated breakindent patch. Let me know if you encounter any
problems.
Vim compiles fine with that patch. Thank you.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
On Thu, May 30, 2013 at 7:45 AM, Gary Johnson garyj...@spocom.com wrote:
On 2013-05-29, Shougo wrote:
Hello.
I developed completeselect option feature in Vim.
It determines how to select candidate in ins-completion.
The possible values are:
0 select and insert first candidate
1 select
On Thu, May 30, 2013 at 7:30 AM, Shougo shougo.ma...@gmail.com wrote:
Hello.
I developed completeselect option feature in Vim.
It determines how to select candidate in ins-completion.
The possible values are:
0 select and insert first candidate
1 select first candidate but not insert
But this is really cool anyway:
http://vim-adventures.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
48 matches
Mail list logo
