aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/lua
Commit message (Collapse)AuthorAge
* ts: Add language version to vim.treesitter (#14255)TJ DeVries2021-03-30
|
* chore(ts): show grammar that triggers the errorMatthieu Coudron2021-03-16
| | | | to help debugging
* Merge pull request #13875 from smolck/vim_fn_error_on_apiBjörn Linse2021-03-09
|\ | | | | vim.fn: throw error when trying to use API function
| * Fix unused varargsmolck2021-02-06
| |
| * remove extra line, remove () in errorsmolck2021-02-04
| |
| * vim.fn: throw error when trying to use API functionsmolck2021-02-03
| |
* | fix(notify): Expected 3 arguments error (#13905)notomo2021-02-09
| |
* | Merge pull request #13843 from teto/notif_providerMatthieu Coudron2021-02-08
|\ \ | |/ |/| [RDY] Notification provider
| * feat: adds vim.notifyMatthieu Coudron2021-01-31
| | | | | | | | | | | | | | | | | | | | | | | | | | Adds function to notify the user like this: `:lua vim.notify("hello user")` embeds log levels vim.log.levels. you can then reassign vim.notify to for instance ``` function notify_external(msg, log_level, opts) vim.fn.jobstart({"notify-send", msg }) end ```
* | Use abort() instead of assert(false) for things that should never happenJames McCoy2021-01-31
|/ | | | | | | | assert() is compiled out for release builds, but we don't want to continue running in these impossible situations. This also resolves the "implicit fallthrough" warnings for the asserts in switch cases.
* lintchentau2021-01-26
|
* lua: complete methods in metatablesBjörn Linse2021-01-26
|
* Don't show entire context when completingTony Chen2021-01-26
|
* feat: add completion to ':lua'TJ DeVries2021-01-26
|
* Missing argument for package.loadlib()matveyt2021-01-22
| | | | | | Allow for foo.bar.baz module name Make luaopen_module() name compatible with Lua 5.1
* api: add vim.version (#13762)Michael Lingelbach2021-01-18
| | | | | | | | | | | | | retrun a structured version dict :lua print(vim.inspect(vim.version())) { api_compatible = 0, api_level = 7, api_prerelease = true, major = 0, minor = 5, patch = 0 }
* runtime: propagate lua parsing errors while using "require"dm1try2020-12-10
|
* executor: use new nlua_ name patternBjörn Linse2020-12-01
|
* startup: add init.lua as an alternative user config, fixes #7895dm1try2020-12-01
|
* fix(treesitter): allow ranges in set_included_rangesThomas Vigouroux2020-11-23
|
* treesitter: refactor some thingsThomas Vigouroux2020-11-23
|
* fix: NULL segfaults brought to you by @vigouxTJ DeVries2020-11-18
|
* lsp: vim.lsp.diagnostic (#12655)TJ DeVries2020-11-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Breaking Changes: - Deprecated all `vim.lsp.util.{*diagnostics*}()` functions. - Instead, all functions must be found in vim.lsp.diagnostic - For now, they issue a warning ONCE per neovim session. In a "little while" we will remove them completely. - `vim.lsp.callbacks` has moved to `vim.lsp.handlers`. - For a "little while" we will just redirect `vim.lsp.callbacks` to `vim.lsp.handlers`. However, we will remove this at some point, so it is recommended that you change all of your references to `callbacks` into `handlers`. - This also means that for functions like |vim.lsp.start_client()| and similar, keyword style arguments have moved from "callbacks" to "handlers". Once again, these are currently being forward, but will cease to be forwarded in a "little while". - Changed the highlight groups for LspDiagnostic highlight as they were inconsistently named. - For more information, see |lsp-highlight-diagnostics| - Changed the sign group names as well, to be consistent with |lsp-highlight-diagnostics| General Enhancements: - Rewrote much of the getting started help document for lsp. It also provides a much nicer configuration strategy, so as to not recommend globally overwriting builtin neovim mappings. LSP Enhancements: - Introduced the concept of |lsp-handlers| which will allow much better customization for users without having to copy & paste entire files / functions / etc. Diagnostic Enhancements: - "goto next diagnostic" |vim.lsp.diagnostic.goto_next()| - "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()| - For each of the gotos, auto open diagnostics is available as a configuration option - Configurable diagnostic handling: - See |vim.lsp.diagnostic.on_publish_diagnostics()| - Delay display until after insert mode - Configure signs - Configure virtual text - Configure underline - Set the location list with the buffers diagnostics. - See |vim.lsp.diagnostic.set_loclist()| - Better performance for getting counts and line diagnostics - They are now cached on save, to enhance lookups. - Particularly useful for checking in statusline, etc. - Actual testing :) - See ./test/functional/plugin/lsp/diagnostic_spec.lua - Added `guisp` for underline highlighting NOTE: "a little while" means enough time to feel like most plugins and plugin authors have had a chance to refactor their code to use the updated calls. Then we will remove them completely. There is no need to keep them, because we don't have any released version of neovim that exposes these APIs. I'm trying to be nice to people following HEAD :) Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
* Removed restricted mode - Fix #11972georg3tom2020-11-11
|
* Merge pull request #13227 from bfredl/earlyinspectBjörn Linse2020-11-05
|\ | | | | lua: make vim.inspect available early so it can be used for path debugging
| * lua: make vim.inspect available early so it can be used for path debuggingBjörn Linse2020-11-05
| |
* | treesitter: separate tree and parserThomas Vigouroux2020-11-04
|/ | | | While this might sound silly, it is needed for further improvements.
* startup: handle autoload and lua packages during startupBjörn Linse2020-11-02
| | | | ¡NO HAY BANDA!
* Merge pull request #12870 from bfredl/themeparkBjörn Linse2020-11-01
|\ | | | | Color themes (per window/line) and lua theme providers
| * api: add API for themesBjörn Linse2020-11-01
| | | | | | | | | | | | | | | | | | | | co-author: hlpr98 <hlpr98@gmail.com> (dict2hlattrs function) orange is sus?? NOVEMBER DAWN erase the lie that is redraw_later()
* | Merge pull request #13192 from bfredl/nodeidBjörn Linse2020-11-01
|\ \ | | | | | | ] treesitter: add node:id()
| * | treesitter: add node:id()Björn Linse2020-11-01
| |/
* | treesitter: fix wrong string formattingThomas Vigouroux2020-11-01
| |
* | tree-sitter: error out when parsing failsThomas Vigouroux2020-11-01
|/ | | | | This can happen when there is ABI mismatches, and removes the assumption parsing alwasy succeeds (which is wrong).
* treesitter: allow custom parser for highlighterThomas Vigouroux2020-10-12
| | | | | | | | | | | Also allow to get parser ranges. This will be useful for language injection, allowing us to tweak the parser's ranges on the fly. Update runtime/lua/vim/treesitter.lua Co-authored-by: Paul Burlumi <paul@burlumi.com>
* api: multiple decoration providers at onceBjörn Linse2020-10-10
|
* treesitter: check language ABI version on loadThomas Vigouroux2020-10-08
| | | | This is will avoid some issues at runtime.
* lua: vim.wait allows control of fast events (#13053)TJ DeVries2020-10-06
| | | | | | | | | * lua: vim.wait allows control of fast events * fixup: remove requirement of function for easier waiting * fixup: lint * fixup: bfredl comments
* treesitter: add string parser (#13008)Thomas Vigouroux2020-09-30
|
* lua: cleanup naming conventions of executor functionsBjörn Linse2020-09-10
|
* treesitter: use new on_bytes interfaceBjörn Linse2020-09-09
| | | | | | | | | | This will significantly reduce the parsing work needed e.g. when rehighlighting after every keypress in insert mode. Also add safety check for tree-sitter trying to read past the end of a line. This can happen after we sent an incorrect buffer update.
* treesitter: add node:field() to get field childrenThomas Vigouroux2020-09-01
|
* treesitter: allow to iterate over node childrenThomas Vigouroux2020-08-31
|
* lua: add vim.register_keystroke_callback (#12536)TJ DeVries2020-08-14
| | | | | | | | | | | | | | | * feat: Add vim.register_keystroke_callback * fixup: Forgot to remove mention of old option * fixup: Answer jamessan comments * fixup: Answer norcalli comments * fixup: portability * Update runtime/doc/lua.txt Co-authored-by: Ashkan Kiani <ashkan.k.kiani@gmail.com>
* fix: runtimepath always updates lua package.pathTJ DeVries2020-08-10
|
* Merge pull request #12653 from erw7/fix-build-freebsd-ciJames McCoy2020-07-20
|\ | | | | build: Fix build failure with CI in FreeBSD
| * build: Fix build failure with CI in FreeBSDerw72020-07-20
| | | | | | | | Co-authored-by: James McCoy <jamessan@jamessan.com>
* | lua: Fix crash on unprotected lua errors (#12658)TJ DeVries2020-07-19
|/ | | | | | | | | | | | | | | | | | Can be reproduced with a script like this: -- in some lua file vim.fn.timer_start(10, function() error("uh....") end) -- will cause neovim to crash with the following error. PANIC: unprotected error in call to Lua API (nlua_CFunction_func_call failed.) After this, it will instead print the error message from the top of the stack, like so. tmp/error_nvim.lua:10: uh... Also added an example test. Previously this test caused the embedded nvim to panic.
* lua: Add ability to pass tables with __callTJ DeVries2020-07-10
| | | | | | | | | | | | vim-patch:8.2.1054: not so easy to pass a lua function to Vim vim-patch:8.2.1084: Lua: registering function has useless code I think I have also opened up the possibility for people to use these callbacks elsewhere, since I've added a new struct that we should be able to use. Also, this should allow us to determine what the state of a list is in Lua or a dictionary in Lua, since we now can track the luaref as we go.
* lua: Add ability to pass lua functions directly to vimLTJ DeVries2020-07-10
|
generated by cgit (git 2.34.1) at 2025-06-25 14:08:14 +0000