Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] vim-patch:8.0.0234,8.0.0236,8.0.0225 #8052

Merged
merged 4 commits into from Mar 4, 2018

Conversation

ckelsel
Copy link
Contributor

@ckelsel ckelsel commented Feb 22, 2018

vim-patch:8.0.0225: put in Visual block mode terminates early

Problem: When a block is visually selected and put is used on the end of
the selection only one line is changed.
Solution: Check for the end properly. (Christian Brabandt, neovim issue 5781)

vim/vim@9957a10

vim-patch:8.0.0234: crash when using put in Visual mode

Problem: When several lines are visually selected and one of them is short,
using put may cause a crash. (Axel Bender)
Solution: Check for a short line. (Christian Brabandt)

vim/vim@941c12d

vim-patch:8.0.0236: gcc complains about uninitialized variable

Problem: Gcc complains that a variable may be used uninitialized. Confusion
between variable and label name. (John Marriott)
Solution: Initialize it. Rename end to end_lnum.

vim/vim@6a717f1

Problem:    When several lines are visually selected and one of them is short,
            using put may cause a crash. (Axel Bender)
Solution:   Check for a short line. (Christian Brabandt)

vim/vim@941c12d
Problem:    Gcc complains that a variable may be used uninitialized. Confusion
            between variable and label name. (John Marriott)
Solution:   Initialize it.  Rename end to end_lnum.

vim/vim@6a717f1
@marvim marvim added the RFC label Feb 22, 2018
@ckelsel
Copy link
Contributor Author

ckelsel commented Feb 23, 2018

refer to #7999 vim-patch:8.0.0236: gcc complains about uninitialized variable

&& (lnum <= curbuf->b_visual.vi_end.lnum
|| lnum <= curbuf->b_visual.vi_start.lnum));
}
} while (VIsual_active && lnum <= end_lnum);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not port 8.0.0225 first? It will be confusing to merge it later.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I didn't realize we had already covered this in #5781. Please try to mention that if you can, it will save time.

Problem:    When a block is visually selected and put is used on the end of
            the selection only one line is changed.
Solution:   Check for the end properly. (Christian Brabandt, neovim issue
            5781)

vim/vim@9957a10
@ckelsel ckelsel changed the title [RFC] vim-patch:8.0.0234,8.0.0236 [RFC] vim-patch:8.0.0234,8.0.0236,8.0.0225 Mar 4, 2018
@ckelsel
Copy link
Contributor Author

ckelsel commented Mar 4, 2018

1690Error: Error fetching file: Failed downloading https://github.com/libmpack/libmpack-lua/releases/download/1.0.7/libmpack-lua-1.0.7.tar.gz - libmpack-lua-1.0.7.tar.gz
1691mingw32-make[2]: *** [CMakeFiles\mpack.dir\build.make:60: usr/lib/luarocks/rocks/mpack] Error 1
1692mingw32-make[2]: Leaving directory 'C:/projects/neovim/.deps'
1693mingw32-make[1]: *** [CMakeFiles\Makefile2:577: CMakeFiles/mpack.dir/all] Error 2
1694mingw32-make[1]: Leaving directory 'C:/projects/neovim/.deps'
1695mingw32-make: *** [Makefile:83: all] Error 2
1696
1697C:\projects\neovim\.deps>exit /b 2 
1698

@justinmk justinmk merged commit 544cef0 into neovim:master Mar 4, 2018
@justinmk justinmk removed the RFC label Mar 4, 2018
@ckelsel ckelsel deleted the vim-8.0.0234 branch March 5, 2018 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants