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
On Thursday, May 9, 2013 7:54:38 AM UTC+9, ZyX wrote:
I don't hope that capture() contains highlight attributes. It should be plain
text. And I guess fixing redir nesting has problems.
1. There are plugins that depend on original behavior. This break compatible.
2. If skipped 'redir END' with e
Feng Xiao wrote:
> Attached is the syntax highlighting file for Google Protocol Buffers.
> Please help include it in vim runtime.
Thanks!
It has a bit of a scary copyright notice. Is that really needed?
We need to at least check if it is compatible with the Vim license.
Otherwise redistributio
ZyX wrote:
> This is a description of proposed new python interfaces.
Well, that's a very long list. Do we really need all of this?
Let's at least order by usefulness. First add things that help
plugin writers most. I'm assuming that very few users will type
Python commands, I expect them to
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 fin
Hi vim-dev,
Attached is the syntax highlighting file for Google Protocol Buffers.
Please help include it in vim runtime.
Thanks,
Feng
--
--
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 ht
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 t
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
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 d
> 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 becaus
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 features
Hello All,
The JavaScript syntax file does not currently highlight regular
expression literals which contain any modifiers other than g and/or i.
So, for example, the following literal would not be highlighted
/^Match me$/gm
ECMA-262 edition 5.1[1] defines the flags in the syntax in ยง7.8.5 as
be
This is a description of proposed new python interfaces.
==
New python objects
==
vim.mappings/{buffer}.mappings:
Dictionary-like object mapping mode characters to vim.modemappings objects
below. Unlike vim.buffers iteration is being done for keys.
modema
> 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 writte
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 t
On Thu, Apr 18, 2013 at 4:58 PM, glts <676c7...@gmail.com> wrote:
> Hi,
>
> I have recently learnt of a patch that was submitted to the list almost
> five years ago. Please see here:
>
> https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ
>
> The reception was positive but for some rea
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 a
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:
> http://www.vim.org/s
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
--
19 matches
Mail list logo