aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/screen.c
Commit message (Collapse)AuthorAge
...
* | Invalidate grid on allction when in ext_multigridVille Hakulinen2020-09-06
| | | | | | | | | | | | When in ext_multigrid mode, after a window gets resized neovim wont currently send all the needed events fill the window's blank space and thus' UIs will have invalid grid state.
* | extmark: refiy "Decoration" abstractionBjörn Linse2020-09-03
|/ | | | one very important thought
* Merge pull request #12621 from Shougo/vim-8.1.1564Matthieu Coudron2020-08-09
|\ | | | | [RDY] vim-patch:8.1.1564, 1570, 1623, 1712 : sign column takes up space
| * vim-patch:8.1.1564: sign column takes up spaceShougo Matsushita2020-07-23
| | | | | | | | | | | | | | Problem: Sign column takes up space. (Adam Stankiewicz) Solution: Optionally put signs in the number column. (Yegappan Lakshmanan, closes vim/vim#4555, closes vim/vim#4515) https://github.com/vim/vim/commit/394c5d8870b15150fc91a4c058dc571fd5eaa97e
| * vim-patch:8.1.1712: signs in number column cause text to be misalignederw72020-07-23
| | | | | | | | | | | | Problem: Signs in number column cause text to be misaligned. Solution: Improve alignment. (Yasuhiro Matsumoto, closes vim/vim#4694) https://github.com/vim/vim/commit/d6bcff457799e491c3d27880858ec08e758e1849
| * vim-patch:8.1.1623: display wrong with signs in narrow number columnerw72020-07-23
| | | | | | | | | | | | | | Problem: Display wrong with signs in narrow number column. Solution: Increase the numbercolumn width if needed. (Yegappan Lakshmanan, closes vim/vim#4606) https://github.com/vim/vim/commit/e4b407f536ba8bd007152649a347a95320d80fce
| * vim-patch:8.1.1564: sign column takes up spaceShougo Matsushita2020-07-23
| | | | | | | | | | | | | | Problem: Sign column takes up space. (Adam Stankiewicz) Solution: Optionally put signs in the number column. (Yegappan Lakshmanan, closes vim/vim#4555, closes vim/vim#4515) https://github.com/vim/vim/commit/394c5d8870b15150fc91a4c058dc571fd5eaa97e
* | vim-patch:8.2.1004: line numbers below filler lines not always updatedJan Edmund Lazo2020-08-02
| | | | | | | | | | | | | | Problem: Line numbers below filler lines not always updated. Solution: Don't break out of the win_line() loop too early. (Christian Brabandt, closes vim/vim#6294, closes vim/vim#6138) https://github.com/vim/vim/commit/511feec6f0a9e954f1d7353425fa51232b1a8e88
* | vim-patch:8.1.2172: spell highlight is wrong at start of the lineJan Edmund Lazo2020-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) https://github.com/vim/vim/commit/7751d1d1a3d447d0d48f57f34e0da9f7c6ac433d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue #12104 is fixed. Skip the test for the following reasons: - unknown regression caused by https://github.com/neovim/neovim/issues/12104 - cannot revert failing test from https://github.com/neovim/neovim/commit/ed0d135247790f67ead7f1a8c21a020790e80a74
* | terminal: fix terminal attribute overflowerw72020-07-29
|/ | | | fixes #11548
* vim-patch:8.2.0766: display error when using 'number' and 'breakindent'Jan Edmund Lazo2020-05-21
| | | | | | | Problem: Display error when using 'number' and 'breakindent'. Solution: Adjust extra spaces in the first row. (Ken Takata, closes vim/vim#6089, closes vim/vim#5986) https://github.com/vim/vim/commit/e882f7a73c8fa48707de71035eb0a7ccc6ac8548
* vim-patch:8.2.0309: window-local values have confusing nameJan Edmund Lazo2020-05-11
| | | | | | Problem: Window-local values have confusing name. Solution: Rename w_p_bri* to w_briopt_*. https://github.com/vim/vim/commit/b81f56fb57c87a7490dd79908c257437d1958447
* vim-patch:8.2.0308: 'showbreak' does not work for a very long lineJan Edmund Lazo2020-05-11
| | | | | | | Problem: 'showbreak' does not work for a very long line. (John Little) Solution: Check whether 'briopt' contains "sbr". (Ken Takata, closes vim/vim#5523, closes vim/vim#5684) https://github.com/vim/vim/commit/1aa76b8fd06c278fe36c39b0bbe7233c775d7423
* vim-patch:8.2.0681: pattern for 'hlsearch' highlighting may leakJan Edmund Lazo2020-05-03
| | | | | | | Problem: Pattern for 'hlsearch' highlighting may leak. (Dominique Pelle) Solution: Call end_search_hl() to make sure the previous pattern is freed. (closes vim/vim#6028) https://github.com/vim/vim/commit/0b6849e9e302286e906d97e4ba017dd66561a9ce
* vim-patch:8.0.1123: cannot define a toolbar for a windowJan Edmund Lazo2020-04-26
| | | | | | | | | | Problem: Cannot define a toolbar for a window. Solution: Add a window-local toolbar. https://github.com/vim/vim/commit/1b9645de3c05f37b5c30e78f999351b0cf486ade "WinBar" code in "screen.c" was not ported. Fix https://github.com/neovim/neovim/issues/11513#issuecomment-562012827
* vim-patch:8.2.0464: typos and other small problemsJan Edmund Lazo2020-04-13
| | | | | | Problem: Typos and other small problems. Solution: Fix the typos. Add missing file to distribution. https://github.com/vim/vim/commit/2d9d409ad4fab1ae7ceaecc0ef0e9b511d868374
* vim-patch:8.1.1745: compiler warning for unused argumentJan Edmund Lazo2020-04-13
| | | | | | Problem: Compiler warning for unused argument. Solution: Add UNUSED. Change comments to new style. https://github.com/vim/vim/commit/1f164b19685d8ad709b11f3f1933685469251e30
* vim-patch:8.1.2378: using old C style commentsJan Edmund Lazo2020-04-12
| | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/5d18efecfd6c45d69f55268948a22cd0465bb955
* api/ui: win_viewport event for visible range and cursor position in windowBjörn Linse2020-04-01
|
* Merge pull request #11716 from teto/folds_auto_backupMatthieu Coudron2020-03-02
|\ | | | | [RFC] foldcolumn autowidth
| * foldcolumn: allow auto:XMatthieu Coudron2020-02-29
| | | | | | | | | | | | | | | | Similar to signcolumn, allow foldcolumn to adapt itself to the number of folds. Regression: vim supports a maximum fdc of 12, this limits it to 9.
* | vim-patch:8.1.1642: may use uninitialized variableJan Edmund Lazo2020-03-01
|/ | | | | | Problem: May use uninitialized variable. (Patrick Palka) Solution: Initialize variables earlier. (closes vim/vim#4623) https://github.com/vim/vim/commit/ec572ad6a6cb0d4e71901951a70a4f038d48cb17
* vim-patch:8.1.1868: multi-byte chars in 'listchars' fail with 'linebreak' setJan Edmund Lazo2020-02-20
| | | | | | | | Problem: Multibyte characters in 'listchars' don't work correctly if 'linebreak' is also enabled. (Martin Tournoij) Solution: Make it work correctly. (Christian Brabandt, closes vim/vim#4822, closes vim/vim#4812) https://github.com/vim/vim/commit/69cbbecf548f390197259ca30cfe147c3e59ce5a
* treesitter: cleanup some luahl stuffBjörn Linse2020-02-10
|
* treesitter: use internal "decorations" bufferBjörn Linse2020-02-10
|
* Merge pull request #11755 from bfredl/qf_msgBjörn Linse2020-01-26
|\ | | | | screen: add missing redraws after a message
| * screen: add missing redraws after a messageBjörn Linse2020-01-26
| |
* | vim-patch:8.1.2245: third character of 'listchars' tab shows in wrong placeJan Edmund Lazo2020-01-24
| | | | | | | | | | | | | | Problem: Third character of 'listchars' tab shows in wrong place when 'breakindent' is set. Solution: Set c_final to NUL. (Naruhiko Nishino, closes vim/vim#5165) https://github.com/vim/vim/commit/2f7b7b1e123d505637d21e0df28eb9e92667479c
* | vim-patch:8.2.0146: wrong indent when 'showbreak' and 'breakindent' are setJan Edmund Lazo2020-01-23
|/ | | | | | | Problem: Wrong indent when 'showbreak' and 'breakindent' are set and 'briopt' includes "sbr". Solution: Reset "need_showbreak" where needed. (Ken Takata, closes vim/vim#5523) https://github.com/vim/vim/commit/dfede9a70b3136988a8f262742101ad5cb98f46d
* shed biking: it's always extmarks, never marks extendedBjörn Linse2020-01-20
|
* Merge pull request #11715 from teto/fix_fillcharMatthieu Coudron2020-01-20
|\ | | | | [RDY] fillchars: fix display on closed fold
| * fillchars: fix display on closed foldMatthieu Coudron2020-01-14
| | | | | | | | | | | | | | | | The rollback of the last written symbol was not thorough, hence confusing the code later on and causing a buggy display. To reproduce, use `set fillchars+=foldopen:▾,foldsep:│` and close a fold. Foldcolumn should display a glitch.
* | vim-patch:8.1.2031: cursor position wrong when resizing and using concealJan Edmund Lazo2020-01-19
| | | | | | | | | | | | | | Problem: Cursor position wrong when resizing and using conceal. Solution: Set the flags that the cursor position is valid when setting the row and column during redrawing. (closes vim/vim#4931) https://github.com/vim/vim/commit/5babc6e858afbfa54aa0e203a64b9c70175487b7
* | extmarks/bufhl: reimplement using new marktree data structureBjörn Linse2020-01-16
|/ | | | | | | | | | | | | | | | | | | | Add new "splice" interface for tracking buffer changes at the byte level. This will later be reused for byte-resolution buffer updates. (Implementation has been started, but using undocumented "_on_bytes" option now as interface hasn't been finalized). Use this interface to improve many edge cases of extmark adjustment. Changed tests indicate previously incorrect behavior. Adding tests for more edge cases will be follow-up work (overlaps on_bytes tests) Don't consider creation/deletion of marks an undoable event by itself. This behavior was never documented, and imposes complexity for little gain. Add nvim__buf_add_decoration temporary API for direct access to the new implementation. This should be refactored into a proper API for decorations, probably involving a huge dict. fixes #11598
* screen: fix pvs/v1048Jan Edmund Lazo2019-12-29
|
* vim-patch:8.0.1491: the minimum width of the popup menu is hard codedJan Edmund Lazo2019-12-29
| | | | | | | Problem: The minimum width of the popup menu is hard coded. Solution: Add the 'pumwidth' option. (Christian Brabandt, James McCoy, closes vim/vim#2314) https://github.com/vim/vim/commit/a8f04aa275984183bab5bb583b128f38c64abb69
* fillchars: adding foldopen, foldsep, foldcloseMatthieu Coudron2019-12-25
| | | | | You can try it with set fillchars+=foldopen:▾,foldsep:│,foldclose:▸
* tree-sitter: implement query functionality and highlighting prototype ↵Björn Linse2019-12-22
| | | | [skip.lint]
* win_line: Fix crash with 'rightleft' in :terminal #11460erw72019-11-28
| | | | | | | | | | | | | | | | fixes #11438 Backtrace: 0 schar_from_ascii ( p=0x801cc9e112c3 <error: Cannot access memory at address 0x801cc9e112c3>, c=32 ' ') at ../src/nvim/screen.c:5263 1 0x00007f31460eccc5 in win_line (wp=wp@entry=0x7fffc9df6230, lnum=lnum@entry=11, startrow=startrow@entry=10, endrow=41, nochange=false, number_only=number_only@entry=false) at ../src/nvim/screen.c:4025 2 0x00007f31460eed8e in win_update (wp=wp@entry=0x7fffc9df6230) at ../src/nvim/screen.c:1403 3 0x00007f31460f011f in update_screen (type=<optimized out>) at ../src/nvim/screen.c:502 4 0x00007f3146138ef4 in normal_redraw (s=s@entry=0x7fffd0a5f700) at ../src/nvim/normal.c:1247 5 0x00007f314613b159 in normal_check (state=0x7fffd0a5f700) at ../src/nvim/normal.c:1324 6 0x00007f31460accfe in state_enter (s=0x7fffd0a5f700) at ../src/nvim/state.c:28 7 0x00007f3146143099 in normal_enter (cmdwin=<optimized out>, noexmode=<optimized out>) at ../src/nvim/normal.c:463 8 0x00007f314618b541 in main (argc=<optimized out>, argv=<optimized out>) at ../src/nvim/main.c:580
* doc: fix typosBrian Wignall2019-11-27
| | | | close #11459
* vim-patch:8.1.1922: in diff mode global operations can be very slowJan Edmund Lazo2019-11-16
| | | | | | | Problem: In diff mode global operations can be very slow. Solution: Do not call diff_redraw() many times, call it once when redrawing. And also don't update folds multiple times. https://github.com/vim/vim/commit/4f57eefe1e84b5a90e08474092ea6fc8825ad5c9
* vim-patch:8.1.2120: some MB_ macros are more complicated than necessaryJan Edmund Lazo2019-10-06
| | | | | | | Problem: Some MB_ macros are more complicated than necessary. (Dominique Pelle) Solution: Simplify the macros. Expand inline. https://github.com/vim/vim/commit/1614a14901558ca091329315d14a7d5e1b53aa47
* win_line: update `w_last_cursorline` alwaysDaniel Hahler2019-10-04
| | | | | | | | | | | | Vim patch 8.1.0856 (54d9ea6) caused a performance regression in Neovim, when `set conceallevel=1 nocursorline` was used, since then due to refactoring in 23c71d5 `w_last_cursorline` would never get updated anymore. Adds/uses `redrawdebug+=nodelta` for testing this. Fixes https://github.com/neovim/neovim/issues/11100. Closes https://github.com/neovim/neovim/pull/11101.
* Fix redraw regression with w_p_cole in visual modeDaniel Hahler2019-10-02
| | | | | Fixes https://github.com/neovim/neovim/issues/11024, regressed in 23c71d51. Closes https://github.com/neovim/neovim/pull/11120.
* screen: missing redraw/highlight for ruler in message areaBjörn Linse2019-09-22
|
* vim-patch:8.1.2060: "precedes" in 'listchars' not used properlyJustin M. Keyes2019-09-21
| | | | | | | | (Credit: Zach Wegner, https://github.com/neovim/neovim/pull/11034) Problem: "precedes" in 'listchars' not used properly. Solution: Correctly handle the "precedes" char in list mode for long lines. https://github.com/vim/vim/commit/bffba7f7042f6082e75b42484b15f66087b01941
* Fix "precedes" listchar behavior in wrap modeZach Wegner2019-09-21
| | | | | | | | | | | | Previously, the "precedes" character would be rendered on every row when w_skipcol > 0 (i.e., when viewing a single line longer than the entire screen), instead of just on the first row. Make sure to only render it on the first row in this case. Add a test for this behavior. Fix documentation for the "precedes" character, which erroneously stated that it was only active when wrap mode was off.
* screen: fix vcol counting with virtual text. Fixes #9941Björn Linse2019-09-21
|
* win_update: fix redraw regression (#11027)Daniel Hahler2019-09-18
| | | | | | | Before 6e9ea5adc `win_ins_lines` would return `FAIL` for `i/line_count == 0`. Handle this by checking it in the outer `if`. Ref: https://github.com/neovim/neovim/commit/6e9ea5ad#commitcomment-35084669
* screen: redrawdebug=nothrottleBjörn Linse2019-09-06
|
generated by cgit (git 2.34.1) at 2026-10-20 22:59:50 +0000