Hi list!
Am 09.05.2013 05:51, schrieb Bram Moolenaar:
[..]
5. add collaborative editing
[..]
This is a feature that Im looking for a long time. Im not so deep inside
that I would be able to write the code for this, but maybe I can give a
hint from the Libreoffice-project, which uses this way
On Thu, May 23, 2013 at 1:32 PM, Oliver Rath r...@mglug.de wrote:
Hi list!
Am 09.05.2013 05:51, schrieb Bram Moolenaar:
[..]
5. add collaborative editing
[..]
This is a feature that Im looking for a long time. Im not so deep inside
that I would be able to write the code for this, but
Hello Bram, hello Ron,
Bram Moolenaar wrote:
Hello Vim users,
[...]
Besides that, if you are maintaining runtime files, please send me any
pending updates. I will not make big changes just before the release,
everything needs some time for testing. Let's set a deadline at the end
of May.
Hallo Bram,
Thomas Köhler wrote:
Attached, you can find a new version of prolog.vim (syntax
highlightning for prolog) and koehler.vim (my colorscheme). The
former fixes a bug in prologClauseHead higlightning, the later
now supports the Underline and Ignore groups.
While I'm at it, I also
Thomas Köhler wrote:
Hello Bram, hello Ron,
Bram Moolenaar wrote:
Hello Vim users,
[...]
Besides that, if you are maintaining runtime files, please send me any
pending updates. I will not make big changes just before the release,
everything needs some time for testing. Let's set a
BTW: Is there any upcoming support for c++11 especially indent of c++11
files? Syntax highlighting can be done by external systax files but the
indenting could not be modified by users.
Really? Check out :h 'indentexpr'. It could be modified, but you will either
have to do some hacks
Ron Aaron wrote:
I know it's late to vote, but some sort of sane 'gdb' integration would
be supremely useful. I haven't found any packages for this that don't
involve a lot of setup.
There are several implementations, including my own Agide.
Pick one that is the best and improve it...
Most
I know it's late to vote, but some sort of sane 'gdb' integration would be
supremely useful. I haven't found any packages for this that don't involve a
lot of setup.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Jan Pobrislo wrote:
Glib inside gvim, since gtk+ uses glib internally. More precisely glib is
that part of gtk+ that does not deal with gui, so there's no gvim without
glib. (Unless there's implementation of gvim not based on gtk which I'm
unaware of).
A gvim can be compiled using motif under
Ken Takata wrote:
2013/05/11 Sat 5:25:21 UTC+9 Bram Moolenaar wrote:
Ken Takata wrote:
2013/05/10 Fri 10:21:37 UTC+9 mattn wrote:
On Friday, May 10, 2013 3:55:02 AM UTC+9, Bram Moolenaar wrote:
https://code.google.com/p/vim-soc2008-regexp/wiki/nfa_bugs
Andrei (the
I have two patches to submit...
I think the IDE features can provide by plugins, I am making an IDE project.
2013/5/14 Bram Moolenaar b...@moolenaar.net
Ken Takata wrote:
2013/05/11 Sat 5:25:21 UTC+9 Bram Moolenaar wrote:
Ken Takata wrote:
2013/05/10 Fri 10:21:37 UTC+9 mattn
Hi,
2013/05/11 Sat 5:25:21 UTC+9 Bram Moolenaar wrote:
Ken Takata wrote:
2013/05/10 Fri 10:21:37 UTC+9 mattn wrote:
On Friday, May 10, 2013 3:55:02 AM UTC+9, Bram Moolenaar wrote:
https://code.google.com/p/vim-soc2008-regexp/wiki/nfa_bugs
Andrei (the student who worked on
On Sat, 11 May 2013 04:45:50 +0200, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
1) Add VimL api to hook into the eventloops. The unix poll() eventloop seems
simple enough to start with.
Is it guaranteed to be available? Think MS-Windows or IBM-mainframe.
Nope, neither are
On Sat, 11 May 2013 15:44:10 +0200, Xavier de Gaye xdeg...@gmail.com wrote:
An alternative would be to allow any python thread to call the vim-python
interface through message passing.
That indeed is also possible, but for it to work properly you need to create
interface for waking the main
On 12/05/13 21:28, Jan Pobrislo wrote:
On Sat, 11 May 2013 04:45:50 +0200, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
1) Add VimL api to hook into the eventloops. The unix poll() eventloop seems
simple enough to start with.
Is it guaranteed to be available? Think MS-Windows or
On Mon, May 13, 2013 at 02:40:20AM +0200, Tony Mechelynck wrote:
On 12/05/13 21:28, Jan Pobrislo wrote:
Glib inside gvim, since gtk+ uses glib internally. More precisely glib is
that part of gtk+ that does not deal with gui, so there's no gvim without
glib. (Unless there's implementation of
On Fri, May 10, 2013 at 10:54 AM, Jan Pobrislo wrote:
I'm quite curious what is meant by IDE-like features. From my experience
most of that is covered by plugins already, except for one significant
roadblock: inability to communicate with external processes without blocking
whole UI. There
Dominique Pelle wrote:
mattn mattn...@gmail.com wrote:
On Thursday, May 9, 2013 1:26:40 PM UTC+9, Bram Moolenaar wrote:
Taro Muraoka wrote:
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
Hi vimmers!
On Sat, May 11, 2013 at 11:45 AM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 10/05/13 10:54, Jan Pobrislo wrote:
On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar b...@moolenaar.net
wrote:
The top five of the voting list:
http://www.vim.org/sponsor/vote_results.php
Hi, Bram and list
2013/5/9(Thu) 12:51:48 UTC+9 Bram Moolenaar:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
In recent years, the resolution of the display
Bram Moolenaar wrote:
Not required for Vim itself, but there can be plugins that require it.
There has been a interest in a pluggable RE engine like grep has --
Specifically, the perl RE is best in breed by almost independent
evaluation --
it even includes python additions.
It' also
On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar b...@moolenaar.net wrote:
The top five of the voting list:
http://www.vim.org/sponsor/vote_results.php
1. add IDE features
2. add integration with Python instead of inventing more Vim script
3. fix all problems, big and small; make Vim more
Hi,
2013/05/10 Fri 10:21:37 UTC+9 mattn wrote:
On Friday, May 10, 2013 3:55:02 AM UTC+9, Bram Moolenaar wrote:
https://code.google.com/p/vim-soc2008-regexp/wiki/nfa_bugs
Andrei (the student who worked on this) does mention multi-byte. He
says it slows down the execution, thus the
I'm sure everybody has their favorite patch that he would like to see
included.
Maybe one should rather think of the breakindent patch as a basic feature of a
modern text editors that fully supports soft word wrap.
--
--
You received this message from the vim_dev maillist.
Do not top-post!
Andy Spencer wrote:
On 2013-05-09 05:51, Bram Moolenaar wrote:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
How about the gvim port to GTK 3? I'll see if
Ken Takata wrote:
2013/05/10 Fri 10:21:37 UTC+9 mattn wrote:
On Friday, May 10, 2013 3:55:02 AM UTC+9, Bram Moolenaar wrote:
https://code.google.com/p/vim-soc2008-regexp/wiki/nfa_bugs
Andrei (the student who worked on this) does mention multi-byte. He
says it slows down the
mattn mattn...@gmail.com wrote:
On Thursday, May 9, 2013 1:26:40 PM UTC+9, Bram Moolenaar wrote:
Taro Muraoka wrote:
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
regexp engine for patterns
On 10/05/13 23:05, Dominique Pellé wrote:
mattn mattn...@gmail.com wrote:
On Thursday, May 9, 2013 1:26:40 PM UTC+9, Bram Moolenaar wrote:
Taro Muraoka wrote:
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the
On 10/05/13 10:54, Jan Pobrislo wrote:
On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar b...@moolenaar.net wrote:
The top five of the voting list:
http://www.vim.org/sponsor/vote_results.php
1. add IDE features
2. add integration with Python instead of inventing more Vim script
3. fix all
On 09/05/13 05:51, Bram Moolenaar wrote:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
[...]
Maybe we could decide that Vim 7.3.999 + 1 will be 7.4.000, and make
Hi Ron!
On Mi, 08 Mai 2013, Ron Aaron wrote:
2. add integration with Python instead of inventing more Vim script
I hope this doesn't mean Python will be *required*. That would be a badness.
Pretty sure not. I think the python interpreter will always be optional.
regards,
Christian
--
Hi Bram!
On Do, 09 Mai 2013, Bram Moolenaar wrote:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
The top five of the voting list:
Can you elaborate on the IDE features that you have planned?
--
--
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
Yay - time for a new branch! 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
1. Include the Python patches that ZyX has created. This improves the
Vim API from the Python interface.
I just wanted to write an RFC with new interfaces. These are even bigger
changes, so it would be bad idea to start writing them without discussion. But
these are unlikely to be written
Am 09.05.2013 05:51, schrieb Bram Moolenaar:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999.
I don't want to find out what happens if we go over that, so it's time
for Vim 7.4!
Wish:
Vim 7.4 becomes a release with all current patches and no new
I'd like to see the breakindent patch included.
Yes, please!
--
--
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
Ron Aaron wrote:
On Thursday, May 9, 2013 6:51:48 AM UTC+3, Bram Moolenaar wrote:
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
That's very exciting!
2. add integration with Python instead of inventing more Vim script
I hope this doesn't mean
Yasuhiro Matsumoto wrote:
On Thursday, May 9, 2013 1:26:40 PM UTC+9, Bram Moolenaar wrote:
Taro Muraoka wrote:
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
regexp engine for patterns
Christian Brabandt wrote:
On Do, 09 Mai 2013, Bram Moolenaar wrote:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
The top five of the voting list:
On Friday, May 10, 2013 3:55:02 AM UTC+9, Bram Moolenaar wrote:
https://code.google.com/p/vim-soc2008-regexp/wiki/nfa_bugs
Andrei (the student who worked on this) does mention multi-byte. He
says it slows down the execution, thus the multi-byte support should be
there. We need to find the
On 2013-05-09 05:51, Bram Moolenaar wrote:
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
How about the gvim port to GTK 3? I'll see if I can get that working if
Hello Vim users,
We are now at patch level 7.3.931. In a few weeks we would reach 999. I
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
The top five of the voting list:
http://www.vim.org/sponsor/vote_results.php
1. add IDE features
2. add integration with
[Replied only to the Vim Developers' list.]
On Thu, 9 May 2013, Bram Moolenaar wrote:
it's time for Vim 7.4!
[...]
1. Include the Python patches that ZyX has created. This improves
the Vim API from the Python interface.
I know you cannot possibly be expected to add similar support for
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
regexp engine for patterns that might not work with the new one.
I want to look into this patch from view point of multibyte characters.
Where can I
Christian J. Robinson wrote:
[Replied only to the Vim Developers' list.]
On Thu, 9 May 2013, Bram Moolenaar wrote:
it's time for Vim 7.4!
[...]
1. Include the Python patches that ZyX has created. This improves
the Vim API from the Python interface.
I know you cannot
Taro Muraoka wrote:
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
regexp engine for patterns that might not work with the new one.
I want to look into this patch from view point of multibyte
--- On Wed, 5/8/13, Christian J. Robinson hept...@gmail.com wrote:
From: Christian J. Robinson hept...@gmail.com
Subject: Re: Plans for Vim 7.4
To: vim_dev@googlegroups.com
Date: Wednesday, May 8, 2013, 9:01 PM
[Replied only to the Vim Developers' list.]
On Thu, 9 May 2013, Bram
On Wed, 8 May 2013, Suresh Govindachar wrote:
What are these extras Christian is referring to?
Mostly it's just been a case of occasionally seeing a new Python→Vim
integration feature added and I have thought, Oh, I wish the
Python→Perl interface had that too. Oh well.
Among them, I
On Thursday, May 9, 2013 6:51:48 AM UTC+3, Bram Moolenaar wrote:
don't want to find out what happens if we go over that, so it's time for
Vim 7.4!
That's very exciting!
2. add integration with Python instead of inventing more Vim script
I hope this doesn't mean Python will be *required*.
On Thursday, May 9, 2013 6:51:48 AM UTC+3, Bram Moolenaar wrote:
Hello Vim users,
... so it's time for Vim 7.4!
Wonderful news!
2. add integration with Python instead of inventing more Vim script
I hope this doesn't mean Python will be required, that would be a badness.
--
--
You
What about support fuzzy matching?
2013/5/9 Bram Moolenaar b...@moolenaar.net
Christian J. Robinson wrote:
[Replied only to the Vim Developers' list.]
On Thu, 9 May 2013, Bram Moolenaar wrote:
it's time for Vim 7.4!
[...]
1. Include the Python patches that ZyX has
52 matches
Mail list logo
