> Perhaps the patch didn't apply properly. Can you please take the current
> version in Mercurial and aplly you changes to that?
I merged your changes.
https://github.com/vim-jp/cpp-vim/ (master branch)
And below is diff from your last changes
https://gist.github.com/mattn/5124324
--
--
Yo
Yasuhiro Matsumoto wrote:
> > > What code did you use?
> > Vim source code. Happens in all functions with nested {}.
>
>
> I checked 20 files in vim's source code, but I didn't see the problem.
> Did you replace syntax/c.vim and syntax/cpp.vim ? Or put into your after
> directory?
>
> > > C
> > What code did you use?
> Vim source code. Happens in all functions with nested {}.
I checked 20 files in vim's source code, but I didn't see the problem.
Did you replace syntax/c.vim and syntax/cpp.vim ? Or put into your after
directory?
> > Currently, when I use last updated c.vim/cpp.v
Yasuhiro Matsumoto wrote:
> > Unfortunately I now see many "}" highlighted as an error in C code.
> >
> > I removed the changes for now.
> >
> > I'll push the current version to the repository.
>
> What code did you use?
Vim source code. Happens in all functions with nested {}.
> Currently,
> Unfortunately I now see many "}" highlighted as an error in C code.
>
> I removed the changes for now.
>
> I'll push the current version to the repository.
What code did you use?
Currently, when I use last updated c.vim/cpp.vim, C++11 lambda expression has
wrong syntax.
http://go-gyazo.apps
Yasuhiro Matsumoto wrote:
> Yes, C11 is not C++11. It's ISO/IEC 9899: 2011.
Unfortunately I now see many "}" highlighted as an error in C code.
I removed the changes for now.
I'll push the current version to the repository.
--
In many of the more relaxed civilizations on the Outer Eastern Rim
Yes, C11 is not C++11. It's ISO/IEC 9899: 2011.
On 3/2/13, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
>> > This uses the variable cpp_no_cpp11. Can we document this?
>>
>> https://gist.github.com/5047752
>
> Thanks.
>
>> > There also is c_no_c11, I suppose that has a different meaning
Yasuhiro Matsumoto wrote:
> > This uses the variable cpp_no_cpp11. Can we document this?
>
> https://gist.github.com/5047752
Thanks.
> > There also is c_no_c11, I suppose that has a different meaning.
>
> It exists in c.vim already.
>
> Sorry I can add more in well‐chosen words...
I mean t
> This uses the variable cpp_no_cpp11. Can we document this?
https://gist.github.com/5047752
> There also is c_no_c11, I suppose that has a different meaning.
It exists in c.vim already.
Sorry I can add more in well‐chosen words...
--
--
You received this message from the "vim_dev" maillist
Yasuhiro Matsumoto wrote:
> We updated c.vim / cpp.vim for support C++11.
>
> https://github.com/vim-jp/cpp-vim
>
> In the final analysis, we dropped syntax of ternary operator in C++11.
>
> https://github.com/vim-jp/cpp-vim/issues/7
>
> If lambda is contained in ternary operator, syntax beco
ex. lambda in ternary operator
https://github.com/vim-jp/cpp-vim/issues/7
--
--
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
Hi bram.
We updated c.vim / cpp.vim for support C++11.
https://github.com/vim-jp/cpp-vim
In the final analysis, we dropped syntax of ternary operator in C++11.
https://github.com/vim-jp/cpp-vim/issues/7
If lambda is contained in ternary operator, syntax become too complex.
So if user doesn't s
12 matches
Mail list logo
