Fabian David Schmidt

@protiumx sorry for not having had a look at this more in depth, on a high level, the PR is fine, I'd probably eventually do some clean up for personal...

The PR would have to support that then I guess. You could always embed a defer call or something I guess to recall setting the title for the time being...

Yes please so we can pin down the actual issue. I'll review the selection callbacks as part of tree feature + large RFC in #210 anyways and so would be...

> I know that there is https://github.com/nvim-telescope/telescope-smart-history.nvim, but that plugin feels like a little over-kill (it requires sqlite instead of using files) for a feature that could be added in...

Yeah, there are a lot of wacky cases to consider. I guess that's why it is better left to the user. In other words, best approach is adding something like...

> When checking the mode with vim.api.nvim_get_mode().mode it sometimes evaluates to i (insert) and sometimes n (normal), despite always staying in insert mode. I would try to get the mode...

I've been working extensively on this general concept of actions on multi selections upstream at `telescope.nvim`. The reason that never got merged is because it was very hard to agree...

Sure, very happy to have you aboard :) I'd just say dive in and attend issues/PRs, ping where required, and we'll take it from there. If something doesn't work, we...

Hi there, I'm afraid this extension is unmaintained, as I haven't been using it myself in I don't know how long. You're happy to make PRs to add features/fix bugs...

If we track the name of the picker (as per https://github.com/nvim-telescope/telescope.nvim/pull/1473), the back-end would be straightforward. Nevertheless, the canonical way to pick another cached picker would be `builtin.pickers`. > Is...