Question 1

How to install telescope-egrepify with packer.nvim?

Accepted Answer

While the README uses lazy.nvim, for packer.nvim, add it as a plugin dependency, ensure Telescope and plenary.nvim are installed, and require the extension in your setup. Follow similar configuration steps as shown in the README.

Question 2

telescope-egrepify vs telescope live_grep: which should I use?

Accepted Answer

Use telescope-egrepify if you need precise search with dynamic ripgrep flags and AND logic; stick with live_grep for simpler fuzzy searching. Egrepify adds overhead but offers more control for targeted queries.

Question 3

How to add a custom prefix like for invert matches?

Accepted Answer

In your Telescope configuration, add a new entry to the prefixes table, e.g., ['!'] = { flag = 'invert-match' }, as demonstrated in the README's configuration example. This maps '!' to ripgrep's --invert-match flag.

Question 4

Does telescope-egrepify work without ripgrep installed?

Accepted Answer

No, it relies on ripgrep for search functionality, parsing its JSON output and building commands. Ripgrep must be installed and accessible, as the plugin is designed around its features and flags.

Question 5

Is treesitter highlighting in telescope-egrepify slow on large files?

Accepted Answer

Yes, enabling results_ts_hl can cause performance issues, especially with large codebases. The README recommends disabling it if you experience latency, as it's an opt-in feature with computational overhead.

Question 6

Can I toggle prefixes during a search, and how?

Accepted Answer

Yes, by default, press <C-z> in insert mode or 'z' in normal mode to toggle prefixes on and off, allowing you to switch between enhanced and standard search modes interactively, as per the mappings table.

telescope-egrepify.nvim

What is telescope-egrepify.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions