AdeAttwood/ivy.nvim
1
0
Fork 0
Code Issues Pull requests Projects Wiki Activity Actions
ivy.nvim/plugin/ivy.lua

32 lines
919 B
Lua
Raw Normal View History

chore: initial commit
2022-07-10 20:07:33 +00:00
local controller = require "ivy.controller"
feat: split out register backend so it can be used as an external API Summary: Split out the register backend function from being a private function. A backend is a table that will define all of the attributes for a run function. The attributes are as follows: - **command** The name of the command that will be registered as a vim user command. - **items** The callback function that will be passed to the run function that will gather the items for selection - **callback** The callback function run when an item is selected The following are optional: - **keymap** The string passed to `nvim_set_keymap`, this will always be registered in normal mode - **description** The text description that will be used in the user command - **name** The name of the backend, this will fallback to the command if its not set It will also allow to register a backend in a couple of different ways: - With a backend module table - With a backend module name - With a backend module name and override options This will look for for a lua module `ivy.backends.files`. The module will be required and registered as a backend. ```lua register_backend "ivy.backends.files" ``` This will do the same with the module string however, before the backend is registered the keymap will be overridden ```lua register_backend({ "ivy.backends.file", { keymap = "<C-p>" } }) ``` Test Plan: CI / Manual testing locally
2024-06-16 20:44:16 +00:00
local register_backend = require "ivy.register_backend"
chore: initial commit
2022-07-10 20:07:33 +00:00
-- Put the controller in to the vim global so we can access it in mappings
-- better without requires. You can call controller commands like `vim.ivy.xxx`.
ci: add luacheck
2022-08-06 14:02:42 +00:00
-- luacheck: ignore
chore: initial commit
2022-07-10 20:07:33 +00:00
vim.ivy = controller
feat: add the paste functionality into the ivy prompt Now when you paste and you are in an ivy buffer the paste will be added to the prompt not into the completion window. You can use your usual paste key binding I.E. <SHIFT>+<INSERT> <CTRL>+<SHIFT>+<V> Ref: #11
2023-06-02 16:05:57 +00:00
vim.paste = (function(overridden)
return function(lines, phase)
local file_type = vim.api.nvim_buf_get_option(0, "filetype")
if file_type == "ivy" then
vim.ivy.paste()
else
overridden(lines, phase)
end
end
end)(vim.paste)
feat: split out register backend so it can be used as an external API Summary: Split out the register backend function from being a private function. A backend is a table that will define all of the attributes for a run function. The attributes are as follows: - **command** The name of the command that will be registered as a vim user command. - **items** The callback function that will be passed to the run function that will gather the items for selection - **callback** The callback function run when an item is selected The following are optional: - **keymap** The string passed to `nvim_set_keymap`, this will always be registered in normal mode - **description** The text description that will be used in the user command - **name** The name of the backend, this will fallback to the command if its not set It will also allow to register a backend in a couple of different ways: - With a backend module table - With a backend module name - With a backend module name and override options This will look for for a lua module `ivy.backends.files`. The module will be required and registered as a backend. ```lua register_backend "ivy.backends.files" ``` This will do the same with the module string however, before the backend is registered the keymap will be overridden ```lua register_backend({ "ivy.backends.file", { keymap = "<C-p>" } }) ``` Test Plan: CI / Manual testing locally
2024-06-16 20:44:16 +00:00
register_backend "ivy.backends.buffers"
register_backend "ivy.backends.files"
register_backend "ivy.backends.lines"
register_backend "ivy.backends.lsp-workspace-symbols"
feat: add highlight on matching chars in results buffer
2022-07-23 19:53:07 +00:00
feat: add ripgrep backend `rg` will now be used over `ag` if it is available. This is because `rg` is a faster alternative reduces lag when searching larger codebases. `ag` is also now conditionally loaded if the command is available.
2023-05-23 07:01:38 +00:00
if vim.fn.executable "rg" then
feat: split out register backend so it can be used as an external API Summary: Split out the register backend function from being a private function. A backend is a table that will define all of the attributes for a run function. The attributes are as follows: - **command** The name of the command that will be registered as a vim user command. - **items** The callback function that will be passed to the run function that will gather the items for selection - **callback** The callback function run when an item is selected The following are optional: - **keymap** The string passed to `nvim_set_keymap`, this will always be registered in normal mode - **description** The text description that will be used in the user command - **name** The name of the backend, this will fallback to the command if its not set It will also allow to register a backend in a couple of different ways: - With a backend module table - With a backend module name - With a backend module name and override options This will look for for a lua module `ivy.backends.files`. The module will be required and registered as a backend. ```lua register_backend "ivy.backends.files" ``` This will do the same with the module string however, before the backend is registered the keymap will be overridden ```lua register_backend({ "ivy.backends.file", { keymap = "<C-p>" } }) ``` Test Plan: CI / Manual testing locally
2024-06-16 20:44:16 +00:00
register_backend "ivy.backends.rg"
feat: add ripgrep backend `rg` will now be used over `ag` if it is available. This is because `rg` is a faster alternative reduces lag when searching larger codebases. `ag` is also now conditionally loaded if the command is available.
2023-05-23 07:01:38 +00:00
elseif vim.fn.executable "ag" then
feat: split out register backend so it can be used as an external API Summary: Split out the register backend function from being a private function. A backend is a table that will define all of the attributes for a run function. The attributes are as follows: - **command** The name of the command that will be registered as a vim user command. - **items** The callback function that will be passed to the run function that will gather the items for selection - **callback** The callback function run when an item is selected The following are optional: - **keymap** The string passed to `nvim_set_keymap`, this will always be registered in normal mode - **description** The text description that will be used in the user command - **name** The name of the backend, this will fallback to the command if its not set It will also allow to register a backend in a couple of different ways: - With a backend module table - With a backend module name - With a backend module name and override options This will look for for a lua module `ivy.backends.files`. The module will be required and registered as a backend. ```lua register_backend "ivy.backends.files" ``` This will do the same with the module string however, before the backend is registered the keymap will be overridden ```lua register_backend({ "ivy.backends.file", { keymap = "<C-p>" } }) ``` Test Plan: CI / Manual testing locally
2024-06-16 20:44:16 +00:00
register_backend "ivy.backends.ag"
feat: add ripgrep backend `rg` will now be used over `ag` if it is available. This is because `rg` is a faster alternative reduces lag when searching larger codebases. `ag` is also now conditionally loaded if the command is available.
2023-05-23 07:01:38 +00:00
end
feat: highlight the completion chars in for gui Ref: #9
2022-09-02 20:28:06 +00:00
vim.cmd "highlight IvyMatch cterm=bold gui=bold"
Reference in a new issue Copy permalink