Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: I can't explain the following

X-seq: zsh-users 27701
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: linuxtechguy@xxxxxxxxx
Cc: zsh <zsh-users@xxxxxxx>
Subject: Re: I can't explain the following
Date: Tue, 26 Apr 2022 18:22:40 -0700
Archived-at: <https://zsh.org/users/27701>
In-reply-to: <CA+rB6GK-z6DD-nNwLtUZqwUfo+T=oV3+iQDPEpnVCzsVtT1K2A@mail.gmail.com>
List-id: <zsh-users.zsh.org>
References: <CA+rB6GK-z6DD-nNwLtUZqwUfo+T=oV3+iQDPEpnVCzsVtT1K2A@mail.gmail.com>

On Tue, Apr 26, 2022 at 8:51 AM Jim <linux.tech.guy@xxxxxxxxx> wrote:
>
> What I can't figure out is why zsh/"less" does what it does. Could someone enlighten me?

It's this:

> LESSOPEN='|lesspipe %s'

> Is there a way of "tracing" what is happening?

strace -ff -o tracefile less ...

... and then look through the set of files that are produced.  To save
you the trouble:

execve("/bin/sh", ["sh", "-c", "/bin/zsh -c lesspipe\\ C.gz"],
0x7ffc15c0b800 /* 56 vars */) = 0

Now, why it's running lesspipe with "/bin/zsh -c" instead of with
/bin/sh or at least "/bin/zsh -fc" I don't know.  The doc for "less"
doesn't mention using $SHELL for this case.

Follow-Ups:
- Re: I can't explain the following
  - From: Jim

References:
- I can't explain the following
  - From: Jim

Messages sorted by: Reverse Date, Date, Thread, Author