Date: Fri, 16 Oct 2020 16:20:05 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Robert Huff <roberthuff@rcn.com> Cc: questions@freebsd.org Subject: Re: sh scripting question Message-ID: <444kmtudmy.fsf@be-well.ilk.org> In-Reply-To: <24457.35680.223661.203846@jerusalem.litteratus.org> (Robert Huff's message of "Fri, 16 Oct 2020 08:00:32 -0400") References: <d50ba2c9-617f-6842-ef89-f5933be8f8b3@hotmail.com> <DB8PR06MB64427D88E17F02711EE657A3F6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016113408.16d58d68@archlinux> <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <24457.35680.223661.203846@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff <roberthuff@rcn.com> writes: > OP here. > The filenames at hand were generated by "find" and - on casual > inspection - have no oddities other than the embedded spaces. Since find is in use, I think the canonical solution is to use "find -print0"..."xargs -0" But it's not always convenient to use that mechanism, so there are other methods that have been used quite a few times, depending on the tools the user is comfortable with. In my case, it might involve an inline sed invocation to add the quoting for the spaces. Be well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444kmtudmy.fsf>