Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Ralf Damaschke <rwspam@gmx.de>
Newsgroups: comp.unix.shell
Subject: Re: IFS=$'\n'
Date: 13 Aug 2024 21:56:56 GMT
Organization: C.H.A.O.S.
Lines: 18
Message-ID: <pan$989b5$e7369b52$2a19adc3$14541b89@y2plugh.fqdn.th-h.de>
References: <v9f5c1$3q99m$1@dont-email.me>
	<83a5hgad4i.fsf@helmutwaitzmann.news.arcor.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net uOcmAPrTN0G1MEmEKA5oOA8wdaQU24JPZrxEyMk/OFnybKRJXR
Cancel-Lock: sha1:WkGirXCgt4ASxydA0IbJemQMS1I= sha256:WSShuO94T5RHRjkbuyg65bzSSzRFWMLJQ+6ts9m8rSI=
User-Agent: Pan/0.144 (Time is the enemy; 28ab3ba git.gnome.org/pan2)
Bytes: 1447

Helmut Waitzmann wrote:

> But – according to the new POSIX standard
>  ([links to 2024 opengroup specs for find and xargs}) –
>  one can use “xargs“ to get rid of any linefeed trouble at all:
> 
>    find . -iname \*fred\* -type f -print0 |
>    xargs -0 -r -x -- ls -lt --
> 
>  That will work with any file names, even those containing a linefeed
>  character.

OK, print0 is going to become standard, but nowadays I already prefer
(when I use iname for my comfort)

    find . -iname \*fred\* -type f -exec ls -lt -- {} +

I don't see any advantage using print0 and xargs -0.