I'm running into command line length limitations for large projects (many files found by :relevant-files). Seems that functions like eproject-list-project-files* can generate very long strings, and try to pass them to the shell (e.g. grep via eproject-grep).
I haven't seen any previous issues about this -- have any others seen and/or worked around this limit?
As an alternative for consideration (maybe there's a better solution?), I started implementing some eproject definitions with the find-cmd package, and creating "find | xargs" based extras. e.g. "relevant files" defined with (and (type "f") (or (name ".h") (name ".c")))).
I'm running into command line length limitations for large projects (many files found by :relevant-files). Seems that functions like eproject-list-project-files* can generate very long strings, and try to pass them to the shell (e.g. grep via eproject-grep).
I haven't seen any previous issues about this -- have any others seen and/or worked around this limit?
As an alternative for consideration (maybe there's a better solution?), I started implementing some eproject definitions with the find-cmd package, and creating "find | xargs" based extras. e.g. "relevant files" defined with (and (type "f") (or (name ".h") (name ".c")))).