![\"preview\"](\"https://user-images.githubusercontent.com/38540736/226447816-c696153f-ccee-4e4a-8b6a-55e53ee737f8.png\")
The goal of this plugin is not to be an opinionated bufferline with (more or\nless) limited customization options. Rather, it tries to provide a general\nframework allowing you to build your ideal bufferline, whatever that\nmight look like.
\n
nvim-cokeline aims to be the most customizable bufferline plugin around. If\nyou have an idea in mind of what your bufferline should look like, you should\nbe able to make it look that way. If you can't, open an issue and we'll try to\nmake it happen!
Here's a (very limited) showcase of what it can be configured to look like\n(check out Example configs for more\nexamples):
\nlocal get_hex = require('cokeline/utils').get_hex\n\nrequire('cokeline').setup({\n default_hl = {\n fg = function(buffer)\n return\n buffer.is_focused\n and get_hex('ColorColumn', 'bg')\n or get_hex('Normal', 'fg')\n end,\n bg = function(buffer)\n return\n buffer.is_focused\n and get_hex('Normal', 'fg')\n or get_hex('ColorColumn', 'bg')\n end,\n },\n\n components = {\n {\n text = function(buffer) return ' ' .. buffer.devicon.icon end,\n fg = function(buffer) return buffer.devicon.color end,\n },\n {\n text = function(buffer) return buffer.unique_prefix end,\n fg = get_hex('Comment', 'fg'),\n style = 'italic',\n },\n {\n text = function(buffer) return buffer.filename .. ' ' end,\n style = function(buffer)\n if buffer.is_hovered and not buffer.is_focused then\n return 'underline'\n\tend\n end\n },\n {\n text = 'ο',\n on_click = function(_, _, _, _, buffer)\n\tbuffer:delete()\n end\n },\n {\n text = ' ',\n }\n },\n})\n![\"cokeline-default\"](\"https://user-images.githubusercontent.com/38540736/226447806-0d4be251-788e-495c-abf7-ae5041dcc702.png\")
local get_hex = require('cokeline/utils').get_hex\n\nlocal green = vim.g.terminal_color_2\nlocal yellow = vim.g.terminal_color_3\n\nrequire('cokeline').setup({\n default_hl = {\n fg = function(buffer)\n return\n buffer.is_focused\n and get_hex('Normal', 'fg')\n or get_hex('Comment', 'fg')\n end,\n bg = get_hex('ColorColumn', 'bg'),\n },\n\n components = {\n {\n text = 'ο½',\n fg = function(buffer)\n return\n buffer.is_modified and yellow or green\n end\n },\n {\n text = function(buffer) return buffer.devicon.icon .. ' ' end,\n fg = function(buffer) return buffer.devicon.color end,\n },\n {\n text = function(buffer) return buffer.index .. ': ' end,\n },\n {\n text = function(buffer) return buffer.unique_prefix end,\n fg = get_hex('Comment', 'fg'),\n style = 'italic',\n },\n {\n text = function(buffer) return buffer.filename .. ' ' end,\n style = function(buffer) return buffer.is_focused and 'bold' or nil end,\n },\n {\n text = ' ',\n },\n },\n})\n![\"cokeline-noib3\"](\"https://user-images.githubusercontent.com/38540736/226447808-fc834732-efd1-4fd1-a0de-65ebea213d3f.png\")
local get_hex = require('cokeline/utils').get_hex\n\nrequire('cokeline').setup({\n default_hl = {\n fg = function(buffer)\n return\n buffer.is_focused\n and get_hex('Normal', 'fg')\n or get_hex('Comment', 'fg')\n end,\n bg = 'NONE',\n },\n\n components = {\n {\n text = function(buffer) return (buffer.index ~= 1) and 'β' or '' end,\n fg = get_hex('Normal', 'fg')\n },\n {\n text = function(buffer) return ' ' .. buffer.devicon.icon end,\n fg = function(buffer) return buffer.devicon.color end,\n },\n {\n text = function(buffer) return buffer.filename .. ' ' end,\n style = function(buffer) return buffer.is_focused and 'bold' or nil end,\n },\n {\n text = 'ο',\n on_click = function(buffer)\n buffer:delete()\n end\n },\n {\n text = ' ',\n },\n },\n})\n![\"cokeline-bufferline-lua\"](\"https://user-images.githubusercontent.com/38540736/226447803-13f3d3ee-454f-42be-81b4-9254f95503e4.png\")
Even when you have a lot of buffers open, nvim-cokeline is rendered to always\nkeep the focused buffer visible and in the middle of the bufferline. Also, if a\nbuffer doesn't fit entirely we still try to include as much of it as possible\nbefore cutting off the rest.
![\"rendering\"](\"https://user-images.githubusercontent.com/38540736/226447817-4f3679c8-a10a-48ad-8329-b21c3ee54968.gif\")
If a buffer has an LSP client attached to it, you can configure the style of a\ncomponent to change based on how many errors, warnings, infos and hints are\nreported by the LSP.
\n![\"lsp-styling\"](\"https://user-images.githubusercontent.com/38540736/226447813-4ec42530-9e86-43f5-98ed-fd7b4012120b.gif\")
You can focus and close any buffer by typing its pick_letter. Letters are\nassigned by filename by default (e.g. foo.txt gets the letter f), and by\nkeyboard reachability if the letter is already assigned to another buffer.
local is_picking_focus = require('cokeline/mappings').is_picking_focus\nlocal is_picking_close = require('cokeline/mappings').is_picking_close\nlocal get_hex = require('cokeline/utils').get_hex\n\nlocal red = vim.g.terminal_color_1\nlocal yellow = vim.g.terminal_color_3\n\nrequire('cokeline').setup({\n default_hl = {\n focused = function(buffer)\n return\n buffer.is_focused\n and get_hex('Normal', 'fg')\n or get_hex('Comment', 'fg')\n end,\n bg = get_hex('ColorColumn', 'bg'),\n },\n\n components = {\n {\n text = function(buffer) return (buffer.index ~= 1) and 'β' or '' end,\n },\n {\n text = ' ',\n },\n {\n text = function(buffer)\n return\n (is_picking_focus() or is_picking_close())\n and buffer.pick_letter .. ' '\n or buffer.devicon.icon\n end,\n fg = function(buffer)\n return\n (is_picking_focus() and yellow)\n or (is_picking_close() and red)\n or buffer.devicon.color\n end,\n style = function(_)\n return\n (is_picking_focus() or is_picking_close())\n and 'italic,bold'\n or nil\n end,\n },\n {\n text = ' ',\n },\n {\n text = function(buffer) return buffer.filename .. ' ' end,\n style = function(buffer) return buffer.is_focused and 'bold' or nil end,\n },\n {\n text = 'ο',\n on_click = function(buffer)\n buffer:delete()\n end,\n },\n {\n text = ' ',\n },\n },\n})\n![\"buffer-pick\"](\"https://user-images.githubusercontent.com/38540736/226447793-8e2341b3-e454-49dc-af84-72d3b56f40d3.gif\")
You can add a left sidebar to integrate nicely with file explorer plugins like\nnvim-tree.lua,\nCHADTree or\nNERDTree.
\nlocal get_hex = require('cokeline/utils').get_hex\n\nlocal yellow = vim.g.terminal_color_3\n\nrequire('cokeline').setup({\n default_hl = {\n focused = function(buffer)\n return\n buffer.is_focused\n and get_hex('Normal', 'fg')\n or get_hex('Comment', 'fg')\n end,\n bg = get_hex('ColorColumn', 'bg'),\n },\n\n sidebar = {\n filetype = 'NvimTree',\n components = {\n {\n text = ' NvimTree',\n fg = yellow,\n bg = get_hex('NvimTreeNormal', 'bg'),\n style = 'bold',\n },\n }\n },\n\n components = {\n {\n text = function(buffer) return (buffer.index ~= 1) and 'β' or '' end,\n },\n {\n text = ' ',\n },\n {\n text = function(buffer)\n return buffer.devicon.icon\n end,\n fg = function(buffer)\n return buffer.devicon.color\n end,\n },\n {\n text = ' ',\n },\n {\n text = function(buffer) return buffer.filename .. ' ' end,\n style = function(buffer)\n return buffer.is_focused and 'bold' or nil\n end,\n },\n {\n text = 'ο',\n on_click = function(buffer)\n buffer:delete()\n end,\n },\n {\n text = ' ',\n },\n },\n})\n![\"sidebars\"](\"https://user-images.githubusercontent.com/38540736/226447821-de543b87-909c-445f-ac6e-82f5f6bbf9aa.png\")
When files with the same filename belonging to different directories are opened\nsimultaneously, you can include a unique filetree prefix to distinguish between\nthem:
\n![\"unique-prefix\"](\"https://user-images.githubusercontent.com/38540736/226447822-3315ad2f-35c9-4fc3-a777-c01cd8f2fe46.gif\")
Left click on a buffer to focus it, and right click to delete it. Alternatively, define custom click handlers for each component that override the default behavior.
\n![\"clickable-buffers\"](\"https://user-images.githubusercontent.com/38540736/226447799-e845d266-0658-44e3-bd89-f706577844bf.gif\")
Each component has access to an is_hovered property, and can be given custom on_mouse_enter and on_mouse_leave handlers, allowing for implementations of close buttons, diagnostic previews, and more complex funcionality.
![\"reordering\"](\"https://user-images.githubusercontent.com/38540736/226447818-bdf63d70-e153-4353-992d-d317a5764c09.gif\")
![\"close-icons\"](\"https://user-images.githubusercontent.com/38540736/226447802-29b2919e-dd20-4789-8d6a-250d6d453c64.gif\")
require(\"cokeline.history\"):last():focus()\nIf you have an idea or feature request, don't hesitate to open an issue!
\nThe two main requirements are Neovim 0.5+ and the termguicolors option to be\nset. If you want to display devicons in your bufferline you'll also need the\nkyazdani42/nvim-web-devicons\nplugin and a patched font (see Nerd Fonts).
As of v0.4.0, nvim-lua/plenary.nvim is required as well.
\n{\n \"willothy/nvim-cokeline\",\n dependencies = {\n \"nvim-lua/plenary.nvim\", -- Required for v0.4.0+\n \"kyazdani42/nvim-web-devicons\", -- If you want devicons\n },\n config = true\n}\nvim.opt.termguicolors = true\n\nrequire('packer').startup(function()\n -- ...\n use({\n 'willothy/nvim-cokeline',\n requires = {\n \"nvim-lua/plenary.nvim\", -- Required for v0.4.0+\n \"kyazdani42/nvim-web-devicons\", -- If you want devicons\n },\n config = function()\n require(\"cokeline\").setup()\n end\n })\n -- ...\nend)\nIf your config is still written in Vimscript and you use\nvim-plug:
\ncall plug#begin('~/.config/nvim/plugged')\n \" ...\n Plug 'nvim-lua/plenary.nvim' \" Required for v0.4.0+\n Plug 'kyazdani42/nvim-web-devicons' \" If you want devicons\n Plug 'willothy/nvim-cokeline'\n \" ...\ncall plug#end()\n\nset termguicolors\nlua << EOF\n require('cokeline').setup()\nEOF\n\n\nnote\nCheck out the wiki for more details and API documentation.
\n
All the configuration is done by changing the contents of the Lua table passed to\nthe setup function.
The valid keys are:
\nrequire('cokeline').setup({\n -- Only show the bufferline when there are at least this many visible buffers.\n -- default: `1`.\n show_if_buffers_are_at_least = int,\n\n buffers = {\n -- A function to filter out unwanted buffers. Takes a buffer table as a\n -- parameter (see the following section for more infos) and has to return\n -- either `true` or `false`.\n -- default: `false`.\n filter_valid = function(buffer) -> true | false,\n\n -- A looser version of `filter_valid`, use this function if you still\n -- want the `cokeline-{switch,focus}-{prev,next}` mappings to work for\n -- these buffers without displaying them in your bufferline.\n -- default: `false`.\n filter_visible = function(buffer) -> true | false,\n\n -- Which buffer to focus when a buffer is deleted, `prev` focuses the\n -- buffer to the left of the deleted one while `next` focuses the one the\n -- right.\n -- default: 'next'.\n focus_on_delete = 'prev' | 'next',\n\n -- If set to `last` new buffers are added to the end of the bufferline,\n -- if `next` they are added next to the current buffer.\n -- if set to `directory` buffers are sorted by their full path.\n -- if set to `number` buffers are sorted by bufnr, as in default Neovim\n -- default: 'last'.\n new_buffers_position = 'last' | 'next' | 'directory' | 'number' | function(buffer_a, buffer_b) -> true | false,\n\n -- If true, right clicking a buffer will close it\n -- The close button will still work normally\n -- Default: true\n delete_on_right_click = true | false,\n },\n\n mappings = {\n -- Controls what happens when the first (last) buffer is focused and you\n -- try to focus/switch the previous (next) buffer. If `true` the last\n -- (first) buffers gets focused/switched, if `false` nothing happens.\n -- default: `true`.\n cycle_prev_next = true | false,\n\n -- Disables mouse mappings\n -- default: `false`.\n disable_mouse = true | false,\n },\n\n -- Maintains a history of focused buffers using a ringbuffer\n history = {\n enabled = true | false (default: true)\n size = int (default: 2)\n },\n\n rendering = {\n -- The maximum number of characters a rendered buffer is allowed to take\n -- up. The buffer will be truncated if its width is bigger than this\n -- value.\n -- default: `999`.\n max_buffer_width = int,\n },\n\n pick = {\n -- Whether to use the filename's first letter first before\n -- picking a letter from the valid letters list in order.\n -- default: `true`\n use_filename = true | false,\n\n -- The list of letters that are valid as pick letters. Sorted by\n -- keyboard reachability by default, but may require tweaking for\n -- non-QWERTY keyboard layouts.\n -- default: `'asdfjkl;ghnmxcvbziowerutyqpASDFJKLGHNMXCVBZIOWERTYQP'`\n letters = 'string',\n },\n\n -- The default highlight group values.\n -- The `fg` and `bg` keys are either colors in hexadecimal format or\n -- functions taking a `buffer` parameter and returning a color in\n -- hexadecimal format. Similarly, the `style` key is either a string\n -- containing a comma separated list of items in `:h attr-list` or a\n -- function returning one.\n default_hl = {\n -- default: `ColorColumn`'s background color for focused buffers,\n -- `Normal`'s foreground color for unfocused ones.\n fg = ('hlgroup' | '#rrggbb') | function(buffer) -> ('#rrggbb' | 'hlgroup'),\n\n -- default: `Normal`'s foreground color for focused buffers,\n -- `ColorColumn`'s background color for unfocused ones.\n -- default: `Normal`'s foreground color.\n bg = ('hlgroup' | '#rrggbb') | function(buffer) -> ('hlgroup' | '#rrggbb'),\n\n -- default: `'NONE'`.\n style = 'attr1,attr2,...' | function(buffer) -> 'attr1,attr2,...',\n },\n\n -- The highlight group used to fill the tabline space\n fill_hl = 'TabLineFill',\n\n -- A list of components to be rendered for each buffer. Check out the section\n -- below explaining what this value can be set to.\n -- default: see `/lua/cokeline/defaults.lua`\n components = {..},\n\n -- Custom areas can be displayed on the right hand side of the bufferline.\n -- They act identically to buffer components, except their methods don't take a Buffer object.\n -- If you want a rhs component to be stateful, you can wrap it in a closure containing state.\n rhs = {..},\n\n -- Tabpages can be displayed on either the left or right of the bufferline.\n -- They act the same as other components, except they are passed TabPage objects instead of\n -- buffer objects.\n tabs = {\n placement = \"left\" | \"right\",\n components = {..}\n },\n\n -- Left sidebar to integrate nicely with file explorer plugins.\n -- This is a table containing a `filetype` key and a list of `components` to\n -- be rendered in the sidebar.\n -- The last component will be automatically space padded if necessary\n -- to ensure the sidebar and the window below it have the same width.\n sidebar = {\n filetype = '<filetype>',\n components = {..},\n },\n})\nfunction(buffer)?Some of the configuration options can be functions that take a Buffer as a\nsingle parameter. This is useful as it allows users to set the values of\ncomponents dynamically based on the buffer that component is being rendered\nfor.
The Buffer type is just a Lua table with the following keys:
Buffer = {\n -- The buffer's order in the bufferline (1 for the first buffer, 2 for the\n -- second one, etc.).\n index = int,\n\n -- The buffer's internal number as reported by `:ls`.\n number = int,\n\n is_focused = true | false,\n\n is_modified = true | false,\n\n is_readonly = true | false,\n\n -- The buffer is the first visible buffer in the tab bar\n is_first = true | false,\n\n -- The buffer is the last visible buffer in the tab bar\n is_last = true | false,\n\n -- The mouse is hovering over the current component in the buffer\n -- This is a special variable in that it will only be true for the hovered *component*\n -- on render. This is to allow components to respond to hover events individually without managing\n -- component state.\n is_hovered = true | false\n\n -- The mouse is hovering over the buffer (true for all components)\n buf_hovered = true | false\n\n -- The buffer's type as reported by `:echo &buftype`.\n type = 'string',\n\n -- The buffer's filetype as reported by `:echo &filetype`.\n filetype = 'string',\n\n -- The buffer's full path.\n path = 'string',\n\n -- The buffer's filename.\n filename = 'string',\n\n -- A unique prefix used to distinguish buffers with the same filename\n -- stored in different directories. For example, if we have two files\n -- `bar/foo.md` and `baz/foo.md`, then the first will have `bar/` as its\n -- unique prefix and the second one will have `baz/`.\n unique_prefix = 'string',\n\n -- The letter that is displayed when picking a buffer to either focus or\n -- close it.\n pick_letter = 'char',\n\n -- This needs the `kyazdani42/nvim-web-devicons` plugin to be installed.\n devicon = {\n -- An icon representing the buffer's filetype.\n icon = 'string',\n\n -- The colors of the devicon in hexadecimal format (useful to be passed\n -- to a component's `fg` field (see the `Components` section).\n color = '#rrggbb',\n },\n\n -- The values in this table are the ones reported by Neovim's built in\n -- LSP interface.\n diagnostics = {\n errors = int,\n warnings = int,\n infos = int,\n hints = int,\n },\n}\nIt also has methods that can be used in component event handlers:
\n---@param self Buffer\n---Deletes the buffer\nfunction Buffer:delete()\n\n---@param self Buffer\n---Focuses the buffer\nfunction Buffer:focus()\n\n---@param self Buffer\n---@return number\n---Returns the number of lines in the buffer\nfunction Buffer:lines()\n\n---@param self Buffer\n---@return string[]\n---Returns the buffer's lines\nfunction Buffer:text()\n\n---@param buf Buffer\n---@return boolean\n---Returns true if the buffer is valid\nfunction Buffer:is_valid()\nTabPages?Each method on a tab component is passed a TabPage object as an argument.
TabPage, like Buffer, is simply a Lua table with some relevant data attached.
TabPage = {\n -- The tabpage number, as reported by `nvim_list_tabpages`\n number = integer,\n -- A list of Window objects contained in the TabPage (see wiki for more info)\n windows = Window[],\n -- The currently focused window in the TabPage\n focused = Window,\n -- True if the TabPage is the current TabPage\n is_active = boolean,\n -- True if the TabPage is first in the list\n is_first = boolean,\n -- True if the TabPage is last in the list\n is_last = boolean\n}\ncomponents?You can configure what each buffer in your bufferline will be composed of by\npassing a list of components to the setup function.
For example, let's imagine we want to construct a very minimal bufferline\nwhere the only things we're displaying for each buffer are its index, its\nfilename and a close button.
\nThen in our setup function we'd have:
require('cokeline').setup({\n -- ...\n\n components = {\n {\n text = function(buffer) return ' ' .. buffer.index end,\n },\n {\n text = function(buffer) return ' ' .. buffer.filename .. ' ' end,\n },\n {\n text = 'σ°
',\n on_click = function(buffer)\n buffer:delete()\n end\n },\n {\n text = ' ',\n }\n }\n}\nin this case every buffer would be composed of four components: the first\ndisplaying a space followed by the buffer index, the second one the filename\npadded by a space on each side, then a close button that allows us to\n:bdelete the buffer by left-clicking on it, and finally an extra space.
This way of dividing each buffer into distinct components, combined with the\nability to define every component's text and color depending on some property\nof the buffer we're rendering, allows for great customizability.
\nEvery component passed to the components list has to be a table of the form:
{\n text = 'string' | function(buffer) -> 'string',\n\n -- The foreground, backgrond and style of the component. `style` is a\n -- comma-separated string of values defined in `:h attr-list`.\n fg = '#rrggbb' | function(buffer) -> '#rrggbb',\n bg = '#rrggbb' | function(buffer) -> '#rrggbb',\n style = 'attr1,attr2,...' | function(buffer) -> 'attr1,attr2,...',\n\n -- Or, alternatively, the name of the highlight group\n highlight = 'string' | function(buffer) -> string | nil,\n\n -- If `true` the buffer will be deleted when this component is\n -- left-clicked (usually used to implement close buttons, overrides `on_click`).\n -- deprecated, it is recommended to use the Buffer:delete() method in an on_click event\n -- to implement close buttons instead.\n delete_buffer_on_left_click = true | false,\n\n -- Handles click event for a component\n -- If not set, component will have the default click behavior\n -- buffer is a Buffer object, not a bufnr\n on_click = nil | function(idx, clicks, buttons, modifiers, buffer)\n\n -- Called on a component when hovered\n on_mouse_enter = nil | function(buffer, mouse_col)\n\n -- Called on a component when unhovered\n on_mouse_leave = nil | function(buffer)\n\n truncation = {\n -- default: index of the component in the `components` table (1 for the\n -- first component, 2 for the second, etc.).\n priority = int,\n\n -- default: `right`.\n direction = 'left' | 'middle' | 'right',\n },\n}\nthe text key is the only one that has to be set, all the others are optional\nand can be omitted.
The truncation table controls what happens when a buffer is too long to be\ndisplayed in its entirety.
More specifically, if a buffer's width (given by the sum of the widths of all\nits components) is bigger than the rendering.max_buffer_width config option,\nthe buffer will be truncated.
The default behaviour is truncate the buffer by dropping components from right\nto left, with the text of the last component that's included also being\nshortened from right to left. This can be modified by changing the values of\nthe truncation.priority and truncation.direction keys.
The truncation.priority controls the order in which components are dropped:\nthe first component to be dropped will be the one with the lowest priority. If\nthat's still not enough to bring the width of the buffer within the\nrendering.max_buffer_width limit, the component with the second lowest\npriority will be dropped, and so on. Note that a higher priority means a\nsmaller integer value: a component with a priority of 5 will be dropped\nafter a component with a priority of 6, even though 6 > 5.
The truncation.direction key simply controls from which direction a component\nis shortened. For example, you might want to set the truncation.direction of\na component displaying a filename to 'middle' or 'left', so that if\nthe filename has to be shortened you'll still be able to see its extension,\nlike in the following example (where it's set to 'left'):
![\"buffer-truncation\"](\"https://user-images.githubusercontent.com/38540736/226447798-6aee2e0f-f957-42ab-96dd-3618e78ba4ba.png\")
history?The History keeps track of the buffers you access using a ringbuffer, and provides\nan API for accessing Buffer objects from the history.
\nYou can access the history using require(\"cokeline.history\"), or through the global _G.cokeline.history.
The History object provides these methods:
---Adds a Buffer object to the history\nfunction History:push(bufnr: int)\nend\n\n---Removes and returns the oldest Buffer object in the history\nfunction History:pop(): Buffer | nil\nend\n\n---Returns a list of Buffer objects in the history,\n---ordered from oldest to newest\nfunction History:list(): Buffer[]\nend\n\n---Returns an iterator of Buffer objects in the history,\n---ordered from oldest to newest\nfunction History:iter(): fun(): Buffer | nil\nend\n\n---Get a Buffer object by history index\nfunction History:get(idx: int): Buffer | nil\nend\n\n---Get a Buffer object representing the last-accessed buffer (before the current one)\nfunction History:last(): Buffer | nil\nend\n\n---Returns true if the history is empty\nfunction History:is_empty(): boolean\nend\n\n---Returns the maximum number of buffers that can be stored in the history\nfunction History:capacity(): int\nend\n\n---Returns true if the history contains the given buffer\nfunction History:contains(bufnr: int): bool\nend\n\n---Returns the number of buffers in the history\nfunction History:len(): int\nend\nYou can use the mappings module to create mappings from Lua:
vim.keymap.set(\"n\", \"<leader>bp\", function()\n require('cokeline.mappings').pick(\"focus\")\nend, { desc = \"Pick a buffer to focus\" })\n\n-- etc....\nAlternatively, we expose the following <Plug> mappings which can be used as the right hand\nside of other mappings:
-- Focus the previous/next buffer\n<Plug>(cokeline-focus-prev)\n<Plug>(cokeline-focus-next)\n\n-- Switch the position of the current buffer with the previous/next buffer.\n<Plug>(cokeline-switch-prev)\n<Plug>(cokeline-switch-next)\n\n-- Focuses the buffer with index `i`.\n<Plug>(cokeline-focus-i)\n\n-- Switches the position of the current buffer with the buffer of index `i`.\n<Plug>(cokeline-switch-i)\n\n-- Focus a buffer by its `pick_letter`.\n<Plug>(cokeline-pick-focus)\n\n-- Close a buffer by its `pick_letter`.\n<Plug>(cokeline-pick-close)\nA possible configuration could be:
\nlocal map = vim.api.nvim_set_keymap\n\nmap('n', '<S-Tab>', '<Plug>(cokeline-focus-prev)', { silent = true })\nmap('n', '<Tab>', '<Plug>(cokeline-focus-next)', { silent = true })\nmap('n', '<Leader>p', '<Plug>(cokeline-switch-prev)', { silent = true })\nmap('n', '<Leader>n', '<Plug>(cokeline-switch-next)', { silent = true })\n\nfor i = 1,9 do\n map('n', ('<F%s>'):format(i), ('<Plug>(cokeline-focus-%s)'):format(i), { silent = true })\n map('n', ('<Leader>%s'):format(i), ('<Plug>(cokeline-switch-%s)'):format(i), { silent = true })\nend\n