On Thu, 17 Jul 2025 at 03:51, Christian Brabandt wrote:
>
> On Di, 15 Jul 2025, Mark Manning wrote:
>
> > Ok, let me try this. (I finally got 'git diff' to work.)
>
> Thanks. Now I got 3 slightly varying patches :) Which one would you like
> to applied? If I see this correctly, those functions ar
Mark,
Re: https://www.vim.org/scripts/script.php?script_id=6159
On Sun, 13 Jul 2025 at 16:30, Mark Manning
wrote:
>
> Using Vim 9.1
>
> Hi everyone! I got a C source file and started to edit it and did not see my
> colors come up like normal. So for the last five hours I have been working on
>
Christian,
On Wed, 3 Jul 2024 at 06:52, Christian J. Robinson
wrote:
>
> This script doesn't highlight properly:
> vim9script
>
> def Out(in: bool): bool
>
> if in
> echo "yay!"
> else
> echo "boo!"
> endif
>
> return in
> endde
G'day Ron,
On Sun, 3 Sept 2023 at 22:33, Ron Aaron wrote:
> I was just given a bug report for a new version of my syntax file, and
> the problem is that a syntax keyword with a lone '[' doesn't work (it
> causes an error message E789)
>
> I have 'syn iskeyword 33-255' (because everything excep
On Sun, 3 Sept 2023 at 02:31, 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.
>
You can read them and write them at top-level but, from a
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 file changes,
> small improvements to the Vim9 class implementations and bug fixes.
>
> If you check the Milesto
On Mon, 28 Aug 2023 at 00:23, Yegappan Lakshmanan
wrote:
> 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,
> >>
> >>
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
> and the following items in the todo.txt file:
>
> - Change access: public by default, private by prefixing "_".
> Check
On Fri, 25 Aug 2023 at 15:21, Ernie Rael wrote:
> On 23/08/24 9:10 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
>> metho
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:
>
> - Private methods?
> either: private def Func()
> or: def _Func()
> Perhaps use "private" keyword instead o
On Wed, 9 Aug 2023 at 04:52, Christian Brabandt wrote:
>
> On Mi, 09 Aug 2023, Doug Kearns wrote:
>
> > Runtime file updates often include test updates (e.g., filetype
> detection tests) and changes to runtime infrastructure (e.g.,
> runtime/ftplugin.vim) are also arguably
On Wed, 9 Aug 2023 at 03:56, Christian Brabandt wrote:
>
> On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
>
> > I am not suggesting a separate minor release for each runtime file
> update here.
> > Otherwise, we will have too many minor releases. Can we make a minor
> release
> > only for PRs th
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 runtime. It
> often caused confusion, with PR author asking "part of
> my c
In Sat, 5 Aug 2023 at 22:53, Maxim Kim wrote:
> https://groups.google.com/g/vim_announce/c/tWahca9zkt4
>
It is with deep sadness that I receive this news.
There is no one in our field that I have more respect for and I'm grateful
I was able to express that sentiment to him not long ago.
Adopti
On Sun, 15 Jan 2023 at 02:34, Bram Moolenaar wrote:
>
> Most of the implementation of classes has been done. Feel free to give
> it a try. You might run into something that is still a todo item, or a
> bug. Please report this in a reproducible way.
>
> This is a good moment to evaluate the cur
On Fri, 3 Feb 2023 at 04:28, Bram Moolenaar wrote:
>
> Doug Kearns wrote:
>
> > I was just looking at the constructor documentation and noticed that the
> > default constructor includes parameters for each field in the order they
> > were declared. Having to chan
On Sun, 15 Jan 2023 at 02:34, Bram Moolenaar wrote:
>
> Most of the implementation of classes has been done. Feel free to give
> it a try. You might run into something that is still a todo item, or a
> bug. Please report this in a reproducible way.
>
> This is a good moment to evaluate the cur
On Mon, 23 Jan 2023 at 23:53, Bram Moolenaar wrote:
>
> I expected a lively discussion about alternatives for the class
> implementation, but nothing much happened.
Some of us are old soldiers with too many scars. :)
I'm a bit short on time today but I have a few thoughts, some of which may
be p
Here's an update on the vim9script -> lua transpiler that TJ Devries
has been working on for some time.
https://www.youtube.com/watch?v=zPQSST-M3fM
Nice work TJ.
Regards,
Doug
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
On Mon, 26 Dec 2022 at 02:02, Bram Moolenaar wrote:
[...]
> > This following currently defines a field and is, without context,
> > indistinguishable from any other assignment. Is that intended?
>
> With "var" it's indistinguishable from another declaration, I don't
> think it matters much tha
On Mon, 19 Dec 2022 at 00:33, Bram Moolenaar wrote:
>
> One thing I'm not yet sure about is the declaration. Currently it works
> like this:
>
> this.name: string
> this.gender: Gender
>
> Notice that there is no "var" keyword. It's not needed to recognize the
> declaration. I
On Mon, 12 Sept 2022 at 05:14, Bram Moolenaar wrote:
> Let's try to summarize:
This sounds good to me.
Thanks,
Doug
--
--
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.or
Bram,
It looks like this patch may have slipped through the cracks?
Thanks,
Doug
--
--
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
On Tue, 5 Apr 2022 at 22:32, Bram Moolenaar wrote:
>
>
>
> I found one on https://book.mercurial-scm.org/. Not sure if it's the
> same or the best, but it looks useful.
>
https://www.mercurial-scm.org/guide is the same page and includes a link to
the book.
Regards,
Doug
--
--
You received
On Tue, 5 Apr 2022 at 21:32, Christian Brabandt wrote:
> Oh and it looks like the Mercurial guide
> https://mercurial.selenic.com/guide/ vanished, so please also remove the
> link to that guide.
>
The guide is still there at https://mercurial.selenic.com/guide. Drop the
trailing forward slas
On Thu, 13 Jan 2022 at 04:55, Manuel Ortega wrote:
> Ah, it seems I misremembered the details. But my point remains pretty much
> the same. I'd said it was unexpected for the comment char of vim9script to
> be '#'; it's at least as unexpected for it to be '#', and even
> more unexpected for
On Mon, 20 Sept 2021 at 11:44, Charles Campbell wrote:
>
> Hello,
>
> Its been brought to my attention (thanks, Naruhiko Nishino) that vim's
> heredoc's syntax highlighting may not need to support commenting, either
> old-style or vim9 style. Some of the examples show vimL use, where
> comment sup
On Mon, 20 Sept 2021 at 14:01, Ron Aaron wrote:
>
> Changes to the existing 8th syntax and ftplugin files:
>
> diff --git a/runtime/ftplugin/8th.vim b/runtime/ftplugin/8th.vim
> index 14301187d..60a7b0cb4 100644
> --- a/runtime/ftplugin/8th.vim
> +++ b/runtime/ftplugin/8th.vim
> @@ -1,7 +1,7 @@
>
On Sun, 13 Jun 2021 at 15:23, Yegappan Lakshmanan
wrote:
> Hi all,
>
> I have been using Vim for more than 25 years and contributing to
> the Vim development for 20 years. I have captured my contributions
> to Vim over the years in the following page:
>
> https://gist.github.com/yegappan/4f4cbea5
On Sun, 11 Apr 2021 at 22:53, Bram Moolenaar wrote:
> It is possible to only match "endif" at the start of the line or after a
> bar:
>
> '\:\%(^\||\)\s*el\%[seif]\>:\%(^\||\)\s*en\%[dif]\>,'
>
> But then the cursor will move to the start of the line or the bar.
> Putting in \zs to positio
G'day all,
I have noticed that there are often pull requests for updates to runtime
files created against the main repo rather than being directed to the
appropriate maintainers.
GitHub apparently has a feature[1] that allows for file ownership. If
adopted this would cause the maintainer to be n
On Sat, 15 Aug 2020 at 00:44, Bram Moolenaar wrote:
>
> Doug Kearns wrote:
>
> > I've noticed that most of the ftplugins that support browsefilter don't
> > test for the "gui_gtk" feature.
> >
> > Is there a process in place for executing bulk
G'day all,
I've noticed that most of the ftplugins that support browsefilter don't
test for the "gui_gtk" feature.
Is there a process in place for executing bulk ftplugin updates in a case
like this or should I just contact all the maintainers?
Thanks,
Doug
--
--
You received this message fro
Please see attached.
Regards,
Doug
--
--
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 Goog
On 14 August 2013 05:03, Dominique Pellé wrote:
> I could narrow it down further. I can reproduce it with:
>
> # Create a file (6 space and a x, bug does not happen with less than 6
> spaces):
> $ echo " x" > foo
> $ valgrind --log-file=valgrind.log vim -u NONE -N -c 'syn on' foo
>
> Then
On 14 June 2013 13:37, 陈云杰 wrote:
> after ruby code:
>
> 'asdf'<<"||"<<'asdfasdf'
>
> syntax highlight has broken
That appears to be broken with much earlier versions. E.g. 7.3.638
Of course, formatting it 'nicely' fixes the problem.
'asdf' << "||" << 'asdfasdf'
The heuristic to differentiate
On 12 June 2013 15:13, Ben Fritz wrote:
> On Monday, June 10, 2013 8:47:35 PM UTC-5, Hiroshi Shirosaki wrote:
>>
>> rubyPredefinedConstant pattern looks much slower with this file.
>>
>> syntime result:
>>
>> :set re=0
>>
>> TOTAL COUNT MATCH SLOWEST AVERAGE NAME PATT
On Thu, Aug 5, 2010 at 3:20 AM, Shawn B. wrote:
> As per numerous requests I've been told to post here to get my updated
> phpcomplete.vim script (http://www.vim.org/scripts/script.php?
> script_id=3171) included as the default in 7.3. How does one go about
> doing that?
In general you'd contact
On 3/12/09, Roberto Miura Honji wrote:
> Vim will participate?
>
> I'm thinking to try a project with vim if it's possible.
> Someone know something about this?
There has been some recent discussion regarding GSoC on this list.
Regards,
Doug
--~--~-~--~~~---~--~
On 2/15/09, Danek Duvall wrote:
> If
> there are any Python script torture tests I should run, let me know; I'm
> not sure what the best python scripts are to play with.
You could play with the distributed Python omni completion:
autoload/pythoncomplete.vim
Regards,
Doug
--~--~
On 2/11/09, Tom Link wrote:
>
> Hi folks,
>
> Maybe somebody has some use for this. I wrote a small ruby script that
> allows the creation of vimballs (plain text or gzipped) from the
> command line. It's still young and fresh and experimental. I ran it
> over my own plugins and the generate
On 1/15/09, Yasuhiro MATSUMOTO wrote:
>
> Hi all.
>
> Starting vim with arguments '*.rb' is very slow. It cause vim search
> ruby path from system call in 'ftplugin/ruby.vim'.
> 'ftplugin/perl.vim' check perlpath as global variable with
> exists('perlpath'). I use poor spec machine, and I w
Nikolai,
On 10/21/08, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
>
> Has remove() always thrown an error if idx is beyond the end of list?
>
> Either way, what's the reasoning behind it doing so? If the items
> aren't there to begin with, then great, that's precisely what I want.
Ignoring th
On 9/4/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> I have now added a search box to the search page on www.vim.org where
> you can specifically search for Vim scripts, anywhere on the internet.
> This uses Google Code Search.
Excellent! Thanks Bram.
Regards,
Doug
--~--~-~--~~-
G'day Martin,
On 8/27/07, krischik <[EMAIL PROTECTED]> wrote:
> My proposal (if you have not guessed already) is to merge more
> separate plug ins into modes.
We do something similar with http://vim-ruby.rubyforge.org/ which
distributes all of the 'official' Ruby related runtime files in a
s
On 8/1/07, hamlen <[EMAIL PROTECTED]> wrote:
>
> Bug: A nested, transparent syntax region loses its transparency when
> extending its containing region.
This looks like the bug I reported back in February so Bram is aware
of it. It's listed in todo.txt.
Regards,
Doug
--~--~-~--~~--
On 8/1/07, hamlen <[EMAIL PROTECTED]> wrote:
>
> Okay, sorry for the repeat.
No problem. You couldn't have been sure from the TODO description
anyway I suspect. :)
> Where can I see todo.txt?
:help TODO or :help known-bugs
Regards,
Doug
--~--~-~--~~~---~--~~
47 matches
Mail list logo
