aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* main: fix FALLTHROUGH hints (#8623)John Dallahan2018-06-22
| | | | GCC (Clang also?) does not recognize FALLTHROUGH comments when the case is wrapped in braces.
* Merge pull request #7551 from bfredl/setl_bufwinBjörn Linse2018-06-22
|\ | | | | fix copying setl options for buffer currently displayed in another window
| * buffer: fix copying setl options for buffer currently displayed in another ↵Björn Linse2018-06-21
| | | | | | | | | | | | | | | | | | | | | | window vim-patch:8.0.1836: buffer-local window options may not be recent Problem: Buffer-local window options may not be recent if the buffer is still open in another window. Solution: Copy the options from the window instead of the outdated window options. (Bjorn Linse, closes vim/vim#2336) https://github.com/vim/vim/commit/25782a7ff4755daf16c2e1cb5e5f826b13b672ce
* | Merge #8618 'Replace b_changedtick with always-inline functions'Justin M. Keyes2018-06-22
|\ \
| * | *: Replace b_changedtick with new always-inline functionsZyX2018-06-22
| | | | | | | | | Ref #8474
* | | defaults: shortmess+=F (#8619)Justin M. Keyes2018-06-22
|/ / | | | | | | | | | | Because we default to laststatus=2 (statusline is always visible), the :edit message is not useful. ref #6289
* | vim-patch:8.0.0648: possible use of NULL pointerJan Edmund Lazo2018-06-21
| | | | | | | | | | | | | | Problem: Possible use of NULL pointer if buflist_new() returns NULL. (Coverity) Solution: Check for NULL pointer in set_bufref(). https://github.com/vim/vim/commit/fadacf01d0dbcc7a96ef5eee0ad57956eeab04d7
* | vim-patch:8.0.0621: :stag does not respect 'switchbuf'Jan Edmund Lazo2018-06-21
|/ | | | | | | | Problem: The ":stag" command does not respect 'switchbuf'. Solution: Check 'switchbuf' for tag commands that may open a new window. (Ingo Karkat, closes vim/vim#1681) Define macros for the return values of getfile(). https://github.com/vim/vim/commit/8ad80dea089ffeb1a845199c013e9bb4be1cd22e
* vim-patch:8.0.0468: g< after aborting an Ex command (#7941)KunMing Xie2018-06-21
| | | | | | | | Problem: After aborting an Ex command g< does not work. (Marcin Szamotulski) Solution: Postpone clearing scrollback messages to until the command line has been entered. Also fix that the screen isn't redrawn if after g< the command line is cancelled. https://github.com/vim/vim/commit/f2405ed2321da4a879fe0b0703af780fc0432c63
* vim-patch:8.0.{0632,1536} (#8609)Jan Edmund Lazo2018-06-21
| | | | | | | | | | | | | | vim-patch:8.0.0632: the quotestar test is still a bit flaky Problem: The quotestar test is still a bit flaky. Solution: Kill any existing server to make the retry work. Wait for the register to be filled. https://github.com/vim/vim/commit/1c13c0fe3e7b15750464ffbc39a4648aa5c639be vim-patch:8.0.1536: quotestar test is flaky when using the GUI Problem: Quotestar test is flaky when using the GUI. Solution: Add check that the star register arrived at the server. Increase timeouts. https://github.com/vim/vim/commit/791010e648a68490440e202222938c8a93b9d0d3
* vim-patch:8.0.0616: not always setting 'background' correctly after :hi ↵Jan Edmund Lazo2018-06-21
| | | | | | | | | | | | | | Normal (#8606) Problem: When setting the cterm background with ":hi Normal" the value of 'background' may be set wrongly. Solution: Check that the color is less than 16. Don't set 'background' when it was set explicitly. (Lemonboy, closes vim/vim#1710) https://github.com/vim/vim/commit/1615b36b91b094263240d7b555283ddf33208f62 Restore reset_option_was_set(), removed in 419da839e0cbdf6251bc31dc218fa629ccc91b44 ref #8595 ref #8597
* 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
* | 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
* | 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
| * | 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
* / 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
* | 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 :-)~
* | 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
|\ \
| * | 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
generated by cgit (git 2.34.1) at 2025-06-29 03:20:22 +0000