Update generated neovim config
This commit is contained in:
@ -117,6 +117,7 @@ See |mini.nvim-buffer-local-config| for more details.
|
||||
* `MiniPickBorder` - window border.
|
||||
* `MiniPickBorderBusy` - window border while picker is busy processing.
|
||||
* `MiniPickBorderText` - non-prompt on border.
|
||||
* `MiniPickCursor` - cursor during active picker (hidden by default).
|
||||
* `MiniPickIconDirectory` - default icon for directory.
|
||||
* `MiniPickIconFile` - default icon for file.
|
||||
* `MiniPickHeader` - headers in info buffer and previews.
|
||||
@ -854,7 +855,7 @@ Refresh active picker
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
*MiniPick.default_match()*
|
||||
`MiniPick.default_match`({stritems}, {inds}, {query}, {do_sync})
|
||||
`MiniPick.default_match`({stritems}, {inds}, {query}, {opts})
|
||||
Default match
|
||||
|
||||
Filter target stritems to contain query and sort from best to worst matches.
|
||||
@ -926,11 +927,13 @@ Parameters ~
|
||||
{inds} `(table)` Array of `stritems` indexes to match. All of them should point
|
||||
at string elements of `stritems`. No check is done for performance reasons.
|
||||
{query} `(table)` Array of strings.
|
||||
{do_sync} `(boolean|nil)` Whether to match synchronously. Default: `nil`.
|
||||
{opts} `(table|nil)` Options. Possible fields:
|
||||
- <sync> `(boolean)` - Whether to match synchronously. Default: `false`.
|
||||
- <preserve_order> `(boolean)` - Whether to skip sort step. Default: `false`.
|
||||
|
||||
Return ~
|
||||
`(table|nil)` Depending on whether computation is synchronous (either `do_sync`
|
||||
is truthy or there is an active picker):
|
||||
`(table|nil)` Depending on whether computation is synchronous (either `opts.sync`
|
||||
is `true` or there is an active picker):
|
||||
- If yes, array of `stritems` indexes matching the `query` (from best to worst).
|
||||
- If no, `nil` is returned with |MiniPick.set_picker_match_inds()| used later.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user