Heading for a release

[Bram Moolenaar]

It's been a long time since a new Vim release was created.
Many features have been added, it's time to concentrate on reliablity.
I will stop adding larger changes and especially anything that looks
risky.

There is still time to try out those new features and fix things that
don't work well. That is especially about:
- The listener feature - listener_add()
- Popup windows - popup_create()
- Sound support - sound_playfile()
- Text properties - prop_add()
- variable tabstops - 'vartabs'
- mapping keys with modifiers - modifyOtherKeys

Especially that last one is still recent, and I already found a few
problems it caused, there might be more.

--
"Beware of bugs in the above code; I have only proved
it correct, not tried it." -- Donald Knuth

/// Bram Moolenaar -- Br...@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 ///

[Christian Brabandt]

On Mi, 23 Okt 2019, Bram Moolenaar wrote:

> It's been a long time since a new Vim release was created.
> Many features have been added, it's time to concentrate on reliablity.
> I will stop adding larger changes and especially anything that looks
> risky.
>
> There is still time to try out those new features and fix things that
> don't work well. That is especially about:
> - The listener feature - listener_add()
> - Popup windows - popup_create()
> - Sound support - sound_playfile()
> - Text properties - prop_add()
> - variable tabstops - 'vartabs'
> - mapping keys with modifiers - modifyOtherKeys
>
> Especially that last one is still recent, and I already found a few
> problems it caused, there might be more.

Sounds great. Does that also mean, no new translateable strings will be
added/changed?

Best
Christian
--
Wer nicht mit der Zeit geht, muß mit der Zeit gehen.

[Andy Massimino]

Would this be vim 8.2, vim 9 or vim X?

--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20191024115321.GC26491%40256bit.org.

[Bram Moolenaar]

It's unlikely new strings get added. Existing strings might still get
fixes, but there should not be that many.

--
This computer is so slow, it takes forever to execute and endless loop!

[Bram Moolenaar]

Andy Massimino wrote:

> Would this be vim 8.2, vim 9 or vim X?

Vim 8.2.

--
BEDEVERE: Why do you think she is a witch?
SECOND VILLAGER: She turned me into a newt.
BEDEVERE: A newt?
SECOND VILLAGER: (After looking at himself for some time) I got better.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

[Paul Jolly]

> > Would this be vim 8.2, vim 9 or vim X?
>
> Vim 8.2.

With the exception of:

https://groups.google.com/forum/#!topic/vim_dev/3z7KlLbGpwk

from a govim perspective we're very happy with the stability of the
features we're using.

Thank you again.


Paul

[Bram Moolenaar]

Paul Jolly wrote:

> > > Would this be vim 8.2, vim 9 or vim X?
> >
> > Vim 8.2.
>
> With the exception of:
>
> https://groups.google.com/forum/#!topic/vim_dev/3z7KlLbGpwk

This cannot be reproduced. popup_getoptions() doesn't block on
anything. Perhaps the problem is that the result is rather big, goes
over a buffer limit and sending the reply blocks on that?

> from a govim perspective we're very happy with the stability of the
> features we're using.
>
> Thank you again.

Glad to hear that.

--
BEDEVERE: Wait. Wait ... tell me, what also floats on water?
ALL: Bread? No, no, no. Apples .... gravy ... very small rocks ...
ARTHUR: A duck.

[Christian Brabandt]

On Do, 24 Okt 2019, Bram Moolenaar wrote:

> It's unlikely new strings get added. Existing strings might still get
> fixes, but there should not be that many.

Okay, here is an updated de.po file then.

Will also send out updated runtime files soon.

Best,
Christian
--
Mann der Arbeit, aufgewacht!
Und erkenne deine Macht!
Alle Räder stehen still, wenn dein starker Arm es will.
-- Georg Herwegh

[Bram Moolenaar]

Christian wrote:

> On Do, 24 Okt 2019, Bram Moolenaar wrote:
>
> > It's unlikely new strings get added. Existing strings might still get
> > fixes, but there should not be that many.
>
> Okay, here is an updated de.po file then.

I'll include it, thanks.

> Will also send out updated runtime files soon.

Good.

--
I once paid $12 to peer at the box that held King Tutankhamen's little
bandage-covered midget corpse at the De Young Museum in San Francisco. I
remember thinking how pleased he'd be about the way things turned out in his
afterlife.
(Scott Adams - The Dilbert principle)

[David Fishburn]

I have a couple of runtime files to update as well.

How soon do you need them?

--
--
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+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201910242013.x9OKDoom027242%40masaka.moolenaar.net.

[Paul Jolly]

> > With the exception of:
> >
> > https://groups.google.com/forum/#!topic/vim_dev/3z7KlLbGpwk
>
> This cannot be reproduced. popup_getoptions() doesn't block on
> anything. Perhaps the problem is that the result is rather big, goes
> over a buffer limit and sending the reply blocks on that?

Sorry, I wasn't suggesting that this is something that has definitely
been traced as a Vim problem, rather I just wanted to highlight that's
the only outstanding "Vim" issue from our side, which could equally
turn out to be a govim issue on further investigation.

> > from a govim perspective we're very happy with the stability of the
> > features we're using.
> >
> > Thank you again.
>
> Glad to hear that.

Very excited for this release - it made govim possible!


Paul

[Bram Moolenaar]

David Fishburn wrote:

> I have a couple of runtime files to update as well.
> How soon do you need them?

It should still be a few weeks away, but it's good to also give runtime
files some testing before the release.

--
An easy way to determine if you have enough teamwork to be doomed is simply to
measure how long it takes from the time you decide to go to lunch together
until the time you actually eat.