Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Kaz Kylheku <643-408-1753@kylheku.com>
Newsgroups: comp.unix.shell
Subject: Re: Another shellcheck rant...
Date: Wed, 5 Mar 2025 18:50:30 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <20250305104105.793@kylheku.com>
References: <vq9od5$18ps$2@news.xmission.com>
Injection-Date: Wed, 05 Mar 2025 19:50:31 +0100 (CET)
Injection-Info: dont-email.me; posting-host="e703fbd4fabb26684ed42c07be41654f";
	logging-data="2674094"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18BPh5wStu/zTsAjrRjAH3pYujS3esT4ps="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:KNMRqGc/1gUpHxLqT+MlNM6mgOg=
Bytes: 1614

On 2025-03-05, Kenny McCormack <gazelle@shell.xmission.com> wrote:
> I have a loop like:
>
>     exec 3< somefile
>     while read -ru3 fn; do
> 	ffmpeg -i "$fn" ... "OutDir/$fn"
>     done
>
> Shellcheck flags both the "read" and the "ffmpeg", with messages to the
> effect that ffmpeg might swallow up stdin - not realizing that the -u3
> means the "read" is not reading from stdin.

Maybe the shellcheck code does know about -u, but simply doesn't
recognize it when it is clumped like that, together with another
option and its own argument.


-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca