Re: Different variable assignments

On 12.10.2024 09:42, Frank Winkler wrote:

On 12.10.2024 03:59, Janis Papanagnou wrote:
 
 >It depends on your shell. If you choose Kornshell you won't have that
 >issue and can write it as you've done with the output as you'd expect.
 >
 >$ uname -a | read var
 >$ echo "$var"
 >Linux [...snip...]
 >
 >The reason is that the last command in a pipeline will (in Kornshell)
 >be executed in the "current" shell context.
 
Interesting hint! I wasn't aware that there are such differences between
the shells.

Yes, it's a subtle difference, but an important one; many shell users
wondered about the behavior of other shells, and you need to know the
internal information about subprocesses used in pipes to understand
why it doesn't work (in other shells), or why it does in ksh.

And indeed, some simple tests seem to work in an interactive
ksh.

You can rely on it with any official ksh (since ksh88) and branches of
them. (But don't count on it if you're using some inferior ksh clone.)

 
Let's see the whole story. For historical reasons, I'm actually using
ksh for almost all scripts instead of bash for interactive use - not
knowing about the fact above.

From your description below I'm not sure you still have a question or
whether you're just describing what you intended to do and are fine
with ksh's pipeline behavior. (Specifically I'm unsure about the 'B'
and what you mean by "sub-command B" in your example(s).)

If something is still not working for you, please clarify.

 
There, I run command A which is producing output and which is calling
sub-command B, also producing output. This works fine.
What I want to achieve is to grab some parts of the output and store it
in a variable but without changing the output on the screen.
 
So I tried something like
 
tty=`tty`
A | tee $tty | ... | read var

$ man tty
tty - print the file name of the terminal connected to standard input

The 'tty' command in your 'tee' pipeline command has no tty attached;
it reads from the pipe. That's why   A | tee $(tty) | ... | read var
doesn't work as you expected. You have to grab the tty information
outside the pipeline (as you've experienced).

Janis

 
"tee `tty`" inside the command fails, so I do it outside. The output of
A is still there but B's is gone (because B doesn't know anything about
the "tee"?) and the whole thing doesn't seem to be still working. $var
is empty, though this is a ksh script and the stuff behind "tee" is also
working.
To my understanding, the default B can be changed with an option but
when I set it to "B | tee $tty", there's still no output.
 
AFAIR, "var=`...`" works better but as the primary job is the command
itself and the variable is just a spin-off product, I'd prefer to do the
assignment at the end. I believe it looks better then ;) ...
 
Probably it would also be feasible with some temp files but I try to
avoid them wherever possible.
 
Happy week-end!
 
    fw