Workspace based workflow with mini.pick?

[AmerM137]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.pick

Question

I am wondering how a simple workspace based workflow can be implemented using mini.pick (maybe with mini.extra also). For example, in sublime text and lite-xl, you can add a folder to the project/workspace and then your fuzzy finders automatically include the files for searching. This does not require any LSP whatsoever, it's just a workspace based find_files or live_grep.

A typical workflow when starting a new project is to add the language standard library directories to the workspace so you can easily search for both a function or class in your project as well as in the core libraries.

The core libraries will always reside in the same directory so I don't mind hardcoding the search paths. I just need them to be included in my pickers so I can search them when needed.

[echasnovski]

Not sure the full "file files inside all of these directories" is concisely feasible. Both "find files" and "grep" pickers are mostly designed to work within a single directory. The 'grep_live' picker can take globs argument to limit the search, but it would have to be filtering paths inside some single parent directory.

I think the most realistic approach here would be something like #1141, i.e. a "two staged" search: first select a directory to run search or open file explorer; then do the search or explore. I use it in my config. For the case of different hardcoded libraries, the first step might be a plain MiniPick.start() with custom array of hardcoded paths as items with a similar second step.

[AmerM137]

Thanks for the info, the snippet below works.

MiniPick.registry.projects = function()
  local cwd = vim.fn.expand('~/stdlib')
  local choose = function(item)
    vim.schedule(function() MiniPick.builtin.files(nil, { source = { cwd = item.path } }) end)
  end
  return MiniExtra.pickers.explorer({ cwd = cwd }, { source = { choose = choose } })
end

This allows me to pick between different directories under '~/stdlib' then launch a files picker after for that directory.

question: if I replace the return statement with the following, I end up in my current directory, why is that? I copied your version out of curiosity.

return MiniPick.builtin.files({ cwd = cwd }, { source = { choose = choose } })

I am guessing that explorer works only directories but the file picker handles only files.

[echasnovski]

question: if I replace the return statement with the following, I end up in my current directory, why is that? I copied your version out of curiosity.

return MiniPick.builtin.files({ cwd = cwd }, { source = { choose = choose } })

I am guessing that explorer works only directories but the file picker handles only files.

Not quite. The reason is that MiniExtra.pickers.explorer() supports cwd as local option (because it fits the idea of "explore in this directory") while MiniPick.builtin.files() does not. I myself don't really like the inconsistency, but the reason is that cwd is the general property of any picker source and having two ways of doing the same thing is a bit redundant.

The usage in my config is a mistake that was propagated during my recent config cleanup. It was meant to use MiniExtra.pickers.explorer indeed. Sorry for the confusion.

As a workaround, users can adjust MiniPick.registry.files to accept cwd as local option. But that would indeed search all files in the cwd (which can take a bit longer), but maybe that is what you want in the first place. With adjusted registry, you can use return MiniPick.registry.files({ cwd = cwd }, { source = { choose = choose } }).

[AmerM137]

Sounds good, thanks for the info!