On Wed, Dec 18, 2019 at 11:10 PM Gary Johnson wrote:
>
> On 2019-12-18, Andy Massimino wrote:
> > Please don't change endfunction/endif/endwhile... it makes it hard for
> > plugins
> > like match-up to make % work. Also complicates things for very little
> > benefit,
> > at best saving a tiny a
On 2019-12-18, Andy Massimino wrote:
> Please don't change endfunction/endif/endwhile... it makes it hard for plugins
> like match-up to make % work. Also complicates things for very little
> benefit,
> at best saving a tiny amount of typing, at worst makes it easy to lose track
> of
> scopes.
Yasuhiro Matsumoto wrote:
> This too, pls
>
> https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/51.patch
OK.
--
Just think of all the things we haven't thought of yet.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for
Please don't change endfunction/endif/endwhile... it makes it hard for
plugins like match-up to make % work. Also complicates things for very
little benefit, at best saving a tiny amount of typing, at worst makes it
easy to lose track of scopes.
On Wed, Dec 18, 2019, 4:27 PM Bram Moolenaar wrote
Patch 8.2.0023
Problem:Command line editing not sufficiently tested.
Solution: Add more tests. (Dominique Pelle, closes #5374)
Files: src/testdir/Make_all.mak, src/testdir/test_alot.vim,
src/testdir/test_cmdline.vim, src/testdir/test_ex_mode.vim
*** ../vim-8.2.0022/src/te
Wei Zhang wrote:
> Only one request, can we just replace all the endif endwhile endfor
> endfunction with a single end statement?
It would be even more readable if we use "}":
if cond
do something
}
for i in list
do something
}
{
Patch 8.2.0022
Problem:Click in popup window doesn't close it in the GUI. (Sergey Vlasov)
Solution: When processing the selection also send a button release event.
(closes #5367)
Files: src/gui.c
*** ../vim-8.2.0021/src/gui.c 2019-12-01 22:09:14.0 +0100
--- src/
Only one request, can we just replace all the endif endwhile endfor endfunction
with a single end statement?
--
--
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.
Patch 8.2.0021
Problem:Timer test fails too often on Travis with MacOS.
Solution: Be less strict with the time.
Files: src/testdir/test_timers.vim
*** ../vim-8.2.0020/src/testdir/test_timers.vim 2019-09-08 21:15:44.0
+0200
--- src/testdir/test_timers.vim 2019-12-18 20:09:41.
Patch 8.2.0020
Problem:Mouse clicks in the command line not tested.
Solution: Add tests. (Dominique Pelle, closes #5366)
Files: src/testdir/test_termcodes.vim
*** ../vim-8.2.0019/src/testdir/test_termcodes.vim 2019-11-26
19:21:32.0 +0100
--- src/testdir/test_termcodes.v
Pardon the question, but which are the situations right now where vimscript
is the bottleneck in terms of speed? From my (maybe little) experience with
the editor, if vim is sometimes slow/sluggish is because of a slow syntax
highlighting script. What kind of problems would a faster vimscript
Andy Massimino wrote:
> The timings are very encouraging. Is the primary speedup in the function
> parsing or better argument passing?
The main speedup is that instead of parsing each line over and over
again, it is parsed once and turned into instructions which can be
executed quickly.
What
The timings are very encouraging. Is the primary speedup in the function
parsing or better argument passing?
We have lambdas to write filter and map statements but for performance
critical applications it's still much faster to use an eval string instead
due to the function call overhead. (I.e.
Prabir Shrestha wrote:
> Glad to see you are already thinking of vim 9 and it is good to see the
> rythm of having a new goal ever year. I was personally waiting to hear more
> people comment on the ECMAScript
> (https:/ta.github.io/WasmExplorer//github.com/vim/vim/pull/5198) support
> befor
I tested the current patchlevel and it works as before, thank you for the
fix!
--
--
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 me
I really like the approach to unify the scripting interfaces, bringing Vim
closer to Acme where any language can extend the editor by echoing plain text.
Thank you for the roadmap, I will definitely be a tester!
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
16 matches
Mail list logo
