| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Currently, multigrid mouse drag positions are handled incorrectly if the
drag event is not in the top left grid. Fix this by not adjusting the
position of the event in jump_to_mouse.
related: #15091
|
| |
|
|
|
|
| |
fix style.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
mouse_find_win() can return NULL.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Fix click on foldcolumn if it has tabline
* Fixes to correctly determine if tablie was clicked when multigrid is enabled
* Separate foldcolumn checks into functions
* Add test case for click on foldcolumn with split window
* Fix foldcolumn click used nvim_input() on multigrid enabled
|
|
|
|
|
|
|
|
|
| |
before the behaviour of 'mouse' was inconsistent in external UI,
as some remapping logic would check has_mouse() and others don't
(no difference in TUI or vim classic). With this change, the behaviour
is consistently up to the UI decide (see ui.txt edit)
Behaviour of tui.c is unaffected by this change.
|
|
|
|
|
|
|
|
|
| |
No unmerged Vim patch, applicable to Neovim, depend on WinBar feature.
It was merged only for merging Vim patches.
It is currently useless in Neovim.
Remove it to avoid rendering issues.
Close https://github.com/neovim/neovim/issues/12689
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Insufficient test coverage for the Netbeans interface.
Solution: Add more tests. Fix an uncovered bug. (Yegappan Lakshmanan,
closes vim/vim#7240)
https://github.com/vim/vim/commit/dbfa795d8b66c99ee758b132d6043871b9061563
N/A patches for version.c:
vim-patch:8.2.1165: insufficient testing for the Tcl interface
Problem: Insufficient testing for the Tcl interface.
Solution: Add more tests. (Yegappan Lakshmanan, closes vim/vim#6423)
https://github.com/vim/vim/commit/e4358906fdbd0b2df1889dad49c79a9c8cee5ac4
|
|
|
|
|
|
|
|
|
|
| |
co-author: hlpr98 <hlpr98@gmail.com> (dict2hlattrs function)
orange is sus??
NOVEMBER DAWN
erase the lie that is redraw_later()
|
|
|
|
|
|
| |
Problem: Quick clicks in the WinBar start Visual mode.
Solution: Use a double click in the WinBar like a normal click.
https://github.com/vim/vim/commit/d327b0c68fa9b32877123f77560f4521a9eb39db
|
|
|
|
|
|
| |
Problem: Click in window toolbar starts Visual mode.
Solution: Add the MOUSE_WINBAR flag.
https://github.com/vim/vim/commit/eb163d73b11c10b461a2839530173a33d7915a33
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
would previously only work with ascii fillchars.
Added a test.
|
|\ |
|
| |
| |
| |
| |
| | |
You can try it with
set fillchars+=foldopen:▾,foldsep:│,foldclose:▸
|
|/ |
|
|
|
| |
closes #11372
|
|
|
|
|
|
|
|
| |
add proper msg_set_pos event, delet win_scroll_over_*
make compositor click through unfocusable grids
add MsgArea attribute for the message/cmdline area, and add docs and tests
|
|
|
|
| |
Co-Author: Dongdong Zhou <dzhou121@gmail.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using 'listchars' is a nice way to highlight tabs that were included by accident
for buffers that set 'expandtab'.
But maybe one does not want this for buffers that set 'noexpandtab', so now one
can use:
autocmd FileType go let &l:listchars .= ',tab: '
|
|/
|
|
|
|
|
| |
wp->w_height_inner now contains the "inner" size, regardless if the
window has been drawn yet or not. It should be used instead of
wp->w_grid.Rows, for stuff that is not directly related to accessing
the allocated grid memory, such like cursor movement and terminal size
|
| |
|
| |
|
|
|
|
| |
This check is meaningless, we assume the terminal supports reverse-mode.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Problem: Crash if timer closes window while dragging status line.
Solution: Check if the window still exists. (Yasuhiro Matsumoto, closes
vim/vim#1979)
https://github.com/vim/vim/commit/989a70c590c2bd109eb362d3a0e48cb1427ae13d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Some macros are in lower case.
Solution: Make a few more macros upper case. Avoid lower case macros use an
argument twice.
https://github.com/vim/vim/commit/91acfffc1e6c0d8c2abfb186a0e79a5bf19c3f3f
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Store text in ScreenLines as UTF-8, so it can be sent as-is to the UI
layer. `utfc_char2bytes(off,buf)` is removed, as `ScreenLines[off]` now
already contains this representation.
To recover the codepoints that the screen arrays previously contained, use
utfc_ptr2char (or utf_ptr2char to ignore composing chars).
NB: This commit does NOT change how screen.c processes incoming UTF-8 data
from buffers, cmdline, messages etc. Any algorithm that operates on UCS-4
(like arabic shaping, treatment of non-printable chars)
is left unchanged for now.
|
| |
|
| |
|
| |
|
|
|
|
| |
ref: #7887
|
| |
|
|
|
|
| |
fixes #5341, #5801
|
|
|
|
| |
remove pointless control chars in the text stream
|
|\ |
|