| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| | |
Closes #2040
Closes #3370
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Screen.lua needed a little cosmetical adjustment to print out the color nicely.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix warnings with gcc 6.1
|
|/ /
| |
| |
| | |
The intentional behavior of do_sub was checked in vim
|
|\ \
| | |
| | | |
vim-patch: 7.4.1036
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Problem: Only terminals with up to 256 colors work properly.
Solution: Use the 256 color behavior for all terminals with 256 or more
colors. (Robert de Bath)
https://github.com/vim/vim/commit/fa03fd6c4a9fe05274d62ddefd645cb5801d2023
|
|\ \
| | |
| | | |
vim-patch:7.4.1046
|
|/ /
| |
| |
| |
| |
| |
| | |
Problem: No test coverage for menus.
Solution: Load the standard menus and check there is no error.
https://github.com/vim/vim/commit/2d6c8002729821acc54a4de41d5c5f3d50594973
|
|\ \
| | |
| | | |
test: Fix running tests from Ninja
|
| |/ |
|
|\ \
| |/
|/| |
vim-patch:7.4.1102, 7.4.1110, 7.4.1832
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Memory leak in debug commands.
Solution: Free memory before overwriting the pointer. (hint by Justin Keyes)
https://github.com/vim/vim/commit/dc303bce10c60a3314078ea168064552fadf01af
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Test 108 fails when language is French.
Solution: Force English messages. (Dominique Pelle)
https://github.com/vim/vim/commit/8c600052fabe4859470d9d0ba2ddd74a52ea9745
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Debugger has no stack backtrace support.
Solution: Add "backtrace", "frame", "up" and "down" commands. (Alberto
Fanjul, closes vim/vim#433)
https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
|
|\ \
| | |
| | | |
msg_puts_printf: remove char_u
|
| |/ |
|
|\ \
| | |
| | | |
vim-patch:7.4.1513
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: "J" fails if there are not enough lines. (Christian Neukirchen)
Solution: Reduce the count, only fail on the last line.
https://github.com/vim/vim/commit/41e0f2f48f541eb2c8eb5620d3f1d270eb979154
|
|\ \ \
| | | |
| | | | |
vim-patch:7.4.1568,7.4.1571,7.4.1728
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
patch 7.4.1728
Problem: The help for functions require a space after the "(".
Solution: Make CTRL-] on a function name ignore the arguments. (Hirohito
Higashi)
https://github.com/vim/vim/commit/81edd171a9465cf99cede4fa4a7b7bca3d538b0f
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
patch 7.4.1571
Problem: No test for ":help"
Solution: Add a test for what 7.4.1568 fixed. (Higashi Higashi)
https://github.com/vim/vim/commit/8e15ffcde757ffc6cfe8b5e384948b3278e9af33
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
patch 7.4.1568
Problem: Using CTRL-] in help on option in parentheses doesn't work.
Solution: Skip the "(" in "('". (Hirohito Higashi)
https://github.com/vim/vim/commit/00f9e0dbbd3472db217d56639fad9346b9eb3b82
|
|\ \ \ \
| |/ / /
|/| | | |
vim-patch.sh: Ignore “git describe” failures in list_vim_patches
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's acceptable for “git describe --tags --exact-match …” to fail, since
all runtime updates commits are untagged. All that matters is that we
get a tag when one exists.
Therefore, ignore the failure status of the git describe call, relying
on the captured output instead.
|
|\ \ \
| |_|/
|/| | |
Run shellcheck (shell scripting linter) on shell scripts.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are a total of 5 shell scripts in the Neovim source tree.
All but runtime\macros\less.sh had warnings/errors when run through
Shellcheck (http://www.shellcheck.net/).
This commit fixes all warnings/errors and also changes the shebang to
"#!/bin/sh" when possible (this was not possible for vim-patch.sh
because it uses many bashisms).
The shellcheck errors that were fixed are:
SC2068: Double quote array expansions to avoid re-splitting elements.
SC2086: Double quote to prevent globbing and word splitting.
SC2124: Assigning an array to a string! Assign as array, or use *
instead of @ to concatenate
SC2155: Declare and assign separately to avoid masking return values.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently,
```
if bool then
--stuff
elseif bool2 then
--morestuff
elseif bool3 then
--more stuff
else
--fail
end
```
Would get indented out strangely when using =. Now it behaves correctly.
|
|\ \ \ \
| | | | |
| | | | | |
build: fix '-fno-sanitize-recover' warning in Clang 3.7
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vim-patch:7.4.1037,fa73534
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Updated runtime files.
https://github.com/vim/vim/commit/fa7353428f705f7a13465a1943dddeede4083023
Missing in runtime/doc: if_tcl.txt, tags, todo.txt, version5.txt. Some
other changes related to binary nrformats were already merged.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: Using "q!" when there is a modified hidden buffer does not unload
the current buffer, resulting in the need to abandon it again.
Solution: When using "q!" unload the current buffer when needed. (Yasuhiro
Matsumoto, Hirohito Higashi)
https://github.com/vim/vim/commit/027387f70c671f62e3e08e0bdd09ec05b0232735
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
term_close use-after-free
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Closes #4393
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
References #4393
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
os/env.c: cosmetic changes, restrict pointers
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
...and small refactorings:
- Style changes
- Variable renames
- Changes in variable scope
This change won't bring new problems (undefined behavior) as `memcpy` is
already being used in the function.
|