zsh-users
 help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh <zsh-users@zsh.org>
Subject: Re: I can't explain the following
Date: Wed, 27 Apr 2022 10:20:56 -0500	[thread overview]
Message-ID: <CA+rB6GJ1o-GK2KmkFksFrtmquHK8q1pXRa5bvU8V9M9q6Q7xAA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y3ts6igm5M9AjE_Nv-_X=Bi4S0=fKWA-xXHixJorJoBA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

If I wasn't testing things in .zshenv, I wouldn't have known anything
about this. Another reason to watch what goes into startup files,
especially .zshenv.

Feels like I'm watching "Catch 22".

On Tue, Apr 26, 2022 at 8:22 PM Bart Schaefer <schaefer@brasslantern.com>
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.  The doc for "less"
> doesn't mention using $SHELL for this case.
>

I wonder if the folks maintaining less would even consider this an issue?
Oh well.
At least I know what is going on, and what I shouldn't do in .zshenv since
I doubt I
will stop using less. Makes me wonder if less is the only command that does
something like this.

Thanks for the info.  Learned my something new for the day.

Jim Murphy

[-- Attachment #2: Type: text/html, Size: 1349 bytes --]

  reply	other threads:[~2022-04-27 15:23 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 [this message]
2022-04-27 15:59     ` Bart Schaefer
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=CA+rB6GJ1o-GK2KmkFksFrtmquHK8q1pXRa5bvU8V9M9q6Q7xAA@mail.gmail.com \
    --to=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    --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).