Hi,
On Mon, Aug 28, 2023 at 6:47 PM errael wrote:
> I looked around to get a feel... The following fixes the "access to
> private static" var in the example, if you want to include it. Not tested
> much.
>
> diff --git a/src/vim9expr.c b/src/vim9expr.c
> --- a/src/vim9expr.c
> +++
Hi,
On Mon, Aug 28, 2023 at 12:14 PM errael wrote:
> When I build objmember, with no modifications, and run this I see two
> problems
>
>1. Able to access private static
>2. Compile error when trying to write public static
>
>
I am able to reproduce the second issue even using a two
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
On Mon, Aug 28, 2023 at 9:11 PM Christian Brabandt wrote:
>
>
> On Mo, 28 Aug 2023, Tony Mechelynck wrote:
>
> > Christian, do you have any recommendations for someone who would want
> > to continue porting the changes from git to Mercurial if you ever
> > decide to close your own Mercurial
On 23/08/28 12:50 PM, Christian Brabandt wrote:
On Mo, 28 Aug 2023, Ernie Rael wrote:
On 23/08/28 12:13 PM, Christian Brabandt wrote:
No, it wasn't. I've never published, or otherwise made available,
vimscript/vim9script (this is the first vim[9]script I've done). I have seen
a lot of talk in
runtime(tags): update helptags
Commit:
https://github.com/vim/vim/commit/00d07a97ad750f2d2849a649f85ab1610a0b0866
Author: Christian Brabandt
Date: Mon Aug 28 21:45:16 2023 +0200
runtime(tags): update helptags
Signed-off-by: Christian Brabandt
diff --git a/runtime/doc/tags
On Mo, 28 Aug 2023, Ernie Rael wrote:
> On 23/08/28 12:13 PM, Christian Brabandt wrote:
> No, it wasn't. I've never published, or otherwise made available,
> vimscript/vim9script (this is the first vim[9]script I've done). I have seen
> a lot of talk in this forum on managing plugins and such
On 23/08/28 12:13 PM, Christian Brabandt wrote:
On So, 27 Aug 2023, Ernie Rael wrote:
Greetings,
In March of 2022 I started porting Splice[1], a 3 way merge tool written in
vim/python, to vim9script. I had never used vimscript and felt weak when it
came
to merging; so "two birds with one
runtime: Set b:undo_indent where missing (#12944)
Commit:
https://github.com/vim/vim/commit/0382f05dbd659d8e39ee4e71c1e5062ac5c0a8fd
Author: dkearns
Date: Tue Aug 29 05:32:59 2023 +1000
runtime: Set b:undo_indent where missing
(https://github.com/vim/vim/issues/12944)
runtime: Set b:undo_ftplugin where missing (#12943)
Commit:
https://github.com/vim/vim/commit/f937ab32a1ac3a560f217ca4ce8305ab2d5b0b74
Author: dkearns
Date: Tue Aug 29 05:32:27 2023 +1000
runtime: Set b:undo_ftplugin where missing
(https://github.com/vim/vim/issues/12943)
patch 9.0.1815: pango_coverage_unref() deprecated in pango > 1.51
Commit:
https://github.com/vim/vim/commit/fe1463674c4c97388409a8c91dd525e7b7afb69e
Author: James McCoy
Date: Mon Aug 28 21:29:13 2023 +0200
patch 9.0.1815: pango_coverage_unref() deprecated in pango > 1.51
patch 9.0.1814: Vim9 no error on duplicate object member var
Commit:
https://github.com/vim/vim/commit/2ba9d2e14e3633c92a32abba2a12533f93fefbf5
Author: Yegappan Lakshmanan
Date: Mon Aug 28 21:26:23 2023 +0200
patch 9.0.1814: Vim9 no error on duplicate object member var
Problem:
patch 9.0.1813: linebreak incorrect drawn with breakindent
Commit:
https://github.com/vim/vim/commit/1d3e0e8f3110a7807431eae056914ccea57b057b
Author: zeertzjq
Date: Mon Aug 28 21:20:16 2023 +0200
patch 9.0.1813: linebreak incorrect drawn with breakindent
Problem: 'linebreak' is
patch 9.0.1812: CI still fails with sodium_mlock error()
Commit:
https://github.com/vim/vim/commit/93ebb5e75e564403624314c84c97293427d001d6
Author: Christian Brabandt
Date: Mon Aug 28 21:17:36 2023 +0200
patch 9.0.1812: CI still fails with sodium_mlock error()
Problem: CI still
On Mon, Aug 28, 2023 at 7:05 PM Christian Brabandt wrote:
[…]
> I use git, because all the information can easily be found in the
> internet and it is still very actively developed and a lot of questions
> on how to use it have already been asked :).
>
> For mercurial I have to refresh my
On So, 27 Aug 2023, Ernie Rael wrote:
> Greetings,
>
> In March of 2022 I started porting Splice[1], a 3 way merge tool written in
> vim/python, to vim9script. I had never used vimscript and felt weak when it
> came
> to merging; so "two birds with one stone". There's now a pure vim9script
>
On Mo, 28 Aug 2023, Tony Mechelynck wrote:
> Christian, do you have any recommendations for someone who would want
> to continue porting the changes from git to Mercurial if you ever
> decide to close your own Mercurial mirror, or is it not worth the
> trouble unless this new Mercurial mirror is
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 9.0.1632 and with a slightly
On Mo, 28 Aug 2023, tux. wrote:
> If your PHP runs on E_ALL and everything’s fine, you’re probably good indeed.
>
> Unlike Git, hg won’t need too many tutorials on the internet because it’s
> intuitive to use. :-p
I already pushed two different heads for hg, so I already broke the
workflow
If your PHP runs on E_ALL and everything’s fine, you’re probably good indeed.
Unlike Git, hg won’t need too many tutorials on the internet because it’s
intuitive to use. :-p
YMMV…
> On Montag, Aug. 28, 2023 at 7:05 PM, Christian Brabandt (mailto:cbli...@256bit.org)> wrote:
>
> On Mo, 28 Aug
On Mo, 28 Aug 2023, tux0r wrote:
> Ahoy,
>
> > I'll also need to check the amount of work to migrate the old php5 code to
> > an updated php version.
>
> I’m sure there’s not /too/ much work involved. Basically,
>
> 1) replace mysql_* by mysqli_* (if used),
Yes, that was actually all that
I am just someone that followed the discussion google mailing lists. I
guess the reason I did is because I always found the community to be trying
to help each other and Bram always caring about vim and the users.
Another recurring thing I remember was someone sending some patch he would
just
Ahoy,
> I'll also need to check the amount of work to migrate the old php5 code to an
> updated php version.
I’m sure there’s not /too/ much work involved. Basically,
1) replace mysql_* by mysqli_* (if used),
2) depending on the target version, add default parameters (PHP 8 prefers a
slightly
On So, 27 Aug 2023, Yegappan Lakshmanan wrote:
> On Sun, Aug 27, 2023 at 11:09 AM Christian Brabandt
> wrote:
> >
> > I would think once Yegappan thinks the Vim9 classes is good enough to
> > release, I'd go ahead. Not sure how much work this is left to be done,
> > but I'd rather sooner
On So, 27 Aug 2023, Yegappan Lakshmanan wrote:
> Hi Christian,
>
> On Sun, Aug 27, 2023 at 11:09 AM Christian Brabandt
> wrote:
> >
> > >
> > > On Thu, 24 Aug 2023 at 06:18, Christian Brabandt
> > > wrote:
> > >
> > > Hi,
> > > this is a small update over what happened the last few
25 matches
Mail list logo
