From: Bart Schaefer <email@example.com> To: firstname.lastname@example.org Cc: zsh <email@example.com> Subject: Re: I can't explain the following Date: Wed, 27 Apr 2022 08:59:36 -0700 [thread overview] Message-ID: <CAH+w=7b9Urd0TqON+1qNb6CZpK2-Zj0Ss+h95mNO5QXRzNLSmg@mail.gmail.com> (raw) In-Reply-To: <CA+rB6GJ1o-GK2KmkFksFrtmquHK8q1pXRa5bvU8V9M9q6Q7xAA@mail.gmail.com> On Wed, Apr 27, 2022 at 8:22 AM Jim <firstname.lastname@example.org> wrote: > >> 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. > > I wonder if the folks maintaining less would even consider this an issue? That execve() is pretty obviously coming from system(). Try writing a little C program that calls system() and strace that, maybe the library is supplying the "/bin/zsh -c" part because lesspipe is a script (which is also undocumented and potentially wrong, since the script does have a #! line). > At least I know what is going on, and what I shouldn't do in .zshenv since I doubt I > will stop using less. You could stop setting LESSOPEN. I long ago decided the "convenience" of having gzip files etc. automatically unpacked was not worth the other side-effects.
next prev parent reply other threads:[~2022-04-27 16:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 15:49 Jim 2022-04-27 1:22 ` Bart Schaefer 2022-04-27 15:20 ` Jim 2022-04-27 15:59 ` Bart Schaefer [this message] 2022-04-27 17:47 ` Jim
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAH+w=7b9Urd0TqON+1qNb6CZpK2-Zj0Ss+h95mNO5QXRzNLSmg@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: I can'\''t explain the following' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.vuxu.org/mirror/zsh/ This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).