On Mo, 14 Jul 2025, Tony Mechelynck wrote:
> Are you sure you pushed it to https://www.vim.org/hgweb/vim/ ? "hg in"
> gives me nothing new after the runtime files changeset which followed
> patch 1540 yesterday.
I did now trigger it manually.
> N.B. I am getting sporadically "HTTP error 503: S
On Mon, Jul 14, 2025 at 9:48 PM Christian Brabandt wrote:
>
>
> On Mo, 14 Jul 2025, Tony Mechelynck wrote:
>
> > After applying patches 1539 and 1540 I get the following in all builds
> > (Tiny, Normal and Huge):
> >
> > insexpand.c: In function ‘ins_compl_new_leader’:
> > insexpand.c:2459:9: warn
Sorry - I decided that name was way too long and shortened it to
cStdCLibFunctions
On Monday, July 14, 2025 at 4:09:56 PM UTC-5 Mark Manning wrote:
> @Doug Kearns,
>
> Ok. How about if I made it something like
>
> cStandardCLibraryFunctions
>
> as the name and then the list could then be i
@Doug Kearns,
Ok. How about if I made it something like
cStandardCLibraryFunctions
as the name and then the list could then be included into a
later cFunction command? Would that be a good idea? Also,
I think I'm going to have to try the command that is in the
"still to be released" c.vim that
runtime(python): highlight bytes in python
Commit:
https://github.com/vim/vim/commit/a24f5be86d895981cb84266f98bae9f14407264b
Author: Rob B
Date: Mon Jul 14 22:30:59 2025 +0200
runtime(python): highlight bytes in python
- Highlight bytes literals
- Do not highlight Unicode es
runtime(python2): highlight unicode strings in python2
Commit:
https://github.com/vim/vim/commit/baa781a4c35d7cc07d28bb6f0062c7fddf8e8556
Author: Rob B
Date: Mon Jul 14 22:21:44 2025 +0200
runtime(python2): highlight unicode strings in python2
fixes: https://github.com/vim/vim/is
patch 9.1.1544: :retab cannot be limited to indentation only
Commit:
https://github.com/vim/vim/commit/836e54f5de8479a39f6d1dd4a13202af0e447311
Author: Hirohito Higashi
Date: Mon Jul 14 22:11:34 2025 +0200
patch 9.1.1544: :retab cannot be limited to indentation only
Problem: :re
runtime(erlang): Add support for triple-quoted strings and docstrings
Commit:
https://github.com/vim/vim/commit/e85a66a4d4a44bc13862a7b43ca22d929b97503a
Author: Csaba Hoch
Date: Mon Jul 14 22:02:18 2025 +0200
runtime(erlang): Add support for triple-quoted strings and docstrings
E
patch 9.1.1543: Wayland: clipboard appears to not be working
Commit:
https://github.com/vim/vim/commit/d0bf380efa4ab0aabc5479274043f0de1115a232
Author: Foxe Chen
Date: Mon Jul 14 21:54:23 2025 +0200
patch 9.1.1543: Wayland: clipboard appears to not be working
Problem: Wayland: c
patch 9.1.1542: Coverity complains about uninitialized variable
Commit:
https://github.com/vim/vim/commit/6865bdc914cf998f23ff4c80bae60bff6639d8c3
Author: Christian Brabandt
Date: Mon Jul 14 21:46:46 2025 +0200
patch 9.1.1542: Coverity complains about uninitialized variable
Probl
On Mo, 14 Jul 2025, Tony Mechelynck wrote:
> After applying patches 1539 and 1540 I get the following in all builds
> (Tiny, Normal and Huge):
>
> insexpand.c: In function ‘ins_compl_new_leader’:
> insexpand.c:2459:9: warning: ‘save_w_wrow’ may be used uninitialized
> [-Wmaybe-uninitialized]
>
patch 9.1.1541: Vim9: error when last enum value ends with a comma
Commit:
https://github.com/vim/vim/commit/ada6b27ff1b17584779a3b6d55f89f5db1aec75e
Author: Yegappan Lakshmanan
Date: Mon Jul 14 21:27:34 2025 +0200
patch 9.1.1541: Vim9: error when last enum value ends with a comma
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
>
13 matches
Mail list logo
