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
Have a nice day,
Berny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/02/2017 11:55 PM, Eric Blake wrote:
> I think that always outputting ./ by default is a GOOD thing, and that if you
> want to strip it, you should put in
> extra effort (whether that be post-processing, [...])
E.g. with realpath(1):
$ find -e
Eric Blake wrote:
For the record, POSIX
That's already been stated in the prior conversation, even though
you claim you know that:
"Please don't assume that I haven't been following the conversation".
So why are you repeating closed issues?
find ''
magically starting t
Eric Blake wrote:
Ah, but that's where you're missing the point. Changing interactive
behavior does NOT require that you are forced to always type the new
command-line option, because you are free to set up a wrapper function,
alias, or script on $PATH, which will supply that option on your beh
On 02/28/2017 11:28 AM, James Youngman wrote:
>> (in the sense that the find command line is a little language with
>>> specified semantics and the user is communicating their wishes by using
>>> that language). POSIX specifies no semantics for the case where no path
>>> name argument is specifie
On 03/02/2017 04:24 PM, L A Walsh wrote:
>> Please, do NOT make the behavior depend on an environment variable.
>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 previo
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 wh
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,
