Re: Re: [PATCH 3/4] findcmd: define the user import finder function
From:
Matheus Afonso Martins Moreira
Subject:
Re: Re: [PATCH 3/4] findcmd: define the user import finder function
Date:
Fri, 03 May 2024 04:39:06 +0000
> Why does this only find executable files?
My intention was to eliminate as many non-candidate entries
as possible. For example, developers might put data files among
the code files, it would be useful if they were not searched. That's
why I also set the no direcrories flag.
I admit I was somewhat tempted by the availability of the flags
when I studied the source code. I saw it there and wanted to find
an interesting use for it. There are other possible solutions, of course.
Developers could put data in /usr/share and ~/.local/share.
> Executable scripts tend to be unsuitable for sourcing anyway
> because they assume that they will be run in their own shell process
That's a very good point. Would you say that the proper semantics
of a library shell script would be that of a non-executable file?
Would a non-executable files only filter for the finder function
be useful?
Thanks for the feedback,
Matheus