Windows: start /MAX gvim - scroll issue
If I run this from a cmd window: start /MAX gvim Then open a large file and use Ctrl-F/Page-Down or Ctrl-B/Page-Up, gvim will scroll by too few lines. This doesn’t seem to be a problem if I just do “gvim” on the command line and then manually maximize the window with my mouse. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/28F619CD-68E6-4503-99F0-B3B23FD2C683%40hxcore.ol.
Patch 8.2.2994
Patch 8.2.2994
Problem:Various code is not fully tested.
Solution: Add a few more tests. (Yegappan Lakshmanan, closes #8378)
Files: src/testdir/test_excmd.vim, src/testdir/test_mapping.vim,
src/testdir/test_modeline.vim, src/testdir/test_options.vim,
src/testdir/test_paste.vim, src/vim9compile.c
*** ../vim-8.2.2993/src/testdir/test_excmd.vim 2021-06-12 13:46:38.055854976
+0200
--- src/testdir/test_excmd.vim 2021-06-13 21:49:44.585715050 +0200
***
*** 596,602
" some options cannot be changed in a sandbox
call assert_fails('set exrc', 'E48:')
call assert_fails('set cdpath', 'E48:')
! if has('xim')
call assert_fails('set imstyle', 'E48:')
endif
endfunc
--- 596,602
" some options cannot be changed in a sandbox
call assert_fails('set exrc', 'E48:')
call assert_fails('set cdpath', 'E48:')
! if has('xim') && has('gui_gtk')
call assert_fails('set imstyle', 'E48:')
endif
endfunc
*** ../vim-8.2.2993/src/testdir/test_mapping.vim2021-04-30
19:43:06.618062735 +0200
--- src/testdir/test_mapping.vim2021-06-13 21:49:44.585715050 +0200
***
*** 485,490
--- 485,495
call assert_equal(['n ,k'],
\ execute('nmap ,k')->trim()->split("\n"))
+ " map with space at the beginning
+ exe "nmap \ w "
+ call assert_equal(['n w '],
+ \ execute("nmap \ w")->trim()->split("\n"))
+
nmapclear
endfunc
***
*** 1411,1414
--- 1416,1434
bwipe!
endfunc
+ " Test for abbreviations with 'latin1' encoding
+ func Test_abbreviate_latin1_encoding()
+ set encoding=latin1
+ call assert_fails('abbr ab#$c ABC', 'E474:')
+ new
+ iabbr #i #include
+ iabbr ## #enddef
+ exe "normal i#i\"
+ call assert_equal('#include', getline(1))
+ exe "normal 0Di##\"
+ call assert_equal('#enddef', getline(1))
+ %bw!
+ set encoding=utf-8
+ endfunc
+
" vim: shiftwidth=2 sts=2 expandtab
*** ../vim-8.2.2993/src/testdir/test_modeline.vim 2020-08-12
18:50:31.883655785 +0200
--- src/testdir/test_modeline.vim 2021-06-13 21:49:44.585715050 +0200
***
*** 334,337
--- 334,363
call delete('Xmodeline')
endfunc
+ " Test for the 'modeline' default value in compatible and non-compatible modes
+ " for root and non-root accounts
+ func Test_modeline_default()
+ set compatible
+ call assert_false()
+ set nocompatible
+ call assert_equal(IsRoot() ? 0 : 1, )
+ set compatible
+ call assert_false()
+ set compatible
+ call assert_equal(IsRoot() ? 0 : 1, )
+ set compatible& modeline&
+ endfunc
+
+ " Some options cannot be set from the modeline when 'diff' option is set
+ func Test_modeline_diff_buffer()
+ call writefile(['vim: diff foldmethod=marker wrap'], 'Xfile')
+ set foldmethod& nowrap
+ new Xfile
+ call assert_equal('manual', )
+ call assert_false()
+ set wrap&
+ call delete('Xfile')
+ bw
+ endfunc
+
" vim: shiftwidth=2 sts=2 expandtab
*** ../vim-8.2.2993/src/testdir/test_options.vim2021-06-13
20:27:32.889357660 +0200
--- src/testdir/test_options.vim2021-06-13 21:49:44.585715050 +0200
***
*** 1160,1163
--- 1160,1180
set cmdheight&
endfunc
+ " To specify a control character as a option value, '^' can be used
+ func Test_opt_control_char()
+ set wildchar=^v
+ call assert_equal("\", nr2char())
+ set wildcharm=^r
+ call assert_equal("\", nr2char())
+ " Bug: This doesn't work for the 'cedit' and 'termwinkey' options
+ set wildchar& wildcharm&
+ endfunc
+
+ " Test for the 'errorbells' option
+ func Test_opt_errorbells()
+ set errorbells
+ call assert_beeps('s/a1b2/x1y2/')
+ set noerrorbells
+ endfunc
+
" vim: shiftwidth=2 sts=2 expandtab
*** ../vim-8.2.2993/src/testdir/test_paste.vim 2021-03-15 18:36:16.725494781
+0100
--- src/testdir/test_paste.vim 2021-06-13 21:49:44.585715050 +0200
***
*** 159,166
--- 159,226
call feedkeys("i\", 'xt')
call assert_false()
call assert_equal('Hello', getline(1))
+ " command-line completion for 'pastetoggle' value
+ call feedkeys(":set pastetoggle=\\\"\", 'xt')
+ call assert_equal('"set pastetoggle=', @:)
set pastetoggle&
bwipe!
endfunc
+ " Test for restoring option values when 'paste' is disabled
+ func Test_paste_opt_restore()
+ set autoindent expandtab ruler showmatch
+ if has('rightleft')
+ set revins hkmap
+ endif
+ set smarttab softtabstop=3 textwidth=27 wrapmargin=12
+ if has('vartabs')
+ set varsofttabstop=10,20
+ endif
+
+ " enabling 'paste' should reset the above options
+ set paste
+ call assert_false()
+ call assert_false()
+ if has('rightleft')
+ call assert_false()
+ call assert_false()
+ endif
+ call assert_false()
+ call assert_false()
+ call assert_false()
+ call assert_equal(0, )
+ call assert_equal(0, )
+ call assert_equal(0, )
Re: Minor updates to help
Yegappan wrote: > On Sun, Jun 13, 2021 at 10:46 AM Christian Brabandt > wrote: > > > > > > On So, 13 Jun 2021, Yegappan Lakshmanan wrote: > > > > > Hi, > > > > > > The help mentions that when 'paste' is set, the 'smartindent' option > > > will be reset. But it currently doesn't work this way. The 'smartindent' > > > option is not disabled when 'paste' is set. I am attaching a minor update > > > to the help text to remove this. > > > > Shouldn't we rather fix the code? so that when paste is in effect, vim > > would not indent lines based on what is pasted. > > > > Yes. I noticed this when adding a test for this. It makes sense to > disable smartindent when 'paste' is set and restore the old value > when 'paste' is disabled. I think 'smartindent' belongs to the second list, options that keep their value but their effect is disabled. 'formatoptions' also belongs in the second list. -- I have read and understood the above. X /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// \\\ \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202106131940.15DJeJBK680146%40masaka.moolenaar.net.
Re: Patch 8.2.2993
On 2021-06-13, Bram Moolenaar wrote: > Patch 8.2.2993 > Problem:'fileencodings' default value should depend on 'encoding'. (Gary > Johnson) > Solution: When 'encoding' is "utf-8" use a different default value for > 'fileencodings'. > Files: src/mbyte.c, src/option.c, src/proto/option.pro, > src/testdir/test_options.vim Thanks! 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 this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613190919.GA18980%40phoenix.
Re: Travis CI no longer triggers
On So, 13 Jun 2021, Christian Brabandt wrote: > > On So, 13 Jun 2021, Marius Gedminas wrote: > > > On Sat, Jun 12, 2021 at 12:54:33PM +0200, Bram Moolenaar wrote: > > > The last patch to have been run on Travis is 8.2.2966. Since then it > > > looks like this CI is no longer picking up patches. Anyone knows why? > > > > Travis CI gives 1 free credits to OSS projects. This is not a > > monthly/yearly amount, it's a one-time donation. Once the credits run > > out, you have to pay, or email Travis and ask for an additional one-time > > donation that starts the cycle anew. > > > > I'm familiar with some organizations maintaining OSS software that have > > emailed Travis to ask for credits and have waited months to get a > > response. Most of them gave up and migrated to alternative CI > > solutions, usually GitHub Actions. > > > > You can check the amount of used and remaining credits after logging in > > to travis-ci.com: > > > > - https://travis-ci.com/account/plan/usage (for personal projects) > > - https://travis-ci.com/organizations/ORGANIZATION/plan/usage (for > > GitHub organizations) > > Yes, looks like we have no more credits available. That info page was > nor really helpful, I couldn't manage to receive any statistics, not > sure what is wrong with that. I think we have only used it for s390 and > arm64 builds, not sure if there are alternatives for this architecture. Oh, I just noticed this also affects the appimage. So we don't have an automatic appimage anymore. *grml* Best, Christian -- In meinem Reich gibt es keine Zensur, sprach der Löwe. Jeder darf das sagen, was ich will. -- Gerhard Branstner -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613185216.GE532641%40256bit.org.
Re: Minor updates to help
On So, 13 Jun 2021, Yegappan Lakshmanan wrote: > Hi Christian, > > On Sun, Jun 13, 2021 at 10:46 AM Christian Brabandt > wrote: > > > > > > On So, 13 Jun 2021, Yegappan Lakshmanan wrote: > > > > > Hi, > > > > > > The help mentions that when 'paste' is set, the 'smartindent' option > > > will be reset. But it currently doesn't work this way. The 'smartindent' > > > option is not disabled when 'paste' is set. I am attaching a minor update > > > to the help text to remove this. > > > > Shouldn't we rather fix the code? so that when paste is in effect, vim > > would not indent lines based on what is pasted. > > > > Yes. I noticed this when adding a test for this. It makes sense to > disable smartindent when 'paste' is set and restore the old value > when 'paste' is disabled. Yeah´, We had a similar issue a couple of years ago with smarttab and expandtab, see (54f018cd5994c3ffcd0740526e56db6934edf1f2 (tag: v7.4.868)) Best, Christian -- Jambus: Bluesmusikerfahrzeug -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613185004.GD532641%40256bit.org.
Re: Travis CI no longer triggers
On So, 13 Jun 2021, Marius Gedminas wrote: > On Sat, Jun 12, 2021 at 12:54:33PM +0200, Bram Moolenaar wrote: > > The last patch to have been run on Travis is 8.2.2966. Since then it > > looks like this CI is no longer picking up patches. Anyone knows why? > > Travis CI gives 1 free credits to OSS projects. This is not a > monthly/yearly amount, it's a one-time donation. Once the credits run > out, you have to pay, or email Travis and ask for an additional one-time > donation that starts the cycle anew. > > I'm familiar with some organizations maintaining OSS software that have > emailed Travis to ask for credits and have waited months to get a > response. Most of them gave up and migrated to alternative CI > solutions, usually GitHub Actions. > > You can check the amount of used and remaining credits after logging in > to travis-ci.com: > > - https://travis-ci.com/account/plan/usage (for personal projects) > - https://travis-ci.com/organizations/ORGANIZATION/plan/usage (for > GitHub organizations) Yes, looks like we have no more credits available. That info page was nor really helpful, I couldn't manage to receive any statistics, not sure what is wrong with that. I think we have only used it for s390 and arm64 builds, not sure if there are alternatives for this architecture. Best, Christian -- DAU kommt und fragt, wo denn der Einschalter für den PC ist. Er bekommt gezeigt, wo er angeht. Ca. eine halbe Stunde später kommt derselbe und fragt, wo die Kiste ausgeschaltet wird. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613184432.GC532641%40256bit.org.
Re: Minor updates to help
Hi Christian, On Sun, Jun 13, 2021 at 10:46 AM Christian Brabandt wrote: > > > On So, 13 Jun 2021, Yegappan Lakshmanan wrote: > > > Hi, > > > > The help mentions that when 'paste' is set, the 'smartindent' option > > will be reset. But it currently doesn't work this way. The 'smartindent' > > option is not disabled when 'paste' is set. I am attaching a minor update > > to the help text to remove this. > > Shouldn't we rather fix the code? so that when paste is in effect, vim > would not indent lines based on what is pasted. > Yes. I noticed this when adding a test for this. It makes sense to disable smartindent when 'paste' is set and restore the old value when 'paste' is disabled. - 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 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3D8DO0g3fk%2B80V-H9woK%3D1JNZSMRKxQwvrSz7hGatjdoA%40mail.gmail.com.
Patch 8.2.2993
Patch 8.2.2993
Problem:'fileencodings' default value should depend on 'encoding'. (Gary
Johnson)
Solution: When 'encoding' is "utf-8" use a different default value for
'fileencodings'.
Files: src/mbyte.c, src/option.c, src/proto/option.pro,
src/testdir/test_options.vim
*** ../vim-8.2.2992/src/mbyte.c 2021-06-04 17:11:44.516100707 +0200
--- src/mbyte.c 2021-06-13 20:14:31.026449788 +0200
***
*** 733,740
// When using Unicode, set default for 'fileencodings'.
if (enc_utf8 && !option_was_set((char_u *)"fencs"))
! set_string_option_direct((char_u *)"fencs", -1,
! (char_u *)"ucs-bom,utf-8,default,latin1", OPT_FREE, 0);
#if defined(HAVE_BIND_TEXTDOMAIN_CODESET) && defined(FEAT_GETTEXT)
// GNU gettext 0.10.37 supports this feature: set the codeset used for
--- 733,739
// When using Unicode, set default for 'fileencodings'.
if (enc_utf8 && !option_was_set((char_u *)"fencs"))
! set_fencs_unicode();
#if defined(HAVE_BIND_TEXTDOMAIN_CODESET) && defined(FEAT_GETTEXT)
// GNU gettext 0.10.37 supports this feature: set the codeset used for
*** ../vim-8.2.2992/src/option.c2021-06-02 13:28:11.435120452 +0200
--- src/option.c2021-06-13 20:20:27.590208534 +0200
***
*** 535,540
--- 535,553
#endif
}
+ static char_u *fencs_utf8_default = (char_u *)"ucs-bom,utf-8,default,latin1";
+
+ /*
+ * Set the "fileencodings" option to the default value for when 'encoding' is
+ * utf-8.
+ */
+ void
+ set_fencs_unicode()
+ {
+ set_string_option_direct((char_u *)"fencs", -1, fencs_utf8_default,
+ OPT_FREE, 0);
+ }
+
/*
* Set an option to its default value.
* This does not take care of side effects!
***
*** 558,566
dvi = ((flags & P_VI_DEF) || compatible) ? VI_DEFAULT : VIM_DEFAULT;
if (flags & P_STRING)
{
// Use set_string_option_direct() for local options to handle
// freeing and allocating the value.
! if (options[opt_idx].indir != PV_NONE)
set_string_option_direct(NULL, opt_idx,
options[opt_idx].def_val[dvi], opt_flags, 0);
else
--- 571,582
dvi = ((flags & P_VI_DEF) || compatible) ? VI_DEFAULT : VIM_DEFAULT;
if (flags & P_STRING)
{
+ // 'fencs' default value depends on 'encoding'
+ if (options[opt_idx].var == (char_u *)_fencs && enc_utf8)
+ set_fencs_unicode();
// Use set_string_option_direct() for local options to handle
// freeing and allocating the value.
! else if (options[opt_idx].indir != PV_NONE)
set_string_option_direct(NULL, opt_idx,
options[opt_idx].def_val[dvi], opt_flags, 0);
else
***
*** 1684,1689
--- 1700,1707
#endif
newval = term_bg_default();
}
+ else if ((char_u **)varp == _fencs && enc_utf8)
+ newval = fencs_utf8_default;
// expand environment variables and ~ (since the
// default value was already expanded, only
*** ../vim-8.2.2992/src/proto/option.pro2020-12-31 17:40:57.536087870
+0100
--- src/proto/option.pro2021-06-13 20:14:34.998450906 +0200
***
*** 1,5
--- 1,6
/* option.c */
void set_init_1(int clean_arg);
+ void set_fencs_unicode(void);
void set_string_default(char *name, char_u *val);
void set_number_default(char *name, long val);
void set_local_options_default(win_T *wp, int do_buffer);
*** ../vim-8.2.2992/src/testdir/test_options.vim2021-06-12
13:46:38.055854976 +0200
--- src/testdir/test_options.vim2021-06-13 20:24:08.813816632 +0200
***
*** 1140,1145
--- 1140,1153
call assert_equal('vt', )
set formatoptions
call assert_equal('tcq', )
+
+ call assert_equal('ucs-bom,utf-8,default,latin1', )
+ set fencs=latin1
+ set fencs&
+ call assert_equal('ucs-bom,utf-8,default,latin1', )
+ set fencs=latin1
+ set all&
+ call assert_equal('ucs-bom,utf-8,default,latin1', )
endfunc
" Test for the 'cmdheight' option
*** ../vim-8.2.2992/src/version.c 2021-06-13 18:38:44.688673497 +0200
--- src/version.c 2021-06-13 20:27:01.789432221 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2993,
/**/
--
BEDEVERE:Why do you think she is a witch?
SECOND VILLAGER: She turned me into a newt.
BEDEVERE:A newt?
SECOND VILLAGER: (After looking at himself for some time) I got better.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES
Re: ":set fileencodings&" does not restore initial value
Gary Johnson wrote: > When starting Vim on a Linux system, 'fileencodings' is set to > "ucs-bom,utf-8,default,latin1". But, after executing > > set fileencodings& > > or > > set all& > > the value changes to "usc-bom" even though the value of 'encoding' > has remained "utf-8". ":help fileencodings" says: > > 'fileencodings' 'fencs' string (default: "ucs-bom", > "ucs-bom,utf-8,default,latin1" when > 'encoding' is set to a Unicode value) > > I think the behavior of ":set fileencodings&" and ":set all&" is > contrary to the documentation and is a bug. > > Example: > > $ vim -N -u NONE -i NONE > :verbose set encoding? fileencodings? > encoding=utf-8 > fileencodings=ucs-bom,utf-8,default,latin1 > :set all& > :verbose set encoding? fileencodings? > encoding=utf-8 > fileencodings=ucs-bom The generic options code only handles a static default value. In this case the default value depends on the 'encoding' option. That requires some extra code to handle the exception. I think it's worth it. -- This computer is so slow, it takes forever to execute and endless loop! /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// \\\ \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202106131828.15DIS6k7663804%40masaka.moolenaar.net.
Re: Travis CI no longer triggers
On Sat, Jun 12, 2021 at 12:54:33PM +0200, Bram Moolenaar wrote: > The last patch to have been run on Travis is 8.2.2966. Since then it > looks like this CI is no longer picking up patches. Anyone knows why? Travis CI gives 1 free credits to OSS projects. This is not a monthly/yearly amount, it's a one-time donation. Once the credits run out, you have to pay, or email Travis and ask for an additional one-time donation that starts the cycle anew. I'm familiar with some organizations maintaining OSS software that have emailed Travis to ask for credits and have waited months to get a response. Most of them gave up and migrated to alternative CI solutions, usually GitHub Actions. You can check the amount of used and remaining credits after logging in to travis-ci.com: - https://travis-ci.com/account/plan/usage (for personal projects) - https://travis-ci.com/organizations/ORGANIZATION/plan/usage (for GitHub organizations) Marius Gedminas -- We're sysadmins. To us, data is a protocol-overhead. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613182106.yklbu3vpy47ps5xt%40blynas. signature.asc Description: PGP signature
Re: Minor updates to help
On So, 13 Jun 2021, Yegappan Lakshmanan wrote: > Hi, > > The help mentions that when 'paste' is set, the 'smartindent' option > will be reset. But it currently doesn't work this way. The 'smartindent' > option is not disabled when 'paste' is set. I am attaching a minor update > to the help text to remove this. Shouldn't we rather fix the code? so that when paste is in effect, vim would not indent lines based on what is pasted. Best, Christian -- O du alter Kakadu Stets gedenk ich Kakadeiner Ich mißtraue Kakadir und verwünsche Kakadich. Das Gegenteil eines Kaka-du ist übrigens nicht ein Pingu-ihn.) -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613174619.GB532641%40256bit.org.
Re: My contributions to the Vim development
On Sa, 12 Jun 2021, 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/4f4cbea5c018693159a8b61e3668ff8e Cool. Nice achievement. I started following vim development around version 7.3 so not quite as much as your contribution count :) Very much appreciated your contributions! Best, Christian -- Seitdem es Flugzeuge gibt, sind die entfernten Verwandten auch nicht mehr das, was sie einmal waren. -- Helmut Qualtinger -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613173833.GA532641%40256bit.org.
Minor updates to help
Hi, The help mentions that when 'paste' is set, the 'smartindent' option will be reset. But it currently doesn't work this way. The 'smartindent' option is not disabled when 'paste' is set. I am attaching a minor update to the help text to remove this. - 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 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7moRFd8gwYS%2Br2shP60QiFpqCJNnweGnOBKd3HtotR1SQ%40mail.gmail.com. help.diff Description: Binary data
Patch 8.2.2992
Patch 8.2.2992
Problem:Vim9: completion for :disassemble is incomplete.
Solution: Recognize the "debug" and "profile" arguments.
Files: src/cmdexpand.c, src/vim9execute.c, src/proto/vim9execute.pro,
src/vim.h, src/testdir/test_cmdline.vim
*** ../vim-8.2.2991/src/cmdexpand.c 2021-06-13 17:20:04.827963921 +0200
--- src/cmdexpand.c 2021-06-13 17:51:58.490964718 +0200
***
*** 1557,1566
case CMD_function:
case CMD_delfunction:
- case CMD_disassemble:
xp->xp_context = EXPAND_USER_FUNC;
xp->xp_pattern = arg;
break;
case CMD_echohl:
set_context_in_echohl_cmd(xp, arg);
--- 1557,1568
case CMD_function:
case CMD_delfunction:
xp->xp_context = EXPAND_USER_FUNC;
xp->xp_pattern = arg;
break;
+ case CMD_disassemble:
+ set_context_in_disassemble_cmd(xp, arg);
+ break;
case CMD_echohl:
set_context_in_echohl_cmd(xp, arg);
***
*** 2120,2125
--- 2122,2128
{EXPAND_USER_VARS, get_user_var_name, FALSE, TRUE},
{EXPAND_FUNCTIONS, get_function_name, FALSE, TRUE},
{EXPAND_USER_FUNC, get_user_func_name, FALSE, TRUE},
+ {EXPAND_DISASSEMBLE, get_disassemble_argument, FALSE, TRUE},
{EXPAND_EXPRESSION, get_expr_name, FALSE, TRUE},
# endif
# ifdef FEAT_MENU
*** ../vim-8.2.2991/src/vim9execute.c 2021-06-13 14:33:16.407820426 +0200
--- src/vim9execute.c 2021-06-13 18:26:29.459985603 +0200
***
*** 5371,5376
--- 5371,5410
}
/*
+ * Handle command line completion for the :disassemble command.
+ */
+ void
+ set_context_in_disassemble_cmd(expand_T *xp, char_u *arg)
+ {
+ char_u*p;
+
+ // Default: expand user functions, "debug" and "profile"
+ xp->xp_context = EXPAND_DISASSEMBLE;
+ xp->xp_pattern = arg;
+
+ // first argument already typed: only user function names
+ if (*arg != NUL && *(p = skiptowhite(arg)) != NUL)
+ {
+ xp->xp_context = EXPAND_USER_FUNC;
+ xp->xp_pattern = skipwhite(p);
+ }
+ }
+
+ /*
+ * Function given to ExpandGeneric() to obtain the list of :disassemble
+ * arguments.
+ */
+ char_u *
+ get_disassemble_argument(expand_T *xp, int idx)
+ {
+ if (idx == 0)
+ return (char_u *)"debug";
+ if (idx == 1)
+ return (char_u *)"profile";
+ return get_user_func_name(xp, idx - 2);
+ }
+
+ /*
* ":disassemble".
* We don't really need this at runtime, but we do have tests that require it,
* so always include this.
*** ../vim-8.2.2991/src/proto/vim9execute.pro 2021-05-07 17:55:51.967584415
+0200
--- src/proto/vim9execute.pro 2021-06-13 17:55:24.670198729 +0200
***
*** 7,12
--- 7,14
int exe_typval_instr(typval_T *tv, typval_T *rettv);
char_u *exe_substitute_instr(void);
int call_def_function(ufunc_T *ufunc, int argc_arg, typval_T *argv, partial_T
*partial, typval_T *rettv);
+ void set_context_in_disassemble_cmd(expand_T *xp, char_u *arg);
+ char_u *get_disassemble_argument(expand_T *xp, int idx);
void ex_disassemble(exarg_T *eap);
int tv2bool(typval_T *tv);
void emsg_using_string_as(typval_T *tv, int as_number);
*** ../vim-8.2.2991/src/vim.h 2021-06-13 15:15:58.41285 +0200
--- src/vim.h 2021-06-13 17:49:27.703373124 +0200
***
*** 777,782
--- 777,783
#define EXPAND_MAPCLEAR 47
#define EXPAND_ARGLIST48
#define EXPAND_DIFF_BUFFERS 49
+ #define EXPAND_DISASSEMBLE50
// Values for exmode_active (0 is no exmode)
#define EXMODE_NORMAL 1
*** ../vim-8.2.2991/src/testdir/test_cmdline.vim2021-06-13
17:20:04.827963921 +0200
--- src/testdir/test_cmdline.vim2021-06-13 18:34:05.241839830 +0200
***
*** 810,815
--- 810,825
call feedkeys(":legac call strle\\\"\", 'xt')
call assert_equal("\"legac call strlen(", @:)
+ " completion for the :disassemble command
+ call feedkeys(":disas deb\\\"\", 'xt')
+ call assert_equal("\"disas debug", @:)
+ call feedkeys(":disas pro\\\"\", 'xt')
+ call assert_equal("\"disas profile", @:)
+ call feedkeys(":disas debug Test_cmdline_complete_var\\\"\",
'xt')
+ call assert_equal("\"disas debug Test_cmdline_complete_various", @:)
+ call feedkeys(":disas profile
Test_cmdline_complete_var\\\"\", 'xt')
+ call assert_equal("\"disas profile Test_cmdline_complete_various", @:)
+
" completion for the :match command
call feedkeys(":match Search /pat/\\\"\", 'xt')
call assert_equal("\"match Search /pat/\", @:)
*** ../vim-8.2.2991/src/version.c 2021-06-13 17:20:04.831963910 +0200
--- src/version.c 2021-06-13 17:45:23.384033351 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2992,
/**/
--
CRONE: Who sent
":set fileencodings&" does not restore initial value
When starting Vim on a Linux system, 'fileencodings' is set to "ucs-bom,utf-8,default,latin1". But, after executing set fileencodings& or set all& the value changes to "usc-bom" even though the value of 'encoding' has remained "utf-8". ":help fileencodings" says: 'fileencodings' 'fencs' string (default: "ucs-bom", "ucs-bom,utf-8,default,latin1" when 'encoding' is set to a Unicode value) I think the behavior of ":set fileencodings&" and ":set all&" is contrary to the documentation and is a bug. Example: $ vim -N -u NONE -i NONE :verbose set encoding? fileencodings? encoding=utf-8 fileencodings=ucs-bom,utf-8,default,latin1 :set all& :verbose set encoding? fileencodings? encoding=utf-8 fileencodings=ucs-bom The OS is Ubuntu 20.04.2. The Vim version is: VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jun 11 2021 21:55:17) Included patches: 1-2976 Compiled by gary@aurora Normal version with GTK2 GUI. Features included (+) or not (-): +acl -farsi +mouse_sgr +tag_binary -arabic+file_in_path -mouse_sysmouse-tag_old_static +autocmd +find_in_path -mouse_urxvt -tag_any_white +autochdir +float +mouse_xterm -tcl -autoservername+folding +multi_byte-termguicolors +balloon_eval -footer+multi_lang-terminal -balloon_eval_term +fork()-mzscheme +terminfo +browse+gettext +netbeans_intg +termresponse +builtin_terms -hangul_input +num64 +textobjects +byte_offset +iconv +packages +textprop +channel +insert_expand +path_extra+timers +cindent +ipv6 -perl +title +clientserver +job +persistent_undo +toolbar +clipboard +jumplist +popupwin +user_commands +cmdline_compl -keymap+postscript+vartabs +cmdline_hist +lambda+printer +vertsplit +cmdline_info -langmap -profile +virtualedit +comments +libcall +python+visual +conceal +linebreak -python3 +visualextra +cryptv+lispindent+quickfix +viminfo +cscope+listcmds +reltime +vreplace +cursorbind+localmap -rightleft +wildignore +cursorshape -lua -ruby +wildmenu +dialog_con_gui+menu +scrollbind+windows +diff +mksession +signs +writebackup +digraphs +modify_fname +smartindent +X11 +dnd +mouse -sound -xfontset -ebcdic+mouseshape+spell +xim -emacs_tags-mouse_dec +startuptime +xpm +eval +mouse_gpm +statusline+xsmp_interact +ex_extra -mouse_jsbterm -sun_workshop +xterm_clipboard +extra_search -mouse_netterm +syntax-xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -g3 -DFEAT_CONCEAL -DFEAT_MOUSE_SGR -DFEAT_VARTABS -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions 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 this message because you are subscribed to
Patch 8.2.2991
Patch 8.2.2991
Problem:Vim9: no completion for :vim9 and :legacy.
Solution: Expand argument as a command. (closes #8377)
Files: src/cmdexpand.c, src/testdir/test_cmdline.vim
*** ../vim-8.2.2990/src/cmdexpand.c 2021-06-02 13:28:11.423120478 +0200
--- src/cmdexpand.c 2021-06-13 17:17:55.036307843 +0200
***
*** 1370,1375
--- 1370,1377
case CMD_verbose:
case CMD_vertical:
case CMD_windo:
+ case CMD_vim9cmd:
+ case CMD_legacy:
return arg;
case CMD_filter:
*** ../vim-8.2.2990/src/testdir/test_cmdline.vim2021-05-30
14:21:53.852508536 +0200
--- src/testdir/test_cmdline.vim2021-06-13 17:17:07.928440319 +0200
***
*** 804,809
--- 804,815
call feedkeys(":topleft new\\\"\", 'xt')
call assert_equal("\"topleft new", @:)
+ " completion for vim9 and legacy commands
+ call feedkeys(":vim9 call strle\\\"\", 'xt')
+ call assert_equal("\"vim9 call strlen(", @:)
+ call feedkeys(":legac call strle\\\"\", 'xt')
+ call assert_equal("\"legac call strlen(", @:)
+
" completion for the :match command
call feedkeys(":match Search /pat/\\\"\", 'xt')
call assert_equal("\"match Search /pat/\", @:)
*** ../vim-8.2.2990/src/version.c 2021-06-13 17:03:02.022872843 +0200
--- src/version.c 2021-06-13 17:11:24.777411717 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2991,
/**/
--
FIRST VILLAGER: We have found a witch. May we burn her?
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131520.15DFKdNN620187%40masaka.moolenaar.net.
Patch 8.2.2990
Patch 8.2.2990
Problem:Jupyter Notebook files are not recognized.
Solution: Recognize *.ipynb. (closes #8375)
Files: runtime/filetype.vim, src/testdir/test_filetype.vim
*** ../vim-8.2.2989/runtime/filetype.vim2021-06-06 20:15:49.880755525
+0200
--- runtime/filetype.vim2021-06-13 16:58:53.807627858 +0200
***
*** 855,860
--- 855,863
" JSON
au BufNewFile,BufRead *.json,*.jsonp,*.webmanifestsetf json
+ " Jupyter Notebook is also json
+ au BufNewFile,BufRead *.ipynb setf json
+
" Kixtart
au BufNewFile,BufRead *.kix setf kix
*** ../vim-8.2.2989/src/testdir/test_filetype.vim 2021-06-06
20:15:49.880755525 +0200
--- src/testdir/test_filetype.vim 2021-06-13 16:59:16.595557104 +0200
***
*** 257,263
\ 'jgraph': ['file.jgr'],
\ 'jovial': ['file.jov', 'file.j73', 'file.jovial'],
\ 'jproperties': ['file.properties', 'file.properties_xx',
'file.properties_xx_xx', 'some.properties_xx_xx_file'],
! \ 'json': ['file.json', 'file.jsonp', 'file.webmanifest', 'Pipfile.lock'],
\ 'jsp': ['file.jsp'],
\ 'kconfig': ['Kconfig', 'Kconfig.debug', 'Kconfig.file'],
\ 'kivy': ['file.kv'],
--- 257,263
\ 'jgraph': ['file.jgr'],
\ 'jovial': ['file.jov', 'file.j73', 'file.jovial'],
\ 'jproperties': ['file.properties', 'file.properties_xx',
'file.properties_xx_xx', 'some.properties_xx_xx_file'],
! \ 'json': ['file.json', 'file.jsonp', 'file.webmanifest', 'Pipfile.lock',
'file.ipynb'],
\ 'jsp': ['file.jsp'],
\ 'kconfig': ['Kconfig', 'Kconfig.debug', 'Kconfig.file'],
\ 'kivy': ['file.kv'],
*** ../vim-8.2.2989/src/version.c 2021-06-13 15:38:55.574605083 +0200
--- src/version.c 2021-06-13 17:00:42.859292146 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2990,
/**/
--
It is too bad that the speed of light hasn't kept pace with the
changes in CPU speed and network bandwidth. --
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131503.15DF3ftv616263%40masaka.moolenaar.net.
Re: Test failure
* Yegappan Lakshmanan [2021-06-13 06:06 -0700]:
> Hi,
>
> On Sun, Jun 13, 2021 at 5:50 AM Elimar Riesebieter wrote:
> >
> > Hi all,
> >
> > building 8.2.2984 gives me:
> >
> > From test_excmd.vim:
> > Found errors in Test_sandbox():
> > command line..script
> > /source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function
> > RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but
> > got 'E519: Option not supported: imstyle': set imstyle
> >
> > Arch: amd64
> > Buildenv: tmux zsh
> > Compiler: clang-12
> >
>
> Are you building with the Athena GUI support?
Yes
> What is the output of
> the following Vim
> commands?
>
> :echo has('xim')
> :echo has('gui_gtk')
The build host is a headless machine. I am building Debian packages
for all supported gui versions and tiny, nox variants.
Elimar
--
Excellent day for drinking heavily.
Spike the office water cooler;-)
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20210613141310.rpuv5kuv6bpcvgcc%40toy.home.lxtec.de.
Patch 8.2.2989
Patch 8.2.2989
Problem:Vim9: memory leak when debugging a :def function.
Solution: Free the debug instructions.
Files: src/vim9compile.c
*** ../vim-8.2.2988/src/vim9compile.c 2021-06-13 14:15:26.522510754 +0200
--- src/vim9compile.c 2021-06-13 15:37:20.114988987 +0200
***
*** 10045,10050
--- 10045,10057
VIM_CLEAR(dfunc->df_instr);
dfunc->df_instr = NULL;
}
+ if (dfunc->df_instr_debug != NULL)
+ {
+ for (idx = 0; idx < dfunc->df_instr_debug_count; ++idx)
+ delete_instr(dfunc->df_instr_debug + idx);
+ VIM_CLEAR(dfunc->df_instr_debug);
+ dfunc->df_instr_debug = NULL;
+ }
#ifdef FEAT_PROFILE
if (dfunc->df_instr_prof != NULL)
{
*** ../vim-8.2.2988/src/version.c 2021-06-13 15:15:58.41285 +0200
--- src/version.c 2021-06-13 15:38:43.622653018 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2989,
/**/
--
A village. Sound of chanting of Latin canon, punctuated by short, sharp
cracks. It comes nearer. We see it is a line of MONKS ala SEVENTH SEAL
flagellation scene, chanting and banging themselves on the foreheads with
wooden boards.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131339.15DDdOdd597902%40masaka.moolenaar.net.
Re: Specifying a count to the yy, dd, cc, >>, << and !! commands
Hi Bram, On Sun, Jun 13, 2021 at 6:25 AM Bram Moolenaar wrote: > > > Yegappan wrote: > > > A count can be specified before or after the first letter of the > > yy, dd, cc, >>, << and !! commands. This is not mentioned in > > the Vim help. There are a couple of discussions regarding this: > > > > https://vi.stackexchange.com/questions/31428/removing-multiple-lines-d3d-vs-3dd > > https://vi.stackexchange.com/questions/2543/how-can-i-map-dcountd > > > > The opengroup Vi specification indirectly mentions this: > > https://pubs.opengroup.org/onlinepubs/9699919799/utilities/vi.html#tag_20_152_13_02 > > > > It would be good to mention this in the Vim help. > > We can add something below ":help operator". It already mentions that a > count on the operator and a count on the motion is multiplied. How > about this: > > *motion-count-multiplied* > If the motion includes a count and the operator also had a count before it, > the two counts are multiplied. For example: "2d3w" deletes six words. > *operator-doubled* > When doubling the operator it operates on a line. When using a count, before > or after the first character, that many lines are operated upon. Thus `3dd` > deletes three lines. A count before and after the first character is > multiplied, thus `2y3y` yanks six lines. > Looks good to me. 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 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7mFuLSmAYVo7QT54_8xB_dTHK4TP3d7iGAFGTO70b%2BSbw%40mail.gmail.com.
Re: Specifying a count to the yy, dd, cc, >>, << and !! commands
Yegappan wrote: > A count can be specified before or after the first letter of the > yy, dd, cc, >>, << and !! commands. This is not mentioned in > the Vim help. There are a couple of discussions regarding this: > > https://vi.stackexchange.com/questions/31428/removing-multiple-lines-d3d-vs-3dd > https://vi.stackexchange.com/questions/2543/how-can-i-map-dcountd > > The opengroup Vi specification indirectly mentions this: > https://pubs.opengroup.org/onlinepubs/9699919799/utilities/vi.html#tag_20_152_13_02 > > It would be good to mention this in the Vim help. We can add something below ":help operator". It already mentions that a count on the operator and a count on the motion is multiplied. How about this: *motion-count-multiplied* If the motion includes a count and the operator also had a count before it, the two counts are multiplied. For example: "2d3w" deletes six words. *operator-doubled* When doubling the operator it operates on a line. When using a count, before or after the first character, that many lines are operated upon. Thus `3dd` deletes three lines. A count before and after the first character is multiplied, thus `2y3y` yanks six lines. -- Hacker: Someone skilled in computer programming (good guy). Cracker: A hacker that uses his skills to crack software (bad guy). /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// \\\ \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202106131325.15DDPUS0594162%40masaka.moolenaar.net.
Patch 8.2.2988
Patch 8.2.2988
Problem:Vim9: debugger test fails.
Solution: Get the debugger instructions when needed.
Files: src/vim.h, src/vim9.h
*** ../vim-8.2.2987/src/vim.h 2021-06-13 14:01:22.756396984 +0200
--- src/vim.h 2021-06-13 15:10:36.826883698 +0200
***
*** 1801,1806
--- 1801,1807
CT_DEBUG // use df_instr_debug, overrules CT_PROFILE
} compiletype_T;
+ // Keep in sync with INSTRUCTIONS().
#ifdef FEAT_PROFILE
# define COMPILE_TYPE(ufunc) (debug_break_level > 0 ? CT_DEBUG : do_profiling
== PROF_YES && (ufunc)->uf_profiling ? CT_PROFILE : CT_NONE)
#else
*** ../vim-8.2.2987/src/vim9.h 2021-06-13 14:01:22.756396984 +0200
--- src/vim9.h 2021-06-13 15:14:42.221267292 +0200
***
*** 493,502
// Used for "lnum" when a range is to be taken from the stack and "!" is used.
#define LNUM_VARIABLE_RANGE_ABOVE -888
#ifdef FEAT_PROFILE
# define INSTRUCTIONS(dfunc) \
! ((do_profiling == PROF_YES && (dfunc->df_ufunc)->uf_profiling) \
! ? (dfunc)->df_instr_prof : (dfunc)->df_instr)
#else
! # define INSTRUCTIONS(dfunc) ((dfunc)->df_instr)
#endif
--- 493,509
// Used for "lnum" when a range is to be taken from the stack and "!" is used.
#define LNUM_VARIABLE_RANGE_ABOVE -888
+ // Keep in sync with COMPILE_TYPE()
#ifdef FEAT_PROFILE
# define INSTRUCTIONS(dfunc) \
! (debug_break_level > 0 \
! ? (dfunc)->df_instr_debug \
! : ((do_profiling == PROF_YES && (dfunc->df_ufunc)->uf_profiling) \
! ? (dfunc)->df_instr_prof \
! : (dfunc)->df_instr))
#else
! # define INSTRUCTIONS(dfunc) \
! (debug_break_level > 0 \
! ? (dfunc)->df_instr_debug \
! : (dfunc)->df_instr)
#endif
*** ../vim-8.2.2987/src/version.c 2021-06-13 14:33:16.411820418 +0200
--- src/version.c 2021-06-13 15:15:32.788969443 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2988,
/**/
--
|
Ceci n'est pas une pipe.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131316.15DDGQRw592564%40masaka.moolenaar.net.
Re: Test failure
Hi,
On Sun, Jun 13, 2021 at 5:50 AM Elimar Riesebieter wrote:
>
> Hi all,
>
> building 8.2.2984 gives me:
>
> From test_excmd.vim:
> Found errors in Test_sandbox():
> command line..script
> /source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function
> RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but
> got 'E519: Option not supported: imstyle': set imstyle
>
> Arch: amd64
> Buildenv: tmux zsh
> Compiler: clang-12
>
Are you building with the Athena GUI support? What is the output of
the following Vim
commands?
:echo has('xim')
:echo has('gui_gtk')
Thanks,
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 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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/CAAW7x7m18Jt0J%3DNmb-yCJZa7bOj0Ghwg84moSe9v75TKDtSqxw%40mail.gmail.com.
Re: My contributions to the Vim development
Hi Bram, On Sun, Jun 13, 2021 at 5:02 AM Bram Moolenaar wrote: > > Yegappan wrote: > > > 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/4f4cbea5c018693159a8b61e3668ff8e > > Impressive, your contributions have helped many Vim users! > Thanks. > > I wonder why you wrote it down now. Applying for a job? > No. :-). I have never used my Vim contributions to further my professional career. 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 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7nbX18PEMYo83FzsHXiWJ-cbEAPqYnuaAC5TPehL0bHmA%40mail.gmail.com.
Test failure
Hi all, building 8.2.2984 gives me: >From test_excmd.vim: Found errors in Test_sandbox(): command line..script /source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but got 'E519: Option not supported: imstyle': set imstyle Arch: amd64 Buildenv: tmux zsh Compiler: clang-12 Thanks Elimar -- "Talking much about oneself can also be a means to conceal oneself." -Friedrich Nietzsche -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210613125005.xkglvrqol5s7i4yx%40toy.home.lxtec.de.
Patch 8.2.2987
Patch 8.2.2987
Problem:Build failure with normal features.
Solution: Remove #define.
Files: src/vim9execute.c
*** ../vim-8.2.2986/src/vim9execute.c 2021-06-13 14:01:22.760396977 +0200
--- src/vim9execute.c 2021-06-13 14:32:04.008005224 +0200
***
*** 738,750
int error;
int idx;
int did_emsg_before = did_emsg;
#ifdef FEAT_PROFILE
! compiletype_T compile_type = do_profiling == PROF_YES
!&& ufunc->uf_profiling ? CT_PROFILE : CT_NONE;
! #else
! # define compile_type CT_NONE
#endif
-
if (func_needs_compiling(ufunc, compile_type)
&& compile_def_function(ufunc, FALSE, compile_type, NULL)
== FAIL)
--- 738,749
int error;
int idx;
int did_emsg_before = did_emsg;
+ compiletype_T compile_type = CT_NONE;
+
#ifdef FEAT_PROFILE
! if (do_profiling == PROF_YES && ufunc->uf_profiling)
! compile_type = CT_PROFILE;
#endif
if (func_needs_compiling(ufunc, compile_type)
&& compile_def_function(ufunc, FALSE, compile_type, NULL)
== FAIL)
*** ../vim-8.2.2986/src/version.c 2021-06-13 14:15:26.522510754 +0200
--- src/version.c 2021-06-13 14:33:07.563843007 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2987,
/**/
--
Westheimer's Discovery:
A couple of months in the laboratory can
frequently save a couple of hours in the library.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131233.15DCXh5X579741%40masaka.moolenaar.net.
Patch 8.2.2986
Patch 8.2.2986
Problem:Build failure without the profile feature.
Solution: Add #ifdef.
Files: src/vim9compile.c
*** ../vim-8.2.2985/src/vim9compile.c 2021-06-13 14:01:22.756396984 +0200
--- src/vim9compile.c 2021-06-13 14:14:29.098650395 +0200
***
*** 1871,1880
switch (compile_type)
{
- case CT_NONE:
- return dfunc->df_instr == NULL;
case CT_PROFILE:
return dfunc->df_instr_prof == NULL;
case CT_DEBUG:
return dfunc->df_instr_debug == NULL;
}
--- 1871,1882
switch (compile_type)
{
case CT_PROFILE:
+ #ifdef FEAT_PROFILE
return dfunc->df_instr_prof == NULL;
+ #endif
+ case CT_NONE:
+ return dfunc->df_instr == NULL;
case CT_DEBUG:
return dfunc->df_instr_debug == NULL;
}
*** ../vim-8.2.2985/src/version.c 2021-06-13 14:01:22.760396977 +0200
--- src/version.c 2021-06-13 14:15:11.694546896 +0200
***
*** 752,753
--- 752,755
{ /* Add new patch number below this line */
+ /**/
+ 2986,
/**/
--
Eye have a spelling checker, it came with my PC;
It plainly marks four my revue mistakes I cannot sea.
I've run this poem threw it, I'm sure your please to no,
It's letter perfect in it's weigh, my checker tolled me sew!
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106131215.15DCFtxC571310%40masaka.moolenaar.net.
Patch 8.2.2985
Patch 8.2.2985
Problem:Vim9: a compiled function cannot be debugged.
Solution: Add initial debugging support.
Files: src/vim9.h, src/vim9compile.c, src/proto/vim9compile.pro,
src/vim.h, src/eval.c, src/vim9execute.c, src/userfunc.c,
src/vim9type.c, src/testdir/test_debugger.vim,
src/testdir/test_vim9_disassemble.vim
*** ../vim-8.2.2984/src/vim9.h 2021-06-06 17:02:49.753789485 +0200
--- src/vim9.h 2021-06-12 18:04:15.659477801 +0200
***
*** 168,173
--- 168,175
ISN_PROF_START, // start a line for profiling
ISN_PROF_END, // end a line for profiling
+ ISN_DEBUG,// check for debug breakpoint
+
ISN_UNPACK, // unpack list into items, uses isn_arg.unpack
ISN_SHUFFLE,// move item on stack up or down
ISN_DROP, // pop stack and discard value
***
*** 453,458
--- 455,462
isn_T *df_instr_prof; // like "df_instr" with profiling
int df_instr_prof_count; // size of "df_instr_prof"
#endif
+ isn_T *df_instr_debug; // like "df_instr" with debugging
+ int df_instr_debug_count; // size of "df_instr_debug"
int df_varcount;// number of local variables
int df_has_closure; // one if a closure was created
*** ../vim-8.2.2984/src/vim9compile.c 2021-06-12 18:30:51.510966898 +0200
--- src/vim9compile.c 2021-06-13 13:58:03.548742416 +0200
***
*** 174,180
char_u*ctx_line_start;// start of current line or NULL
garray_T ctx_instr; // generated instructions
! int ctx_profiling; // when TRUE generate ISN_PROF_START
garray_T ctx_locals; // currently visible local variables
int ctx_locals_count; // total number of local variables
--- 174,180
char_u*ctx_line_start;// start of current line or NULL
garray_T ctx_instr; // generated instructions
! compiletype_T ctx_compile_type;
garray_T ctx_locals; // currently visible local variables
int ctx_locals_count; // total number of local variables
***
*** 1857,1863
* "profile" indicates profiling is to be done.
*/
int
! func_needs_compiling(ufunc_T *ufunc, int profile UNUSED)
{
switch (ufunc->uf_def_status)
{
--- 1857,1863
* "profile" indicates profiling is to be done.
*/
int
! func_needs_compiling(ufunc_T *ufunc, compiletype_T compile_type)
{
switch (ufunc->uf_def_status)
{
***
*** 1866,1880
case UF_COMPILED:
{
- #ifdef FEAT_PROFILE
dfunc_T *dfunc = ((dfunc_T *)def_functions.ga_data)
+ ufunc->uf_dfunc_idx;
! return profile ? dfunc->df_instr_prof == NULL
! : dfunc->df_instr == NULL;
! #else
! break;
! #endif
}
case UF_NOT_COMPILED:
--- 1866,1883
case UF_COMPILED:
{
dfunc_T *dfunc = ((dfunc_T *)def_functions.ga_data)
+ ufunc->uf_dfunc_idx;
! switch (compile_type)
! {
! case CT_NONE:
! return dfunc->df_instr == NULL;
! case CT_PROFILE:
! return dfunc->df_instr_prof == NULL;
! case CT_DEBUG:
! return dfunc->df_instr_debug == NULL;
! }
}
case UF_NOT_COMPILED:
***
*** 1945,1953
return FAIL;
}
}
! if (func_needs_compiling(ufunc, PROFILING(ufunc))
&& compile_def_function(ufunc, ufunc->uf_ret_type == NULL,
! PROFILING(ufunc), NULL) == FAIL)
return FAIL;
}
if (ufunc->uf_def_status == UF_COMPILE_ERROR)
--- 1948,1956
return FAIL;
}
}
! if (func_needs_compiling(ufunc, COMPILE_TYPE(ufunc))
&& compile_def_function(ufunc, ufunc->uf_ret_type == NULL,
! COMPILE_TYPE(ufunc), NULL) == FAIL)
return FAIL;
}
if (ufunc->uf_def_status == UF_COMPILE_ERROR)
***
*** 2313,2326
garray_T *instr = >ctx_instr;
int idx = instr->ga_len;
! if (cctx->ctx_has_cmdmod && ((isn_T *)instr->ga_data)[idx - 1]
.isn_type == ISN_CMDMOD)
! --idx;
#ifdef FEAT_PROFILE
! if (cctx->ctx_profiling && ((isn_T *)instr->ga_data)[idx - 1]
! .isn_type == ISN_PROF_START)
! --idx;
#endif
return idx;
}
--- 2316,2343
garray_T *instr =
Re: My contributions to the Vim development
Yegappan wrote: > 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/4f4cbea5c018693159a8b61e3668ff8e Impressive, your contributions have helped many Vim users! I wonder why you wrote it down now. Applying for a job? -- Any resemblance between the above views and those of my employer, my terminal, or the view out my window are purely coincidental. Any resemblance between the above and my own views is non-deterministic. The question of the existence of views in the absence of anyone to hold them is left as an exercise for the reader. The question of the existence of the reader is left as an exercise for the second god coefficient. (A discussion of non-orthogonal, non-integral polytheism is beyond the scope of this article.) (Ralph Jennings) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// \\\ \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202106131201.15DC1vHO567955%40masaka.moolenaar.net.
