Open clach04 opened 6 months ago
Looks like this is trigged by the use of command line argument stuffing, grep already has this (expected) behavior when passing args. For example:
ptig: ? rg git scm
Query time: 0.00 seconds
ptig: ? rg -i git scm
Too many search terms (use quotes)
ptig: ? rg -y git scm
Too many search terms (use quotes)
ptig: ? rg -y "git scm"
Query time: 0.00 seconds
ptig: ? rg -i -y "git scm"
Query time: 0.00 seconds
New filename find calls grep with command line args (for search filename only).
Idea, potentially stuff additional arguments into do_grep() as additional parameters to skip this trigger unless user has explicitly issued command line flags.
Two issues:
find filename no longer includes encrypted files, example,
f aesop
-e
(or-k
for encrypted only)) flag, example,f -e aesop
set enc
find filename using search terms with spaces raise error,
Too many search terms (use quotes)
. Example,f git scm
f "git scm"
Sample session ptig: ? f git scm Too many search terms (use quotes)
Since fix/change https://github.com/clach04/puren_tonbo/commit/240ffdba2eeffe96dcc83e6b5ddaabe15cc3c770 find (filename only search) no longer searches for filenames with spaces without escaping. This is inconsistent with search/grep and a regression from previous behavior.
the later is the workaround. By default should not need to escape in ptig, defaults to literal mode.