Question 1

How to use lucene-grep for searching in code files with specific extensions?

Accepted Answer

Use GLOB patterns like '*.{clj,edn}' as a positional argument after the query, e.g., './lmgrep "main" "*.{clj,edn}"'. This recursively searches files with .clj or .edn extensions, similar to grep's --include.

Question 2

lucene-grep vs grep: which is better for log analysis with stemming?

Accepted Answer

lucene-grep excels for linguistic-heavy tasks like stemming and phrase matching, using Lucene's analyzers, while grep is faster for simple regex. Choose lucene-grep if you need advanced text processing, but grep for basic, high-speed searches.

Question 3

How to configure stemming for different languages in lucene-grep?

Accepted Answer

Use the --stemmer flag with options like english, french, or german, or specify it in a JSON analysis config. For example, '--stemmer=english' applies English stemming, as detailed in the text analysis section.

Question 4

Can lucene-grep output results in JSON format for scripting?

Accepted Answer

Yes, use the --format=json flag to output results as JSON, including line numbers and text. Combined with --with-details, it adds raw highlights, making it easy to parse in other tools.

Question 5

Is lucene-grep compatible with Windows and how to install it?

Accepted Answer

Yes, it supports Windows via Scoop or direct binary downloads. Install using 'scoop install lmgrep' from the scoop-clojure bucket, or grab the binary from GitHub releases, but note some features like binary file skipping are limited.

Question 6

How to pipe data from another command into lucene-grep?

Accepted Answer

Pipe input to STDIN, e.g., 'cat file.txt | ./lmgrep "query"'. For streamed matching with dynamic queries, use --streamed and pass JSON with query and text, as shown in the examples.

lmgrep

What is lmgrep?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions