patch 9.0.1816: configure: sed uses non-portable regex
Commit:
https://github.com/vim/vim/commit/bddc6adca647f7f20ff6e1b7913e394d09c5eb23
Author: ichizok
Date: Tue Aug 29 20:54:32 2023 +0200
patch 9.0.1816: configure: sed uses non-portable regex
Problem: configure: sed uses
Hi Christian,
On Tue, Aug 29, 2023 at 12:06 PM Christian Brabandt <
vim-dev-git...@256bit.org> wrote:
> so let me summarize: the current proposal is to remove the public keyword
> completely (?) and make all attributes public by default (unless they start
> with _)? So by removing this keyword,
On Tue, Aug 29, 2023 at 9:20 AM dkearns wrote:
>
> Is there some strong objection to requiring a keyword modifier? Why is a
> default needed at all?
>
If we always require a keyword modifier (like private, public, etc.)
in a member/method
declaration, then it will be too cumbersome to add this
patch 9.0.1818: dynamically linking perl is broken
Commit:
https://github.com/vim/vim/commit/55460da26c2756ec057c03c7d8641eda861bfcd2
Author: Christian Brabandt
Date: Tue Aug 29 21:31:28 2023 +0200
patch 9.0.1818: dynamically linking perl is broken
Problem: dynamically linking
runtime(heex): Add HEEX comments to match_words in ftplugin (#12957)
Commit:
https://github.com/vim/vim/commit/3ac2d3da5fdf20dfddb450a49502ef47b1f581d4
Author: Jason King
Date: Tue Aug 29 15:11:55 2023 -0500
runtime(heex): Add HEEX comments to match_words in ftplugin
Hi,
On Tue, Aug 29, 2023 at 11:03 AM Gianmaria Bajo
wrote:
> Also readable doesn't exist anywhere else. If simplicity is the ultimate
> goal, I'd say this PR is ok in just removing public. We can live without
> readonly but even more so without stuff invented for vimscript that
> doesn't exist
patch 9.0.1822: Vim9: no check for duplicate members in extended classes
Commit:
https://github.com/vim/vim/commit/e3b6c78ddc4acf238af35d7fac585e7ead27392f
Author: Yegappan Lakshmanan
Date: Tue Aug 29 22:32:02 2023 +0200
patch 9.0.1822: Vim9: no check for duplicate members in extended
patch 9.0.1817: configure: using obsolete AC_HEADER_STDC
Commit:
https://github.com/vim/vim/commit/0e82b59df3fc12dc006e45e17222bcbb0462903f
Author: Illia Bobyr
Date: Tue Aug 29 21:16:29 2023 +0200
patch 9.0.1817: configure: using obsolete AC_HEADER_STDC
Problem: configure:
Hi,
On Tue, Aug 29, 2023 at 9:08 AM errael wrote:
> readonly is working AFAICT. I still need to put together some tests. I
> can't try writing to a readonly static because of the compilation failure
> bug that prevents writing to class statics. One nice thing about readonly
> is that it doesn't
patch 9.0.1819: Github CI too complex
Commit:
https://github.com/vim/vim/commit/3e1e63de185712a6afa7b4acf4488a5dbcbe5e5f
Author: ichizok
Date: Tue Aug 29 22:16:34 2023 +0200
patch 9.0.1819: Github CI too complex
Problem: Github CI too complex
Solution: CI: Tidy up matrix
patch 9.0.1820: Rexx files may not be recognised
Commit:
https://github.com/vim/vim/commit/e06afb7860805537ccd69966bc03169852c9b378
Author: Doug Kearns
Date: Tue Aug 29 22:21:35 2023 +0200
patch 9.0.1820: Rexx files may not be recognised
Problem: Rexx files may not be
runtime(sh): Update ftplugin (#12950)
Commit:
https://github.com/vim/vim/commit/2ac708b548660b232a32c52d89bde3d8596646c0
Author: dkearns
Date: Wed Aug 30 06:24:37 2023 +1000
runtime(sh): Update ftplugin (https://github.com/vim/vim/issues/12950)
Remove :Help command via the
patch 9.0.1821: Vim9 constructors are always static
Commit:
https://github.com/vim/vim/commit/4b9777a1dfc10bd2634404cb039a0df539549c93
Author: Gianmaria Bajo
Date: Tue Aug 29 22:26:30 2023 +0200
patch 9.0.1821: Vim9 constructors are always static
Problem: Vim9 constructors are
Hi,
On Tue, Aug 29, 2023 at 1:42 PM Christian Brabandt <
vim-dev-git...@256bit.org> wrote:
> Should the example here
> https://github.com/vim/vim/blob/d01a0df61d2a322645fb393ed704fcec38e0d0fe/runtime/doc/vim9class.txt#L186-L200
>
> also be changed to use underscores? Otherwise we wouldn't need
Hi,
On Tue, Aug 29, 2023 at 1:38 PM errael wrote:
>
>-
>
>Able to access private static
>-
>
>Compile error when trying to write public static
>
> There's another one (a real shocker).
>
> It's OK to write to a private member.
>
> vim9script
>
> class C
> this._m: number
>
On Mo, 28 Aug 2023, Tony Mechelynck wrote:
> Thanks a lot for that script, I saved it where it won't get lost. I
> think that I could understand it better with just a little study but
> that it isn't really out of my mental reach.
There is one more important thing to remember. This script uses
On 23/08/28 11:55 AM, Tony Mechelynck wrote:
On Thu, Aug 24, 2023 at 4:17 PM Ernie Rael wrote:
On 23/08/24 2:44 AM, Tony Mechelynck wrote:
[...]
Well, if the Mercurial mirror goes puff, I'll have to decide
either to fall back on the Vim from my distro (always somewhat behind,
currently
runtime(editorconfig): generate helptags, remove unused files
Commit:
https://github.com/vim/vim/commit/7129de868cc00fb2644aa17c06c42f7bd58a2650
Author: Christian Brabandt
Date: Tue Aug 29 15:42:31 2023 +0200
runtime(editorconfig): generate helptags, remove unused files
Remove
runtime(doc): mention special case of i_CTRL-R_-
Commit:
https://github.com/vim/vim/commit/a5eb6785efcc36a97e071722408acc20d6c6e606
Author: Christian Brabandt
Date: Tue Aug 29 16:22:38 2023 +0200
runtime(doc): mention special case of i_CTRL-R_-
closes:
Hi all,
The CI ASAN test is currently failing due to a memory leak. The fix for
this is in the https://github.com/vim/vim/pull/12948 PR.
Regards,
Yegappan
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
20 matches
Mail list logo
