aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* vim-patch:8.0.1438: filetype detection test not updated for changeJan Edmund Lazo2018-10-27
| | | | | | Problem: Filetype detection test not updated for change. Solution: Update the test. https://github.com/vim/vim/commit/0479e910c423d71e2b96bc721feffad5808e767a
* Merge pull request #9149 from bfredl/virt_culBjörn Linse2018-10-25
|\ | | | | screen: show virt_text when 'cursorline' is set
| * screen.c: remove redundant wp->w_hl_attr_normalBjörn Linse2018-10-25
| |
| * screen: fix glitches with nvim_buf_set_virtual_textBjörn Linse2018-10-25
| | | | | | | | | | - virtual text disappeared when 'cursorline' was set - virtual text was shifted when emtpy line was visually selected.
* | UI: add missing redraw after enter_tabpageBjörn Linse2018-10-25
|/ | | | | | | redraw_all_later() isn't guaranteed to update must_redraw after switching tab, we must do it ourselves. fixes #9152
* Merge #9145 'CI, nodejs fixes'Justin M. Keyes2018-10-22
|\
| * auevents.lua: keep events in alphabetical orderJustin M. Keyes2018-10-22
| |
* | ui: disable clearing almost everywhereBjörn Linse2018-10-22
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid clearing the screen in most situations. NOT_VALID should be equivalent to CLEAR unless some external force messed up the terminal, for these situations <c-l> and :mode will still clear the screen. Also eliminate some obsolete code in screen.c, that dealt with that in vim drawing window 1 can mess up window 2, but this never happens in nvim. But what about slow terminals? There is two common meanings in which a terminal is said to be "slow": Most commonly (and in the sense of vim:s nottyfast) it means low bandwidth for sending bytes from nvim to the terminal. If the screen is very similar before and after the update_screen(CLEAR) this change should reduce bandwidth. If the screen is quite different, but there is no new regions of contiguous whitespace, clearing doesn't reduce bandwidth significantly. If the new screen contains a lot of whitespace, it will depend of if vsplits are used or not: as long as there is no vsplits, ce is used to cheaply clear the rest of the line, so full-screen clear is not needed to reduce bandwith. However a left vsplit currently needs to be padded with whitespace all the way to the separator. It is possible ec (clear N chars) can be used to reduce bandwidth here if this is a problem. (All of this assumes that one doesn't set Normal guibg=... on a non-BCE terminal, if you do you are doomed regardless of this change). Slow can also mean that drawing pixels on the screen is slow. E-ink screens is a recent example. Avoiding clearing and redrawing the unchanged part of the screen will always improve performance in these cases.
* fix warning: null arg passed to 'nonnull' paramJustin M. Keyes2018-10-21
| | | | Found by clang scan-build 5.0
* fix warning: null arg passed to 'nonnull' paramJustin M. Keyes2018-10-21
| | | | Found by clang scan-build 5.0
* fix warning: "Assigned value is garbage"Justin M. Keyes2018-10-21
| | | | | | | clang scan-build noticed that find_command() may bitmask `eap->flags`. cmd_can_preview() only uses `ea.cmdidx`, but let's fix the warning... Found by clang scan-build 5.0
* fix warning: "Dead assignment"Justin M. Keyes2018-10-21
| | | | | | | `tv` is passed to the TYPVAL_ENCODE_CONV_FUNC_BEFORE_* macros, which don't appear to actually use that parameter. Found by clang scan-build 5.0
* fix warning: null pointer dereferenceJustin M. Keyes2018-10-21
| | | | Found by clang scan-build 5.0
* fix warning: garbage/uninitialized valueJustin M. Keyes2018-10-21
| | | | | | | According to clang scan-build, `fromcol` could be uninitialized at line 2645. Found by clang scan-build 5.0
* fix warning: "Uninitialized argument"Justin M. Keyes2018-10-21
| | | | | | clang scan-build thinks os_system() could set `do_profiling` flag. Found by clang scan-build 5.0
* Merge pull request #9144 from bfredl/ui_event_compatBjörn Linse2018-10-21
|\ | | | | api/ui: verify compatibility of UI events
| * api/ui: verify compatibility of UI eventsBjörn Linse2018-10-21
| |
* | tui.c: Fix ext.set_underline_color for !has_colon_rgbJustin M. Keyes2018-10-20
| | | | | | | | PVS/V523: The 'then' statement is equivalent to the 'else' statement.
* | screen.c: Fix PVS/V560: condition is always falseJustin M. Keyes2018-10-20
|/
* Merge #9086 'vim-patch:8.1.0448'Justin M. Keyes2018-10-18
|\
| * test/old: stub CanRunVimInTerminal()Justin M. Keyes2018-10-16
| |
| * vim-patch:8.1.0448: cursorline not removed when using 'cursorbind'Justin M. Keyes2018-10-16
| | | | | | | | | | | | Problem: Cursorline not removed when using 'cursorbind'. (Justin Keyes) Solution: Store the last cursor line per window. (closes vim/vim#3488) https://github.com/vim/vim/commit/4a5abbd6138240d109278fe1f0b45489d22f712d
* | Merge #9124 'vim-patch:8.0.1672'Justin M. Keyes2018-10-17
|\ \
| * | vim-patch:8.0.1672: error during completion causes command to be cancelledJan Edmund Lazo2018-10-13
| | | | | | | | | | | | | | | | | | Problem: Error during completion causes command to be cancelled. Solution: Reset did_emsg before waiting for another character. (Tom M.) https://github.com/vim/vim/commit/72532d354e699f1cceec34c0b08e1de4d3ea9641
* | | vim-patch:8.0.1067: try/catch in timer does not prevent it from being stoppedJan Edmund Lazo2018-10-16
| | | | | | | | | | | | | | | | | | | | | Problem: Using try/catch in timer does not prevent it from being stopped. Solution: Reset the exception context and use did_emsg instead of called_emsg. https://github.com/vim/vim/commit/e723c42836d971180d1bf9f98916966c5543fff1
* | | vim-patch:8.0.0670: can't use input() in a timer callbackJan Edmund Lazo2018-10-15
| |/ |/| | | | | | | | | | | Problem: Can't use input() in a timer callback. (Cosmin Popescu) Solution: Reset vgetc_busy and set timer_busy. (Ozaki Kiichi, closes vim/vim#1790, closes vim/vim#1129) https://github.com/vim/vim/commit/1e8e14552e0cc8881411eb8fbe39a654dae42554
* | vim-patch:8.1.0476: memory leaks in test_escaped_glob (#9127)Jan Edmund Lazo2018-10-14
|/ | | | | Problem: Memory leaks in test_escaped_glob. Solution: Avoid failure when running the shell, use the sandbox. https://github.com/vim/vim/commit/a2aad028305c306ecf33e0fd720fe1ed98596371
* Merge #9095 'CI/travis/macOS: fix missing pip3'Justin M. Keyes2018-10-13
|\
| * test: adjust timer testsJustin M. Keyes2018-10-13
| | | | | | | | | | Timer tests are less reliable on Travis CI macOS 10.12 (most egregious). Also somewhat on 10.13.
* | memline: process_still_running is boolJan Edmund Lazo2018-10-13
| |
* | vim-patch:8.1.0473: user doesn't notice file does not exist when swap file doesJan Edmund Lazo2018-10-13
|/ | | | | | | Problem: User doesn't notice file does not exist when swap file does. Solution: Add a note that the file cannot be found. Make the "still running" notice stand out. https://github.com/vim/vim/commit/d6105cb4085ad166910897a640693d3bada603e1
* Merge pull request #9121 from bfredl/virt_invalidBjörn Linse2018-10-13
|\ | | | | API: make nvim_buf_set_virtual_text handle invalid chars
| * api: make nvim_buf_set_virtual_text handle invalid charsBjörn Linse2018-10-13
| | | | | | | | | | Clients are supposed to supply only valid text, but if it is invalid, translate it rather than messing up the screen
* | vim-patch:8.0.1590: padding in list type wastes memory (#9119)Jan Edmund Lazo2018-10-13
| | | | | | | | | | | | Problem: Padding in list type wastes memory. Solution: Reorder struct members to optimize padding. (Dominique Pelle, closes vim/vim#2704) https://github.com/vim/vim/commit/1a840240376f2858d489736f9eed6d2975225fdf
* | signs: Add "numhl" argument #9113Reto Schnyder2018-10-13
|/ | | | | close #9113 ref #9040
* Merge pull request #8968 from ckelsel/vim-8.0.0685James McCoy2018-10-12
|\ | | | | [RFC] vim-patch:8.0.0685
| * vim-patch:8.0.0685: when conversion fails written file may be truncatedckelsel2018-10-12
| | | | | | | | | | | | | | | | Problem: When making backups is disabled and conversion with iconv fails the written file is truncated. (Luo Chen) Solution: First try converting the file and write the file only when it did not fail. (partly by Christian Brabandt) https://github.com/vim/vim/commit/e6bf655bc4de1b7f4586e1f5c2fc4978141c3aa3
* | vim-patch:8.0.1489: there is no easy way to get the global directory (#9109)Jan Edmund Lazo2018-10-12
| | | | | | | | | | | | | | Problem: There is no easy way to get the global directory, esp. if some windows have a local directory. Solution: Make getcwd(-1) return the global directory. (Andy Massimino, closes vim/vim#2606) https://github.com/vim/vim/commit/5459129af2a832a027a1e7ca2d6177c26647d64f
* | Merge #8902 'doc'Justin M. Keyes2018-10-12
|\ \ | |/ |/|
| * doc: xdg, MAINTAIN.md, channel-id, job controlJustin M. Keyes2018-10-11
| | | | | | | | - tutor: emphasize K
* | Merge #9106 from janlazo/vim-8.0.1837Justin M. Keyes2018-10-11
|\ \ | | | | | | vim-patch:8.0.1837
| * | lintJan Edmund Lazo2018-10-10
| | |
| * | vim-patch:8.0.1837: one character cmdline abbreviation not triggered after '<,'>Jan Edmund Lazo2018-10-10
| |/ | | | | | | | | | | Problem: One character cmdline abbreviation not triggered after '<,'>. Solution: Skip over the special range. (Christian Brabandt, closes vim/vim#2320) https://github.com/vim/vim/commit/5e3423d192bfa502c6704f731fa2ec6821f9a2f0
* / vim-patch:8.0.1777: cannot cleanup before loading another colorscheme (#9104)Jan Edmund Lazo2018-10-11
|/ | | | | Problem: Cannot cleanup before loading another colorscheme. Solution: Add the ColorSchemePre autocommand event. https://github.com/vim/vim/commit/60a68362aa73f4a6cb534688978f9dc2b16e60fe
* vim-patch:8.1.0468: MS-Windows: filter command with pipe character fails (#9101)Jan Edmund Lazo2018-10-10
| | | | | | | Problem: MS-Windows: Filter command with pipe character fails. (Johannes Riecken) Solution: Find the pipe character outside of quotes. (Yasuhiro Matsumoto, closes vim/vim#1743, closes vim/vim#3523) https://github.com/vim/vim/commit/0664089eccec1083dd04ef2255856fb34ce62f15
* lintJan Edmund Lazo2018-10-09
|
* vim-patch:8.0.1423: error in return not caught by try/catchJan Edmund Lazo2018-10-09
| | | | | | Problem: Error in return not caught by try/catch. Solution: Call update_force_abort(). (Yasuhiro Matsomoto, closes vim/vim#2483) https://github.com/vim/vim/commit/fabaf753e26df5a89a854673d14c15a1fa6b321a
* Merge pull request #9079 from bfredl/tui_cursorBjörn Linse2018-10-09
|\ | | | | TUI cursor fixes: avoid memory errors after resize with invalid cursor position
| * TUI: delete "first-row" workaround after resizeBjörn Linse2018-10-06
| | | | | | | | | | This was caused by cursor position being invalid right after tui_grid_resize, which is now fixed
| * TUI: always use safe cursor movement after resizeBjörn Linse2018-10-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The old code could lead to a memory error in the following situation: 0. The previous cursor position was row 50 since before, on a grid larger than 50 rows. 1. grid_resize changes the grid height to 40, and invalidly assumes the resize moved the physical cursor to row 0 2. Some event used a operation that could move the cursor (such as clear), and then reset the cursor to the "true" position row 50 (pointless after #8221, but I forgot to remove it) 3. raw_line/cheap_to_print is invoked, and tries to inspect the grid at row 50 (memory error) 4. grid_cursor_goto would have been called at this point, and set a valid cursor position 0-39.
generated by cgit (git 2.34.1) at 2025-08-08 20:14:43 +0000