BTW, `--include` arguments are ignored by Geany when the recursive option is
not set, because of [this
commit](https://github.com/geany/geany/commit/a0d6a1f618d963e95df656b3e9cc150e4adb95c4).
(For me, that commit wasn't necessary, grep does filter files passed
explicitly. Ideally we wouldn't
My implied question was what other options are order dependent and could be
screwed up by the change?
Better to do away with grep totally as I commented elsewhere.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Indeed, they don't. But it's an issue, at least for me.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2321#issuecomment-534760566
Hmm, grep docs don't mention any order requirement for include/exclude.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2321#issuecomment-534760322
If I do a 'Find in Files' I can fill in the 'Files' setting to limit search to
a particular file pattern (fif_files).
However, if I put in '--exclude' and '--exclude-dir' parameters into 'Extra
options' it won't work. This is because '--include' has to come before
--exclude*, but Geany puts