[vim/vim] Make 'virtualedit' option global-local (#8638)

14 views
Skip to first unread message

Gary Johnson

unread,
Jul 25, 2021, 12:19:55 PM7/25/21
to vim/vim, Subscribed

You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/8638

Commit Summary

  • Make the 'virtualedit' option global-local
  • Merge branch 'master' into gj_ve_global_local

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

codecov[bot]

unread,
Jul 25, 2021, 2:10:47 PM7/25/21
to vim/vim, Subscribed

Codecov Report

Merging #8638 (c7a4cc0) into master (a764e73) will decrease coverage by 87.60%.
The diff coverage is 8.62%.

Impacted file tree graph

@@             Coverage Diff             @@

##           master    #8638       +/-   ##

===========================================

- Coverage   90.08%    2.47%   -87.61%     

===========================================

  Files         150      148        -2     

  Lines      169462   164221     -5241     

===========================================

- Hits       152659     4072   -148587     

- Misses      16803   160149   +143346     
Flag Coverage Δ
huge-clang-none ?
huge-gcc-none ?
huge-gcc-testgui ?
huge-gcc-unittests 2.47% <8.62%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/buffer.c 3.47% <0.00%> (-88.98%) ⬇️
src/change.c 1.54% <0.00%> (-91.43%) ⬇️
src/drawscreen.c 1.63% <0.00%> (-84.75%) ⬇️
src/edit.c 0.00% <0.00%> (-92.89%) ⬇️
src/misc2.c 5.35% <0.00%> (-87.07%) ⬇️
src/normal.c 0.50% <0.00%> (-95.54%) ⬇️
src/ops.c 0.00% <0.00%> (-96.00%) ⬇️
src/register.c 0.21% <0.00%> (-91.82%) ⬇️
src/optionstr.c 21.48% <7.14%> (-73.66%) ⬇️
src/option.c 16.84% <33.33%> (-77.45%) ⬇️
... and 146 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a764e73...c7a4cc0. Read the comment docs.

vim-dev ML

unread,
Jul 25, 2021, 2:26:58 PM7/25/21
to vim/vim, vim-dev ML, Your activity

On 2021-07-25, Gary Johnson wrote:
> -------------------------------------------------------------------------------
I'm getting CI failures from this PR that I don't understand. For
example, a build titled "linux (huge, gcc, none)" fails with these
last lines in the log:

749 File 'sign.c'
750 Lines executed:94.58% of 1200
751 Creating 'sign.c.gcov'
752
753 {'message': "Couldn't find a repository matching this job.", 'error': True}
754 Error: Process completed with exit code 1.

Huh? I have no idea what that means or what to do about it.

How do I fix that?

Regards,
Gary

Christian Brabandt

unread,
Jul 25, 2021, 2:46:38 PM7/25/21
to vim/vim, vim-dev ML, Comment

This error can be ignored. For some reason the coverity job only works when the patch has been merged. Don't know why or how to fix it.


You are receiving this because you commented.

Bram Moolenaar

unread,
Jul 25, 2021, 3:37:09 PM7/25/21
to vim/vim, vim-dev ML, Comment

Thanks, mostly looks good.
One situation is not covered: If the global value is set, there is no way do disable it locally, since an empty value means to use the global value. How about using "none", using it for the local value would then overrule the global value.
There are actually other options where this could be useful. But since nobody asked for it, probably less so.


You are receiving this because you commented.

Gary Johnson

unread,
Jul 25, 2021, 3:47:57 PM7/25/21
to reply+ACY5DGGG7B23D4JAHY...@reply.github.com, vim...@googlegroups.com
On 2021-07-25, Bram Moolenaar wrote:
> Thanks, mostly looks good.
> One situation is not covered: If the global value is set, there is no way do
> disable it locally, since an empty value means to use the global value. How
> about using "none", using it for the local value would then overrule the global
> value.
> There are actually other options where this could be useful. But since nobody
> asked for it, probably less so.

I noticed that, but since other options I checked seemed to have
that same problem, I thought it was a deliberate feature of
global-local options.

If you'd like "none", I'll add it.

Regards,
Gary

vim-dev ML

unread,
Jul 25, 2021, 3:48:17 PM7/25/21
to vim/vim, vim-dev ML, Your activity

Gabriel Dupras

unread,
Jul 25, 2021, 3:55:15 PM7/25/21
to vim/vim, vim-dev ML, Comment

An example of this is 'showbreak'. From the help files:

A window-local value overrules a global value.  If the global value is
set and you want no value in the current window use NONE:
	:setlocal showbreak=NONE


You are receiving this because you commented.

Gary Johnson

unread,
Jul 25, 2021, 10:04:40 PM7/25/21
to vim/vim, vim-dev ML, Push

@ghgary pushed 1 commit.

  • 013bffc Add "none" to 'virtualedit' values


You are receiving this because you are subscribed to this thread.

View it on GitHub or unsubscribe.

Bram Moolenaar

unread,
Jul 26, 2021, 5:45:50 AM7/26/21
to vim/vim, vim-dev ML, Comment


Gabriel Dupras wrote:

> An example of this is `'showbreak'`. From the help files:
>
> ```
> A window-local value overrules a global value. If the global value is
> set and you want no value in the current window use NONE:
> :setlocal showbreak=NONE
> ```

For 'virtualedit' we can use either NONE or none. Best is probably to
accept both.

--
hundred-and-one symptoms of being an internet addict:
242. You turn down a better-paying job because it doesn't come with
a free e-mail account.

/// Bram Moolenaar -- Br...@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 are receiving this because you commented.

Gary Johnson

unread,
Jul 26, 2021, 9:38:35 AM7/26/21
to vim/vim, vim-dev ML, Push

@ghgary pushed 1 commit.

  • a7d486a Add "NONE" as alternative spelling of "none"


You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,
Jul 26, 2021, 4:19:40 PM7/26/21
to vim/vim, vim-dev ML, Comment

Closed #8638 via 53ba05b.


You are receiving this because you commented.

Reply all
Reply to author
Forward
0 new messages