Eric Blake wrote:
On 03/02/2017 01:25 AM, L A Walsh wrote:
However given that some like the current behavior, a way to
allow users a choice of of no-path being the same as "." or
not-prepending "dot" would be the addition of an ENV var
along the lines of "FIND_NOPATH_PREPENDS_NODOT" (or whatever!).
Please, do NOT make the behavior depend on an environment variable.
That is a sure way to break scripts that are not expecting the
environment to cause a change in behavior. If you want a different
behavior, the right way to do it is via a new command-line option.
----
Please do not make blanket statements: A foolish consistency is
the Hobgoblin of small minds.", and please don't come into the
middle of a discussion without reading the previous conversation:
> ... I find the addition of "./" -- for interactive
> use, to be *Visual Clutter*. I was hoping for a simple 'short-cut'
> for interactive use to get rid of the visual clutter ...
This is not about a POSIX specified feature (it's undefined), and
is not about something that would normally be used with scripts, so
your argument doesn't seem applicable.
This topic is about a default, interactive behavior. Not only
does that not apply to scripts, but, by definition, precludes use
of command-line options.
-l
