aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* vim-patch:8.0.0{469,581,583} (#8601)Jan Edmund Lazo2018-06-20
| | | | | | | | | | | | | | | | | vim-patch:8.0.0469: compiler warnings on MS-Windows Problem: Compiler warnings on MS-Windows. Solution: Add type casts. (Christian Brabandt) https://github.com/vim/vim/commit/0c0d4eca4dd6252f22ec39f2d561a5e8a68e9a4e vim-patch:8.0.0581: moving folded text is sometimes not correct Problem: Moving folded text is sometimes not correct. Solution: Bail out when "move_end" is zero. (Matthew Malcomson) https://github.com/vim/vim/commit/94be619e30e82d28cadeea5e0766c6f5c321ff8b vim-patch:8.0.0583: fold test hangs on MS-Windows Problem: Fold test hangs on MS-Windows. Solution: Avoid overflow in compare. https://github.com/vim/vim/commit/b11c826ddc459813f9f991cdb8e8736b686a6328
* vim-patch:8.0.0669: CTRL-N at start of the buffer does not work correctly ↵Jan Edmund Lazo2018-06-20
| | | | | | | | (#8600) Problem: In Insert mode, CTRL-N at start of the buffer does not work correctly. (zuloloxi) Solution: Wrap around the start of the buffer. (Christian Brabandt) https://github.com/vim/vim/commit/24a9e348aa88a6c60ae0cdf5c4a777d8c03b08ca
* vim-patch:8.0.0636: when reading the undo file fails may use uninitialized ↵Jan Edmund Lazo2018-06-20
| | | | | | | data (#8599) Problem: When reading the undo file fails may use uninitialized data. Solution: Always clear the buffer on failure. https://github.com/vim/vim/commit/56f2db562ddc6c69026d55360f0cfaacd8adc26a
* Merge #8579 win: cmake: Improvements for building with IDEsJustin M. Keyes2018-06-20
|\
| * cmake: Organize targets into foldersb-r-o-c-k2018-06-17
| | | | | | | | | | | | Enabling CMake's USE_FOLDERS option and adding the FOLDER property to targets allows some IDEs to list the targets in an organized hierarchy of folders.
| * build/win: Add workaround for Windows command length limitb-r-o-c-k2018-06-14
| | | | | | | | | | | | | | | | | | | | When building with the Ninja generator on Windows, it was possible for the external_blobs target to fail when the generated command exceeds the command length limit (8191 characters). To workaround the problem, a CMake script is used to copy the files instead of a shell command. Visual Studio bug report: https://developercommunity.visualstudio.com/content/problem/212207/file-open-cmake-the-command-line-is-too-long.html
| * Revert "makedeps.bat"b-r-o-c-k2018-06-12
| |
| * deps: Build bundled dependencies automatically for IDEsb-r-o-c-k2018-06-10
| | | | | | | | | | | | Environment variables are used to detect when the project is being built from within Clion or Visual Studio, so that the build process can be simplified by automatically building the bundled dependencies for them.
* | Merge #8596 from janlazo/vim-8.0.0615Justin M. Keyes2018-06-20
|\ \
| * | lintJan Edmund Lazo2018-06-19
| | |
| * | vim-patch:8.0.0617: hardcopy test hangs on MS-WindowsJan Edmund Lazo2018-06-19
| | | | | | | | | | | | | | | | | | Problem: Hardcopy test hangs on MS-Windows. Solution: Check the postscript feature is supported. https://github.com/vim/vim/commit/763209c57bf50ae777f9c2929eeea01eff7ae6ee
| * | vim-patch:8.0.0615: using % with :hardcopy wrongly escapes spacesJan Edmund Lazo2018-06-19
| | | | | | | | | | | | | | | | | | Problem: Using % with :hardcopy wrongly escapes spaces. (Alexey Muranov) Solution: Expand % differently. (Christian Brabandt, closes vim/vim#1682) https://github.com/vim/vim/commit/bf15b8d78b22661db8b19d662b62bb9a061cdd37
* | | vim-patch:8.0.0551: the typeahead buffer is reallocated too often (#8598)Jan Edmund Lazo2018-06-20
| | | | | | | | | | | | | | | Problem: The typeahead buffer is reallocated too often. Solution: Re-use the existing buffer if possible. https://github.com/vim/vim/commit/d34f9b1155a6b470e1dc766ff98192f440e7eba7
* | | Merge #8503 from janlazo/vim-8.0.0549Justin M. Keyes2018-06-20
|\ \ \
| * | | vim-patch:8.0.0568: 1gd may hangJan Edmund Lazo2018-06-19
| | | | | | | | | | | | | | | | | | | | | | | | Problem: "1gd" may hang. Solution: Don't get stuck in one position. (Christian Brabandt, closes vim/vim#1643) https://github.com/vim/vim/commit/60402d68da09997cacdeec71fd22c9344f8f40d5
| * | | vim-patch:8.0.0549: no test for the 8g8 commandJan Edmund Lazo2018-06-19
| |/ / | | | | | | | | | | | | | | | Problem: No test for the 8g8 command. Solution: Add a test. (Dominique Pelle, closes vim/vim#1615) https://github.com/vim/vim/commit/395b6bab33e5ed9a0377d7f140e98fd3ab682672
* | | vim-patch:8.0.0546: swap file exists briefly when opening the command window ↵Jan Edmund Lazo2018-06-19
| | | | | | | | | | | | | | | | | | | | | | | | (#8588) Problem: Swap file exists briefly when opening the command window. Solution: Set the noswapfile command modifier before splitting the window. (James McCoy, closes vim/vim#1620) https://github.com/vim/vim/commit/3bab93998d01a01b7f2a071fa3b8054bb0094625
* | | Merge #8576 from justinmk/startup-empty-stdinJustin M. Keyes2018-06-19
|\ \ \ | |/ / |/| |
| * | startup: delete empty stdin buffer if other files were openedJustin M. Keyes2018-06-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | DWIM: avoid empty buffer 1 when stdin was empty. If other files were specified at startup, we assume that stdin is only accidentally not-a-TTY: user did not intend to send text from it. ref #8560 ref #8561
| * | startup: go to buffer 2 if stdin is emptyJustin M. Keyes2018-06-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If stdin is not a TTY we read it into buffer 1, as text. But if the stdin pipe is empty, Nvim was most likely invoked for some other reason. DWIM: select buffer 2 (if it exists). Example: echo file1 | xargs nvim closes #8560 closes #8561 ref https://github.com/equalsraf/neovim-qt/issues/417
* | | vim-patch:8.0.0537: illegal memory access with :z and large count (#8592)Jan Edmund Lazo2018-06-19
| | | | | | | | | | | | | | | | | | Problem: Illegal memory access with :z and large count. Solution: Check for number overflow, using long instead of int. (Dominique Pelle, closes vim/vim#1612) https://github.com/vim/vim/commit/fa0ad0bb0b4255e64ebcf9269d60a942e0ae7ff9
* | | Merge pull request #8593 from jamessan/vim-patch-printf-fixJames McCoy2018-06-19
|\ \ \ | |/ / |/| | vim-patch: Replace shell variables in printf with formatted args
| * | 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
|\ \
generated by cgit (git 2.34.1) at 2025-06-26 01:51:26 +0000