Re: Commit: patch 9.1.0376: Vim9: Trailing commands after class/enum keywords ignored

Hi, On Sat, Apr 27, 2024 at 10:08 AM Christian J. Robinson wrote: > > I think this patch, or one of the others around this same time, broke adding > comments after "}", as in the following: > > vim9script > > class Foo > static const bar = { # {{{ > baz: 'qux' > } # }}} > endclass > > Results

Re: [vim/vim] cbuffer/cad doesn't take visual selection as range '<,'>cad (Issue #14638)

Hi Christian, On Fri, Apr 26, 2024 at 9:02 AM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > Hm, even the mentioned > > '<,'>cgetbuffer does no longer work. It seems at least the following two > commands would need to use

Re: [vim/vim] compile_def_function() is too long. Move out the code to compile the body of a function (PR #14622)

Hi Christian, On Tue, Apr 23, 2024 at 11:46 PM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > Hi Yegappan, > Coverity complains about this one here however: > https://scan5.scan.coverity.com/#/project-view/41242/10101?selectedIssue=1596610 > > I think this is a false positive? > > >

Re: [vim/vim] Running test_vim9_builtin.vim tests is slow (PR #14614)

On Sun, Apr 21, 2024 at 6:09 PM Yegappan Lakshmanan < vim-dev-git...@256bit.org> wrote: > The tests in test_vim9_builtin.vim use the CheckDefAndScriptFailure(), > CheckDefExecFailure(), etc. functions from the vim9.vim file. > These functions store the supplied lines in a file

Re: matchbufline() and the 'ignorecase' option value

Hi, On Thu, Feb 22, 2024 at 7:56 AM shane.qian wrote: > > > The recently introduced matchbufline() and matchstrlist() functions > > use the 'ignorecase' option value. If this option is set, then these > > functions ignore the case when matching the strings. > > So the behavior of a plugin using

matchbufline() and the 'ignorecase' option value

Hi all, The recently introduced matchbufline() and matchstrlist() functions use the 'ignorecase' option value. If this option is set, then these functions ignore the case when matching the strings. So the behavior of a plugin using these functions depends on a user configuration. To ignore this

Re: [vim/vim] Add a place holder section for version 9.2 (PR #14060)

Hi, On Mon, Feb 19, 2024 at 6:52 PM Maxim Kim wrote: > Should we have Breaking changes section as well? > > one that comes to my mind is default colorscheme visual highlight now has > defined foreground which breaks colorschemes that were relying on Visual > guifg=NONE. > > > Yes. I have

New PRs - tests and coverage

Hi all, When you submit a new PR, after the CI tests are successfully completed, the coverage information is shown in the PR diff page. Can you please go through that and make sure that most of the newly added or modified lines are covered by tests? If not, please add additional tests to make

Re: Question about tooling and stiling

Hi, On Mon, Feb 12, 2024 at 6:55 AM Luca Saccarola wrote: > > Hi, > I was experimenting with setting up clangd and clang-format for the > codebase. I've read the `:h develop` but I still have missing > information. > > 1. Tabs or spaces? The documentation doesn't specify it and the source >

Re: [vim/vim] Add support for the diff() function using the built-in diff support (PR #12321)

Hi, On Fri, Feb 2, 2024 at 10:54 PM rickhowe wrote: > Hi, > > Thank you for providing diff(). I checked how it works while comparing > with nvim's vim.diff() as follows. > Note that nvim's vim.diff() is a lua function whereas the newly introduced diff() is a Vim builtin function. Lua uses

Re: Commit: patch 9.1.0071: Need a diff() Vim script function

Hi, On Fri, Feb 2, 2024 at 12:56 PM John Marriott wrote: > > > > On 02-Feb-2024 08:30, Christian Brabandt wrote: > > patch 9.1.0071: Need a diff() Vim script function > > Commit: > https://github.com/vim/vim/commit/fa37835b8c0ed0f83952978fca4c332335ca7c46 > Autho

Re: [vim/vim] Add a new list-based interface for programming list options in Vim (Issue #13891)

Hi, On Fri, Jan 19, 2024 at 3:02 PM bfrg wrote: > @yegappan Why v:vim.opt.shiftwidth and not > just v:opt.shiftwidth (or v:option.shiftwidth)? The vim prefix seems > redundant. > > > I chose v:vim to be consistent with the Python and Lua language interfaces.

Re: [vim/vim] Add a new list-based interface for programming list options in Vim (Issue #13891)

Hi Christian, On Fri, Jan 19, 2024 at 2:39 PM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > That patch would only help, if it makes a list or Dict for options with > several sub-options. > Yes. But that patch can be enhanced to return an option value with several sub-values as a

Re: [vim/vim] Add a new list-based interface for programming list options in Vim (Issue #13891)

Hi, On Fri, Jan 19, 2024 at 1:04 PM Timothy Madden wrote: > Many list options in Vim, like 'path' and 'tags', are difficult to parse > correctly from a string, because of the escapes that need to be applied > (for the comma ',' and backslash '' characters). Also for the generating a > :set

Re: Commit: patch 9.1.0009: Cannot easily get the list of matches

On Sun, Jan 7, 2024 at 8:30 AM Yegappan Lakshmanan wrote: > Hi all, > > On Thu, Jan 4, 2024 at 1:45 PM Christian Brabandt > wrote: > >> patch 9.1.0009: Cannot easily get the list of matches >> >> Commit: >> https://github.com/vim/vim/commit/f93b1c881a9

Re: Commit: patch 9.1.0009: Cannot easily get the list of matches

Hi Gary, On Mon, Jan 8, 2024 at 12:14 PM Gary Johnson wrote: > On 2024-01-07, Yegappan Lakshmanan wrote: > > > To demonstrate the use of the new matchbufline() function, I have created > > the following script. This does search text completion from the list of > words >

Re: Commit: patch 9.1.0009: Cannot easily get the list of matches

Hi all, On Thu, Jan 4, 2024 at 1:45 PM Christian Brabandt wrote: > patch 9.1.0009: Cannot easily get the list of matches > > Commit: > https://github.com/vim/vim/commit/f93b1c881a99fa847a1bafa71877d7e16f18e6ef > Author: Yegappan Lakshmanan > Date: Thu Jan 4 22:28:46 2024 +

Re: Vim 9.1 has been released

Happy to see the 9.1 release. Thanks Christian for your hard work in making this release happen. Regards, Yegappan On Tue, Jan 2, 2024 at 9:46 AM Christian Brabandt wrote: > Dear Vim users, > > The Vim project is happy to announce that Vim 9.1 has finally been > released. This release is

Re: Function to find all matches in a string?

Hi Tim, On Sat, Dec 23, 2023 at 2:35 PM Tim Chase wrote: > I was looking for something similar to Python's re.findall()/finditer() > function to answer a question on Reddit[1] but was surprised I > couldn't find anything in > > :help function-list > > The general intent would be to take an

Re: [vim/vim] Fix error messages for :type/:class used in expressions (PR #13706)

Hi Ernie, On Wed, Dec 20, 2023 at 10:40 AM errael wrote: > @chrisbra @yegappan > If it is relevant, when considering if this > PR should make it into vim9.1, this PR is all about error messages. It was > delayed a few days by

Re: Commit: runtime(doc): Create Changelog until v9.0.2175 (#13728)

Hi Christian, On Tue, Dec 19, 2023 at 11:15 AM Christian Brabandt wrote: > runtime(doc): Create Changelog until v9.0.2175 (#13728) > > Commit: > https://github.com/vim/vim/commit/5872bcb6e8dfc15d7a5c0aaaf94d8029f3a1fa3f > Author: Christian Brabandt > Date: Tue Dec 19 20:10:43 2023 +0100 > >

Re: After applying patches 9.0.2168 to 9.0.2173 : warning -Wmaybe-uninitialized in vim9cmds.c (not in Tiny)

On Sun, Dec 17, 2023 at 2:20 AM Tony Mechelynck < antoine.mechely...@gmail.com> wrote: > On Sun, Dec 17, 2023 at 3:26 AM Yegappan Lakshmanan > wrote: > > > > Hi Tony, > > > > On Sat, Dec 16, 2023 at 3:50 PM Tony Mechelynck < > antoine.mechely

Re: After applying patches 9.0.2168 to 9.0.2173 : warning -Wmaybe-uninitialized in vim9cmds.c (not in Tiny)

Hi Tony, On Sat, Dec 16, 2023 at 3:50 PM Tony Mechelynck < antoine.mechely...@gmail.com> wrote: > vim9cmds.c: In function ‘compile_defer’: > vim9cmds.c:2051:18: warning: ‘type’ may be used uninitialized > [-Wmaybe-uninitialized] > 2051 | else if (check_func_args_from_type(cctx, type,

Re: [vim/vim] Support final object and class variables (PR #13655)

Hi, I was waiting for PR https://github.com/vim/vim/pull/13670 to be merged. As that PR is now merged, this PR (support for final and const object/class variables) is ready. Regards, Yegappan On Sun, Dec 10, 2023 at 11:21 AM Yegappan Lakshmanan < vim-dev-git...@256bit.org> wrote: >

Re: [vim/vim] Treat null the same as using null_ when used in an assignment (PR #13492)

On Sun, Nov 19, 2023 at 5:32 AM dkearns wrote: > It seems it's not currently possible to distinguish null from the default > values? If bool, number and float are to become nullable then they probably > also need null_ values for consistency. > -- > > I noticed this

Re: [vim/vim] Treat null the same as using null_ when used in an assignment (PR #13492)

On Sun, Nov 19, 2023 at 12:18 PM errael wrote: > (In awe of the evolution of this PR) > > There's a difference between script/:def. > > vim9script > > var sv1 = null > echo typename(sv1) > def F1() > var fv1 = null > echo typename(fv1) > enddef > F1() > > Expect function to report

Re: [vim/vim] Vim9script internals, how to read the source code and in what order (Discussion #13543)

Hi, On Sat, Nov 18, 2023 at 3:14 AM stefanos wrote: > I'm fascinated by programming languages and I always find myself digging > deep in their internals to learn how each creator implements specific > language features they may find interesting. > > In case of Vim's scripting language, how do I

Vim9 class implementation update

Hi all, The following Vim9 class features have been implemented so far: 1. Class definition and object creation 2. Class variables and methods 3. Object variables and methods 4. Read-only, Read-write and private access control for class/object variables 5. Extending a class (overriding methods)

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Sun, Oct 1, 2023 at 4:16 PM Ernie Rael wrote: > On 23/10/01 2:56 PM, Yegappan Lakshmanan wrote: > > > On Sun, Oct 1, 2023 at 11:06 AM Ernie Rael wrote: > >> On 23/10/01 6:44 AM, Yegappan Lakshmanan wrote: >> >> Hi, >> >> On Sun, Oct 1, 2023 at

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Sun, Oct 1, 2023 at 11:24 AM Ernie Rael wrote: > On 23/10/01 8:02 AM, shane qian wrote: > > 1. we may ask core members to vote, if class is just a struct then no all > of those arguments. these were all gone. :smile: > > 2. it was just saying **default** was to be `public`, didn't mean no >

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Sun, Oct 1, 2023 at 11:06 AM Ernie Rael wrote: > On 23/10/01 6:44 AM, Yegappan Lakshmanan wrote: > > Hi, > > On Sun, Oct 1, 2023 at 5:17 AM shane qian wrote: > >> and I meant vim9script so far I felt it's good for type-checking and >> performance, but vim9 cla

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Sun, Oct 1, 2023 at 7:20 AM shane qian wrote: > hi yegappan, > > > 4. about the `term`, I believe easy way or pre-agreed term before impl and > documented it may be better. > > > Please look at the list of outstanding Vim9 class items in the todo.txt file:

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Sun, Oct 1, 2023 at 7:20 AM shane qian wrote: > hi yegappan, > > 1. first of all, to me the `simple` meant `class` is class like `struct`, > I was not like the OOP in vim9script actually, but well that probably would > not be accepted by you all now. > Bram didn't intend the Vim9 classes to

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

Hi, On Sun, Oct 1, 2023 at 5:17 AM shane qian wrote: > and I meant vim9script so far I felt it's good for type-checking and > performance, but vim9 class to me I felt a bit burdened, not sure if > still a chance to make it be simple to use (use for scripting), still wish > that's the goal.

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

Hi, On Fri, Sep 29, 2023 at 2:51 PM errael wrote: > Shades of Java's PECS. > > There were two ways to deal with #12965 > . > >1. Adjust the parser to meet the spec. > > The spec currently states that: Object methods of the base class can be

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

On Fri, Sep 29, 2023 at 12:50 PM vim-dev ML wrote: > Hi Christian, > > On Fri, Sep 29, 2023 at 10:30 AM Christian Brabandt < > ***@***.***> wrote: > > > what is contr-variant? > > > > > > Consider the following example (from #12965): > > class A > endclass > > class B extends A > endclass > >

Re: [vim/vim] Support contra-variant type check for object method arguments (similar to Dart) (PR #13221)

Hi Christian, On Fri, Sep 29, 2023 at 10:30 AM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > what is contr-variant? > > > Consider the following example (from #12965): class A endclass class B extends A endclass class C extends B endclass In this example, type "C" is a covariant

Re: lockvar/unlockvar

Hi, On Mon, Sep 25, 2023 at 8:26 AM Ernie Rael wrote: > > Hi all, > > I'm wondering if I'm seeing an error > > ":help lockvar" seems to indicate that the following should work. > The goal is to get a writable variable "l1" that holds a locked list. > > vim9script > var l0: list> = [

Re: [vim/vim] Fix class constructor regression (PR #13113)

Hi, On Sun, Sep 24, 2023 at 6:44 AM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > thanks! > > > The CI ASAN test is failing after this patch. There is a memory leak with this PR. Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type

Re: [vim/vim] Language Specification: interface interitance (Discussion #13085)

On Sun, Sep 17, 2023 at 11:34 AM dkearns wrote: > Sorry, this is moving a bit fast for me to keep up. > > >1. An interface can have only read-only and read-write instance >variables. > > Interfaces generally specify behaviour, not data, and languages with this > sort of type system

Re: [vim/vim] [vim9script] Regression after fixing constructor argument type checking bug (Issue #13102)

Hi, On Sat, Sep 16, 2023 at 1:30 AM Lifepillar wrote: > Steps to reproduce > > Patch 9.0.1724 (“vim9class constructor argument type checking bug”) has > introduced a regression in one of my Vim 9 libraries. I have a test suite > that caught that >

Re: [vim/vim] Interfaces should not support class methods and variables (PR #13100)

Hi, On Sat, Sep 16, 2023 at 10:26 AM errael wrote: > This seems like it should work. Gets > > E1315: White space required after name: I1, I2 > > vim9script > > interface I1 > def F1() > def F2() > endinterface > > interface I2 > def F2() > def F3() > endinterface > > interface

Re: [vim/vim] Class members are accesible only from the class where they are defined. (PR #13086)

Hi Christian, On Sat, Sep 16, 2023 at 4:20 AM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > Coverity complains about this part here: > I have opened the PR https://github.com/vim/vim/pull/13103 to fix this. Regards, Yegappan > *** CID 1544700: Control flow issues (DEADCODE) >

Re: [vim/vim] How do I contribute to the project? (Discussion #13087)

Hi, On Thu, Sep 14, 2023 at 10:23 AM Gary Watson wrote: > I'm interested in contributing to the project... Starting up this > discussion thread for two reasons... > >1. To find out the best way I can personally contribute >2. Other people might be interested in contributing too, if so,

Re: [vim/vim] Class members are accesible only from the class where they are defined. (PR #13086)

On Thu, Sep 14, 2023 at 10:32 AM errael wrote: > I played around with vim including this PR. While trying stuff, ran into > #13041 > (comment) > ; > doesn't have anything to do with this PR. > > Unless there's something

Re: bell(), looking for builtin function to ring the bell

Hi, On Wed, Sep 13, 2023 at 9:32 AM Ernie Rael wrote: > > Greetings, > > In a plugin I'm working on, when certain simple errors occur, I want to ring > the bell, some kind of alert. A popup, use in some place in the plugin, is > more than is needed. > > The closest thing I can find is > > call

Re: [vim/vim] vim9class work/bugs TODO for vim9.1 (Discussion #13041)

On Tue, Sep 5, 2023 at 9:56 PM Yegappan Lakshmanan wrote: > > Hi, > > On Tue, Sep 5, 2023 at 8:20 PM errael wrote: >> >> (Short term discussion) >> >> Over a week ago, there was a one week estimate to take bug fixes. Some >> notable missing feat

Re: [vim/vim] vim9class work/bugs TODO for vim9.1 (Discussion #13041)

Hi, On Tue, Sep 5, 2023 at 8:20 PM errael wrote: > (Short term discussion) > > Over a week ago, there was a one week estimate to take bug fixes. Some > notable missing features were discovered: > >1. access control was not implemented (could write to privates) >2. reading/writing

Re: Commit: patch 9.0.1857: [security] heap-use-after-free in is_qf_win()

Hi Christian, On Sun, Sep 3, 2023 at 11:30 AM Christian Brabandt wrote: > > patch 9.0.1857: [security] heap-use-after-free in is_qf_win() > > Commit: > https://github.com/vim/vim/commit/fc68299d436cf87453e432daa77b6d545df4d7ed > Author: Christian Brabandt > Date: Sun Sep 3 20:20:52 2023

Re: vim9class: accessing statics from outside the class

On Sat, Sep 2, 2023 at 9:31 AM Ernie Rael wrote: > AFAICT, it doesn't work. Is anyone working on this? > > I've run into it while working https://github.com/vim/vim/pull/13007. > > I am taking a look, but I don't want duplicate efforts. > I am not working on this. - Yegappan -- -- You

Re: Vim9 class/object member access control

On Sat, Sep 2, 2023 at 5:02 AM Yegappan Lakshmanan wrote: > > Hi all, > > The access control to readonly, read-write and private members in a > class/object discussed in https://github.com/vim/vim/discussions/12979 > should all work now. Let us know if there are any cases

Vim9 class/object member access control

Hi all, The access control to readonly, read-write and private members in a class/object discussed in https://github.com/vim/vim/discussions/12979 should all work now. Let us know if there are any cases where the access control is not correctly enforced. When testing these, I found an existing

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

On Thu, Aug 31, 2023 at 6:50 AM errael wrote: > I have started a discussion (#12979 > ) to capture the > access matrix. > > Thank you. I'll take a look. I would have done something if you'd said "go > ahead" . > > > I have marked the failing cases

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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 >

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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,

Fix for the CI asan test failure due to a memory leak

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

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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 > +++

Re: [vim/vim] Make object/class member variables public by default (PR #12932)

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

Re: Updates on the Vim project

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 release than later. So it depends on how far we > want the Vim9

Re: Updates on the Vim project

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 weeks. > > > > Over the last days, I have been merging mostly runtime

Re: Vim9: Default object member access

Hi Doug, On Sun, Aug 27, 2023 at 7:14 AM Doug Kearns wrote: > > > On Fri, 25 Aug 2023 at 23:50, Yegappan Lakshmanan wrote: >> >> Hi all, >> >> From the email thread >> https://groups.google.com/g/vim_dev/c/yYpFNUHdRho/m/xjgrKqMoBQAJ?pli=1 >>

Re: Support for Private class/object methods

e an underscore indicates private class members and methods > whereas public ones don't have an underscore. > > And another issue: why isn't this thread shown in GitHub Discussions? Wasn't > the whole point of enabling Discussions so that more people can participate > in su

Re: Support for Private class/object methods

t > the whole point of enabling > Discussions so that more people can participate in such decision making? > I am used to sending emails to the mailing list. So I started this email thread. We can use Github discussions going forward for other features. Regards, Yegappan > O

Re: [vim/vim] Change the LSP HTTP header Content-Type field (PR #12295)

Hi, On Fri, Aug 25, 2023 at 4:26 PM Magnus Groß wrote: > @yegappan Is there any reason why the > Content-Type header is set in the first place? It causes problems with > some LSP servers such as haskell-language-server >

Re: Vim9: Default object member access

ds to look at the method/variable definition to see whether it is private or not. I prefer the leading underscore for private methods and member variables. Regards, Yegappan > > -- > shane.xb.qian > > From: vim_dev@googlegroups.com on behalf of

Re: Vim9: Default object member access

_____ > From: vim_dev@googlegroups.com on behalf of > Yegappan Lakshmanan > Sent: Friday, August 25, 2023 9:50:28 PM > To: vim_dev > Subject: Vim9: Default object member access > > Hi all, > > From the email thread > https://groups.google.com/g/vim_de

Vim9: Default object member access

Hi all, >From the email thread https://groups.google.com/g/vim_dev/c/yYpFNUHdRho/m/xjgrKqMoBQAJ?pli=1 and the following items in the todo.txt file: - Change access: public by default, private by prefixing "_". Check for error: can't have the same name twice (ignoring "_" prefix). This

Re: Support for Private class/object methods

Hi, On Thu, Aug 24, 2023 at 9:11 PM Doug Kearns wrote: > > On Fri, 25 Aug 2023 at 13:18, Yegappan Lakshmanan wrote: >> >> Hi all, >> >> The following item is in the todo.txt file for implementing private >> methods in a class: >> >> - Priv

Re: Support for Private class/object methods

Hi, On Thu, Aug 24, 2023 at 8:50 PM Ernie Rael wrote: > > On 23/08/24 8:18 PM, Yegappan Lakshmanan wrote: > > Hi all, > > > > The following item is in the todo.txt file for implementing private > > methods in a class: > > > > - Private meth

Support for Private class/object methods

Hi all, The following item is in the todo.txt file for implementing private methods in a class: - Private methods? either: private def Func() or: def _Func() Perhaps use "private" keyword instead of "_" prefix? Function and method names always start with an uppercase

Re: Updates on the Vim project

Hi Christian, On Wed, Aug 23, 2023 at 1:18 PM Christian Brabandt wrote: > > Hi, > this is a small update over what happened the last few weeks. > > Over the last days, I have been merging mostly runtime file changes, > small improvements to the Vim9 class implementations and bug fixes. >

Re: Commit: runtime(dosini): save and restore cpo value in syntax script

Hi Christian, On Sun, Aug 20, 2023 at 10:51 PM Christian Brabandt wrote: > > > On So, 20 Aug 2023, Yegappan Lakshmanan wrote: > > > On Sun, Aug 20, 2023 at 10:00 PM Christian Brabandt > > wrote: > > > runtime(dosini): save and restore cpo value in synta

Re: Commit: runtime(dosini): save and restore cpo value in syntax script

Hi, On Sun, Aug 20, 2023 at 10:00 PM Christian Brabandt wrote: > > runtime(dosini): save and restore cpo value in syntax script > A similar change is needed in the runtime/syntax/context.vim file also. I used the following command to find this: $ cd vim/runtime/syntax $ egrep '^ +\\' `grep

Re: Where is Bram?

Hi Rob, On Sun, Aug 20, 2023 at 8:27 PM Robert Webb wrote: > > Wow, very sad to hear about Bram, and so young (62). I did quite a lot of > work on vim more than 30 years ago. At first I didn't even have my own > computer. Sometimes I'd print out code at work, take it home, write new code > on

Re: Commit: patch 9.0.1771: regex: combining chars in collections not handled

Hi Christian, On Sun, Aug 20, 2023 at 11:45 AM Christian Brabandt wrote: > > patch 9.0.1771: regex: combining chars in collections not handled > > Commit: > https://github.com/vim/vim/commit/ca22fc36a4e8a315f199893ee8ff6253573f5fbe > Author: Christian Brabandt > Date: Sun Aug 20 20:34:22

Re: vim9class, getting it usable

On Fri, Aug 18, 2023 at 8:22 PM Yegappan Lakshmanan wrote: > > Hi, > > On Fri, Aug 18, 2023 at 8:21 PM Ernie Rael wrote: > > > > Hi all, > > > > Working on a project Feb/Mar using vim9 classes I filed several issues. > > Each time found a workaround, a

Re: vim9class, getting it usable

Hi, On Fri, Aug 18, 2023 at 8:21 PM Ernie Rael wrote: > > Hi all, > > Working on a project Feb/Mar using vim9 classes I filed several issues. Each > time found a workaround, and went on. Finally ran into > > https://github.com/vim/vim/issues/12089 > vim9class: Calling a base class method

PRs for the Vim 9.1 release milestone

Hi all, Most of the outstanding PRs are now either assigned to the vim-9.1 milestone or to the backlog: https://github.com/vim/vim/milestone/1 https://github.com/vim/vim/milestone/2 If you think a PR should be or should not be part of these milestones, let us know. The criteria for the vim-9.1

CI Linux tests are failing

Hi, The CI Linux tests are failing for the past few days due to missing linux-modules-extra-5.15.0-1042-azure package. Should we disable the sound tests temporarily and disable the installation of this package? Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do

Re: Surprising test failure after rebasing PR

Hi, On Mon, Aug 14, 2023 at 6:39 PM Ernie Rael wrote: > > Bunch of failures, all of them > > Set up snd-dummy > E: Package 'linux-modules-extra-5.15.0-1042-azure' has no installation > candidate > > I see this after rebasing and pushing two PR's. > > Is there something I need to do? > No. We

Re: The future of the Vim project

granted admin rights by Brams family, so we can continue with Github. > (Thanks @Fokke!) > > - I invited a few more members to join the Vim organization: Yegappan > Lakshmanan, Dominique Pellé, @mattn and @zeertzjq who have been > contributed to Vim in the past. Congratula

Re: Patch patch 9.0.1679: Cleanup Tests from leftover files

Hi, On Tue, Aug 8, 2023 at 12:57 PM Christian Brabandt wrote: > > > On Di, 08 Aug 2023, Christian Brabandt wrote: > > > patch 9.0.1679: Cleanup Tests from leftover files > > Sorry, trying to get the patch mails working. > > While this seems to fix the recent CI test failures about the file >

Re: Where is Bram?

Hi, On Tue, Aug 8, 2023 at 8:39 AM Yegappan Lakshmanan wrote: > > Hi Dominique, > > On Mon, Aug 7, 2023 at 1:12 PM Dominique Pellé > wrote: > > > > Yegappan Lakshmanan wrote: > > > > > Hi all, > > > > > > I am listing the tasks that Br

Re: Where is Bram?

Hi Dominique, On Mon, Aug 7, 2023 at 1:12 PM Dominique Pellé wrote: > > Yegappan Lakshmanan wrote: > > > Hi all, > > > > I am listing the tasks that Bram used to do for developing and maintaining > > Vim below (as far I can remember): > > > > 1. Dev

Re: Where is Bram?

Hi, On Tue, Aug 8, 2023 at 8:18 AM Doug Kearns wrote: > > On Tue, 8 Aug 2023 at 06:12, Dominique Pellé > wrote: > > > >> About point #9 i.e. "Incorporating the runtime file updates" >> I've always found it odd that some changes were split into >> a commit in src and another commit later in

Re: Where is Bram?

Hi all, I am listing the tasks that Bram used to do for developing and maintaining Vim below (as far I can remember): 1. Developing fixes for Vim crash reports including the analysis of fuzzy test files. 2. Addressing reported security vulnerabilities including those reported in

Re: Where is Bram?

Hi, Can someone with the admin access to https://www.vim.org/ update the "News" section with a link to the message from Bram's family? Regards, Yegappan On Mon, Aug 7, 2023 at 7:13 AM Antonio Giovanni Colombo wrote: > > Hi everybody, > > I too will miss Bram a lot. > > I am a minor contributor

Re: Where is Bram?

Hi, On Sat, Aug 5, 2023 at 9:11 AM Christian Brabandt wrote: > > Am 2023-08-05 16:30, schrieb Yegappan Lakshmanan: > > On Sat, Aug 5, 2023 at 5:53 AM Maxim Kim wrote: > >> > >> https://groups.google.com/g/vim_announce/c/tWahca9zkt4 > >> > > > >

Re: Where is Bram?

3 PM UTC+10 tooth pik wrote: >> >> i've been wondering the same thing -- my guess was he's in africa again >> >> On Sat, Aug 5, 2023 at 12:34 AM Yegappan Lakshmanan >> wrote: >>> >>> Hi all, >>> >>> I haven't seen any emails from

Where is Bram?

Hi all, I haven't seen any emails from Bram to the mailing list for more than a month. Is he on vacation? Has anyone had any contact with him in the last month? Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you

Re: [vim/vim] enable mappings in GTK (PR #12698)

Hi, On Sun, Jul 23, 2023 at 10:33 AM Casey Tucker wrote: > @chrisbra > > hm, can we have tests please? Can we make it a bit more explicit, that is done using the key on non-Macs? > > I may need a bit of advice on how to write a test for this. I imagine the > main

Re: [vim/vim] Why does `bufloaded()` call chdir() under the hood? (Issue #12694)

Hi Christian, On Sun, Jul 23, 2023 at 12:24 PM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > is this actually a problem? > > > Yes. Many of the LSP plugins use the bufloaded() function to check whether a buffer is loaded or not. If the buffer is not loaded, then they call the

Re: [vim/vim] Make charidx() and utf16idx() return value consistent with byteidx() return value (PR #12503)

Hi, On Tue, Jun 20, 2023 at 2:08 PM Yee Cheng Chin wrote: > I guess this is to make it so that you can do something like > byteidx(charidx(…)) and vice versa and have it return itself? And you are > essentially using charidx double duty as a fictional strcharlen() > function (since strlen()

Re: [vim/vim] Make charidx() and utf16idx() return value consistent with byteidx() return value (PR #12503)

Hi, On Tue, Jun 20, 2023 at 2:04 PM Yee Cheng Chin wrote: > May I ask what the motivation is for such a change? This seems counter to > any programming language libraries that I'm aware of. You will end up > returning an "index" that's clearly out of bounds and seems to actively > encourage

Re: LSP: cursor positioning on a multi-byte character with composing characters

Hi Bram, On Sat, Jun 3, 2023 at 3:48 PM Bram Moolenaar wrote: > > > Yegappan wrote: > > > I am updating the Vim9 LSP plugin to support various position > > encodings (utf-8, utf-16 and utf-32). > > I ran into a problem with positioning the cursor on a multibyte > > character with composing

charidx() return value when the string length in bytes is passed as the index

Hi, The byteidx() function returns the length of a string in bytes when the specified character index is equal to the number of characters in the string: echo byteidx("abc", 3) 3 But the charidx() function returns -1 when the specified byte index is equal to the number of bytes in the

  1   2   3   4   5   6   7   8   9   10   >