Rocksolid Light - comp.unix.shell - Re: Command 'strings' reading (not) standard input

Re: Command 'strings' reading (not) standard input

<td0qoa$1sj2v$1@dont-email.me>

https://news.novabbs.org/devel/article-flat.php?id=6614&group=comp.unix.shell#6614

Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: lew.pitcher@digitalfreehold.ca (Lew Pitcher)
Newsgroups: comp.unix.shell
Subject: Re: Command 'strings' reading (not) standard input
Date: Wed, 10 Aug 2022 17:43:39 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 41
Message-ID: <td0qoa$1sj2v$1@dont-email.me>
References: <tcu8re$1f6op$1@dont-email.me> <tcu99g$1d1mf$1@dont-email.me>
<871qtpqj8x.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 10 Aug 2022 17:43:39 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="f0d717242ef404672ee7d216be8fd638";
logging-data="1985631"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18pfqSfRcOPiEFV48bV7PeKhZU5V+6HgC0="
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
git://git.gnome.org/pan2)
Cancel-Lock: sha1:Y35VtsW4JzQ95Sitxs14/eThf2M=

by: Lew Pitcher - Wed, 10 Aug 2022 17:43 UTC

On Tue, 09 Aug 2022 13:01:18 -0700, Keith Thompson wrote:

> Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
>> On Tue, 09 Aug 2022 20:25:50 +0200, Janis Papanagnou wrote:
>>
>>> Thanks to process substitution in newer shells I can write, e.g.,
>>> strings <( zcat file.gz ) | ...
>>>
>>> I am wondering, though, whether there's a reason why 'strings' is
>>> not defined to support (additionally) filter calling semantics
>>> ...(binary stream)... | strings | ...(text stream)...
>>
>> Closed, cannot reproduce
>>
>> 14:32 $ strings <(zcat ./cat.gz) | grep comment
>> .comment
>
> The reported problem is that the strings command does not read from its
> standard input. The command you tried is the one that Janis said
> works. `<(zcat ./cat.gz)` will expand to something like "/dev/fd/63",
> which is passed as a file name argument.
[snip]

Ghu! You're right. I misread Janis' post. Sorry.

But, both the "util-linux" version of strings
(https://github.com/util-linux/util-linux)
/and/ the GNU strings implementation (both part of Slackware Linux)
read their data from standard input, and write their results to
standard output.

In Slackware 14.2, the util-linux version of strings does not report
a version number, but came in the util-linux 2.27.1 implementation.
The GNU version of strings reports "GNU strings version 2.26.20160125"

I find it unusual that Janis' version of strings(1) does /not/ default
to stdin/stdout. Or, perhaps he didn't try it?

--
Lew Pitcher
"In Skills, We Trust"

Re: Command 'strings' reading (not) standard input

<td12oj$1tv5i$1@dont-email.me>

copy mid

https://news.novabbs.org/devel/article-flat.php?id=6615&group=comp.unix.shell#6615

copy link Newsgroups: comp.unix.shell

Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: janis_papanagnou@hotmail.com (Janis Papanagnou)
Newsgroups: comp.unix.shell
Subject: Re: Command 'strings' reading (not) standard input
Date: Wed, 10 Aug 2022 22:00:19 +0200
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <td12oj$1tv5i$1@dont-email.me>
References: <tcu8re$1f6op$1@dont-email.me> <tcu99g$1d1mf$1@dont-email.me>
<871qtpqj8x.fsf@nosuchdomain.example.com> <td0qoa$1sj2v$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 10 Aug 2022 20:00:19 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="798da8edef6600ed2ae6cf5cd78db43c";
logging-data="2030770"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18hWjAJd8ufJbmXvvq6pc6w"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
Thunderbird/45.8.0
Cancel-Lock: sha1:UM9L6meqEg6+k4OkMRJDRGjD3p4=
In-Reply-To: <td0qoa$1sj2v$1@dont-email.me>
X-Enigmail-Draft-Status: N1110

by: Janis Papanagnou - Wed, 10 Aug 2022 20:00 UTC

On 10.08.2022 19:43, Lew Pitcher wrote:
>
> I find it unusual that Janis' version of strings(1) does /not/ default
> to stdin/stdout. Or, perhaps he didn't try it?

As I wrote in my other posts I got fooled by the syntax description
of my strings man page; there I saw that a file was requested and
tried just the often seen stdin/stdout as placeholder '-' (which
didn't work, though, because that has another meaning in my strings
command).

Janis

You're already carrying the sphere!

devel / comp.unix.shell / Re: Command 'strings' reading (not) standard input

Subject	Author
Command 'strings' reading (not) standard input	Lew Pitcher
Command 'strings' reading (not) standard input	Janis Papanagnou