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
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,
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.
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,
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
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
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
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'
> >
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,
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".
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
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
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:
>
>
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
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
***
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'
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
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.vim
* 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
> >
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
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:
> >
> >
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:
>
>
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
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
>
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:
> >
> >
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:
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
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
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,
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
30 matches
Mail list logo
