A telescope.nvim extension designed to provide the best possible suggestions for quickly opening files in Neovim. smart-open will improve its suggestions over time, adapting to your usage.
Warning
In a way, but most other solutions require multiple mappings to search:
- git files
- open buffers
- recent files
The goal of smart-open is to give you highly relevant results with as few keystrokes as possible--so much so that only a single mapping is needed for searching everything while still managing to be quick about it.
The source of suggestions is a combination of files under the current working directory, and your history. Ranking takes the following factors into account:
- How well the file path matches the search text
- How well the file name matches the search text (see notes for file name details)
- Recency of last open
- Whether the file is the last-edited (that is, alternate buffer)
- The file is currently open
- How close the file's parent directory is to the currently-open file's
- "Frecency" - how frequently the file has been opened, with a bias toward recent opens. (See notes on frecency)
- Whether the file is anywhere under the current working directory. This is especially useful if using an extension that cd's to your project's top-level directory.
This ranking algorithm is self-tuning. Over time, the weights of the factors above will be adjusted based upon your interaction with it. The tuning process is especially sensitive to selecting a suggestion that is not at the top. Weights will be adjusted relative to the higher-ranked suggestions that were not selected.
Calculating and tuning all these factors might sound slow, but this is not the case. Results return quickly and the impact of these calculations are optimized to be negligible.
- In certain cases, both the parent directory as well as the filename are treated as the "file name". This is because for some file structures, the filename itself isn't informative. For example, if your JavaScript project uses the convention of
directoryName/index.jsthroughout, then searching for "index" isn't going to be very useful. As a result, we treatindex.jsandinit.luaas special cases, and treatparentDirectory/filenameas though it were the filename. - Search text matching uses the fzy algorithm. If telescope-fzy-native is installed, it will be used.
- Determining how close two files' directories are is just a function of how many directories the two files have in common. This means that for any pair of files in the same directory, the score is more significant the deeper that directory is.
- Frecency controls how long a given file is preserved in history. While it can be replenished by opening that file, this value otherwise dwindles over time. When the value is fully depleted, the file can be cleared from the history, improving performance and disk usage. Frecency uses an implementation of Mozilla's Frecency algorithm (used in Firefox's address bar).
- Thanks to telescope-frecency.nvim for inspiration. This code is also adapted from that code base.
Using an implementation of Mozilla's Frecency algorithm (used in Firefox's address bar), files edited frecently are given higher precedence in the list index.
As the extension learns your editing habits over time, the sorting of the list is dynamically altered to prioritize the files you're likely to need.
- neovim 0.6+ (required)
- ripgrep (required)
- sqlite3 (required)
- telescope.nvim (required)
- sqlite.lua (required)
- nvim-web-devicons (optional)
- telescope-fzy-native.nvim (optional)
- telescope-fzf-native.nvim (optional)
Timestamps, scoring weights, and file records are stored in an SQLite3 database for persistence and speed.
Put the following in your lazy.setup(...):
{
"danielfalk/smart-open.nvim",
branch = "0.2.x",
config = function()
require("telescope").load_extension("smart_open")
end,
dependencies = {
"kkharji/sqlite.lua",
-- Only required if using match_algorithm fzf
{ "nvim-telescope/telescope-fzf-native.nvim", build = "make" },
-- Optional. If installed, native fzy will be used when match_algorithm is fzy
{ "nvim-telescope/telescope-fzy-native.nvim" },
},
}use {
"danielfalk/smart-open.nvim",
branch = "0.2.x",
config = function()
require"telescope".load_extension("smart_open")
end,
requires = {
{"kkharji/sqlite.lua"},
-- Only required if using match_algorithm fzf
{ "nvim-telescope/telescope-fzf-native.nvim", run = "make" },
-- Optional. If installed, native fzy will be used when match_algorithm is fzy
{ "nvim-telescope/telescope-fzy-native.nvim" },
}
}sqlite3 must be installed locally. (if you are on mac it might be installed already)
Download precompiled and set let g:sqlite_clib_path = path/to/sqlite3.dll (note: /)
sudo pacman -S sqlite # Arch
sudo apt-get install sqlite3 libsqlite3-dev # Ubuntusudo dnf install sqlite sqlite-devel sqlite-tcl
programs.neovim.plugins = [
{
plugin = pkgs.vimPlugins.sqlite-lua;
config = "let g:sqlite_clib_path = '${pkgs.sqlite.out}/lib/libsqlite3.so'";
}
];environment.variables = {
LIBSQLITE = "${pkgs.sqlite.out}/lib/libsqlite3.so";
};If no database is found when running Neovim with the plugin installed, a new one is created and entries from shada v:oldfiles are automatically imported.
:Telescope smart_open
..or to map to a key:
vim.keymap.set("n", "<leader><leader>", function ()
require("telescope").extensions.smart_open.smart_open()
end, { noremap = true, silent = true })Options can be set when opening the picker. For example:
require('telescope').extensions.smart_open.smart_open {
cwd_only = true,
filename_first = false,
}-
cwd_only(default:false)Limit the results to files under the current working directory. This is normally not needed because if you prefer this pattern of access, then the plugin will pick up on that over time regardless, to the point where files under
cwdwill be recommended above all others. -
filename_first(default:true)Format filename as "filename path/to/parent/directory" if
trueand "path/to/parent/directory/filename" iffalse.
See default configuration for full details on configuring Telescope.
-
show_scores(default :false)To see the scores generated by the algorithm in the results, set this to
true. -
ignore_patternsPatterns in this table control which files are indexed (and subsequently which you'll see in the finder results).
Defaults can be found in the source code
-
match_algorithm(default:fzy)The algorithm to use for determining how well each file path matches the typed-in search text. Options are
fzfandfzy. Entered text is not the only factor considered in ranking but is typically the most significant. -
disable_devicons(default:false)Disable devicons (if available)
-
open_buffer_indicators(default:{previous = "•", others = "∘"}) -
result_limit(default:40)Limit the number of results returned. Note that this is kept intentionally low by default for performance. The main goal of this plugin is to be able to jump to the file you want with very few keystrokes. Smart open should put relevant results at your fingertips without having to waste time typing too much or scanning through a long list of results. If you need to scan regardless, go ahead and increase this limit. However, if better search results would make that unnecessary and there's a chance that smart open could provide them, please file a bug to help make it better.
telescope.setup {
extensions = {
smart_open = {
match_algorithm = "fzf",
disable_devicons = false,
},
},
}
For files not already in your history, smart-open uses ripgrep for scanning the current directory. (The command is roughly: rg --files --glob-case-insensitive --hidden --ignore-file=<cwd>/.ff-ignore -g <ignore_patterns...>).
As a result, files added to git, but also ignored by git, will not be included. While not common, this is something that git allows. If this becomes a problem you can work around it by either changing your git ignore patterns, editing the file in neovim in some other way, (thereby adding it to the history), or by using ripgrep's .ignore file for overriding git.
Directory
