Commit: runtime(misc): Use consistent "Vim script" spelling

runtime(misc): Use consistent "Vim script" spelling Commit: https://github.com/vim/vim/commit/a4205471adae39c80fb7f151a4f33051fcb80001 Author: h-east Date: Sun Oct 13 19:16:42 2024 +0200 runtime(misc): Use consistent "Vim script" spelling References: https:/

Re: [vim/vim] `writefile`: optionally update the corresponding buffer's `mtime` (PR #15857)

, update that > buffer's > +modified time so future writes to the buffer don't think > there's > +changes outside of vim. there's -> there have been Regards, Gary -- -- You received this message from the &quo

Re: [vim/vim] Update style guides and add formatter (PR #15789)

On 2024-10-08, Christian Brabandt wrote: > I tend to be sympathetic to those changes and getting rid of tabs is a good > change in my opinion (although we lose some alignments). I leave this open for > a few days, but will probably merge it, unless other maintainers strongly > disagree. I don't se

Commit: runtime(vim): Update base-syntax file, improve class, enum and interface highlighting

runtime(vim): Update base-syntax file, improve class, enum and interface highlighting Commit: https://github.com/vim/vim/commit/818c641b6fac73b574a2b760213f515cee9a3c8e Author: Doug Kearns Date: Sun Oct 6 17:00:48 2024 +0200 runtime(vim): Update base-syntax file, improve class, enum and

Re: [vim/vim] Fix style and typo in documents (PR #15801)

On 2024-10-04, zeertzjq wrote: > @zeertzjq commented on this pull request. > > --- > > In runtime/doc/starting.txt: > > > @@ -972,9 +973,9 @@ accordingly. Vim proceeds in this order: >

Re: [vim/vim] ignorecase gets set globally when editing ada file (Issue #15772)

On 2024-10-03, Martin Krischik wrote: > BTW it seems your current version has the same problem (setting > ignorecase, > which should be a user setting) > > But Ada is an ignore case language so that would be annoying for ada > programmer. It would be helpful, especially for those who use

Re: [vim/vim] In .vimrc, how to tell if gvim is under git 3way merge or not? (Discussion #15785)

On 2024-10-02, flyingosprey wrote: > On Windows, I ran > > git config --global --replace-all merge.tool gvimdiff > git config --global --replace-all mergetool.gvimdiff.path "C:/Program > Files/Vim > /vim90/gvim.exe" > git config --global --replace-all mergetool.gvi

Re: [vim/vim] Vim file-save strategy breaks file-watching applications (Issue #15733)

You both make good arguments. This may be worth an exception after all. Regards, Gary -- -- 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

Re: [vim/vim] Vim file-save strategy breaks file-watching applications (Issue #15733)

On 2024-09-24, Nir Lichtman wrote: > Very interesting, I actually noticed this behavior a couple of days ago and I > wasn't sure why it specifically occurred with Vim, but this clears it up. > > Opened a PR to address this issue by changing the default value of bkc: #15739 If

Commit: runtime(vim): Update base-syntax, improve folding function matches

runtime(vim): Update base-syntax, improve folding function matches Commit: https://github.com/vim/vim/commit/35699f17497dcdcfdd747fedaef28f208ac6eb5f Author: Doug Kearns Date: Thu Sep 19 19:51:59 2024 +0200 runtime(vim): Update base-syntax, improve folding function matches

Commit: runtime(vim): Update base-syntax, match Vim9 bool/null literal args to :if/:while/:return

runtime(vim): Update base-syntax, match Vim9 bool/null literal args to :if/:while/:return Commit: https://github.com/vim/vim/commit/4d427d4cab9c942d6871c50f714e18d7edcfe135 Author: Doug Kearns Date: Sun Sep 15 19:21:18 2024 +0200 runtime(vim): Update base-syntax, match Vim9 bool/null

Commit: patch 9.1.0718: hard to know the users personal Vim Runtime Directory

patch 9.1.0718: hard to know the users personal Vim Runtime Directory Commit: https://github.com/vim/vim/commit/4e7249a916bb6bb4be7e113b60381e4284ee574a Author: Christian Brabandt Date: Thu Sep 5 17:46:19 2024 +0200 patch 9.1.0718: hard to know the users personal Vim Runtime Directory

Commit: runtime(vim): Update syntax, improve user-command matching

runtime(vim): Update syntax, improve user-command matching Commit: https://github.com/vim/vim/commit/3c07eb0c6730c258c6955ce8458cf911245c1617 Author: Doug Kearns Date: Mon Sep 2 10:03:37 2024 +0200 runtime(vim): Update syntax, improve user-command matching - Match -addr and

Commit: runtime(vim): Update base-syntax, match bracket mark ranges

runtime(vim): Update base-syntax, match bracket mark ranges Commit: https://github.com/vim/vim/commit/d817609b87fd155e0d71c29ed056effdedbd7ee0 Author: Doug Kearns Date: Sat Aug 31 16:57:32 2024 +0200 runtime(vim): Update base-syntax, match bracket mark ranges Match

Re: gui_xim.c included even in Vim without GUI — is this normal ?

On Mo, 26 Aug 2024, Tony Mechelynck wrote: > P.S. My keymaps work but the X11 dead keys present on my Belgian > keyboard don't. I'll have to re-enable XIM. I never use those, so I cannot say more about it. But I tried to disable gui_xim.c but the Makefile will always compile it, even if it is

Re: gui_xim.c included even in Vim without GUI — is this normal ?

On Mon, Aug 26, 2024 at 3:15 AM Tony Mechelynck wrote: > > On Sat, Aug 24, 2024 at 4:24 PM Christian Brabandt wrote: > > > > > > On Fr, 23 Aug 2024, Tony Mechelynck wrote: > > > > > Hello, I just noticed that the module gui_xim.c is included even in >

Re: gui_xim.c included even in Vim without GUI — is this normal ?

On Sat, Aug 24, 2024 at 4:24 PM Christian Brabandt wrote: > > > On Fr, 23 Aug 2024, Tony Mechelynck wrote: > > > Hello, I just noticed that the module gui_xim.c is included even in > > Vim without GUI, where AFAICT no other GUI module is compiled-in. Is > > this

Re: gui_xim.c included even in Vim without GUI — is this normal ?

On Fr, 23 Aug 2024, Tony Mechelynck wrote: > Hello, I just noticed that the module gui_xim.c is included even in > Vim without GUI, where AFAICT no other GUI module is compiled-in. Is > this normal ? It seems this is mainly for 'imactivatefunc' and for switching the input

gui_xim.c included even in Vim without GUI — is this normal ?

Hello, I just noticed that the module gui_xim.c is included even in Vim without GUI, where AFAICT no other GUI module is compiled-in. Is this normal ? Here is the configuration for my Tiny build without GUI (the src/Makefile is unchanged from the distribution and the src/shadow-tiny/Makefile

Commit: runtime(vim): Update base-syntax, match :loadkeymap after colon and bar

runtime(vim): Update base-syntax, match :loadkeymap after colon and bar Commit: https://github.com/vim/vim/commit/7866d54ecc7ff47d5f3c48bc389dfd85759b9b65 Author: Doug Kearns Date: Fri Aug 23 18:37:55 2024 +0200 runtime(vim): Update base-syntax, match :loadkeymap after colon and bar

Commit: runtime(vim): Update base-syntax, improve :let-heredoc highlighting

runtime(vim): Update base-syntax, improve :let-heredoc highlighting Commit: https://github.com/vim/vim/commit/7884cc74188caea6e42b1456ed90c8a7189dda7c Author: Doug Kearns Date: Fri Aug 23 18:01:35 2024 +0200 runtime(vim): Update base-syntax, improve :let-heredoc highlighting The

Commit: runtime(vim): Improve heredoc handling for all embedded scripts

runtime(vim): Improve heredoc handling for all embedded scripts Commit: https://github.com/vim/vim/commit/95e90781a4c92b7b061213cfa38b35bdbf719cc1 Author: Ken Takata Date: Thu Aug 22 21:29:39 2024 +0200 runtime(vim): Improve heredoc handling for all embedded scripts * Improve

Re: [vim/vim] translation(it): update Italian manpages (a4aa975)

Hi Ken, Thanks for the report, I will try to catch and correct them all. Antonio Il giorno mar 20 ago 2024 alle ore 09:01 K.Takata ha scritto: > Same as above. > > — > Reply to this email directly, view it on GitHub > <https://github.com/vim/vim/commit/a4aa97590b5bb29088336c

Commit: runtime(vim): Update base-syntax, improve :let-heredoc highlighting

runtime(vim): Update base-syntax, improve :let-heredoc highlighting Commit: https://github.com/vim/vim/commit/d164f2a521f8e52e587727657fb1c19e9a25f32a Author: Doug Kearns Date: Fri Aug 16 21:07:15 2024 +0200 runtime(vim): Update base-syntax, improve :let-heredoc highlighting The

it had to be 9.1.669 -- my current functioning vim is 9.1.668 -- i was afraid i was going to have to do some git voodoo to find out

-- -- 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 Google Groups "vim_dev" group. To unsu

Commit: patch 9.1.0664: MS-Windows: console vim did not switch back to main screen on exit

patch 9.1.0664: MS-Windows: console vim did not switch back to main screen on exit Commit: https://github.com/vim/vim/commit/568cbc92a6637ef9272490fb0361adb73f158cfc Author: Ken Takata Date: Wed Aug 7 21:18:24 2024 +0200 patch 9.1.0664: MS-Windows: console vim did not switch back to

Commit: runtime(zip): zip plugin does not work with Vim 9.0

runtime(zip): zip plugin does not work with Vim 9.0 Commit: https://github.com/vim/vim/commit/e2d9b0d499d0504ba0e935024daf1cfa12e349c4 Author: Christian Brabandt Date: Wed Aug 7 08:13:32 2024 +0200 runtime(zip): zip plugin does not work with Vim 9.0 Problem: zip plugin does not

Commit: runtime(zip): raise minimum Vim version to v9.0

runtime(zip): raise minimum Vim version to v9.0 Commit: https://github.com/vim/vim/commit/e1044fb72edfc5d1a49d11e887521ce8900a99a5 Author: Christian Brabandt Date: Mon Aug 5 21:16:11 2024 +0200 runtime(zip): raise minimum Vim version to v9.0 Problem: the zip plugin uses

Commit: runtime(vim): Update base-syntax, improve :set highlighting

runtime(vim): Update base-syntax, improve :set highlighting Commit: https://github.com/vim/vim/commit/ddbb6fe2d0344e93436c5602b7a06169f49a9b52 Author: Doug Kearns Date: Wed Jul 24 20:21:22 2024 +0200 runtime(vim): Update base-syntax, improve :set highlighting - Match bang, &quo

Re: [vim/vim] Can't disable line wrapping in terminal window output (#5769)

a optional filter between the pseudo terminal master side and the reading end of vim. A non-buffering filter like "dd bs=1" would solve the problem. On Saturday, March 30, 2024 at 2:36:31 AM UTC-7 hhx20120607 wrote: > Sadly the problem still exists after nearly 4 years. > >

Re: [vim/vim] `vim` appears to hang with "Press ENTER or type command to continue" (Issue #15300)

product quality and code quality if such particular PR. -- shane.xb.qian -- -- 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

Commit: runtime(vim): Cleanup :match and :loadkeymap syntax test files

runtime(vim): Cleanup :match and :loadkeymap syntax test files Commit: https://github.com/vim/vim/commit/080ba2c69dbb44319e32a3f9370480e1598b21df Author: Doug Kearns Date: Wed Jul 17 19:35:02 2024 +0200 runtime(vim): Cleanup :match and :loadkeymap syntax test files Remove

Re: [SOLVED] Connection timeout on http://hg.256bit.org/vim

On Sa, 13 Jul 2024, Tony Mechelynck wrote: > On Sat, Jul 13, 2024 at 5:03 AM Tony Mechelynck > wrote: > > > > hg in || echo "exit status" $? ; date > > abort: error: Connection timed out > > exit status 255 > > Sat 13 Jul 04:51:13 CEST 2024 > > > > Best regards, > > Tony. > > Works for me now

[SOLVED] Connection timeout on http://hg.256bit.org/vim

On Sat, Jul 13, 2024 at 5:03 AM Tony Mechelynck wrote: > > hg in || echo "exit status" $? ; date > abort: error: Connection timed out > exit status 255 > Sat 13 Jul 04:51:13 CEST 2024 > > Best regards, > Tony. Works for me now (13:06 CEST) Best regards, Tony. -- -- You received this message f

Connection timeout on http://hg.256bit.org/vim

hg in || echo "exit status" $? ; date abort: error: Connection timed out exit status 255 Sat 13 Jul 04:51:13 CEST 2024 Best regards, Tony. -- -- 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, visi

Re: [vim/vim] Segmentation fault on Mac after `set window&` (Issue #15233)

Please verify using latest master. Thanks Chris -- -- 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 subscribe

Commit: runtime(vim): make &indentexpr available from the outside

runtime(vim): make &indentexpr available from the outside Commit: https://github.com/vim/vim/commit/cb7928812e0dffac2750c9b0513915e17dfa116f Author: Christian Brabandt Date: Fri Jul 12 20:02:31 2024 +0200 runtime(vim): make &indentexpr available from the outside close

Commit: patch 9.1.0559: translation of vim scripts can be improved

patch 9.1.0559: translation of vim scripts can be improved Commit: https://github.com/vim/vim/commit/965091001fc131192f0bca49917ed6567cf8f060 Author: RestorerZ Date: Thu Jul 11 21:14:15 2024 +0200 patch 9.1.0559: translation of vim scripts can be improved Problem: translation

Commit: patch 9.1.0547: No way to get the arity of a Vim function

patch 9.1.0547: No way to get the arity of a Vim function Commit: https://github.com/vim/vim/commit/48b7d05a4f88c4326bd5d7a73a523f2d953b3e51 Author: LemonBoy Date: Tue Jul 9 18:24:59 2024 +0200 patch 9.1.0547: No way to get the arity of a Vim function Problem: No way to get the

Re: Increment/decrement broken in tiny Vim builds from 9.1.0172

On Sun, 2024-07-07 at 13:52 -0400, Rob Foehl wrote: > That patch seems to work. As does 9.1.0546.  Thanks! -Rob -- -- 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/maill

Commit: patch 9.1.0546: vim-tiny fails on CTRL-X/CTRL-A

patch 9.1.0546: vim-tiny fails on CTRL-X/CTRL-A Commit: https://github.com/vim/vim/commit/03acd4761be1c2766d3ec17534ea63cdf8dd565d Author: Christian Brabandt Date: Mon Jul 8 21:12:55 2024 +0200 patch 9.1.0546: vim-tiny fails on CTRL-X/CTRL-A Problem: vim-tiny fails on CTRL-X

Commit: runtime(vim): Update base-syntax, improve :match command highlighting

runtime(vim): Update base-syntax, improve :match command highlighting Commit: https://github.com/vim/vim/commit/e85fdc730e2a538db9af72a255207aa3d5f3fafc Author: Doug Kearns Date: Sun Jul 7 20:45:37 2024 +0200 runtime(vim): Update base-syntax, improve :match command highlighting

Commit: patch 9.1.0541: failing test with Vim configured without channel

patch 9.1.0541: failing test with Vim configured without channel Commit: https://github.com/vim/vim/commit/52123879c0c64c64ca6071192a9f8eacd822efd1 Author: Dominique Pellé Date: Sun Jul 7 20:37:12 2024 +0200 patch 9.1.0541: failing test with Vim configured without channel

Re: Increment/decrement broken in tiny Vim builds from 9.1.0172

eated > https://github.com/vim/vim/pull/15178 as a fix. Thanks, that'd have taken me a while :) That patch seems to work. -Rob -- -- 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

Re: Increment/decrement broken in tiny Vim builds from 9.1.0172

On So, 07 Jul 2024, Rob Foehl wrote: > I'd noticed a while ago that increment/decrement (CTRL-A/CTRL-X, of > course) in Fedora-packaged vim-minimal binaries -- essentially tiny > builds -- started producing odd results, e.g. a file containing '1234' > on the firs

Increment/decrement broken in tiny Vim builds from 9.1.0172

I'd noticed a while ago that increment/decrement (CTRL-A/CTRL-X, of course) in Fedora-packaged vim-minimal binaries -- essentially tiny builds -- started producing odd results, e.g. a file containing '1234' on the first/only line looks like this after CTRL-A anywhere in that li

Commit: patch 9.1.0527: inconsistent parameter in Makefiles for Vim executable

patch 9.1.0527: inconsistent parameter in Makefiles for Vim executable Commit: https://github.com/vim/vim/commit/cd33faf6147d3209b7811c1ecb68519375b9e982 Author: RestorerZ Date: Thu Jul 4 17:47:16 2024 +0200 patch 9.1.0527: inconsistent parameter in Makefiles for Vim executable

Re: [vim/vim] (Try to) gracefully handle out-of-memory in bindtextdomain(). (PR #15116)

Op wo 3 jul. 2024 13:06 schreef zeertzjq : > Build failure on macos-14 > Is the return type on OS-14 different? It gives me a ... weird error. Expression expected?? The other uses of the function don't check the return value, so I can't see how it "should" be done. I propose we don't check the

Re: [vim/vim] Sudo vi/vim read-only files can be edited and forcibly saved! How to disable forced savings. (Issue #15126)

You can’t lock down Vim if you give it super user permissions, which you’re doing here. Use sudoedit instead. -- Christian J. RobinsonOn Jun 29, 2024, at 3:24 AM, wangchao732 wrote: Steps to reproduce sudo vim /etc/sudoers wq! Expected behaviour sudo cat /etc/sudoers|grep prometheus prometheus

Commit: runtime(vim): Update base-syntax, fix function tail comments

runtime(vim): Update base-syntax, fix function tail comments Commit: https://github.com/vim/vim/commit/fc64ac0be2c4f9446798de4d66b029526d1afa85 Author: Doug Kearns Date: Sat Jun 22 11:20:36 2024 +0200 runtime(vim): Update base-syntax, fix function tail comments Match Vim9-script

Commit: patch 9.1.0509: not possible to translate Vim script messages

patch 9.1.0509: not possible to translate Vim script messages Commit: https://github.com/vim/vim/commit/ce0ef910df837b9b961f007a0a35064cad85188b Author: Christ van Willegen Date: Thu Jun 20 23:41:59 2024 +0200 patch 9.1.0509: not possible to translate Vim script messages Problem

Re: [vim/vim] Implement lstat() for Windows (PR #15014)

On 2024-06-17, Christian Brabandt wrote: > If that is the case, I am fine with skipping. But I don't know how to detect > that Vim is running in a Mingw/Msys environment. My MINGW64 installation has a couple of environment variables that you could test. MSYSTEM=MINGW64

Commit: runtime(doc): improve the vim-shebang example

runtime(doc): improve the vim-shebang example Commit: https://github.com/vim/vim/commit/ca471145321fa8089071330b7637ad3950ac4f11 Author: Christian Brabandt Date: Mon Jun 17 13:06:34 2024 +0200 runtime(doc): improve the vim-shebang example Signed-off-by: Christian Brabandt diff

Commit: patch 9.1.0492: filetype: Vim-script files not detected by shebang line

patch 9.1.0492: filetype: Vim-script files not detected by shebang line Commit: https://github.com/vim/vim/commit/0d4d23dac0a5a77ccb0ebf1dcf646afe0c6886bf Author: Doug Kearns Date: Sun Jun 16 08:32:15 2024 +0200 patch 9.1.0492: filetype: Vim-script files not detected by shebang line

Commit: runtime(doc): add another tag for vim-shebang feature

runtime(doc): add another tag for vim-shebang feature Commit: https://github.com/vim/vim/commit/f4bc59c4f67786e967db48e944c2cce2c0da8dc1 Author: Christian Brabandt Date: Sat Jun 15 15:52:53 2024 +0200 runtime(doc): add another tag for vim-shebang feature related: https

Commit: runtime(vim): Update base-syntax, match shebang lines (#15011)

runtime(vim): Update base-syntax, match shebang lines (#15011) Commit: https://github.com/vim/vim/commit/ae321b51f7531b23545d64c3a98ed991a31dd5ee Author: dkearns Date: Sat Jun 15 23:06:17 2024 +1000 runtime(vim): Update base-syntax, match shebang lines (https://github.com/vim/vim/issues

Commit: runtime(vim): Update base-syntax, match :sleep arg

runtime(vim): Update base-syntax, match :sleep arg Commit: https://github.com/vim/vim/commit/262e25e5a10438770dc9e23e0d5ffcb116f05d0f Author: Doug Kearns Date: Fri Jun 14 20:16:35 2024 +0200 runtime(vim): Update base-syntax, match :sleep arg Match :sleep arg properly including a

Commit: runtime(vim): Update base-syntax, match :catch and :throw args (#14989)

runtime(vim): Update base-syntax, match :catch and :throw args (#14989) Commit: https://github.com/vim/vim/commit/a3bddb759e77c52431a93a68674790dd02647cd1 Author: dkearns Date: Fri Jun 14 01:48:10 2024 +1000 runtime(vim): Update base-syntax, match :catch and :throw args (https

Commit: runtime(vim): Update g:vimsyn_comment_strings dump file tests

runtime(vim): Update g:vimsyn_comment_strings dump file tests Commit: https://github.com/vim/vim/commit/31441d509aa01f3dadb874f45eae4246363e831c Author: Doug Kearns Date: Wed Jun 12 20:44:10 2024 +0200 runtime(vim): Update g:vimsyn_comment_strings dump file tests Leading

Commit: runtime(vim): Update base-syntax, configurable comment string highlighting (#14931)

runtime(vim): Update base-syntax, configurable comment string highlighting (#14931) Commit: https://github.com/vim/vim/commit/959c3c887b2e52c7141b2a09a53634481911b1b7 Author: dkearns Date: Wed Jun 12 04:18:08 2024 +1000 runtime(vim): Update base-syntax, configurable comment string

Commit: runtime(vim): Update base-syntax, match multiline continued comments (#13936)

runtime(vim): Update base-syntax, match multiline continued comments (#13936) Commit: https://github.com/vim/vim/commit/059cbe8933550e4f2b10ab564fb4398e95280198 Author: dkearns Date: Wed Jun 12 03:27:53 2024 +1000 runtime(vim): Update base-syntax, match multiline continued comments

Commit: runtime(vim): Remove orphaned screen dump files (#14965)

runtime(vim): Remove orphaned screen dump files (#14965) Commit: https://github.com/vim/vim/commit/6ea3dfe8de8571ef16909bb605b8b599d9eff6f2 Author: dkearns Date: Wed Jun 12 03:04:46 2024 +1000 runtime(vim): Remove orphaned screen dump files (https://github.com/vim/vim/issues/14965

Re: [vim/vim] Make indentexpr evaluate from older vim scripts (PR #14936)

On Sun, Jun 9, 2024 at 9:52 AM Christian Brabandt wrote: > Hm, I suppose if we make this change, we also don't need the import > statement anymore. @yegappan @dkearns > what is your opinion on this? > > > If there is a need to support usi

Re: [vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)

not manually open it (or enabled the option of auto, but i > supposed you would not do so), > it should be not impact your other windows e.g source and gdb window. > // please check the code _before_ https://github.com/vim/vim/pull/14903 > that vim9 convert, > // or after that convert, bu

Commit: runtime(doc): Added definitions of Vim scripts and plugins

runtime(doc): Added definitions of Vim scripts and plugins Commit: https://github.com/vim/vim/commit/c593b9ead9b4346724187ab604fa593ead1fa4b2 Author: Ubaldo Tiberi Date: Sun Jun 9 18:47:53 2024 +0200 runtime(doc): Added definitions of Vim scripts and plugins closes: https

Re: [vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)

= {} let g:termdebug_config['wide'] = 164 With the above setting, when I run the ":Termdebug ./vim" command from the Vim src directory, I used to get a window layout with two vertically split windows. The left window is horizontally split into two windows with GDB in the top

Re: [vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)

t; The change in window layout is not caused by the Vim9 script conversion. This is caused by the changes made in https://github.com/vim/vim/commit/ca48202b6f46cfb40a0d1d80033a2f3e8cb7b813. Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-

Re: [vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)

On Sat, Jun 8, 2024 at 9:18 AM Shane-XB-Qian wrote: > i meant the vim9 convert, > as for the layout #13474 (comment) > <https://github.com/vim/vim/pull/13474#issuecomment-1790687647> had > explained it. > > > What was the problem the layout change was trying to addr

Commit: translation(it): Update Italian Vim manpage

translation(it): Update Italian Vim manpage Commit: https://github.com/vim/vim/commit/4032daaa11f090421a417af7dfe962960c1aa97f Author: Antonio Giovanni Colombo Date: Fri Jun 7 13:31:01 2024 +0200 translation(it): Update Italian Vim manpage Signed-off-by: Antonio Giovanni Colombo

Commit: runtime(vim): Update base-syntax, allow whitespace before :substitute pattern

runtime(vim): Update base-syntax, allow whitespace before :substitute pattern Commit: https://github.com/vim/vim/commit/92f4e915908962da2c1969a8d60f1563e06ee00e Author: Doug Kearns Date: Wed Jun 5 19:45:43 2024 +0200 runtime(vim): Update base-syntax, allow whitespace before :substitute

Commit: runtime(man): update Vim manpage

runtime(man): update Vim manpage Commit: https://github.com/vim/vim/commit/ce6fe84db21f00fd30b226200dbb02709514871a Author: Christian Brabandt Date: Tue Jun 4 21:58:32 2024 +0200 runtime(man): update Vim manpage fixes: https://github.com/vim/vim/issues/14916 Signed-off

Re: [vim/vim] .wq! Deletes All data except the line where the cursor is located. (Issue #14892)

Op za 1 jun. 2024 11:58: > >1. Position the cursor on any line and type the following command: > >:.wq! > > > I guess that the . indicates the range of lines to write, the current one... Christ van Willegen > -- -- You received this message from the "vim_dev" maillist. Do not top-post

Re: [vim/vim] Why vim search exclude the letter in current cursor? (Discussion #14871)

rst line，and then I > using "/" to search target words: "www" > when I type "enter" to search，the cursor jump to the first "w" in second line > I think vim will scan word from current letter(not jump to next "www"), but > vim > will

Re: [vim/vim] Update defaults.vim (Issue #14853)

Forcing defaults.vim to always load is not a good idea. I have used Vim since version 3 . The only time I was really upset by an incompatible change was when version 7.4. introduced defaults.vim Ajit On Wednesday, May 29, 2024 at 9:17:55 AM UTC-3 vim-dev ML wrote: > * James Mc

Commit: runtime(vim): re-generate vim syntax from generator

runtime(vim): re-generate vim syntax from generator Commit: https://github.com/vim/vim/commit/393708cff6f92ee34b450b054dfdb73a65f5bcf7 Author: Christian Brabandt Date: Mon May 27 15:50:07 2024 +0200 runtime(vim): re-generate vim syntax from generator related: https://github.com

Commit: runtime(vim): fix syntax vim bug (Close #14858) (#14861)

runtime(vim): fix syntax vim bug (Close #14858) (#14861) Commit: https://github.com/vim/vim/commit/c984b2fd9ddd4107006a698fe81ad7ae22208620 Author: h_east Date: Mon May 27 22:40:25 2024 +0900 runtime(vim): fix syntax vim bug (Close https://github.com/vim/vim/issues/14858) (https

Re: [vim/vim] feat(runtime)!: add padding to commentstrings (PR #14843)

I am fine with the changes in general, and in particular to the fortran ftplugin. It might indeed be a good time for the ftplugin files to be maintained by the Vim Project. On Saturday, May 25, 2024 at 8:18:12 AM UTC-3 dkearns wrote: I generally favour this style and would also prefer

Re: [vim/vim] Refactor to remove STRLEN() part 6 (PR #14796)

On 21-May-2024 09:57, zeertzjq (Vim Github Repository) wrote: *@zeertzjq* commented on this pull request. In src/tag.c <https://github.com/vim/vim/pull/14796#discussion_r1607414

Re: [vim/vim] Make command-line execute vim9script without typing vim9cmd (Issue #14785)

> even if the command line provided better support for Vim 9 script (e.g., > limited editing possibilities). > > Regarding the scratch buffer: what if you want to step? Shall you define > buffer local mappings? > > You may certainly do that (you may even do it in your current V

Re: [vim/vim] Please consider switching to the XDG runtime when no vimrc exists but ~/.config/vim does (Issue #14766)

On 2024-05-13, Diego Viola wrote: > Please consider doing a runtime switch to the XDG one when a ~/.config/vim > directory exists. > > Currently the runtime switch happens when ~/.config/vim/vimrc exists, and > that's fine. > > However, while testing #14757 yesterday, I

Re: [vim/vim] Setting 'showbreak' affects the reported virtual column number in the status line. (Issue #14759)

r. Note that the > status line reports "1012". > > Expected behaviour > > The status line should report "1000". > > Version of Vim > > 9.1.296. > > Environment > > OS: Windows 10 Home. > Terminal: GUI. The number 1012 is corr

Commit: runtime(java): Strive to remain compatible for at least Vim 7.0 (#14744)

runtime(java): Strive to remain compatible for at least Vim 7.0 (#14744) Commit: https://github.com/vim/vim/commit/d3952e8cfe7baed1ff5c8111da5272a038cb55e4 Author: Aliaksei Budavei <32549825+zzzyxw...@users.noreply.github.com> Date: Sat May 11 00:39:31 2024 +0300 runtime(java): Str

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 > <https://github.com/vim/vim/issues/2955#issuecomment-392202171> > '<,'>cgetbuffer does no longer work. It seems at least the follo

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

Hi, Op vr 26 apr. 2024 00:37 schreef Ilan Schemoul : > Version of Vim > > VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 14 2024 09:05:11) > Included patches: 1-579, 1969, 580-1848, 4975, 5016, 5023, 5072, 2068, > 1849-1854, 1857, 1855-1857, 1331, 1858, 1858-1859, 1873, 1860-196

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 thi

Commit: patch 9.1.0368: MS-Windows: Hard to define the Vim Patchlevel with leading zeroes

patch 9.1.0368: MS-Windows: Hard to define the Vim Patchlevel with leading zeroes Commit: https://github.com/vim/vim/commit/dc5cd1cac1a8b25b6259f2b0a7a071f7b840e730 Author: RestorerZ Date: Tue Apr 23 20:33:38 2024 +0200 patch 9.1.0368: MS-Windows: Hard to define the Vim Patchlevel with

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 and

Commit: runtime(vim): Update base-syntax, fix nested function folding (#14397)

runtime(vim): Update base-syntax, fix nested function folding (#14397) Commit: https://github.com/vim/vim/commit/4ba70cab37d2a625d8c59bb136070ef9d1976934 Author: dkearns Date: Mon Apr 15 04:32:56 2024 +1000 runtime(vim): Update base-syntax, fix nested function folding (https

Commit: runtime(vim): don't set compiler, update a comment for vimdoc compiler (#14532)

runtime(vim): don't set compiler, update a comment for vimdoc compiler (#14532) Commit: https://github.com/vim/vim/commit/e92ed1b45c5432235b0541521124d965b9d6a9a2 Author: Shane-XB-Qian Date: Mon Apr 15 02:20:01 2024 +0800 runtime(vim): don't set compiler, update a comment

Commit: runtime(vim): Improve Vim9 and legacy-script comment highlighting (#13104)

runtime(vim): Improve Vim9 and legacy-script comment highlighting (#13104) Commit: https://github.com/vim/vim/commit/04e5363b823827f144409df011376d00ea6df750 Author: dkearns Date: Thu Apr 11 06:18:37 2024 +1000 runtime(vim): Improve Vim9 and legacy-script comment highlighting (https

Commit: runtime(vim): Update base-syntax, no curly-brace names in Vim9 script (#14466)

runtime(vim): Update base-syntax, no curly-brace names in Vim9 script (#14466) Commit: https://github.com/vim/vim/commit/e43ace558aee904f5ebb805daed763961bdbccde Author: dkearns Date: Wed Apr 10 05:19:41 2024 +1000 runtime(vim): Update base-syntax, no curly-brace names in Vim9 script

Commit: runtime(vim): Update syntax generator, autocmd event list parsing

runtime(vim): Update syntax generator, autocmd event list parsing Commit: https://github.com/vim/vim/commit/a44ced5763d377c71c96562b894c1c026ba89328 Author: Doug Kearns Date: Sun Apr 7 17:47:15 2024 +0200 runtime(vim): Update syntax generator, autocmd event list parsing Track

Re: [vim/vim] Refactor to remove STRLEN() part 1 (PR #14287)

On 03-Apr-2024 05:03, Christian Brabandt (Vim Github Repository) wrote: Thanks, looks good to me. Did you meaure how much this saves (e.g. startup time)? — Reply to this email directly, view it on GitHub <https://github.com/vim/vim/pull/14287#issuecomment-2032712670>. You are rec

Re: [vim/vim] Documentation of CTRL-D/CTRL-U is no longer accurate (Issue #14338)

On 2024-04-02, Christian Brabandt wrote: > In any case, things are a bit in flow currently and we are not close to a > release. So some potential fallout can be expected. I try not to break > backwards compatibility intentionally, but of course I'd like Vim to be > improved

Commit: runtime(vim): Distinguish Vim9 builtin object methods from namesake builtin functions (#14348)

runtime(vim): Distinguish Vim9 builtin object methods from namesake builtin functions (#14348) Commit: https://github.com/vim/vim/commit/80aabaab6636faa7cec461acc4b1fcc3a4c89376 Author: Aliaksei Budavei <32549825+zzzyxw...@users.noreply.github.com> Date: Sun Mar 31 19:26:32 2024

Re: [vim/vim] If you `:bdelete` from a `'winfixbuf'` window, what should happen? (Issue #14328)

ymore. The situation is similar as with doing :bdelete for a buffer in a tab that has no other window. Vim closes it's window and even removes the whole tab. It does not make the command fail just because there is no . Is there any reason to handle :bdelete of a winfixbuf-ed buffer d

Re: [vim/vim] Documentation of CTRL-D/CTRL-U is no longer accurate (Issue #14338)

On 2024-03-29, luukvbaal wrote: > I can try, but are we making a decision solely for backward compatibility? Or > can we consider which of the two old behaviors makes more sense for scrolling > the viewport. Either the cursor position stays the same and only starts moving > to be at the top/botline

Commit: runtime(vim): Update base-syntax, match empty blob and :abclear modifiers (#14318)

runtime(vim): Update base-syntax, match empty blob and :abclear modifiers (#14318) Commit: https://github.com/vim/vim/commit/982e191b38b493d148d73871a724381214e4c62f Author: dkearns Date: Thu Mar 28 20:06:03 2024 +1100 runtime(vim): Update base-syntax, match empty blob and :abclear

Re: [vim/vim] Unnecessary multiplications in backspace code (PR #14308)

and the comments ins_bs() to be easier to understand. Update > tests to reset 'smarttab' properly. > > You can view, comment on, or merge this pull request online at: > > https://github.com/vim/vim/pull/14308 Did you examine the assembler produced by the compi

Commit: runtime(vim): Update base-syntax, remove old unused syntax groups. (#14146)

runtime(vim): Update base-syntax, remove old unused syntax groups. (#14146) Commit: https://github.com/vim/vim/commit/76d62985c1ffbd7669ccc628ca43445d14c5aba6 Author: dkearns Date: Sat Mar 23 05:55:25 2024 +1100 runtime(vim): Update base-syntax, remove old unused syntax groups. (https

  1   2   3   4   5   6   7   8   9   10   >