| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
Now remove the addition of "start/*" packages in 'packpath' as
explicit items in 'runtimepath'. This avoids 'runtimepath' from becoming
very long when using a lot of plugins as packages.
To get the effective search path as a list, use |nvim_list_runtime_paths()|
|
| |
|
|
| |
Note that these are not NUL-terminated; the API supports this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Cannot handle binary data.
Solution: Add the Blob type. (Yasuhiro Matsumoto, closes vim/vim#3638)
https://github.com/vim/vim/commit/6e5ea8d2a995b32bbc5972edc4f827b959f2702f
Nvim-specific Blob conversions are implemented in future commits.
Refactor write_blob() to use a FileDescriptor, as f_writefile() was
refactored to use one (does not apply to read_blob()).
Use var_check_lock() in f_add() for Blobs from v8.1.0897.
Add a modeline to test_blob.vim and fix some doc typos.
Include if_perl.txt's VIM::Blob() documentation. Interestingly, this
function already worked before this port, as it just returns a Blob
string literal, not an actual Blob object.
N/A patches for version.c:
vim-patch:8.1.0741: viminfo with Blob is not tested
Problem: Viminfo with Blob is not tested.
Solution: Extend the viminfo test. Fix reading a blob. Fixed storing a
special variable value.
https://github.com/vim/vim/commit/8c8b8bb56c724cc1bfc3d8520eec33f2d399697c
vim-patch:8.1.1022: may use NULL pointer when out of memory
Problem: May use NULL pointer when out of memory. (Coverity)
Solution: Check for blob_alloc() returning NULL.
https://github.com/vim/vim/commit/e142a9467a7f6845a426d8db6efedf246d3c13ac
|
| | |
|
| |
|
|
| |
ref #11456
|
| |
|
|
| |
fix #11456
|
| |
|
|
|
|
|
| |
Extmarks mostly use api-indexing, except for nvim_buf_get_extmarks(),
which uses api-indexing with inclusive ranges.
ref #11456
|
| |
|
| |
ref #15440
|
| |
|
|
|
|
|
| |
Converter functions use a heap-allocated stack to handle complex
nested objects. However, these are often called with simple,
primitive values like integers or bools wrapped in an Object.
Avoid the memory allocation in this case using kvec_withinit_t
|
| |\
| |
| | |
Port VimL's method call syntax - vim-patch:8.1.{1638,1800,1803,1807,1809,1816,1820,1821,1828,1834,1835,1861,1863,1878,1879,1888,1909,1911,1912}
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Function call functions have too many arguments.
Solution: Pass values in a funcexe_T struct.
https://github.com/vim/vim/commit/c6538bcc1cdd1fb83732f22fdc69bd9bb66f968a
Use FUNCEXE_INIT to initialize funcexe_T instances.
call_callback() and other Vim listener related stuff is N/A.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: the reason for removing them is not that there after this refactor
is no use of them, but rather that having them available is an
anti-pattern: they manange an _extra_ heap allocation which has
nothing to do with the functionality of the map itself (khash
manages the real buffers internally). In case there happens to
be a reason to allocate the map structure itself later, this
should be made explicit using xcalloc/xfree calls.
|
| | |
| |
| |
| |
| | |
These things are just maps to pointers, no need to perform
a huge song and dance around it.
|
| |/ |
|
| |\
| |
| | |
refactor(plines): move "plines" (size of printed lines) family of function to own file
|
| | | |
|
| |/
|
|
| |
This error is already handled by 'find_buffer_by_handle'
|
| | |
|
| | |
|
| |
|
|
| |
Full virt_text functionality is provided by nvim_buf_set_extmark
|
| |
|
|
|
|
| |
test(bufhl): CHANGE of tested behaviour (inb4 a proper priority mechanism)
test(decoration): change of test; previous behavior was buggy (ghost
buffer text)
|
| | |
|
| |
|
|
| |
The number of elements comes first and the size of each element second.
|
| | |
|
| |
|
|
| |
#15015
|
| |\
| |
| | |
fix(api/win_get_config): include z-index
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
* Add buffer information to tabline_update
Most terminal implementations of the tabline display buffer and tab
information. Many neovim-qt users disable GuiTabline because it lacks
functionality provided in the terminal implementation.
The tabline_update event should include buffer information too, so client GUIs
can display rich useful tabs.
|
| | |
|
| |
|
|
|
|
|
|
| |
Add `borders = "rounded"` preset for `nvim_open_win`, equivalent to
border = {"╭", "─", "╮", "│", "╯", "─", "╰", "│"}
Also add undocumented "solid" preset to docs.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
api: add nvim_win_call
|
| | | |
|
| |\ \
| |/
|/| |
Minor observational corrections to the nvim_buf_set_extmark documentation
|
| | | |
|
| | |
| |
| |
| |
| | |
nvim_set_decoration_provider() has undefined behavior (if not crash)
if get_decor_provider() returns NULL.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This option, when set, stops nvim_open_win() from potentially firing
buffer-related autocmd events
(BufEnter, BufLeave and BufWinEnter in the case of nvim_open_win()).
|
| |\ \
| | |
| | | |
Revert "api/window: use the "noblock" variants in nvim_win_set_buf"
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 1def3d1542d6a65f057e743faea39a760b50db87.
Plugins may depend on catching the following events
when creating windows:
- BufWinEnter
- BufEnter
- BufLeave
Risky to introduce this breaking change on 0.5 release
when 0.5 release should be out by now.
https://github.com/asvetliakov/vscode-neovim/issues/632#issuecomment-837201224
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* lua: Add vim.opt
* fixup: cleaning
* fixup: comments
* ty clason
* fixup: comments
* this is the last commit. period.
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
[WIP] z-index!
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| | |
API: Adding cterm support to nvim_set_hl
|
| | | | |
|
