aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | vim-patch: Replace shell variables in printf with formatted argsJames McCoy2018-06-19
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ensures that special characters in the variables are not interpreted as escapes/format characters in the printf string, as was seen with upstream patch 8.0.0615. $ ./scripts/vim-patch.sh -p 8.0.0615 Updating Vim sources: /$HOME/src/neovim/.vim-src ✔ Updated Vim sources. ✔ Found Vim revision 'bf15b8d78b22661db8b19d662b62bb9a061cdd37'. Creating patch... Pre-processing patch... ✔ Saved patch to '/$HOME/src/neovim/vim-8.0.0615.patch'. Fetching 'origin/master'. ✔ From https://github.com/neovim/neovim * branch master -> FETCH_HEAD Creating new branch 'vim-8.0.0615' based on 'origin/master'. ✔ Switched to a new branch 'vim-8.0.0615' Branch 'vim-8.0.0615' set up to track remote branch 'master' from 'origin'. Creating empty commit with correct commit message. ./scripts/vim-patch.sh: line 40: printf: `w': invalid format character ✔ [vim-8.0.0615 db7fbb016] vim-patch:8.0.0615: using ./scripts/vim-patch.sh: line 44: printf: `w': invalid format character ✘ [vim-8.0.0615 db7fbb016] vim-patch:8.0.0615: using [ci-skip]
* | vim-patch:8.0.0455: the mode test may hang (#8577)Jan Edmund Lazo2018-06-19
| | | | | | | | | | | | Problem: The mode test may hang in Test_mode(). (Michael Soyka) Solution: Set 'complete' to only search the current buffer (as suggested by Michael) https://github.com/vim/vim/commit/ffea8c99d9658b0b51a848a6f674851851e78fa7
* | vim-patch:8.0.0542: getpos() can return a negative line number (#8580)Jan Edmund Lazo2018-06-19
| | | | | | | | | | Problem: getpos() can return a negative line number. (haya14busa) Solution: Handle a zero topline and botline. (closes vim/vim#1613) https://github.com/vim/vim/commit/a1d5fa65bc7e8a548858e9c295a192b63dcd011b
* | vim-patch:8.0.0598: building with gcc 7.1 yields new warnings (#8585)Jan Edmund Lazo2018-06-19
| | | | | | | | | | Problem: Building with gcc 7.1 yields new warnings. Solution: Initialize result. (John Marriott) https://github.com/vim/vim/commit/9e0f6ec0762575d229b86798b284ca4876bc3d73
* | Merge #8584 from janlazo/vim-8.0.0467Justin M. Keyes2018-06-19
|\ \
| * | vim-patch:8.0.0547: extra line break in verbosefileJan Edmund Lazo2018-06-18
| | | | | | | | | | | | | | | | | | | | | Problem: Extra line break in verbosefile when using ":echomsg". (Ingo Karkat) Solution: Don't call msg_start(). (closes vim/vim#1618) https://github.com/vim/vim/commit/52604f2454e5369f861d3ce34764f74a0999c773
| * | vim-patch:8.0.0467: using g< after :for does not show the right outputJan Edmund Lazo2018-06-18
| |/ | | | | | | | | | | | | Problem: Using g< after :for does not show the right output. (Marcin Szamotulski) Solution: Call msg_sb_eol() in :echomsg. https://github.com/vim/vim/commit/57002ad70c4c32f3afefec24994a974cf3eef3ad
* | Merge #8558 from jamessan/gnucxx-compiler-for-gnu-sourceJustin M. Keyes2018-06-18
|\ \ | | | | | | cmake: Check for GNU compiler, not Linux, to set -D_GNU_SOURCE
| * | cmake: Prefer add_definitions() for setting preprocessor definesJames McCoy2018-06-18
| | |
| * | cmake: Comply with new CMP0054 policyJames McCoy2018-06-18
| | |
| * | Raise minimum CMake version to 2.8.12 and remove compat codeJames McCoy2018-06-18
| | | | | | | | | | | | | | | | | | | | | 2.8.12 is supported by our main CI targets and [repology] confirms that this is broadly supported. [repology]: https://repology.org/metapackage/cmake/information
| * | cmake: Consolidate enabling of "undefined symbol" errorsJames McCoy2018-06-18
| | |
| * | cmake: Explicitly declare C as the project languageJames McCoy2018-06-18
| | | | | | | | | | | | | | | | | | | | | There's a mix of CXX and C related variables being set/referenced in our CMake files. Since we only use C, use an explicit language list of "C" instead of the implicit "C CXX" and replace all uses of CXX variables with their C counterparts
| * | cmake: Check for GNU compiler, not Linux, to set -D_GNU_SOURCEJames McCoy2018-06-18
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Debian hurd-i386 [build] failed (partly) due to -D_GNU_SOURCE not be defined: [215/286] /usr/bin/cc -DINCLUDE_GENERATED_DECLARATIONS -Iconfig -I../src -Isrc/nvim/auto -Iinclude -I/usr/include/luajit-2.1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_LOG -Wdate-time -D_FORTIFY_SOURCE=2 -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -MD -MT src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o -MF src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o.d -o src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o -c ../src/nvim/os/pty_process_unix.c ../src/nvim/os/pty_process_unix.c: In function 'pty_process_tty_name': ../src/nvim/os/pty_process_unix.c:121:10: warning: implicit declaration of function 'ptsname'; did you mean 'ttyname'? [-Wimplicit-function-declaration] return ptsname(ptyproc->tty_fd); Hurd is obviously not Linux, but it is using a GNU compiler and glibc so it needs -D_GNU_SOURCE for the ptsname() definition to be visible. [build]: https://buildd.debian.org/status/fetch.php?pkg=neovim&arch=hurd-i386&ver=0.3.0-2&stamp=1528981349&raw=0
* / use wchar_t instead of WCHAR #6998Matt Kline2018-06-18
|/ | | | wchar_t has better cross-platform support and seems to fix an issue on MinGW when building with `-std=c99`.
* Merge #8502 from janlazo/vim-8.0.0481Justin M. Keyes2018-06-17
|\
| * syntax: refactor syn_finish_line to return boolJan Edmund Lazo2018-06-16
| |
| * vim-patch:8.0.0481: unnecessary if statementJan Edmund Lazo2018-06-16
| | | | | | | | | | | | | | Problem: Unnecessary if statement. Solution: Remove the statement. Fix "it's" vs "its" mistakes. (Dominique Pelle, closes vim/vim#1568) https://github.com/vim/vim/commit/aab93b12cb54fbe5efe9e8f6fde1c46802a3031e
* | Merge #8520 'Ex mode: always "improved" (gQ)'Justin M. Keyes2018-06-17
|\ \
| * | startup: fix -E/-Es without `-u NONE`Justin M. Keyes2018-06-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, -E/-Es without `-u NONE` reads stdin as Ex commands. It should always read stdin as text (into buffer 1), like this: echo foo | nvim -Es +'%p' foo echo foo | nvim -Es -u NORC +'%p' foo
| * | Ex mode: use getexline() instead of getexmodeline()Justin M. Keyes2018-06-17
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes Ex mode (Q, -e) to work like Vim's "improved Ex mode" (gQ, -E). That brings some small behavior differences, but should not impact most Ex scripts (unless, for example, they depend on mappings being disabled--but that can be solved for -e by skipping user config). Before this change: * the screen test hangs. After this change: * Q acts like gQ. * -e/-es differs from -E/-Es only in its treatment of stdin. This moves towards potentially removing getexmodeline(). (HINT: That does NOT mean "removing Ex mode", it means removing the Vi-compatible Ex mode, which differs from Vim's "improved Ex mode" only in some minor details (e.g. mappings are disabled).) ref #1089 :-)~
* | checkhealth: node.js: also search yarn #8528Ahmed El Gabri2018-06-17
| | | | | | | | | | - "neovim" package may be installed with yarn. Check yarn if npm fails. - Use filereadable() instead of glob(). closes #8552
* | vim-patch:8.0.0609: some people still don't know how to quit (#8571)Jan Edmund Lazo2018-06-17
| | | | | | | | | | | | | | | | Problem: For some people the hint about quitting is not sufficient. Solution: Put <Enter> separately. Also use ":qa!" to get out even when there are changes. https://github.com/vim/vim/commit/28a8193e3113f676f89fb6312b099d849df881d3
* | vim-patch:8.0.0625: shellescape() always escapes a newline (#8573)Jan Edmund Lazo2018-06-17
| | | | | | | | | | | | | | Problem: shellescape() always escapes a newline, which does not work with some shells. (Harm te Hennepe) Solution: Only escape a newline when the "special" argument is non-zero. (Christian Brabandt, closes vim/vim#1590) https://github.com/vim/vim/commit/206155280def51160a9d81d983aed639015ffb44
* | Merge #8570 'gen_events.lua: define NUM_EVENTS as enum'Justin M. Keyes2018-06-16
|\ \
| * | build/test: skip empty TEST_TAG, TEST_FILTERJustin M. Keyes2018-06-16
| | | | | | | | | | | | | | | - Empty "--tags=", "--filter=" prevents TEST_FILE from running. - Fix another bug: TEST_FILTER overwrote TEST_TAG.
| * | gen_events.lua: define NUM_EVENTS as an enum valueJustin M. Keyes2018-06-16
| |/ | | | | | | | | | | | | | | | | | | Fix PVS warnings: fileio.c:7293 Medium V547 Expression is always true. fileio.c:7351 Medium V547 Expression 'event == 100' is always false. event_name2nr returns event_T, so PVS infers that nothing outside of that range could possibly be returned.
* | Merge #8569 from janlazo/vim-8.0.0602Justin M. Keyes2018-06-16
|\ \
| * | vim-patch:8.0.0604: gF test fails still on MS-WindowsJan Edmund Lazo2018-06-16
| | | | | | | | | | | | | | | | | | Problem: gF test fails still on MS-Windows. Solution: Use : before the line number and remove it from 'isfname'. https://github.com/vim/vim/commit/712598f210570627534246cb5dcbb4f213367997
| * | vim-patch:8.0.0603: gF test fails on MS-WindowsJan Edmund Lazo2018-06-16
| | | | | | | | | | | | | | | | | | Problem: gF test fails on MS-Windows. Solution: Use @ instead of : before the line number https://github.com/vim/vim/commit/d7aca7a71c7254501c08f04db1798df479df0e89
| * | vim-patch:8.0.0602: when gF fails to edit the file the cursor still movesJan Edmund Lazo2018-06-16
| |/ | | | | | | | | | | | | Problem: When gF fails to edit the file the cursor still moves to the found line number. Solution: Check the return value of do_ecmd(). (Michael Hwang) https://github.com/vim/vim/commit/2a79ed293c077ba791db962f0e121cf97ba4f7a7
* | Merge #8567 from ckelsel/vim-8.0.0530Justin M. Keyes2018-06-16
|\ \ | |/ |/|
| * fix lintckelsel2018-06-16
| |
| * vim-patch:8.0.0545: edit test may fail on some systemsckelsel2018-06-16
| | | | | | | | | | | | Problem: Edit test may fail on some systems. Solution: If creating a directory with a very long path fails, bail out. https://github.com/vim/vim/commit/15ecbd6f3d39ff04862999a577962ef9369a9e53
| * vim-patch:8.0.0543: test_edit causes older xfce4-terminal to closeckelsel2018-06-16
| | | | | | | | | | | | | | Problem: Test_edit causes older xfce4-terminal to close. (Dominique Pelle) Solution: Reduce number of columns to 2000. Try to restore the window position. https://github.com/vim/vim/commit/ba6ec182973af726ce9b7b7eb3753fc3a7ae7d1b
| * vim-patch:8.0.0532: test with long directory name fails on Macckelsel2018-06-16
| | | | | | | | | | | | Problem: Test with long directory name fails on Mac. Solution: Skip the test on Mac systems. https://github.com/vim/vim/commit/c77d6757471fa207520586bbdbc1b30af84cf5c8
| * vim-patch:8.0.0531: test with long directory name fails on non-unix systemsckelsel2018-06-16
| | | | | | | | | | | | Problem: Test with long directory name fails on non-unix systems. Solution: Skip the test on non-unix systems. https://github.com/vim/vim/commit/9b81079ddd839a666682f6bdbc24890bf4d1a42c
| * vim-patch:8.0.0530: buffer overflow when 'columns' is very bigckelsel2018-06-16
|/ | | | | | | Problem: Buffer overflow when 'columns' is very big. (Nikolai Pavlov) Solution: Correctly compute where to truncate. Fix translation. (closes vim/vim#1600) https://github.com/vim/vim/commit/658a3a2caf5852d071b6b1be92d9d6614a6208dc
* Merge #8565 from janlazo/vim-8.0.0575Justin M. Keyes2018-06-16
|\
| * vim-patch:8.0.0577: warning for uninitialized variableJan Edmund Lazo2018-06-16
| | | | | | | | | | | | Problem: Warning for uninitialized variable. (John Marriott) Solution: Initialize "indent". https://github.com/vim/vim/commit/97db5541a65e4614f8753af27996c204946061a9
| * vim-patch:8.0.0575: using freed memory when resetting 'indentexpr'Jan Edmund Lazo2018-06-16
| | | | | | | | | | | | | | Problem: Using freed memory when resetting 'indentexpr' while evaluating it. (Dominique Pelle) Solution: Make a copy of 'indentexpr'. https://github.com/vim/vim/commit/a701b3b6f0f06ac0c9fcc75c6c34a1258fc3b1a2
* | Merge #8543 from janlazo/vim-8.0.0596Justin M. Keyes2018-06-16
|\ \
| * | lintJan Edmund Lazo2018-06-13
| | |
| * | vim-patch:8.0.0596: crash when complete() called after complete_add()Jan Edmund Lazo2018-06-13
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash when complete() is called after complete_add() in 'completefunc'. (Lifepillar) Solution: Bail out if compl_pattern is NULL. (closes vim/vim#1668) Also avoid using freed memory. https://github.com/vim/vim/commit/4475b623960671898dac6a72b13a8d140402afa6
* | | Merge #8526 from janlazo/vim-8.0.0451Justin M. Keyes2018-06-16
|\ \ \ | |_|/ |/| |
| * | charset: include option_defs.h for breakat_flagsJan Edmund Lazo2018-06-12
| | |
| * | vim-patch:8.0.0451: some macros are in lower caseJan Edmund Lazo2018-06-12
| | | | | | | | | | | | | | | | | | | | | Problem: Some macros are in lower case. Solution: Make a few more macros upper case. Avoid lower case macros use an argument twice. https://github.com/vim/vim/commit/91acfffc1e6c0d8c2abfb186a0e79a5bf19c3f3f
* | | get_maphash: fix off-by-oneJustin M. Keyes2018-06-14
| | | | | | | | | | | | | | | | | | Patch-by: oni-link <knil.ino@gmail.com> ref: https://github.com/neovim/neovim/pull/6236#discussion_r195113807
* | | Merge pull request #8546 from bfredl/eobBjörn Linse2018-06-14
|\ \ \ | | | | | | | | Add fillchar for EndOfBuffer and check for invalid UTF-8
| * | | fillchars: make checks more strict and improve testsBjörn Linse2018-06-14
| | | |
generated by cgit (git 2.34.1) at 2025-06-26 01:52:41 +0000