aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* | Merge #9472 from justinmk/pvs-warnings2Justin M. Keyes2019-01-10
|\ \
| * | CMake: Feature-detect __builtin_{add,sub}_overflowJustin M. Keyes2019-01-09
| | |
| * | PVS/V1028: cast operands, not the resultJustin M. Keyes2019-01-09
| | |
| * | assert.h: Check overflow with STRICT_ADD, STRICT_SUBJustin M. Keyes2019-01-09
| | |
* | | vim-patch:8.1.0648: custom operators can't act upon forced motionPedro L. Ramos2019-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Custom operators can't act upon a forced motion. (Christian Wellenbrock) Solution: Add the forced motion to the mode() result. (Christian Brabandt, closes vim/vim#3490) https://github.com/vim/vim/commit/5976f8ff00efcb3e155a89346e44f2ad43d2405a closes #8667 closes #9476 Christian Wellenbrock: > For (most) built in text objects it's possible to force operation on > them to be linewise, for example by using `dVab` (`:h o_V`, > `motion_force`). When using custom text objects (defined as mappings > by plugins for example), this doesn't currently work. > > Example: > > onoremap x viw > > Open a file with a few lines each containing some words. With the > cursor on any word, try: > > 1. `dw` (builtin) deletes some characters > 2. `dVw` (builtin) deletes linewise > 3. `dx` (from mapping) deletes some characters > 4. `dVx` (from mapping) deletes some characters, but should delete > linewise ref: https://github.com/wellle/targets.vim/issues/214 ref: https://gitter.im/neovim/neovim?at=5b379ff7f1664406610e7483
* | | Merge pull request #9479 from bfredl/redrawsignBjörn Linse2019-01-09
|\ \ \ | | | | | | | | screen: remove ad-hoc code path for redrawing signs.
| * | | bufhl: simplify redraw logicBjörn Linse2019-01-09
| | | | | | | | | | | | | | | | | | | | using changed_lines_buf was technically incorrect, as the buffer wasn't modififed.
| * | | remove dead argument of redrawWinlineBjörn Linse2019-01-09
| | | |
| * | | screen: avoid redrawing windows immediately when debug signs are placed.Björn Linse2019-01-09
| | | |
* | | | Merge pull request #9445 from bfredl/pum_apiBjörn Linse2019-01-09
|\ \ \ \ | | | | | | | | | | API: select items in popupmenu
| * | | | api: select items in popupmenuBjörn Linse2019-01-09
| |/ / /
* / / / win/TUI: fix text overrides line numbers #9474erw72019-01-09
|/ / / | | | | | | fixes #9461
* / / API: don't directly call update_screen() in API functionsBjörn Linse2019-01-08
|/ / | | | | | | | | | | | | | | | | There is no need to call update_screen() directly in an API function, mode input processing invokes update_screen() as needed. And if the API call is done in a context where redraw is disabled, then redraw is disabled for a reason. A lot of API functions are of equal semantical strength (nvim_call_function and nvim_execute_lua can also do whatever, nvim_command is not special), this inconsistency has no purpose.
* | vim-patch:8.1.0700: using "gt" sometimes does not redraw a tab (#9464)Justin M. Keyes2019-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Using "gt" sometimes does not redraw a tab. (Jason Franklin) Solution: Always set must_redraw in redraw_all_later(). https://github.com/vim/vim/commit/04b4e1a42409f81d65ae4801ac867dc0bba3d7b8 ref https://github.com/vim/vim/commit/bf3250a8ad39797e3ccdac82d20c6f19533419e4#r31852304 > I fixed it in a more general way, in that if we don't find a window > that doesn't have the redraw type set it, then it will not set > must_redraw, even though that's clearly intended. ref #9152 ref #9155 NA patches: vim-patch:8.1.0698 vim-patch:8.1.0699
* | lintJan Edmund Lazo2019-01-07
| |
* | vim-patch:8.1.0696: when test_edit fails 'insertmode' may not be resetJan Edmund Lazo2019-01-06
| | | | | | | | | | | | | | | | | | Problem: When test_edit fails 'insertmode' may not be reset and the next test may get stuck. (James McCoy) Solution: Always reset 'insertmode' after executing a test. Avoid that an InsertCharPre autocommand or a 'complete' function can change the state. (closes vim/vim#3768) https://github.com/vim/vim/commit/8ad16da7290190f55f88073d5586dfe133fddf45
* | Merge #9459 from janlazo/vim-8.1.0677Justin M. Keyes2019-01-06
|\ \
| * | vim-patch:8.1.0685: get_buf_tv() is named inconsistentlyJan Edmund Lazo2019-01-05
| | | | | | | | | | | | | | | | | | Problem: get_buf_tv() is named inconsistently. Solution: Rename it to tv_get_buf(). (Yegappan Lakshmanan, closes vim/vim#3759) https://github.com/vim/vim/commit/f2d79fa92d0ed90732f52dd88da4ad66c2c5ce13
| * | vim-patch:8.1.0687: sentence text object in Visual mode is not testedJan Edmund Lazo2019-01-05
| | | | | | | | | | | | | | | | | | Problem: Sentence text object in Visual mode is not tested. Solution: Add a test. (Dominique Pelle, closes vim/vim#3758) https://github.com/vim/vim/commit/6d3a1940be9d3f2b079f81baa9b19f839289b69e
| * | vim-patch:8.1.0677: look-behind match may use the wrong line numberJan Edmund Lazo2019-01-05
| | | | | | | | | | | | | | | | | | | | | Problem: Look-behind match may use the wrong line number. (Dominique Pelle) Solution: Use the line number in regsave instead of the one in behind_pos, we may be looking at the previous line. (closes vim/vim#3749) https://github.com/vim/vim/commit/866f3558141aa68862aa2fedbb7747bf2365e838
* | | Merge #8604 from janlazo/vim-8.0.0286Justin M. Keyes2019-01-06
|\ \ \
| * | | vim-patch:8.1.0683: spell highlighting does not always endJan Edmund Lazo2019-01-05
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Spell highlighting does not always end. (Gary Johnson) Solution: Also reset char_attr when spell errors are highlighted. https://github.com/vim/vim/commit/637532b3c0ca41f0de7e90b6f3c0defe06369372
| * | | vim-patch:8.1.0674: leaking memory when updating a single lineJan Edmund Lazo2019-01-05
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Leaking memory when updating a single line. Solution: Do not call start_search_hl() twice. https://github.com/vim/vim/commit/6d5b4f566a2a50c1de7300336e9e4f5e761500a8
| * | | vim-patch:8.0.0286: not always redrawing after screen resizeJan Edmund Lazo2019-01-05
| |/ / | | | | | | | | | | | | | | | | | | | | | Problem: When concealing is active and the screen is resized in the GUI it is not immediately redrawn. Solution: Use update_prepare() and update_finish() from update_single_line(). https://github.com/vim/vim/commit/c10f0e7cb0f35eea489b038e56c87b818eee975b
* | | PVS/V501: diff.c: silence warningJustin M. Keyes2019-01-05
| | | | | | | | | | | | | | | | | | False positive: vim_fgets has side effects. ref 8586770e1fd8
* | | PVS/V547: Expression is always falseJustin M. Keyes2019-01-05
| | |
* | | PVS/V1026: normal.c: signed integer overflowJustin M. Keyes2019-01-05
| | | | | | | | | | | | | | | > V1026 The 'curwin->w_curswant' variable is incremented in the loop. > Undefined behavior will occur in case of signed integer overflow.
* | | PVS/V547: indent.c: xmalloc() never returns NULLJustin M. Keyes2019-01-05
|/ /
* | PVS/V547: window.c: Expression is always trueJustin M. Keyes2019-01-04
| |
* | PVS/V547: viml/parser/expressions.c: Expression is always trueJustin M. Keyes2019-01-04
| |
* | PVS/V751: tui.c, Parameter is not usedJustin M. Keyes2019-01-04
| | | | | | | | | | False positive. Documentation for grid_scroll says "`cols` is always zero, reserved for future use".
* | PVS/V535: shada.c: variable reassigned in inner loopJustin M. Keyes2019-01-04
| | | | | | | | | | False positive: `i` is intentionally, temporarily reassigned. See a70fde1b4585 #9425
* | PVS/V547: diff.c: xmalloc() never returns NULLJustin M. Keyes2019-01-04
| | | | | | | | | | | | Normally we consider OOM to be fatal, but the diff module has extra functionality to handle OOM in case huge files are compared. Use try_malloc instead of xmalloc in that case.
* | PVS/V547: diff.c: Expression is always trueJustin M. Keyes2019-01-04
| |
* | PVS/V501: diff.c: silence warningJustin M. Keyes2019-01-04
| | | | | | | | False positive: vim_fgets has side effects.
* | Visual: highlight char-at-cursorJustin M. Keyes2019-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Decide whether to highlight the visual-selected character under the cursor, depending on 'guicursor' style: - Highlight if cursor is blinking or non-block (vertical, horiz). - Do NOT highlight if cursor is non-blinking block. Traditionally Vim's visual selection does "reverse mode", which perhaps conflicts with the non-blinking block cursor. But 'guicursor' defaults to a vertical bar for selection=exclusive, and this confuses users who expect to see the text highlighted. closes #8983
* | remove check_visual_highlight()Justin M. Keyes2019-01-04
| | | | | | | | This check is meaningless, we assume the terminal supports reverse-mode.
* | vim-patch:8.1.0653: arglist test fails on MS-windowsJan Edmund Lazo2019-01-03
| | | | | | | | | | | | Problem: Arglist test fails on MS-windows. Solution: Only use a file name with a double quote on Unix. https://github.com/vim/vim/commit/3de8c2d1f027410db6a06f0fcd3355d96c8b8596
* | vim-patch:8.1.0651: :args \"foo works like :args without argumentJan Edmund Lazo2019-01-03
| | | | | | | | | | | | Problem: :args \"foo works like :args without argument. Solution: Fix check for empty argument. (closes vim/vim#3728) https://github.com/vim/vim/commit/2ac372ccee1af6f9fa105bf2648d5e4efa554236
* | Merge #9425 'build: enable -Wshadow'Justin M. Keyes2019-01-03
|\ \
| * | UGRID_FOREACH_CELL: avoid shadowed variablesJustin M. Keyes2019-01-02
| | |
| * | build: enable -WshadowJustin M. Keyes2019-01-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note about shada.c: - shada_read_next_item_start was intentionally shadowing `unpacked` and `i` because many of the macros (e.g. ADDITIONAL_KEY) implicitly depended on those variable names. - Macros were changed to parameterize `unpacked` (but not `i`). Macros like CLEAR_GA_AND_ERROR_OUT do control-flow (goto), so any other approach is messy.
* | | TUI: Do not disable BCE for builtin terminfos (#9443)Justin M. Keyes2019-01-02
|/ / | | | | | | | | | | | | | | | | Remove this vestigial hack from #7624. Since 5a0d0286ff4d we blacklist BCE more surgically. And patch_terminfo_bugs() is the more appropriate place for that. ref 5749ecaf228f4a963a4e96ada831f902c73a1e80 ref #4210 #4421 #7035 #7337 #7381 #7425 #7618
* | vim-patch:8.0.0251: not easy to select Python 2 or 3 (#9173)David Jimenez2019-01-02
| | | | | | | | | | | | Problem: It is not so easy to write a script that works with both Python 2 and Python 3, even when the Python code works with both. Solution: Add 'pyxversion', :pyx, etc. (Marc Weber, Ken Takata) https://github.com/vim/vim/commit/f42dd3c3901ea0ba38e67a616aea9953cae81b8d
* | popupmenu: fix positioning with vsplitsBjörn Linse2019-01-01
| |
* | multigrid: do all adjustment in screen.cBjörn Linse2019-01-01
| | | | | | | | | | Adjustment will get more complex with floats, tabgrid etc, so make it into a function.
* | TUI: Konsole DECSCUSR fixup (#9423)Justin M. Keyes2018-12-31
| | | | | | | | | | | | Apparently Konsole's terminfo is still broken. ref #9364 closes #9420
* | multigrid: rename grid->ScreenLines and other grid arraysBjörn Linse2018-12-31
| |
* | multigrid: API version bumpBjörn Linse2018-12-31
| |
* | multigrid: rename to grid.row_offset and grid.requested_rowsBjörn Linse2018-12-31
| |
generated by cgit (git 2.34.1) at 2025-10-02 02:36:40 +0000