James Trew

My approach would be to take advantage of the action to cycle through entries and change the colorscheme when a new entry is "selected". This relates to the `shift_selection` action...

That looks good at first glance.

@MovieMaker93 I don't have any concerns off the top of my head. Are you able to open a PR? I'd be better able to see the change and offer feedback...

I'm thinking it might be easier to just repurpose the `get_selection_window` option. One caveat would be that the `picker` and `entry` params would be nil but I'm not sure how...

I think for large code bases like this, having a custom previewer is probably best. ```lua require("telescope").setup({ pickers = { git_branches = { previewer = require("telescope.previewers").new_termopen_previewer({ get_command = function(entry) return...

> btw, the default mapping for scrolling preview window down is overlapped by git_delete_branch here. Should this be reported as bug? I think this was just a design choice. Overriding...

Oh sorry those symbols are termcodes for `` and `` respectively. Seems to not render well in github.  You can get those insert `` in insert mode. Or replace...

I'm not sure about this. I have a few different thoughts but to put it concisely... `file_sorter` does score entries on initial startup. It's probably just not affecting anything based...

Yeah so just because those sorters actually affect the initial sorting, it doesn't mean they aren't scoring things initially. They're just giving everything the same score. I'm not sure it...

Maybe I muddled the waters of responsibility a little bit. The point I wanted to get across is not really that fzf-native or fzf-native should implement better initial sorting. Their...