Re: Upcoming Vim 8.2 release
The 2019-12-10 21:38, Bram Moolenaar wrote: Thanks for the example, I can see the problem. When the info popup is used redrawing is done differently and a flag isn't set that avoids drawing over the popup menu. Let me set that flag check for side effects. Patch 8.1.2415 is a huge improvement. With ordinary 'info' there is no longer any flickering of the menu, or the "preview" popup. However, replacing the contents of the preview popup still cause the completion menu to flicker (less than before though): https://asciinema.org/a/9lWTPWH7NmS84qoaYDUyNsJTl -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20191210215200.GC11540%40KERERU.localdomain.
Re: Upcoming Vim 8.2 release
Nick Spoons wrote:
> The 2019-12-09 22:06, Bram Moolenaar wrote:
> >It should not flicker that much. Especially now that a mask is used to
> >only redraw what is needed.
>
> Yes that's the tricky bit, it doesn't flicker nearly that much in a
> minimal example, so it's hard to demonstrate. But here is a minimal
> example and there _is_ flickering, particularly when moving from
> completion items with no 'info' to items _with_ 'info':
>
> https://asciinema.org/a/qAVyBR43LeuGgM2jenE4Mb3VS
>
> The example here is the following, where the completion menu is
> triggered with ``:
>
> ```vim
>
> func DummyComplete(findstart, base)
> if a:findstart
> return 0
> else
> let info = range(100)->map({_ -> 'abcde'})->join()
> let noinfo_items = range(5)->map({i -> #{ word: 'word_'..(i+5) }})
> let info_items = range(5, 10)->map({i -> #{ word: 'word_'..i, info: info
> }})
> return noinfo_items + info_items
> endif
> endfunc
>
>
> set completeopt+=popup
> setlocal completefunc=DummyComplete
> ```
Thanks for the example, I can see the problem.
When the info popup is used redrawing is done differently and a flag
isn't set that avoids drawing over the popup menu. Let me set that flag
check for side effects.
BTW: still looking for nice screenshots to use in the Vim 8.2
announcement.
--
"Marriage is a wonderful institution...
but who wants to live in an institution?"
- Groucho Marx
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/201912102038.xBAKcVVW022863%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
The 2019-12-09 22:06, Bram Moolenaar wrote:
It should not flicker that much. Especially now that a mask is used to
only redraw what is needed.
Yes that's the tricky bit, it doesn't flicker nearly that much in a
minimal example, so it's hard to demonstrate. But here is a minimal
example and there _is_ flickering, particularly when moving from
completion items with no 'info' to items _with_ 'info':
https://asciinema.org/a/qAVyBR43LeuGgM2jenE4Mb3VS
The example here is the following, where the completion menu is
triggered with ``:
```vim
func DummyComplete(findstart, base)
if a:findstart
return 0
else
let info = range(100)->map({_ -> 'abcde'})->join()
let noinfo_items = range(5)->map({i -> #{ word: 'word_'..(i+5) }})
let info_items = range(5, 10)->map({i -> #{ word: 'word_'..i, info: info }})
return noinfo_items + info_items
endif
endfunc
set completeopt+=popup
setlocal completefunc=DummyComplete
```
Regards, Nick
--
--
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 the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20191209214402.GA11540%40KERERU.localdomain.
Re: Upcoming Vim 8.2 release
> I'm also really enjoying the popups. I have a screencast here, but it > demonstrates a problem rather than acts as a showcase I think: > > https://asciinema.org/a/ARcxLcTKZepZfnBTsBjFqv88y > > The flickering of both the popupmenu and the 'info' popup are quite > extreme. Admittedly this example is also extreme in the sense that there > are many settings and plugins in use here, including text properties being > used to semantically highlight the buffer. But my efforts to reduce the > issue to any one plugin or option have failed - there is always _some_ > flickering in a completion menu with 'info' and `completeopt+=popup`, and > the more highlights and text_properties in the buffer, the more obvious the > flickering becomes. > > Does the popupmenu have to be destroyed and recreated as the selection > changes? Or can redrawing perhaps be disabled during this period? It should not flicker that much. Especially now that a mask is used to only redraw what is needed. Perhaps your code somehow marks the menu in a way it's destroyed and recreated? Can you make a simplified example (with dummy data) to illustrate the problem? If you have an async way of updating, you can use a timer to simulate that. -- hundred-and-one symptoms of being an internet addict: 237. You tattoo your email address on your forehead. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201912092106.xB9L6fHa025388%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
On Saturday, 30 November 2019 10:13:22 UTC+13, Bram Moolenaar wrote: > > I'm also wondering: what is your favorite improvement since Vim 8.1? > I'm also really enjoying the popups. I have a screencast here, but it demonstrates a problem rather than acts as a showcase I think: https://asciinema.org/a/ARcxLcTKZepZfnBTsBjFqv88y The flickering of both the popupmenu and the 'info' popup are quite extreme. Admittedly this example is also extreme in the sense that there are many settings and plugins in use here, including text properties being used to semantically highlight the buffer. But my efforts to reduce the issue to any one plugin or option have failed - there is always _some_ flickering in a completion menu with 'info' and `completeopt+=popup`, and the more highlights and text_properties in the buffer, the more obvious the flickering becomes. Does the popupmenu have to be destroyed and recreated as the selection changes? Or can redrawing perhaps be disabled during this period? -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/265d1edd-d13a-436b-a17f-67455526b21a%40googlegroups.com.
Re: Upcoming Vim 8.2 release
Ben Jackson wrote: > > what is your favorite improvement since Vim 8.1? > > popup windows :) I guess I'm a little biased, but I think this is a great > improvement, and the API is really nice to use. I'm glad you like it, it was quite a lot of work to implement it all. If someone has a nice screenshot, please show us. I would like to include some in the 8.2 announcement. -- hundred-and-one symptoms of being an internet addict: 197. Your desk collapses under the weight of your computer peripherals. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201912061428.xB6ES9SA004136%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
Ken Takata wrote: > Here is another patch for the latest version8.txt: > > --- a/runtime/doc/version8.txt > +++ b/runtime/doc/version8.txt > @@ -40841,7 +40841,7 @@ Files:src/register.c, src/testdir/t > Patch 8.1.2376 > Problem:Preprocessor indents are incorrect. > Solution: Fix the indents. (Ken Takata, closes #5298) > -Files:src/drawline.c, src/gui_w32.c src/os_mswin.c src/os_win32.c > +Files:src/drawline.c, src/gui_w32.c, src/os_mswin.c, > src/os_win32.c, > src/proto.h > > Patch 8.1.2377 > > > Commas were missing. I'll include it, thanks. -- hundred-and-one symptoms of being an internet addict: 196. Your computer costs more than your car. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201912061428.xB6ES86T004118%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
> what is your favorite improvement since Vim 8.1? popup windows :) I guess I'm a little biased, but I think this is a great improvement, and the API is really nice to use. On Friday, November 29, 2019 at 9:13:22 PM UTC, Bram Moolenaar wrote: > > > It appears the number of bug reports is getting lower. I have included > many pending pull requests. I think we are getting closer to a release. > > If you have any runtime updates, please send them now! > > I'm also wondering: what is your favorite improvement since Vim 8.1? > > -- > hundred-and-one symptoms of being an internet addict: > 142. You dream about creating the world's greatest web site. > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net > \\\ > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ > \\\ > \\\ an exciting new programming language -- http://www.Zimbu.org > /// > \\\help me help AIDS victims -- http://ICCF-Holland.org > /// > -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/1efe08ed-fd93-4c0e-9ba3-f6e6b0f0edb0%40googlegroups.com.
Re: Upcoming Vim 8.2 release
Hi Bram, Here is another patch for the latest version8.txt: --- a/runtime/doc/version8.txt +++ b/runtime/doc/version8.txt @@ -40841,7 +40841,7 @@ Files:src/register.c, src/testdir/t Patch 8.1.2376 Problem:Preprocessor indents are incorrect. Solution: Fix the indents. (Ken Takata, closes #5298) -Files:src/drawline.c, src/gui_w32.c src/os_mswin.c src/os_win32.c +Files:src/drawline.c, src/gui_w32.c, src/os_mswin.c, src/os_win32.c, src/proto.h Patch 8.1.2377 Commas were missing. Retards, Ken Takata -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/9f708409-469f-49a5-8ab0-9feb6c90c6ad%40googlegroups.com.
Re: Upcoming Vim 8.2 release
Ken Takata wrote: > Sorry, my previous patch had a mistake. > Could you apply the following patch? > > --- a/runtime/doc/version8.txt > +++ b/runtime/doc/version8.txt > @@ -35845,7 +35845,7 @@ Solution: Ignore the "browse" modifier > Files:src/ex_cmds.c > > Patch 8.1.1595 > -Problem:MS-Windows with VIMDLL: colors wrong in console. > +Problem:MS-Windows with VIMDLL: colors wrong in the GUI. > Solution: Do not set the terminal colors when not using the GUI. (Ken > Takata, closes #4588) > Files:src/syntax.c > > > I wasn't aware that you changed the description from the commit message of > git. It was changed in June. I'll include this change. -- hundred-and-one symptoms of being an internet addict: 188. You purchase a laptop so you can surf while sitting on the can. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201912051242.xB5CgfnM029576%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
Hi Bram,
2019/12/3 Tue 12:20:00 UTC+9 Ken Takata wrote:
>
> Hi Bram,
>
> 2019/12/3 Tue 4:42:50 UTC+9 Bram Moolenaar wrote:
>>
>>
>> Ken Takata wrote:
>>
>> > I saw the latest version8.txt.
>> > In the "Vim script improvements" section, the ".." operator is not
>> described
>> > explicitly. (It is described as a part of `:scriptversion`.)
>> > How about adding it explicitly?
>>
>> Well, I like to keep this an overview with not too many details.
>>
>> > For the improvements and changes in Vim 8.2, I'd like to list my works
>> for
>> > Windows as well:
>> >
>> > * Revised Windows installer.
>> > Supports translations, silent install, nice appearance.
>> > * VIMDLL: make it possible to merge the common part of gVim and Vim
>> into a
>> > DLL.
>> > This can reduce the total install size.
>>
>> We already had VIMDLL, but it was basically removed and re-implemented.
>>
>
> Ah, I completely forgot about the old VIMDLL implementation. ;-)
> The old one just created a DLL for gvim.exe and didn't share the code with
> vim.exe.
> I wonder if the original author intended to share the code with gvim.exe
> and vim.exe (in a future).
>
>
> > (Enabling this or not in the official Windows package is up to you,
>> Bram.
>> > vim-win32-installer doesn't enable this yet, though.)
>>
>> I rather not change it so short before a release.
>>
>
> OK, enabling VIMDLL by default is a next task for Vim 8.3 (or later).
> If we enable it, we also need to update the nsis script.
> I consider preparing that.
>
>
> > * Drop support for old compilers.
>> > Borland C++, MSVC 2008 or older.
>> >
>> > And other improvements in Vim 8.2 are:
>> >
>> > * Improved 'incsearch'.
>> > * Support modifyOtherKeys.
>> > * Support ConPTY on Windows 10.
>> > Full colors are available in the terminal mode.
>> > * Added /= and %= assignment operators.
>>
>> I updated the text to also mention things that were removed and
>> graduated:
>>
>>
>> Vim script
>> improvements*new-vimscript-8.2*
>> ---
>>
>> Functions can now be called in a chain, using "->": >
>> mylist->filter(filterexpr)->map(mapexpr)->sort()->join()
>> The new `:eval` command can be used if the chain has no result.
>>
>> The `:scriptversion` command was added to allow for changes that are not
>> backwards compatible. E.g. to only use ".." for string concatenation, so
>> that
>> "." can be used to access a dictionary member consistently.
>>
>> `:const` was added to allow for declaring a variable that cannot change:
>> >
>> const TIMER_DELAY = 400
>>
>> A heredoc-style assignment was added to easily assign a list of lines to
>> a
>> variable without quoting or line continuation: >
>> let lines =<< trim END
>>line one
>>line two
>> END
>>
>> The |Blob| type was added. This makes it easy to deal with binary data.
>>
>> The /= and %= assignment operators were added.
>>
>> A Dictionary can be defined with #{} where the keys are used literally.
>> This
>> avoids having to use quotes: >
>> let options = #{width: 30, height: 24}
>>
>>
>> Other improvements*new-other-8.2*
>> --
>>
>> - When 'incsearch' is set it also applies to `:substitute`.
>> - |modifyOtherKeys| was added to allow mapping more key combinations.
>> - ConPTY support was added for Windows 10, supports full color in the
>> terminal.
>> - The windows installer supports translations, silent install and looks
>> better.
>>
>>
>> Changed*changed-8.2*
>>
>> ---
>>
>> The xdiff library was included to avoid the need for an external diff
>> program
>> and to make updating diffs much faster.
>>
>> The code is using a few more modern C features, such as // comments.
>>
>> Support for old compilers has been dropped: Borland C++, MSVC 2008.
>>
>> Hangul input support was removed, it actually didn't work.
>>
>> The FEAT_TAG_OLDSTATIC code was removed, it slowed down tag searches.
>> The FEAT_TAG_ANYWHITE code was removed, is was not enabled in any build.
>> The UNICODE16 code was removed, it was not useful.
>> Workshop support was removed, nobody was using it.
>> The Aap build files were removed, they were outdated.
>> Farsi support was removed, it was outdated and unused.
>>
>> VIMDLL was re-implemented, this shares the common parts between vim and
>> gvim
>> to reduce the total install size.
>>
>> The following features are now included in all versions: |+mbyte|,
>> |+virtualedit|, |+vreplace|, |+localmap|, |+cmdline_hist|,
>> |+cmdline_compl|,
>> |+insert_expand|, |+modify_fname|, |+comments|
>>
>>
> Looks good.
>
Sorry, my previous patch had a mistake.
Could you apply the following patch?
--- a/runtime/doc/version8.txt
+++ b/runtime/doc/version8.txt
@@ -35845,7 +35845,7 @@ Solution: Ignore the "browse"
Re: Upcoming Vim 8.2 release
Hi Bram,
2019/12/3 Tue 4:42:50 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > I saw the latest version8.txt.
> > In the "Vim script improvements" section, the ".." operator is not
> described
> > explicitly. (It is described as a part of `:scriptversion`.)
> > How about adding it explicitly?
>
> Well, I like to keep this an overview with not too many details.
>
> > For the improvements and changes in Vim 8.2, I'd like to list my works
> for
> > Windows as well:
> >
> > * Revised Windows installer.
> > Supports translations, silent install, nice appearance.
> > * VIMDLL: make it possible to merge the common part of gVim and Vim into
> a
> > DLL.
> > This can reduce the total install size.
>
> We already had VIMDLL, but it was basically removed and re-implemented.
>
Ah, I completely forgot about the old VIMDLL implementation. ;-)
The old one just created a DLL for gvim.exe and didn't share the code with
vim.exe.
I wonder if the original author intended to share the code with gvim.exe
and vim.exe (in a future).
> (Enabling this or not in the official Windows package is up to you,
> Bram.
> > vim-win32-installer doesn't enable this yet, though.)
>
> I rather not change it so short before a release.
>
OK, enabling VIMDLL by default is a next task for Vim 8.3 (or later).
If we enable it, we also need to update the nsis script.
I consider preparing that.
> * Drop support for old compilers.
> > Borland C++, MSVC 2008 or older.
> >
> > And other improvements in Vim 8.2 are:
> >
> > * Improved 'incsearch'.
> > * Support modifyOtherKeys.
> > * Support ConPTY on Windows 10.
> > Full colors are available in the terminal mode.
> > * Added /= and %= assignment operators.
>
> I updated the text to also mention things that were removed and
> graduated:
>
>
> Vim script improvements*new-vimscript-8.2*
> ---
>
> Functions can now be called in a chain, using "->": >
> mylist->filter(filterexpr)->map(mapexpr)->sort()->join()
> The new `:eval` command can be used if the chain has no result.
>
> The `:scriptversion` command was added to allow for changes that are not
> backwards compatible. E.g. to only use ".." for string concatenation, so
> that
> "." can be used to access a dictionary member consistently.
>
> `:const` was added to allow for declaring a variable that cannot change: >
> const TIMER_DELAY = 400
>
> A heredoc-style assignment was added to easily assign a list of lines to a
> variable without quoting or line continuation: >
> let lines =<< trim END
>line one
>line two
> END
>
> The |Blob| type was added. This makes it easy to deal with binary data.
>
> The /= and %= assignment operators were added.
>
> A Dictionary can be defined with #{} where the keys are used literally.
> This
> avoids having to use quotes: >
> let options = #{width: 30, height: 24}
>
>
> Other improvements*new-other-8.2*
> --
>
> - When 'incsearch' is set it also applies to `:substitute`.
> - |modifyOtherKeys| was added to allow mapping more key combinations.
> - ConPTY support was added for Windows 10, supports full color in the
> terminal.
> - The windows installer supports translations, silent install and looks
> better.
>
>
> Changed*changed-8.2*
>
> ---
>
> The xdiff library was included to avoid the need for an external diff
> program
> and to make updating diffs much faster.
>
> The code is using a few more modern C features, such as // comments.
>
> Support for old compilers has been dropped: Borland C++, MSVC 2008.
>
> Hangul input support was removed, it actually didn't work.
>
> The FEAT_TAG_OLDSTATIC code was removed, it slowed down tag searches.
> The FEAT_TAG_ANYWHITE code was removed, is was not enabled in any build.
> The UNICODE16 code was removed, it was not useful.
> Workshop support was removed, nobody was using it.
> The Aap build files were removed, they were outdated.
> Farsi support was removed, it was outdated and unused.
>
> VIMDLL was re-implemented, this shares the common parts between vim and
> gvim
> to reduce the total install size.
>
> The following features are now included in all versions: |+mbyte|,
> |+virtualedit|, |+vreplace|, |+localmap|, |+cmdline_hist|,
> |+cmdline_compl|,
> |+insert_expand|, |+modify_fname|, |+comments|
>
>
Looks good.
Regards,
Ken Takata
--
--
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 the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Re: Upcoming Vim 8.2 release
Christian wrote: > please include this minor patch to de.po: I'll include it, thanks. -- hundred-and-one symptoms of being an internet addict: 173. You keep tracking down the email addresses of all your friends (even childhood friends). /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201912021942.xB2Jgdgo012278%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
Ken Takata wrote:
> I saw the latest version8.txt.
> In the "Vim script improvements" section, the ".." operator is not described
> explicitly. (It is described as a part of `:scriptversion`.)
> How about adding it explicitly?
Well, I like to keep this an overview with not too many details.
> For the improvements and changes in Vim 8.2, I'd like to list my works for
> Windows as well:
>
> * Revised Windows installer.
> Supports translations, silent install, nice appearance.
> * VIMDLL: make it possible to merge the common part of gVim and Vim into a
> DLL.
> This can reduce the total install size.
We already had VIMDLL, but it was basically removed and re-implemented.
> (Enabling this or not in the official Windows package is up to you, Bram.
> vim-win32-installer doesn't enable this yet, though.)
I rather not change it so short before a release.
> * Drop support for old compilers.
> Borland C++, MSVC 2008 or older.
>
> And other improvements in Vim 8.2 are:
>
> * Improved 'incsearch'.
> * Support modifyOtherKeys.
> * Support ConPTY on Windows 10.
> Full colors are available in the terminal mode.
> * Added /= and %= assignment operators.
I updated the text to also mention things that were removed and
graduated:
Vim script improvements *new-vimscript-8.2*
---
Functions can now be called in a chain, using "->": >
mylist->filter(filterexpr)->map(mapexpr)->sort()->join()
The new `:eval` command can be used if the chain has no result.
The `:scriptversion` command was added to allow for changes that are not
backwards compatible. E.g. to only use ".." for string concatenation, so that
"." can be used to access a dictionary member consistently.
`:const` was added to allow for declaring a variable that cannot change: >
const TIMER_DELAY = 400
A heredoc-style assignment was added to easily assign a list of lines to a
variable without quoting or line continuation: >
let lines =<< trim END
line one
line two
END
The |Blob| type was added. This makes it easy to deal with binary data.
The /= and %= assignment operators were added.
A Dictionary can be defined with #{} where the keys are used literally. This
avoids having to use quotes: >
let options = #{width: 30, height: 24}
Other improvements *new-other-8.2*
--
- When 'incsearch' is set it also applies to `:substitute`.
- |modifyOtherKeys| was added to allow mapping more key combinations.
- ConPTY support was added for Windows 10, supports full color in the terminal.
- The windows installer supports translations, silent install and looks
better.
Changed *changed-8.2*
---
The xdiff library was included to avoid the need for an external diff program
and to make updating diffs much faster.
The code is using a few more modern C features, such as // comments.
Support for old compilers has been dropped: Borland C++, MSVC 2008.
Hangul input support was removed, it actually didn't work.
The FEAT_TAG_OLDSTATIC code was removed, it slowed down tag searches.
The FEAT_TAG_ANYWHITE code was removed, is was not enabled in any build.
The UNICODE16 code was removed, it was not useful.
Workshop support was removed, nobody was using it.
The Aap build files were removed, they were outdated.
Farsi support was removed, it was outdated and unused.
VIMDLL was re-implemented, this shares the common parts between vim and gvim
to reduce the total install size.
The following features are now included in all versions: |+mbyte|,
|+virtualedit|, |+vreplace|, |+localmap|, |+cmdline_hist|, |+cmdline_compl|,
|+insert_expand|, |+modify_fname|, |+comments|
--
hundred-and-one symptoms of being an internet addict:
172. You join listservers just for the extra e-mail.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/201912021942.xB2Jg8Ba012175%40masaka.moolenaar.net.
Re: Upcoming Vim 8.2 release
Bram, please include this minor patch to de.po: diff --git a/src/po/de.po b/src/po/de.po index 50efb2447..103641e4c 100644 --- a/src/po/de.po +++ b/src/po/de.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: Vim\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-11-13 22:38+0100\n" +"POT-Creation-Date: 2019-12-02 17:17+0100\n" "PO-Revision-Date: 2008-05-24 17:26+0200\n" "Last-Translator: Christian Brabandt \n" "Language-Team: German\n" @@ -2131,9 +2131,6 @@ msgstr "Stil:" msgid "Size:" msgstr "Gre:" -msgid "E256: Hangul automata ERROR" -msgstr "E256: Hangul-Automat Fehler" - msgid "E550: Missing colon" msgstr "E550: Fehlender Doppelpunkt" @@ -4559,7 +4556,7 @@ msgid "shell returned %d" msgstr "Shell gab %d zurck" msgid "E278: Cannot put a terminal buffer in a popup window" -msgstr "E278: Terminal kann nicht in einem Popup-Fenster geffnet werdent." +msgstr "E278: Terminal kann nicht in einem Popup-Fenster geffnet werden." #, c-format msgid "E997: Tabpage not found: %d" Thanks, Christian -- Diejenigen, die zu klug sind, um sich in der Politik zu engagieren, werden dadurch bestraft, daß sie von Leuten regiert werden, die dümmer sind als sie. -- Platon (427-347 v.Chr.) -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20191202162012.GE28132%40256bit.org.
Re: Upcoming Vim 8.2 release
Hi Bram, 2019/11/30 Sat 6:13:22 UTC+9 Bram Moolenaar wrote: > > > It appears the number of bug reports is getting lower. I have included > many pending pull requests. I think we are getting closer to a release. > > If you have any runtime updates, please send them now! > > I'm also wondering: what is your favorite improvement since Vim 8.1? > I saw the latest version8.txt. In the "Vim script improvements" section, the ".." operator is not described explicitly. (It is described as a part of `:scriptversion`.) How about adding it explicitly? --- a/runtime/doc/version8.txt +++ b/runtime/doc/version8.txt @@ -25844,6 +25844,9 @@ Functions can now be called in a chain, mylist->filter(filterexpr)->map(mapexpr)->sort()->join() The new `:eval` command can be used when there is no result. +The ".." operator was added for string concatenation to avoid confusion with a +key access operator for dictionaries. + The `:scriptversion` command was added to allow for changes that are not backwards compatible. E.g. to only use ".." for string concatenation. (I don't know the official name for the "dict.key" operator, though.) For the improvements and changes in Vim 8.2, I'd like to list my works for Windows as well: * Revised Windows installer. Supports translations, silent install, nice appearance. * VIMDLL: make it possible to merge the common part of gVim and Vim into a DLL. This can reduce the total install size. (Enabling this or not in the official Windows package is up to you, Bram. vim-win32-installer doesn't enable this yet, though.) * Drop support for old compilers. Borland C++, MSVC 2008 or older. And other improvements in Vim 8.2 are: * Improved 'incsearch'. * Support modifyOtherKeys. * Support ConPTY on Windows 10. Full colors are available in the terminal mode. * Added /= and %= assignment operators. Regards, Ken Takata -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/89da54f9-2560-4891-b146-f7541273261f%40googlegroups.com.
Upcoming Vim 8.2 release
It appears the number of bug reports is getting lower. I have included many pending pull requests. I think we are getting closer to a release. If you have any runtime updates, please send them now! I'm also wondering: what is your favorite improvement since Vim 8.1? -- hundred-and-one symptoms of being an internet addict: 142. You dream about creating the world's greatest web site. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201911292113.xATLDFF2013885%40masaka.moolenaar.net.
