Re: RFE: allowing "" as a path specification for 'current dir' w/o prepending './' ?

[L A Walsh]

Bernhard Voelker wrote:
> On 03/03/2017 02:23 AM, L A Walsh wrote:
>   
> > Why would there be anyone else on my systems?
> >     
>
> You never walk alone:
>
>   $ ps -ae -o uid | grep -v UID | sort -u | wc -l
>   10
====
   But those *are* 'me'... (18 of them).  In many cases
I've forced processes to run as their own user&group instead of
nobody/nogroup as I wanted the separate trackability.  I probably
pushed for at least a half a dozen of them back to my distro for better
security.  So those are surrogates, or, "clones" if you will.... :-)


BTW, in regards to filenames starting w/'-' for example:



Eric Blake wrote:

On 03/02/2017 04:24 PM, L A Walsh wrote:

> >   ... 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 ...
> >     
> And I find the exact opposite - lack of ./ is visual clutter, because
> with a leading ./, I am guaranteed that it resolves to a filename ...

----
        You are guaranteed that is a filename if it is from the output
of a find command.

	Since the behavior of not prepending "./" would only happen 
in a non-POSIX defined case, there would be no place for such
usage in POSIX-compliant scripts.

        It was meant to be used in an interactive form -- not in
a portable script.

        So you can be *certain*, if 'find' outputs a filename
starting with '-', it's a filename, not a switch.  AFAIK, find doesn't
echo out switches.  If you are using it as input to another script,
use "." as a starting path to get *defined* behavior.  Problem solved.