- Notifications
You must be signed in to change notification settings - Fork12
A telescope extension to view and search your undo tree 🌴
License
debugloop/telescope-undo.nvim
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Visualize your undo tree and fuzzy-search changes in it. For those days where committing early andoften doesn't work out.
After invokingtelescope-undo you can browse the current buffer's undo tree in a text-based treerepresentation by using telescope'smove_selection_next/previous actions. These are mapped toarrow keys or<C-n>,<C-p> by default. Inserted text is fuzzy matched against the additions anddeletions in each undo state in your undo tree and the finder will limit the results accordingly.While this obviously breaks the tree visuals, you can freely search in your undo states. Thepreviewer will always show the diff of the current selection with some context according to theconfig or yourscrolloff value.
If you have found the undo state you were looking for, you can use<C-cr> or<C-r> to revert tothat state. If you'd rather not change your whole buffer, you can use<cr> to yank the additionsof this undo state into your default register (use<S-cr> or<C-y> to yank the deletions).
Install with your favorite Neovim package manager.
As part of your Telescope plugin spec forlazy.nvim:
{"nvim-telescope/telescope.nvim",dependencies= {"nvim-lua/plenary.nvim","debugloop/telescope-undo.nvim", },config=function()require("telescope").setup({-- the rest of your telescope config goes hereextensions= {undo= {-- telescope-undo.nvim config, see below },-- other extensions:-- file_browser = { ... } }, })require("telescope").load_extension("undo")-- optional: vim.keymap.set("n", "<leader>u", "<cmd>Telescope undo<cr>")end,},If you prefer standalone Lazy plugin specs (my personal recommendation), here's how you do that withsome more options as an example:
{"debugloop/telescope-undo.nvim",dependencies= {-- note how they're inverted to above example {"nvim-telescope/telescope.nvim",dependencies= {"nvim-lua/plenary.nvim"}, }, },keys= { {-- lazy style key map"<leader>u","<cmd>Telescope undo<cr>",desc="undo history", }, },opts= {-- don't use `defaults = { }` here, do this in the main telescope specextensions= {undo= {-- telescope-undo.nvim config, see below },-- no other extensions here, they can have their own spec too }, },config=function(_,opts)-- Calling telescope's setup from multiple specs does not hurt, it will happily merge the-- configs for us. We won't use data, as everything is in it's own namespace (telescope-- defaults, as well as each extension).require("telescope").setup(opts)require("telescope").load_extension("undo")end,},Invoke using:
" Directly by calling it through Telescope's extension interface:" using lua:luarequire("telescope").extensions.undo.undo()" using custom options for just this call:luarequire("telescope").extensions.undo.undo({ side_by_side= true })" using legacy Vim script:Telescopeundo" Using the optional mapping:" using lua:luavim.keymap.set("n","<leader>u","<cmd>Telescope undo<cr>")" using legacy Vim script:nmap<leader>u<cmd>Telescope undo<cr>
The available configuration values are:
use_delta, which controls whetherdelta is used for fancydiffs in the preview section. If set to false,telescope-undowill not usedeltaeven whenavailable and fall back to a plain diff with treesitter highlights.use_custom_command, which can be used to use anunsupported diff tool other thandeltaside_by_side, which tellsdeltato render diffs side-by-side. Thus, requiresdeltato beused. Be aware thatdeltaalways uses its own configuration, so it might be that you're gettingthe side-by-side view even if this is set to false.vim_diff_opts, defaults to all of:help vim.diffdefault options, but setsctxlento yourscrolloff value.entry_format, defaults to"state #$ID, $STAT, $TIME"", which contains the three supportedvariables.time_format, defaults to "" for a timeago-style representation. Can be set to aLua date formatstring.saved_only, defaults to false, but can be used to limit shown undo states to those that havebeen saved to disk.
Further, the undo telescope should accept any of the usual telescope attributes as well as thespecialtheme key which auto-extends the telescope themeon top of any of your explicitlyprovided config. Of course, you might also want to remap some of the default keys.
This is what the defaults look like with some additional explanations:
opts= {extensions= {undo= {use_delta=true,use_custom_command=nil,-- setting this implies `use_delta = false`. Accepted format is: { "bash", "-c", "echo '$DIFF' | delta" }side_by_side=false,vim_diff_opts= {ctxlen=vim.o.scrolloff, },entry_format="state #$ID, $STAT, $TIME",time_format="",saved_only=false, }, },},
The full list will always be available in the code providing the defaultshere.
My personal recommendation is the following, which maximizes the width of the preview to enableside-by-side diffs:
opts= {extensions= {undo= {side_by_side=true,layout_strategy="vertical",layout_config= {preview_height=0.8, }, }, },}
By default, the following mappings are enabled.
require("telescope").setup({extensions= {undo= {mappings= {i= { ["<cr>"]=require("telescope-undo.actions").yank_additions, ["<S-cr>"]=require("telescope-undo.actions").yank_deletions, ["<C-cr>"]=require("telescope-undo.actions").restore,-- alternative defaults, for users whose terminals do questionable things with modified <cr> ["<C-y>"]=require("telescope-undo.actions").yank_deletions, ["<C-r>"]=require("telescope-undo.actions").restore, },n= { ["y"]=require("telescope-undo.actions").yank_additions, ["Y"]=require("telescope-undo.actions").yank_deletions, ["u"]=require("telescope-undo.actions").restore, }, }, }, },})
Important
Note how above example uses the call to telescope'ssetup(). This is due to the fact thatdirectly requiring these actions needstelescope-undo to be available already, which it is notinside lazy'sopts key when using above "standalone" spec. See the next example for how to do itinsideopts.
There is one more mapping available,yank_larger. This yanks either the additions or the deletionsbased on their line count, with the additions winning in case of a tie. This is how you configurethis mapping, or remap any of the default actions for that matter:
opts= {extensions= {undo= {mappings= {-- Wrapping the actions inside a function prevents the error due to telescope-undo being not-- yet loaded.i= { ["<cr>"]=function(bufnr)returnrequire("telescope-undo.actions").yank_larger(bufnr)end, },n= { ["y"]=function(bufnr)returnrequire("telescope-undo.actions").yank_larger(bufnr)end, }, }, }, },}
If you wish to disable one of the default mappings, just set it tofalse.
opts= {extensions= {undo= {mappings= {i= { ["<C-y>"]=false, }, }, }, },}
Suggestions, issues and patches are very much welcome. There are some TODOs sprinkeled into the codethat need addressing, but could also use some input and opinions.
About
A telescope extension to view and search your undo tree 🌴
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors7
Uh oh!
There was an error while loading.Please reload this page.
