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

2017-02-28 Thread L A Walsh
Dale R. Worley wrote: I think these show that the current 'find' behavior is desirable. As you note in a later message, 'du' does take '.' as its default argument, and that shows up in its output. 'ls' also takes '.' as its default argument, and that does not show up in its output, but that's

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

2017-02-28 Thread James Youngman
On Mon, Feb 27, 2017 at 12:59 AM, L A Walsh wrote: > > > James Youngman wrote: > >> >> Because, typically, -printf is used for output intended for humans rather >> than programs. >> > >Ahh... This is your 1st mistake. Interactive forms, and the > ones used most often are supposed to be

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

2017-02-28 Thread Dale R. Worley
L A Walsh writes: > What do 'ls' and 'du' do, since in the absence of a path > they start from the current directory but don't seem to > prepend './'. However, I would not want to change how find > operates in the absence of a path -- compatibility problems. I think these show that the curre

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

2017-02-28 Thread Bernhard Voelker
On 02/28/2017 08:35 AM, L A Walsh wrote: >Ok, then what about: > $ var="" > $ find $var > > That won't fail w/error, yet its the same idea..., no? You have to admit that this is a /bad/ script. Even if the writer intended that behavior falling back to using ".", it would have been better