aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/api
Commit message (Collapse)AuthorAge
...
* ui/compositor: add redraws needed due to intersected doublewidth chars.Björn Linse2019-02-02
|
* UI: add "compositor" layer to merge grids for TUI use in a correct wayBjörn Linse2019-02-02
| | | | | | | | Initially we will use this for the popupmenu, floating windows will follow soon NB: writedelay + compositor is weird, we need more flexible redraw introspection.
* doc [ci skip] #9478Justin M. Keyes2019-01-26
| | | | | | | | | | | | - Lua - developer guidelines - MAINTAIN.md - TUI: cleanup - TUI: mention Windows terminfo builtins - cleanup if_pyth, redirect python-bindeval tag Helped-by: Björn Linse <bjorn.linse@gmail.com> Helped-by: erw7 <erw7.github@gmail.com>
* ui: multigrid mouse supportBjörn Linse2019-01-20
|
* API: nvim_set_vvar(): set v: variables #9395jin cong2019-01-14
| | | | closes #9349
* dict_set_var: check value before checking its containerJustin M. Keyes2019-01-14
| | | | | | | - When setting a fixed/locked/readonly var, it is more relevant to report on the key, not its container dict. If its container dict (v:) is readonly, that does not mean the key itself is readonly. - Allow modifying a "fixed" var. "fixed" only prevents deletion.
* api: select items in popupmenuBjörn Linse2019-01-09
|
* API: don't directly call update_screen() in API functionsBjörn Linse2019-01-08
| | | | | | | | | There is no need to call update_screen() directly in an API function, mode input processing invokes update_screen() as needed. And if the API call is done in a context where redraw is disabled, then redraw is disabled for a reason. A lot of API functions are of equal semantical strength (nvim_call_function and nvim_execute_lua can also do whatever, nvim_command is not special), this inconsistency has no purpose.
* multigrid: rename grid->ScreenLines and other grid arraysBjörn Linse2018-12-31
|
* multigrid: API version bumpBjörn Linse2018-12-31
|
* multigrid: reorganize types and global varaiblesBjörn Linse2018-12-31
|
* multigrid: Add multigrid documentationUtkarsh Maheshwari2018-12-31
|
* multigrid: rename event to win_pos, make grid firstBjörn Linse2018-12-31
|
* multigrid: add msg_scroll_start and msg_scroll_reset eventsBjörn Linse2018-12-31
|
* multigrid: send win_hide events when changing tabpageBjörn Linse2018-12-31
|
* multigrid: Fix lint errorsUtkarsh Maheshwari2018-12-31
|
* multigrid: use grid-based coordinates for ext_popupmenuBjörn Linse2018-12-31
|
* multigrid: Get rid of global ScreenLines and set_screengridUtkarsh Maheshwari2018-12-31
|
* multigrid: Put everything on default_grid if not ext_multigridUtkarsh Maheshwari2018-12-31
|
* multigrid: Add win_position eventUtkarsh Maheshwari2018-12-31
| | | | Throttle win_position events
* multigrid: Allow UIs to set grid size different from window sizeUtkarsh Maheshwari2018-12-31
|
* multigrid: Change screen_* functions to grid_* functionsUtkarsh Maheshwari2018-12-31
|
* docJustin M. Keyes2018-12-30
| | | | - CMake features
* doc (#9288)Justin M. Keyes2018-12-09
| | | | | - misc - doc: `:help config`. closes #9329 - cleanup test/README.md
* API: rename nvim_buf_clear_highlight to nvim_buf_clear_namespaceBjörn Linse2018-11-29
| | | | | We want a single function to clear all namespaced buffer objects. This will later include extmarks.
* docJustin M. Keyes2018-11-28
| | | | | | | | | | - develop.txt is for design/guidelines; architecture/concepts should live elsewhere (currently src/nvim/README.md) - move dev-jargon to intro.txt - replace https://neovim.io/community (deprecated) with https://neovim.io/#chat - <Cmd> avoids CmdlineEnter/Leave https://github.com/vim/vim/issues/2889
* API: Implement nvim_win_set_buf() #9100Justin M. Keyes2018-11-25
| | | | closes #9100
* api: implement object namespacesBjörn Linse2018-11-24
| | | | | | | | | Namespaces is a lightweight concept that should be used to group objects for purposes of bulk operations and introspection. This is initially used for highlights and virtual text in buffers, and is planned to also be used for extended marks. There is no plan use them for privileges or isolation, neither to introduce nanespace-level options.
* doc: APIJustin M. Keyes2018-11-05
|
* docJustin M. Keyes2018-11-05
| | | | - update standard-plugin-list. closes #8388
* api: simplify nvim_buf_get_offset functionBjörn Linse2018-11-01
|
* api: implement nvim_buf_get_offset_for_lineBjörn Linse2018-11-01
| | | | | Like line2byte, but works for any buffer, and uses zero-based indexing (API conventions).
* api/ui: verify compatibility of UI eventsBjörn Linse2018-10-21
|
* 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
* ui: reserve the right to split a screen redraw into multiple batches.Björn Linse2018-10-02
|
* ui: rename ext_newgrid to ext_linegridBjörn Linse2018-10-01
|
* func_attr.h: FUNC_ATTR_PRINTFMichael Hoffmann2018-09-23
|
* startup: always wait for UI with --embed, unless --headless also is suppliedBjörn Linse2018-09-22
|
* buffer: add support for virtual text annotationsBjörn Linse2018-09-17
|
* Merge pull request #8915 from rickyz/line_wrappingBjörn Linse2018-09-09
|\ | | | | Fix terminal line wrapping detection in the TUI.
| * tui: Hint wrapped lines to terminals.Ricky Zhou2018-09-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, when neovim would wrap a line across multiple lines, terminal emulators could not detect that the lines represent a single wrapped line as opposed to several separate lines. As a result, many terminals' selection/copying functionality would treat a wrapped line as several newline-delimited lines. Fix this by reenabling a "special trick" from Vim. When a line is wrapped, write the last character of that line followed by the first character of the next line to the terminal. This hints to the terminal that the next line is a continuation of the current line. Extends the raw_line event with a "wrap" parameter which controls when to do wrap hinting.
* | API: Avoid overrun when formatting error-messageJustin M. Keyes2018-09-05
|/ | | | | | | msgpack_rpc_to_object (called by handle_request .. msgpack_rpc_to_array) always NUL-terminates API Strings. But handle_request .. msgpack_rpc_get_handler_for operates on a raw msgpack_object, before preparation.
* ext_cmdline: use new highlight representation for cmdline_blockBjörn Linse2018-08-27
| | | | | | | | | Make sure cmdline updates will receive highlight specifications the same way as screen cells. This is controlled by the ext_newgrid option so nothing is changed by default (as screen cells are also not changed by default). This was already done for the cmdline itself in #8221, this extends it to cmdline_block. Which currently doesn't store highlights, but the placeholder should be one that makes sense for future use.
* runtime/doc: fix broken links found by `make html`Justin M. Keyes2018-08-25
|
* highlight: HlAttrs is a value type; treat it like suchBjörn Linse2018-08-13
|
* API: update docs WRT behaviours/methods for unloaded buffers #7688Peter Hodge2018-07-25
|
* API: add nvim_buf_is_loaded() #7688Peter Hodge2018-07-25
|
* API: buf_get_lines, buf_line_count handle unloaded buffers #7688Peter Hodge2018-07-25
|
* ui: fix glitches where scrolling region affects clearing of screenBjörn Linse2018-07-24
| | | | | | | | the first implemented UI protocol clients (python-gui and builitin TUI) allowed the cleared region to be restricted by setting the scroll region. This was never used by nvim though, and not documented and implemented by newer clients, to check we remain compatible with both kind of clients, ensure the scroll region is in a reset state.
* ui: use line-based rather than char-based updates in screen.cBjörn Linse2018-07-21
| | | | | | | | | | | | | Add ext_newgrid and ext_hlstate extensions. These use predefined highlights and line-segment based updates, for efficiency and simplicity.. The ext_hlstate extension in addition allows semantic identification of builtin and syntax highlights. Reimplement the old char-based updates in the remote UI layer, for compatibility. For the moment, this is still the default. The bulitin TUI uses the new line-based protocol. cmdline uses curwin cursor position when ext_cmdline is active.
generated by cgit (git 2.34.1) at 2025-05-28 21:16:25 +0000