Re: Unable to move away from help buffer

Hi, this behaviour has been changed in v9.1.0557 to work as documented, please see :h :bn for the expected behaviour. If you open the help at :h changed-9.2 and scroll down until the heading Ex commands: you see it is documented there. Thanks, Chris On Mi, 23 Jul 2025, 'hebar...@googlemail.com

Re: Unable to move away from help buffer

Seems I forgot some details: - The behavior described is an OS-independent regression from version 9.1.??? - I'm using the latest version of vim/gvim 9.1.1582. - The behavior is perceived only with help buffers (i.e. ft=help). - Setting ft=text and modifiable doesn't remedy the problem. On Tuesd

Re: Vim.pot in the repository gives noisy diffs

On Do, 17 Jul 2025, Christian Brabandt wrote: > I noticed this too so I tried this out briefly yesterday, but > unfortunately I couldn't make it work by moving the included patches > variable below any translatable line, so that incrementing the patch > number wouldn't cause this. > > Perhap

Re: Vim.pot in the repository gives noisy diffs

On Mi, 16 Jul 2025, Christ van Willegen wrote: > Hi, > > Since Christian added the vim.pot file to the repository, the Patch mails > have become noisy, since translatable strings in ``version.c`` are shifted by > 2 lines for every commit.  > > Would it be possible to change the position of t

Re: C.VIM Syntax file update

Thank you. I mucked up trying to upload the diff a couple of times and thought I had deleted them. But at least this is now down. :-) Thank you again both Doug and Christian. On Wed, Jul 16, 2025 at 1:22 PM Doug Kearns wrote: > On Thu, 17 Jul 2025 at 03:51, Christian Brabandt > wrote: > > > >

Re: C.VIM Syntax file update

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

Re: C.VIM Syntax file update

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 are not highlighted by default, so that would be the right thing to

Re: C.VIM Syntax file update

Ok, I just uploaded the DIFF of the original c.vim file and my c.vim file. Is this what you think he needs? (Only took me six tries to get it uploaded. Ugh.) Mark :-) On Mon, 14 Jul 2025 21:56:22 +1000 Doug Kearns wrote: > Mark, > > Re: https://www.vim.org/scripts/script.php?scrip

Re: C.VIM Syntax file update

I think I'm going to have to try the command that is in the >>> "still to be released" c.vim that you posted about. I want >>> to test it out to see if it is better than what I put into >>> my c.vim file. If it is - then I'll take mine back out of >>

Re: C.VIM Syntax file update

t; 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 r

Re: C.VIM Syntax file update

hing 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 i

Re: C.VIM Syntax file update

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 you posted about. I want >> to test it out to see if it is better than what I put into >> my c.vim file. If it is - th

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

* Tony Mechelynck [250715 07:36]: > On Tue, Jul 15, 2025 at 8:13 AM Christian Brabandt wrote: > > > N.B. I am getting sporadically "HTTP error 503: Service unavailable", > > > often but not every time, and when I don't there are "no changes > > > found". > > > > It might be time to consider migra

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

On Di, 15 Jul 2025, Tony Mechelynck wrote: > I hate git, if I try I expect to be constantly doing the opposite of > what I mean to do. Am I really the only one still getting the Vim > source from the Mercurial server ? It's not so bad, especially if you are only want to keep in sync with lates

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

On Tue, Jul 15, 2025 at 8:13 AM Christian Brabandt wrote: > > > 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

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

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

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

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

Re: C.VIM Syntax file update

I put into > my c.vim file. If it is - then I'll take mine back out of > what I have. > > On Monday, July 14, 2025 at 6:57:08 AM UTC-5 Doug Kearns wrote: > >> Mark, >> >> Re: https://www.vim.org/scripts/script.php?script_id=6159 >> >> On Sun, 13 Jul

Re: C.VIM Syntax file update

uot; c.vim that you posted about. I want to test it out to see if it is better than what I put into my c.vim file. If it is - then I'll take mine back out of what I have. On Monday, July 14, 2025 at 6:57:08 AM UTC-5 Doug Kearns wrote: > Mark, > > Re: https://www.vim.org/scripts/scr

Re: Warnings -Wmaybe-uninitialized (x2) at src/insexpand.c:2459 after applying patches 1539 and 1540

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

