JINNOUCHI Yasushi

The current logic uses telescope's `sorters.get_substr_matcher` itself that uses [always lower cases](https://github.com/nvim-telescope/telescope.nvim/blob/b744cf59752aaa01561afb4223006de26f3836fd/lua/telescope/sorters.lua#L539-L539) to match. IMO to solve this, we must create frecency's original sorter and it should change its behavior...

I implemented in trial: #177. If `'smartcase'` is on, it matches upper case letters when prompt string includes one upper case letter at least. * prompt: `abc` → matches: `abc`,...

Ah, `'smartcase'` is not an option for telescope-frecency. This is for Neovim itself: [Options - Neovim docs](https://neovim.io/doc/user/options.html#'smartcase'). ```lua -- in your init.lua vim.opt.smartcase = true -- and setup telescope require("telescope").setup...

I checked with this minimal init.lua and it works validly. ```lua local lazypath = vim.fn.stdpath "data" .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system { "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", --...

I think using Neovim's native option `'smartcase'` is better because the meaning is exactly the same as the purpose -- matching upper case letters only when input string includes one...

The telescope's matcher now has the same feature as here. I have removed frecency's one and made it use telescope's one in #184.

I changed the initialization process and that message appears when you call `:Telescope frecency` at the first time. I think it is less annoying. If you want to remove that...

`db_client.lua` is removed by #93. So I think a similar method for getting entries from frecency is below. ``` self.state.frecency = require("frecency").frecency().picker:fetch_results() ``` (I have not tried @nikhilkalige's snippets with...

I added naive implementation for fuzzy-matching in #166. It simply converts prompt string, such as `foobar`, into regexp: `f.*o.*o.*b.*a.*r` to match. I tested it, but it matches too much candidates...

I see. I tried #166 and didn't feel much useful. But it is a good idea that users can select “fuzzy” or “unfuzzy” matcher in config. I will implement that....