Path: ...!news.roellig-ltd.de!news.mb-net.net!open-news-network.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.unix.shell Subject: Re: Different variable assignments Date: Sat, 12 Oct 2024 21:32:33 -0000 (UTC) Organization: A noiseless patient Spider Lines: 15 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 12 Oct 2024 23:32:34 +0200 (CEST) Injection-Info: dont-email.me; posting-host="c5355a95aaf967e5c35c649cc5a0b328"; logging-data="352333"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/zJlvU4UVV4Xg/XLXg9i5h" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:WkL554QEIrPl6KyDEAPBqHxpIyU= Bytes: 1966 On Sat, 12 Oct 2024 17:57:16 +0200, Frank Winkler wrote: > I'm still thinking about the difference between "< <(...)" and "<<< > `...`" Not sure about the extra “<”, but “<(«cmd»)” gets substituted with the name of a file (i.e. not stdin) that the process can open and read to get the output of «cmd». Similarly “>(«cmd»)” gets substituted with the name of a file (i.e. not stdout) that the process can open and write to feed input to waiting «cmd». “<<” and “<<<”, on the other hand, are for specifying alternative sources of inline data for stdin, or you can use “«fd»<<” and “«fd»<<<” to specify an alternative «fd» that the process will expect to find already open for reading, to obtain that data.