Re: C.VIM Syntax file update

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

Re: C.VIM Syntax file update

> "What is a PR?" and "How do I do it?" He means 'pull request' in 'Github', or actually you should be Ok to go with 'git patch' workflow as well; just send your code patch mail to him. FYI. check ':h develop.txt' -- shane.xb.qian -- -- You received this message from the "vim_dev" maillist. D

Re: C.VIM Syntax file update

@Christian Brabandt - I'm sorry - although I have been a part of VIM for many years - I hardly ever get on any of the groups. So my question to you is "What is a PR?" and "How do I do it?" If there is a web page that explains all of that - please post or send it to me. Thanks! Mark On Sunda

Re: C.VIM Syntax file update

I actually prefer function names to stay normal color, not sure about others. Having said that I am able to override it for my personal config and in colorschemes I am authoring :) On Sunday, July 13, 2025 at 5:23:17 PM UTC+10 Christian Brabandt wrote: > > On Sa, 12 Jul 2025, Mark Manning wrot

Re: How to read Vim's source code?

Hi, I am afraid, I won't be of much help here, but you have been looking at a quite complex problem. I personally don't see myself capable of doing such complex changes that have the ability to cause regressions in other parts of the code. Also note, that the win_line() function needs to stay i

Re: C.VIM Syntax file update

On Sa, 12 Jul 2025, 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 > making changes to the C.VIM syntax file. I was wondering if it can be > i

Re: Missing tag v9.1.1538 on Mercurial server

On Sa, 12 Jul 2025, Tony Mechelynck wrote: > Mercurial changeset 333ccd1e9743 (corresponding to git changeset > 7306e8fcdb6fd17276b6aafb23a522cefecb5857) adds patchlevel 1538 to > src/version.c but the corresponding tag is missing in .hgtags ; I > don't know about the git tag, bookmark, or whate

Re: Commit: patch 9.1.1528: completion: crash with getcompletion()

Hi, On Di, 08 Jul 2025, Christian Brabandt wrote: > patch 9.1.1528: completion: crash with getcompletion() > > Commit: > https://github.com/vim/vim/commit/f2ec8d4afc0623a477d198c42994544190b4e427 > Author: Christian Brabandt > Date: Tue Jul 8 22:04:10 2025 +0200 > [...] > diff --git a/src

Re: Interpreted languages

P.S. I found how to add +lua: apparently when upgrading lua automatically from 3.13 to 3.14 package lua314-devel had not been installed. Best regards, Tony. On Mon, Jun 30, 2025 at 1:22 AM Tony Mechelynck wrote: > > The gvim I normally use is "Huge without interpreted languages" but I > also com

Commit: runtime(vim): re-generate vim syntax script after v9.1.1487

runtime(vim): re-generate vim syntax script after v9.1.1487 Commit: https://github.com/vim/vim/commit/32f4febdc84a4e7539df7edb446453e2b577cd12 Author: Christian Brabandt Date: Sat Jun 28 20:23:32 2025 +0200 runtime(vim): re-generate vim syntax script after v9.1.1487 Signed-off

Re: failed to build 9.1.1485

that didn't help or was i supposed to export before myconfig? (i did before re-running make) On Fri, Jun 27, 2025 at 2:52 PM Christian Brabandt wrote: > > On Fr, 27 Jun 2025, tooth pik wrote: > > > weird error: > > > > /usr/lib64/gcc/x86_64-suse-linux/7/../.

Re: failed to build 9.1.1485

On Fr, 27 Jun 2025, tooth pik wrote: > weird error: > > /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: > objects/os_unix.o: undefined reference to symbol 'shm_open@@GLIBC_2.2.5' > /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: > /lib64/librt

Re: [vim/vim] Remove the interactive tutor (PR #17600)

On Wed, Jun 25, 2025 at 12:28 PM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > *chrisbra* left a comment (vim/vim#17600) > > > most of the initial porting work was done by @yegappan > so I'd al

Re: Compile warning -Wmaybe-uninitialized in ex_cmds.c after applying patches 9.1.1474 to 1478

On Mi, 25 Jun 2025, Tony Mechelynck wrote: > Compile warning -Wmaybe-uninitialized in ex_cmds.c after applying > patches 9.1.1474 to 1478 > On "make reconfig" in any build using gcc (SUSE Linux) 15.1.1 20250528: > > ex_cmds.c: In function ‘ex_uniq’: > ex_cmds.c:838:24: warning: ‘save_c’ may be

Re: New motion command proposal

On Mon, 09 Jun 2025, Iago Jacob wrote: > [Proposal] New motion command: `binsearch` for binary-search-style line > navigation > > Hi fellow Vim enthusiasts, > > I'd like to propose a new motion command for Vim: `binsearch`, which > facilitates precise cursor movement in **normal** and **visual

Re: Commit: patch 9.1.1439: Last diff folds not merged

On 2025-06-08, Christ van Willegen wrote: > Hi, > > Op zo 8 jun 2025 16:15 schreef Christian Brabandt : > > patch 9.1.1439: Last diff folds not merged > > Commit: https://github.com/vim/vim/commit/ > 3fa0d3514b928e0b21ef24594785f9104a3ffafd > Author: Gary Johnson > Date:� �S

Re: Commit: patch 9.1.1439: Last diff folds not merged

Hi, Op zo 8 jun 2025 16:15 schreef Christian Brabandt : > patch 9.1.1439: Last diff folds not merged > > Commit: > https://github.com/vim/vim/commit/3fa0d3514b928e0b21ef24594785f9104a3ffafd > Author: Gary Johnson > Date: Sun Jun 8 16:00:06 2025 +0200 > > patch 9.1.1439: Last diff folds not

Re: x11/gtk errors when gvim invoked with a -geometry option

On Fri, 06 Jun 2025, tooth pik wrote: > i am now getting weird random looking crappola in front of my PS1 prompt when > i run any script that invokes gvim with a geometry option > > Thu 16:31 ~/.build/vim: start3 > 0;48R0;76VThu 16:31 ~/.build/vim: 8 > > start3 is such a script > > i have ov

Re: x11/gtk errors when gvim invoked with a -geometry option

yes! thank you! On Sun, Jun 8, 2025 at 8:35 AM Christian Brabandt wrote: > > On Fri, 06 Jun 2025, tooth pik wrote: > > > i am now getting weird random looking crappola in front of my PS1 prompt > when i run any script that invokes gvim with a geometry option > > > > Thu 16:31 ~/.build/vim: star

Re: Commit: patch 9.1.1426: completion: register contents not completed

Hi, Op ma 2 jun 2025 20:00 schreef Christian Brabandt : > patch 9.1.1426: completion: register contents not completed > > Commit: > https://github.com/vim/vim/commit/d5fdfa5c9cf00790cf720e15c580a591a09fa906 > Author: glepnir > Date: Mon Jun 2 19:45:41 2025 +0200 > > patch 9.1.1426: compl

Re: Commit: patch 9.1.1408: not easily possible to complete from register content

On Mon, 26 May 2025, Christ van Willegen wrote: > It looks like all the code changes are missing from this patch... Strange, the same patch was pushed successfully to mercurial https://www.vim.org/hgweb/vim/rev/f08b2dd93702 not sure what went wrong with sending. Thanks, Christian -- "You twe

Re: Commit: patch 9.1.1408: not easily possible to complete from register content

Hi Op ma 26 mei 2025 18:30 schreef Christian Brabandt : > patch 9.1.1408: not easily possible to complete from register content > > Commit: > https://github.com/vim/vim/commit/0546068aaef2b1a40faa2945ef7eba249739f219 > Author: glepnir > Date: Mon May 26 18:23:27 2025 +0200 > > patch 9.1.1

Re: [vim/vim] clipboard support for regular vim(not gvim) (Discussion #17343)

On 2025-05-19, Maxim Kim (Vim Github Repository) wrote: > This is up to the people who is in charge of building binaries for the > distribution you're using. And they often create a package that has clipboard and X11 enabled, but the package may not have a name you would expect. For example, Ubun

Re: Commit: patch 9.1.1391: Vim does not have a vertical tabpanel

On Wed, 14 May 2025, 7to...@gmail.com wrote: > > + *E1547* *:redrawtabp* *:redrawtabpanel* > > +:redrawtabp[anel] Redraw the tabline.  Useful to update the tabpanel > > The world "tabline" needs to be changed to "tabpanel" here. A copy/paste > error. Thanks, fixed. Thanks, Christian -- Den

Re: Vim 9.1.1391 : patchlevel 1391 missing in src/version.c

On Wed, 14 May 2025, Tony Mechelynck wrote: > The v9.1.1391 patch for src/version.c includes several changes, but it > does not add an additional patchlevel to the list static int > included_patches[] starting at new line 710, therefore the resulting > Vim identifies itself as revision 9.1.1390.

Re: Commit: patch 9.1.1391: Vim does not have a vertical tabpanel

> + *E1547* *:redrawtabp* *:redrawtabpanel* > +:redrawtabp[anel] Redraw the tabline. Useful to update the tabpanel The world "tabline" needs to be changed to "tabpanel" here. A copy/paste error. Tom -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply

Re: [vim/vim] Incorrect search result (Issue #17312)

I can reproduce tahzibijafar's reported result with Vim 9.1.1365 on Ubuntu 24.04.2 with my normal configuration and with $ vim -N -u NONE -i NONE and the additional settings. I have not looked into the reason. Regards, Gary -- -- You received this message from the "vim_dev" maillist. Do

Re: [vim/vim] feat: hide fold text line - proposal looking for feedback

Christian, Thanks, that is exactly the kind of feedback I was looking for. I should have some time to work on this tomorrow. 1. I agree foldshowline is a good name and I'll make that happen. 2. I will check existing local-window options in options.txt. 3. I will update my draft change

Re: [vim/vim] feat: hide fold text line - proposal looking for feedback

On Wed, 07 May 2025, Jim Harkins wrote: > I started by looking at the feasibility and wound up with a proof of > concept, though I intended to get feedback earlier. > > Feature Proposal > > Enable fold text lines to be hidden, allowing more unfolded lines to > be displayed. > > Use Case > >

[FIXED] Re: "E36 Not enough room" while sourcing handcrafted session file

On Fri, May 9, 2025 at 5:38 PM Tony Mechelynck wrote: > > On Fri, May 9, 2025 at 10:55 AM Christian Brabandt wrote: > > > > > > On Fri, 09 May 2025, Tony Mechelynck wrote: > > > > > On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck > > > wrote: > > > > > > > > Since a few days, while sourcing the f

Re: new gtk errors

Can you please both try patch v9.1.1377 if this helps? If not, please report back. Best would be a new ticket with all information you have. Thanks, Chris On Fri, 09 May 2025, Tony Mechelynck wrote: > The problem I have is not the same as the ticket. For one thing, I get > it "every time", lno

Re: "E36 Not enough room" while sourcing handcrafted session file

On Fri, May 9, 2025 at 10:55 AM Christian Brabandt wrote: > > > On Fri, 09 May 2025, Tony Mechelynck wrote: > > > On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck > > wrote: > > > > > > Since a few days, while sourcing the following session file: > > > > > > " Vim session file > > > " This one was

Re: new gtk errors

The problem I have is not the same as the ticket. For one thing, I get it "every time", lnot "occasionally"; also I am on X11, not Wayland. Typing "gvim -N -u NONE" in a bash shell opens gvim with menu and toolbar but no vertical space for a future editfile; in order to see a command line I have t

Re: "E36 Not enough room" while sourcing handcrafted session file

On Fri, 09 May 2025, Tony Mechelynck wrote: > On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck > wrote: > > > > Since a few days, while sourcing the following session file: > > > > " Vim session file > > " This one was not generated by :mksession. > > > > " e ~/.mozilla/seamonkey/eiox68r9.default

Re: new gtk errors

Hi, Can you both please respond to the mentioned ticket? Is this that bad, that we need to revert? Thanks, Chris On Fri, 09 May 2025, Tony Mechelynck wrote: > P.S. Oh, and X11, I don't use Wayland. > > Best regards, > Tony. > > On Fri, May 9, 2025 at 9:58 AM Tony Mechelynck > wrote: > > > >

Re: new gtk errors

P.S. Oh, and X11, I don't use Wayland. Best regards, Tony. On Fri, May 9, 2025 at 9:58 AM Tony Mechelynck wrote: > > This seems to be the same problem as the one I reported a few minutes > ago as «"E36 Not enough room" while sourcing handcrafted session > file». I am now with gvim 9.1.1374 but i

Re: new gtk errors

This seems to be the same problem as the one I reported a few minutes ago as «"E36 Not enough room" while sourcing handcrafted session file». I am now with gvim 9.1.1374 but it has been happening for a couple of days in earlier versions. Huge version with GTK3 GUI. The GUI opened with just enough h

Re: "E36 Not enough room" while sourcing handcrafted session file

On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck wrote: > > Since a few days, while sourcing the following session file: > > " Vim session file > " This one was not generated by :mksession. > > " e ~/.mozilla/seamonkey/eiox68r9.default/user.js > e ~/.mozilla/seamonkey/r0hh40it.frg-2018+/user.js > lc

Re: new gtk errors

yes that looks like it what's wayland? is it like x11 or kde? opensuse 15.6 On Thu, May 8, 2025 at 4:52 PM Christian Brabandt wrote: > I still don't understand. Is this your issue: > https://github.com/vim/vim/issues/17279 > > Are you also on Wayland? > Are those just warnings? Or does it pre

Re: Commit: patch 9.1.1367: too many strlen() calls in gui.c

On Thu, 08 May 2025, Christ van Willegen wrote: > Hi, > > A typo below: > > > Op wo 7 mei 2025 20:15 schreef Christian Brabandt : > > patch 9.1.1367: too many strlen() calls in gui.c > > + > +           // Make sure resulting NameBuff will not exceed it's bounds. > +       

Re: new gtk errors

I still don't understand. Is this your issue: https://github.com/vim/vim/issues/17279 Are you also on Wayland? Are those just warnings? Or does it prevent resizing? Thanks, Chris On Thu, 08 May 2025, tooth pik wrote: > ordinarily, when i start a raw gvim with no size specified, it assumes the

Re: [vim/vim] fix some wrong style (PR #17278)

On 2025-05-08, glepnir (Vim Github Repository) wrote: > some indent and brace style > > --- > > You can view, comment on, or merge this pull request online at: > > https://github.com/vim/vim/pull/17278 > > Commit Summ

Re: new gtk errors

interestingly, when i start my calendar script, it comes up sized to the requested dimensions, the difference being i use lines= and columns= in a .vim script to obtain the size On Thu, May 8, 2025 at 9:13 AM tooth pik wrote: > ordinarily, when i start a raw gvim with no size specified, it assum

Re: new gtk errors

Hi, And what exactly is the issue, don't understand what you mean with "won't open its requested size"? Can you share a picture and how to reproduce? Did you try `gvim --clean`? k Does it work, if you checkout pqatch v9.1.1367 instead? Perhaps there is an issue with v9.1.1368? Thanks, Chris O

Re: Commit: patch 9.1.1367: too many strlen() calls in gui.c

Hi, A typo below: Op wo 7 mei 2025 20:15 schreef Christian Brabandt : > patch 9.1.1367: too many strlen() calls in gui.c > > + > + // Make sure resulting NameBuff will not exceed it's bounds. > + if (NameBufflen + buflen < MAXPATHL) > + { > ...not exceed its bound

Re: new gtk errors

vim is 9.1.1369 gtk3-devel is 3.24.34 anything else? On Wed, May 7, 2025 at 4:40 PM Christian Brabandt wrote: > > On Wed, 07 May 2025, tooth pik wrote: > > > all of a sudden gvim won't open to its requested size, while various > > "gtk_distribute_natural_allocatio: assertion 'extra_space >= 0'

Re: new gtk errors

On Wed, 07 May 2025, tooth pik wrote: > all of a sudden gvim won't open to its requested size, while various > "gtk_distribute_natural_allocatio:  assertion 'extra_space >= 0' failed" > errors > go to stdout What version? And what is your GTK version? Thanks, Christian -- "Here's something t

Re: "Connection refused" on Mercurial server

Hello everyone, that's right, I had an alarm on my private monitoring system, but unfortunately for work reasons I haven't had time to pay enough attention to the problem. According to the Monitoring the website was down between 4PM and 8PM (CEST) and that was caused by almost 100% memory usag

Re: "Connection refused" on Mercurial server

On Sat, Apr 26, 2025 at 8:03 PM Christian Brabandt wrote: > > > On Fri, 25 Apr 2025, Tony Mechelynck wrote: > > > I'm giving below my "last good" and "first bad" attempts at > > connection. This is still happening at 2025-04-25 23:15 Belgian summer > > time (UTC+0200). > > > > linux-tuxedo:~/.buil

Re: "Connection refused" on Mercurial server

On Fri, 25 Apr 2025, Tony Mechelynck wrote: > I'm giving below my "last good" and "first bad" attempts at > connection. This is still happening at 2025-04-25 23:15 Belgian summer > time (UTC+0200). > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date > comparing with htt

Re: xpm on MinGW-ucrt GUI=yes fails

That fixes part of it. It now fails on line 734 of Make_cyg_ming.mak: #CFLAGS += -DFEAT_XPM_W32 -I $(XPM)/include -I $(XPM)/../include #CFLAGS += -DFEAT_XPM_W32 -I $(XPM)/../include CFLAGS += -DFEAT_XPM_W32 -I xpm/include I don't see the logic in using the XPM macro here. The location of the xp

Commit: patch 9.1.1323: b:undo_ftplugin not executed when re-using buffer

patch 9.1.1323: b:undo_ftplugin not executed when re-using buffer Commit: https://github.com/vim/vim/commit/baa8c90cc0d214e036a3a7980d5cf95cae88a68d Author: Christian Brabandt Date: Sat Apr 19 11:14:11 2025 +0200 patch 9.1.1323: b:undo_ftplugin not executed when re-using buffer

Re: [vim/vim] tests: redundant and strange use of :execute in test_ins_complete.vim (PR #17143)

On Fri, 18 Apr 2025, Christ van Willegen wrote: > index 0e3711eb75530..52721bd532ad0 100644 > --- a/src/ops.c > +++ b/src/ops.c > @@ -248,11 +248,11 @@ get_vts_sum(int *vts_array, int index) > intsum = 0; > inti; > > -// Perform the summation for indeces within the

Re: [vim/vim] tests: redundant and strange use of :execute in test_ins_complete.vim (PR #17143)

Hi, Op vr 18 apr 2025 01:12 schreef zeertzjq : > @zeertzjq pushed 1 commit. > >- d50a4f8 > > >tests: redundant and strange use of :execute in test_ins_complete.vim > > Are you st

Re: Compile warning in all builds in insexpand.c (at patchlevel 9.1.1312, not at patchlevel 9.1.1309)

On Wed, 16 Apr 2025, Tony Mechelynck wrote: > In function ‘ins_compl_build_pum’, > inlined from ‘ins_compl_show_pum’ at insexpand.c:1668:8, > inlined from ‘ins_compl_show_pum’ at insexpand.c:1654:1: > insexpand.c:1520:52: warning: ‘match_count’ may be used uninitialized > [-Wmaybe-uninit

Re: At patchlevel 9.1.1301, compile warning in insexpand.c in Normal and Huge but not Tiny

On Tue, 15 Apr 2025, Tony Mechelynck wrote: > In function ‘cpt_compl_refresh’, > inlined from ‘ins_compl_new_leader’ at insexpand.c:2218:6: > insexpand.c:6450:16: warning: ‘cb’ may be used uninitialized > [-Wmaybe-uninitialized] > 6450 | if (cb) > |^ > inse

Re: Building GUI Vim on MacOS

Platform Mac OSX 10.6.8 - Snow Leopard Tools: XCode with the gnu tools and libraries off the snow leopard install DVD. gcc version 4.2.1 I only used the supplied libraries on the dvd. However, I suppose one could download the gtk2 source code and build gtk2 from source and use the gtk2 option

Re: UCRT compile error

On Fri, 11 Apr 2025, Henry Garcia wrote: > See the attached text file. This error only pops up when using a MinGW > Compiler when the MinGW compiler is configured to use the UCRT as the > default lib: ./configure --with-default-msvcrt=ucrt. I wonder if this > could be fixed so that a MinGW Compi

Re: Patchlevel 9.1.1253 missing

Hm, a few changes were still marked as changed but were not committed. Fixed it now. Thanks, Chris On Sat, 29 Mar 2025, Tony Mechelynck wrote: > AFAICT patchlevel 9.1.1253 is mentioned neither in src/version.c nor > in .hgtags. I suppose this "weirdness" is due to distraction and can > be left

Re: Commit: patch 9.1.1222: using wrong length for last inserted string

> Hi, > > I would argue that: > > - if (insert->length > 0) > - { > - // remove trailing ESC > - --insert->length; > - if (s[insert->length] == ESC) > - s[insert->length] = NUL; > - } > + if (insert.length > 0 && s[insert.length - 1] == ESC) // remove trailing > ESC > + s[insert.length - 1] = NUL

Re: Commit: patch 9.1.1222: using wrong length for last inserted string

Hi, I would argue that: - if (insert->length > 0) - { - // remove trailing ESC - --insert->length; - if (s[insert->length] == ESC) - s[insert->length] = NUL; - } + if (insert.length > 0 && s[insert.length - 1] == ESC) // remove trailing ESC + s[insert.length - 1] = NUL; return s; still does

Re: Commit: patch 9.1.1212: too many strlen() calls in edit.c

On 17-Mar-2025 14:28, Christ van Willegen wrote: Hi, This looks weird. Why is the length always decremented, but the ESC only conditionally overwritten? I guess the length decrement should be inside the if statement?? Christ van Willegen Hi Christ, Yeah, you're right. -- -- You receiv

Re: Commit: patch 9.1.1212: too many strlen() calls in edit.c

Hi, Op zo 16 mrt 2025 21:00 schreef Christian Brabandt : > patch 9.1.1212: too many strlen() calls in edit.c > > Commit: > https://github.com/vim/vim/commit/34954972c27244a4a1fb4eeeae2aa4e021efd100 > Author: John Marriott > Date: Sun Mar 16 20:49:52 2025 +0100 > > patch 9.1.1212: too many

Re: Commit: patch 9.1.1213: cannot :put while keeping indent

On Mon, 17 Mar 2025, 'John Marriott' via vim_dev wrote: > On 17-Mar-2025 07:30, Christian Brabandt wrote: > > patch 9.1.1213: cannot :put while keeping indent > > > > Commit:https://github.com/vim/vim/commit/250739d442b51ba76589d6eb67672d95645527ec > > Author: 64-bitman<60551350+64-bit...@users

Re: Commit: patch 9.1.1213: cannot :put while keeping indent

On 17-Mar-2025 07:30, Christian Brabandt wrote: patch 9.1.1213: cannot :put while keeping indent Commit:https://github.com/vim/vim/commit/250739d442b51ba76589d6eb67672d95645527ec Author: 64-bitman<60551350+64-bit...@users.noreply.github.com> Date: Sun Mar 16 21:10:47 2025 +0100 patch 9.1

Re: [vim/vim] Rotating mouse wheel moves cursor when mouse= (Issue #16905)

On 2025-03-16, Daniel Steinberg (Vim Github Repository) wrote: > Steps to reproduce > > vim --clean > :set mouse= > :help builtin.txt > " Rotate the mouse wheel down > > Expected behaviour > > I expected that with mouse=, Vim would ignore mouse wheel events. > > Rather, the cursor moves in the

Re: Commit: patch 9.1.1204: MS-Windows: crash when passing long string to expand()

On Sun, 16 Mar 2025, 'John Marriott' via vim_dev wrote: > After this patch, clang (v20.1.0 on Win11 x64) generates this warning: > > clang -c -I. -Iproto -DWIN32 -DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 > -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -D__USE_MINGW_ANSI_STDIO -pipe > -Wall -O3 -fomi

Re: Commit: patch 9.1.1204: MS-Windows: crash when passing long string to expand()

On 15-Mar-2025 20:00, Christian Brabandt wrote: patch 9.1.1204: MS-Windows: crash when passing long string to expand() Commit:https://github.com/vim/vim/commit/00a749bd90e6b84e7e5132691d73fe9aa3fdff05 Author: zeertzjq Date: Sat Mar 15 09:53:32 2025 +0100 patch 9.1.1204: MS-Windows: crash

Commit: runtime(syntax-tests): Re-introduce support for "phoney" languages

runtime(syntax-tests): Re-introduce support for "phoney" languages Commit: https://github.com/vim/vim/commit/6852e5c597b5c7c42ffc73679cfee7746652cdc6 Author: Aliaksei Budavei <0x000...@gmail.com> Date: Fri Mar 7 19:12:45 2025 +0100 runtime(syntax-tests): Re-introduce sup

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

Hello Maxim, On 2025-03-06 23:45, Maxim Kim wrote: It would also need an entry in a doc, right? Like in :h g:markdown_minlines Indeed, and I sent yesterday another patch (as an attachment to a reply in this thread) that adds a brief description of the rst_minlines variable to the documentation

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

Hello Marshall, On 2025-03-07 13:21, Marshall Ward wrote: Dragan, I have added your patch to the development PR. Thanks very much for noting this issue. Great, thanks a lot! Several outstanding highlight issues have discouraged me from sending any updates - including some that may have prom

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

Dragan, I have added your patch to the development PR. Thanks very much for noting this issue. Several outstanding highlight issues have discouraged me from sending any updates - including some that may have prompted the change to minlines - but I have started to work on this again and I hope

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

On 2025-03-06 23:06, 'Dragan Simic' via vim_dev wrote: Hello Christian, On 2025-03-06 22:45, Christian Brabandt wrote: On Thu, 06 Mar 2025, 'Dragan Simic' via vim_dev wrote: Following the approach used in other syntax definitions, add support for defining the "syntax sync minlines=..." values

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

On Thu, 06 Mar 2025, Maxim Kim wrote: > It would also need an entry in a doc, right? Like in :h g:markdown_minlines Yes it would and I mentioned it in the PR I created. Unfortunately, the upstream repo doesn't contain docs, so we will have to add it once it is synced back with the Vim repo.

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

It would also need an entry in a doc, right? Like in :h g:markdown_minlines On Friday, March 7, 2025 at 9:17:56 AM UTC+11 Dragan Simic wrote: > Hello Christian, > > On 2025-03-06 22:45, Christian Brabandt wrote: > > On Thu, 06 Mar 2025, 'Dragan Simic' via vim_dev wrote: > > > >> Following the ap

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

Hello Christian, On 2025-03-06 22:45, Christian Brabandt wrote: On Thu, 06 Mar 2025, 'Dragan Simic' via vim_dev wrote: Following the approach used in other syntax definitions, add support for defining the "syntax sync minlines=..." values for rst files in the users' ~/.vimrc files, to allow

Re: [PATCH] runtime(rst): Add support for rst_minlines variable

On Thu, 06 Mar 2025, 'Dragan Simic' via vim_dev wrote: > Following the approach used in other syntax definitions, add support for > defining the "syntax sync minlines=..." values for rst files in the users' > ~/.vimrc files, to allow the users to adjust that value in case syntax > highlighting s

Re: vim9script variable is garbage collected when it shouldn't be?

Sorry for the noise, I realized I need to add "noclear" to the vim9script command. On Wednesday, March 5, 2025 at 11:52:28 AM UTC-7 Christian J. Robinson wrote: > Foo.vim: > > vim9script > > export class Foo > def new() > enddef > def Bar(s: string) >

Re: Commit: patch 9.1.1162: completion popup not cleared in cmdline

On 02-Mar-2025 02:30, Christian Brabandt wrote: patch 9.1.1162: completion popup not cleared in cmdline Commit:https://github.com/vim/vim/commit/ff159253eb55fa881e1fcfc45f1de5d73d15bdd4 Author: glepnir Date: Sat Mar 1 16:17:00 2025 +0100 patch 9.1.1162: completion popup not cleared in cm

Re: [PATCH] Update Erlang syntax for recent language changes

On Thu, 27 Feb 2025, 'Johannes Christ' via vim_dev wrote: > Good morning, > > thank you for the info! I thought it's developed in here. > I have a GitHub account, but thank you for the kind offer :-) I will PR it > there. Perfect. Thank you! Thanks, Christian -- court, n.: A place wh

  1   2   3   4   5   6   7   8   9   10   >