aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/uri.lua
Commit message (Collapse)AuthorAge
* docs: make Lua docstrings consistent #15255Gregory Anders2021-08-22
| | | | | | | | | | | | The official developer documentation in in :h dev-lua-doc specifies to use "--@" for special/magic tokens. However, this format is not consistent with EmmyLua notation (used by some Lua language servers) nor with the C version of the magic docstring tokens which use three comment characters. Further, the code base is currently split between usage of "--@", "---@", and "--- @". In an effort to remain consistent, change all Lua magic tokens to use "---@" and update the developer documentation accordingly.
* feat(vim.uri): Allow URI schemes other than file: without authorityTom Payne2021-07-10
|
* fix(lsp): accept file URIs without a hostnameAlessandro Pezzoni2021-07-10
| | | | | | | RFC 8089, which defines the file URI scheme, also allows URIs without a hostname, i.e. of the form file:/path/to/file. These are returned by some language servers and accepted by other LSP implementations, such as VSCode's, so it is reasonable for us to accept them as well.
* doc: Add docs for uri functions (#12887)TJ DeVries2020-09-14
|
* Change uri_to_fname to not convert non-file URIs (#12351)Mathias Fußenegger2020-05-22
| | | | | | | | | * Change uri_to_fname to not convert non-file URIs A URI with a scheme other than file doesn't have a local file path. * fixup! Change uri_to_fname to not convert non-file URIs * fixup! fixup! Change uri_to_fname to not convert non-file URIs
* LSP: Avoid URI-to-fname conversion for non-file URIs #12243Mathias Fußenegger2020-05-04
| | | Fixes https://github.com/neovim/neovim/issues/12210
* vim.uri: fix uri_to_fname (#12059)Hirokazu Hata2020-03-30
| | | | | fix: #12056 If the colon of the drive letter of windows is URI encoded, it doesn't match the expected pattern, so decode it first.
* Add vim.uri_to_bufnrAshkan Kiani2019-11-20
|
* lua LSP client: initial implementation (#11336)Ashkan Kiani2019-11-13
Mainly configuration and RPC infrastructure can be considered "done". Specific requests and their callbacks will be improved later (and also served by plugins). There are also some TODO:s for the client itself, like incremental updates. Co-authored by at-tjdevries and at-h-michael, with many review/suggestion contributions.