Bundle of more than two dozen new textobjects for Neovim.
- List of Text Objects
- Non-Goals
- Installation
- Configuration
- Advanced Usage
- Limitations
- Other Text Object Plugins
- Credits
textobject | description | inner / outer | forward-seeking | default keymaps | filetypes (for default keymaps) |
---|---|---|---|---|---|
indentation | surrounding lines with same or higher indentation | see overview from vim-indent-object | - | ii , ai , aI , (iI ) |
all |
restOfIndentation | lines down with same or higher indentation | - | - | R |
all |
greedyOuterIndentation | outer indentation, expanded to blank lines; useful to get functions with annotations | outer includes a blank, like ap /ip |
- | ag /ig |
all |
subword | like iw , but treating - , _ , and . as word delimiters and only part of camelCase |
outer includes trailing _ ,- , or space |
- | iS , aS |
all |
toNextClosingBracket | from cursor to next closing ] , ) , or } |
- | - | C |
all |
toNextQuotationMark | from cursor to next unescaped1 " , ' , or ` |
- | - | Q |
all |
restOfParagraph | like } , but linewise |
- | - | r |
all |
entireBuffer | entire buffer as one text object | - | - | gG |
all |
nearEoL | from cursor position to end of line, minus one character | - | - | n |
all |
lineCharacterwise | current line, but characterwise | outer includes indentation and trailing spaces | - | i_ , a_ |
all |
column | column down until indent or shorter line. Accepts {count} for multiple columns. |
- | - | | |
all |
value | value of key-value pair, or right side of a variable assignment (inside one line) | outer includes trailing commas or semicolons | small | iv , av |
all |
key | key of key-value pair, or left side of a variable assignment | outer includes the = or : |
small | ik , ak |
all |
url | link beginning with "http" | - | big | L |
all |
number | numbers, similar to <C-a> |
inner: only pure digits, outer: number including minus sign and decimal point | small | in , an |
all |
diagnostic | LSP diagnostic (requires built-in LSP) | - | big | ! |
all |
closedFold | closed fold | outer includes one line after the last folded line | big | iz , az |
all |
chainMember | field with the full call, like .encode(param) |
outer includes the leading . (or : ) |
small | im , am |
all |
visibleInWindow | all lines visible in the current window | - | - | gw |
all |
restOfWindow | from the cursorline to the last line in the window | - | - | gW |
all |
mdlink | markdown link like [title](url) |
inner is only the link title (between the [] ) |
small | il , al |
markdown, toml |
mdFencedCodeBlock | markdown fenced code (enclosed by three backticks) | outer includes the enclosing backticks | big | iC , aC |
markdown |
cssSelector | class in CSS like .my-class |
outer includes trailing comma and space | small | ic , ac |
css, scss |
htmlAttribute | attribute in html/xml like href="foobar.com" |
inner is only the value inside the quotes trailing comma and space | small | ix , ax |
html, xml, css, scss, vue |
doubleSquareBrackets | text enclosed by [[]] |
outer includes the four square brackets | small | iD , aD |
lua, shell, neorg, markdown |
shellPipe | command stdout is piped to | outer includes the front pipe character | small | iP ,aP |
bash, zsh, fish, sh |
nvim-treesitter-textobjects already does an excellent job when it comes to using treesitter for text objects, such as function arguments or loops. This plugin's goal is therefore not to provide treesitter-based textobjects.
Have nvim-various-textobjs
set up text objects for you:
-- lazy.nvim
{
"chrisgrieser/nvim-various-textobjs",
lazy = false,
opts = { useDefaultKeymaps = true },
},
-- packer
use {
"chrisgrieser/nvim-various-textobjs",
config = function ()
require("various-textobjs").setup({ useDefaultKeymaps = true })
end,
}
If you prefer to set up your own keybindings, use this code and then see the Configuration section for information on setting your own keymaps.
-- lazy.nvim
{
"chrisgrieser/nvim-various-textobjs",
lazy = true,
},
-- packer
use {
"chrisgrieser/nvim-various-textobjs",
}
Note
You can also use the disabledKeymaps
config option to disable only some default keymaps.
The .setup()
call is optional if you are fine with the defaults below.
-- default config
require("various-textobjs").setup {
-- lines to seek forwards for "small" textobjs (mostly characterwise textobjs)
-- set to 0 to only look in the current line
lookForwardSmall = 5,
-- lines to seek forwards for "big" textobjs (mostly linewise textobjs)
lookForwardBig = 15,
-- use suggested keymaps (see overview table in README)
useDefaultKeymaps = false,
-- disable some default keymaps, e.g. { "ai", "ii" }
disabledKeymaps = {},
}
If you want to set your own keybindings, you can do so by calling the respective functions:
- The function names correspond to the textobject names from the overview table.
- The keymaps need to be called as Ex-command, otherwise they will not be
dot-repeatable. (
function () require("various-textobjs").diagnostic() end
as third argument for the keymap works in general, but the text objects will not be dot-repeatable then.)
Previous versions used a boolean parameter, but for verbosity reasons, this plugin now uses "outer"
and "inner"
. For backwards-compatibility with existing keymaps, boolean parameters are still accepted though.
-- example: `?` for diagnostic textobj
vim.keymap.set({ "o", "x" }, "?", '<cmd>lua require("various-textobjs").diagnostic()<CR>')
-- example: `aS` for outer subword, `iS` for inner subword
vim.keymap.set({ "o", "x" }, "aS", '<cmd>lua require("various-textobjs").subword("outer")<CR>')
vim.keymap.set({ "o", "x" }, "iS", '<cmd>lua require("various-textobjs").subword("inner")<CR>')
-- exception: indentation textobj requires two parameters, the first for
-- exclusion of the starting border, the second for the exclusion of ending
-- border
vim.keymap.set(
{ "o", "x" },
"ii",
'<cmd>lua require("various-textobjs").indentation("inner", "inner")<CR>'
)
vim.keymap.set(
{ "o", "x" },
"ai",
'<cmd>lua require("various-textobjs").indentation("outer", "inner")<CR>'
)
-- an additional parameter can be passed to control whether blank lines are included
vim.keymap.set(
{ "o", "x" },
"ai",
'<cmd>lua require("various-textobjs").indentation("outer", "inner", "noBlanks")<CR>'
)
For your convenience, here the code to create mappings for all text objects. You can copypaste this list and enter your own bindings.
➡️ Mappings for all text objects
local keymap = vim.keymap.set
keymap({ "o", "x" }, "ii", "<cmd>lua require('various-textobjs').indentation('inner', 'inner')<CR>")
keymap({ "o", "x" }, "ai", "<cmd>lua require('various-textobjs').indentation('outer', 'inner')<CR>")
keymap({ "o", "x" }, "iI", "<cmd>lua require('various-textobjs').indentation('inner', 'inner')<CR>")
keymap({ "o", "x" }, "aI", "<cmd>lua require('various-textobjs').indentation('outer', 'outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').restOfIndentation()<CR>")
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').greedyOuterIndentation('inner')<CR>"
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').greedyOuterIndentation('outer')<CR>"
)
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').subword('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').subword('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').toNextClosingBracket()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').toNextQuotationMark()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').restOfParagraph()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').entireBuffer()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').nearEoL()<CR>")
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').lineCharacterwise('inner')<CR>"
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').lineCharacterwise('outer')<CR>"
)
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').column()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').value('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').value('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').key('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').key('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').url()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').number('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').number('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').diagnostic()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').closedFold('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').closedFold('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').chainMember('inner')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').chainMember('outer')<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').visibleInWindow()<CR>")
keymap({ "o", "x" }, "YOUR_MAPPING", "<cmd>lua require('various-textobjs').restOfWindow()<CR>")
--------------------------------------------------------------------------------------
-- put these into the ftplugins or autocmds for the filetypes you want to use them with
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').mdlink('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').mdlink('outer')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').mdFencedCodeBlock('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').mdFencedCodeBlock('outer')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').cssSelector('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').cssSelector('outer')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').htmlAttribute('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').htmlAttribute('outer')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').doubleSquareBrackets('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').doubleSquareBrackets('outer')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').shellPipe('inner')<CR>",
{ buffer = true }
)
keymap(
{ "o", "x" },
"YOUR_MAPPING",
"<cmd>lua require('various-textobjs').shellPipe('outer')<CR>",
{ buffer = true }
)
The code below retrieves the next URL (within the amount of lines configured in the setup
call), and opens it in your browser. As opposed to vim's builtin gx
, this is forwardseeking, meaning your cursor does not have to stand on the URL.
vim.keymap.set("n", "gx", function()
-- select URL
require("various-textobjs").url()
-- plugin only switches to visual mode when textobj found
local foundURL = vim.fn.mode():find("v")
if not foundURL then return end
-- retrieve URL with the z-register as intermediary
vim.cmd.normal { '"zy', bang = true }
local url = vim.fn.getreg("z")
-- open with the OS-specific shell command
local opener
if vim.fn.has("macunix") == 1 then
opener = "open"
elseif vim.fn.has("linux") == 1 then
opener = "xdg-open"
elseif vim.fn.has("win64") == 1 or vim.fn.has("win32") == 1 then
opener = "start"
end
local openCommand = string.format("%s '%s' >/dev/null 2>&1", opener, url)
vim.fn.system(openCommand)
end, { desc = "URL Opener" })
Using the indentation textobject, you can also create custom indentation-related utilities. A common operation is to remove the line before and after an indentation. Take for example this case where you are removing the foo
condition:
-- before (cursor on `print("bar")`)
if foo then
print("bar")
print("baz")
end
-- after
print("bar")
print("baz")
The code below achieves this by dedenting the inner indentation textobject (essentially running <ii
), and deleting the two lines surrounding it. As for the mapping, dsi
should make sense since this command is somewhat similar to the ds
operator from vim-surround but performed on an indentation textobject. (It is also an intuitive mnemonic: d
elete s
urrounding i
ndentation.)
vim.keymap.set("n", "dsi", function()
-- select inner indentation
require("various-textobjs").indentation(true, true)
-- plugin only switches to visual mode when a textobj has been found
local notOnIndentedLine = vim.fn.mode():find("V") == nil
if notOnIndentedLine then return end
-- dedent indentation
vim.cmd.normal { "<", bang = true }
-- delete surrounding lines
local endBorderLn = vim.api.nvim_buf_get_mark(0, ">")[1] + 1
local startBorderLn = vim.api.nvim_buf_get_mark(0, "<")[1] - 1
vim.cmd(tostring(endBorderLn) .. " delete") -- delete end first so line index is not shifted
vim.cmd(tostring(startBorderLn) .. " delete")
end, { desc = "Delete surrounding indentation" })
If you have some other useful ideas, feel free to share them in this repo's discussion page.
- This plugin uses pattern matching, so it can be inaccurate in some edge cases.
- The value textobject does not work with multi-line values.
Thanks
- To the Valuable Dev for their blog post on how to get started with creating custom text objects.
- To
@vypxl
and@ii14
for figuring out dot-repeatability.
About Me
In my day job, I am a sociologist studying the social mechanisms underlying the digital economy. For my PhD project, I investigate the governance of the app economy and how software ecosystems manage the tension between innovation and compatibility. If you are interested in this subject, feel free to get in touch.
Blog
I also occasionally blog about vim: Nano Tips for Vim
Profiles
Footnotes
-
This respects vim's quoteescape option. ↩