| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Problem: Crash when closing window from WinBar click. (Ben Jackson)
Solution: Check that window pointer is still valid. (closes vim/vim#4337)
https://github.com/vim/vim/commit/d2fad67e3eb71f48d23f283ef8e7b7ddf4ee180f
|
|
|
|
|
|
| |
Problem: Using window toolbar changes state.
Solution: Always execute window toolbar actions in Normal mode.
https://github.com/vim/vim/commit/a21a6a9ade7bec3a07992d4d900d4ce82eeb8a29
|
|
|
|
|
|
|
|
| |
Problem: Splitting a window with a WinBar damages window layout.
(Lifepillar)
Solution: Take the winbar into account when computing the new window
position. Add WINBAR_HEIGHT().
https://github.com/vim/vim/commit/3167c3e7010ac7e2fd7d3aa198dd2d1dcff8ecc8
|
|
|
|
|
|
| |
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: Window toolbar menu gets a tear-off item.
Solution: Recognize the window toolbar.
https://github.com/vim/vim/commit/378daf87d380b9f3c4f822786dfbfdcad9ca2db9
|
|
|
|
|
|
|
|
| |
toolbar
Problem: Wrong window height when splitting window with window toolbar.
Solution: Add or subtract the window toolbar height.
https://github.com/vim/vim/commit/d326ad6e93604222c64bae51f47521fe9114d1ea
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
| |
fix #12162
|
|
|
| |
Messed this up in ef0398fe88e6cc74f33fb20519997774168d7832
|
| |
|
|
|
|
|
|
|
|
|
| |
According to the spec there is the possibility that when a
VersionedTextDocumentIdentifier is used in a TextEdit the value may be
null. Currently we don't check for this and always assume that it's set.
So currently if a TextEdit comes in for a rename for example with the
version null, it fails as we are comparing the bufnumber with nil.
https://microsoft.github.io/language-server-protocol/specification#versionedTextDocumentIdentifier
|
|
|
|
|
|
|
|
| |
Wrapping it in DCS allows the following features to work with GNU
Screen.
- Changing the cursor style.
- bracketed paste.
- focus reporting.
|
|\ |
|
| |
| |
| |
| | |
...was using wrong macro argument.
|
| | |
|
| |
| |
| |
| | |
to ease up notations.
|
| |
| |
| |
| |
| |
| | |
TODO in a future commit:
- remains 2 instances of changed_lines that dont take into account
buffer
|
| |
| |
| |
| |
| |
| | |
The method with the name 'textDocument/peekDefinition' is not part of
the official language server protocol specification. Therefore no
language server can/will support this. Thereby all related code and
documentation as been removed.
|
| |
| |
| | |
fix #8075
|
|\ \
| | |
| | | |
vim-patch:8.2.{635,638}
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: MS-Windows: messages test fails.
Solution: Clear environment variables.
https://github.com/vim/vim/commit/47a1a8baf9c8eb22b24f667e57a1dab579999a74
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
color
Problem: When using 256 colors DarkYellow does not show expected color.
Solution: Use color 3 instead of 130. (Romain Lafourcade, closes vim/vim#5985)
https://github.com/vim/vim/commit/e93c968f520ee8d6bc29ccc6e18055ac65e832b3
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
ref: a39c8b7ce30ddeed4329c28c42b1b699103dccab
ref: https://github.com/vim/vim/commit/bfe13ccc58ccb96f243a58309800410db1ccb52c
Also:
- Remove unused macos_rvm_dance() function. (It was there for reference,
but we have since resolved (or gave up) on Travis + macOS + ruby.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Expose `vim.lsp.buf.diagnostics_by_buf`
This makes it easier to customize the diagnostics behavior. For example
to defer the update they can override the
`textDocument/publishDiagnostics` callback to only call
`buf_diagnostics_save_positions` and then defer the other actions to a
autocmd event.
|
| |
| |
| |
| | |
When we save the buffer, the buffer is detached and attached again.
So the client also needs to remove the buffer version once.
|
|/ |
|
|
|
|
|
|
|
|
| |
In contrast to other callbacks for LSP requests like
`textDocument/documentSymbols`, does the one for references not open the
quickfix window after the quickfix list was filled. This left the user
in a situation he don't know what or if something had happen.
Related to: neovim/neovim#12170
|
|
|
|
|
|
|
| |
Sometimes treesitter calls for an invalid column within a line, checking
that the column is actually valid and forcing the value avoids an
integer overflow and an infinite sequence of invalid reads.
Fixes #12131
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Improve error message for unsupported bash version, use double square bracket operator
Co-Authored-By: Daniel Hahler <github@thequod.de>
|
| | |
|
| |
| |
| |
| |
| |
| | |
Offsets of window were not taken into account when sending mouse
coordinates to the terminal. Therefore, when nu or rnu is set, the mouse
coordinates sent to the terminal were not correct. Change it to send the
correct coordinates by subtract window offset from col.
|
| |
| |
| |
| |
| |
| |
| |
| | |
There is ErrorCodes in the LSP specification, but in ResponseError.code
it is not used and the actual type is number.
Some language servers response original error cods and this is valid spec.
So we shouldn't assert even if the code does not exist in ErrorCodes.
ref: https://microsoft.github.io/language-server-protocol/specifications/specification-current/#responseMessage
|
| |
| |
| |
| |
| | |
* https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_definition
Co-authored-by: Khangal Jargalsaikhan <khangal.j@irbis.sg>
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
uv_stream_get_write_queue_size isn't a define, it's a
function. It seems like this would always be shadowing the
actual function name.
|
|/ /
| |
| |
| | |
(found for example on openSUSE/Leap 15.*)
|
|\ \
| | |
| | | |
LSP/completion: add textEdit support
|
| | | |
|
| | |
| | |
| | |
| | | |
...ument_completion_list_to_complete_items
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
According to lsp specification, value of insertText should be ignored if
textEdit is provided.
|
| | |
| | |
| | | |
Fixes #11653, #11990. Check for cursor visibility to toggle uv_write call.
|
| | |
| | |
| | | |
This function is also useful for users to create their own `textDocument/signatureHelp` callback function.
|
|\ \ \
| | | |
| | | |
| | | | |
Change resolve() to resolve symbolic links on Windows
Neovim worked the same way as vim for shortcuts, but didn't handle symbolic links and junction cases. This PR implements the same behavior for symbolic links and junctions as for vim.
|
| | | | |
|
| | | | |
|
| | | | |
|