using --pre in RIPGREP_CONFIG_PATH causes "preprocessor command could not start:"

[gcflymoto]

Hi, very excited to be able to share the $HOME/.lessfilter for less with rg --pre filter .. it works fine when called fully from the shell

rg --pre $HOME/.lessfilter  "DVT Builder"  dvt_build.log.zst
28:DVT Builder 22.1.17 Copyright (C) 2005-2022 AMIQ EDA s.r.l.

# but through an rc file: 

cat $HOME/.ripgreprc 
--pre-glob
*.{gz,bz2,xz,zst,zstd,zstandard,pdf}
--pre
$HOME/.lessfilter

# it seems rg over-quotes the command?

env RIPGREP_CONFIG_PATH=$HOME/.ripgreprc rg "DVT Builder" dvt_build.log.zst
DEBUG|grep_regex::literal|crates/regex/src/literal.rs:58: literal prefixes detected: Literals { lits: [Complete(DVT Builder)], limit_size: 250, limit_class: 10 }
DEBUG|globset|crates/globset/src/lib.rs:431: built glob set; 0 literals, 0 basenames, 12 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
DEBUG|globset|crates/globset/src/lib.rs:431: built glob set; 0 literals, 0 basenames, 6 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
dvt_build.log.zst: preprocessor command could not start: '"$HOME/.lessfilter" "dvt_build.log.zst"': No such file or directory (os error 2)

@BurntSushi Any suggestions on how to set $HOME/ripgreprc with a --pre ??

[BurntSushi]

The configuration file doesn't support environment variables. You'll need to pass the full absolute path.

[gcflymoto]

Of course! There is no shell expansion. Perfect thank you @BurntSushi !