From: Mikael Magnusson <email@example.com>
To: Matt Zagrabelny <firstname.lastname@example.org>
Subject: Re: inconsistency between bash and zsh subshells
Date: Mon, 23 May 2022 19:31:59 +0200 [thread overview]
Message-ID: <CAHYJk3S4Rw=SRGNcrWjvMjZx0J9_PEUxh25nGm4iZ5Rww7-WnQ@mail.gmail.com> (raw)
On 5/23/22, Matt Zagrabelny <email@example.com> wrote:
> On Mon, May 23, 2022 at 12:01 PM Mikael Magnusson <firstname.lastname@example.org>
>> On 5/23/22, Matt Zagrabelny <email@example.com> wrote:
>> > Why does the subshell in zsh get executed even though the conditional
>> > branch is not? That is, the "touch"-ing of /tmp/FOO.
>> You're most likely using a poorly written prompt theme and/or thing
>> that updates your terminal title.
> Haha. Probably!
>> Try disabling that code and try
>> again if so.
> Yup - that was it. I removed my .zshrc and it works as expected.
> Thanks for the hint! Time to figure out what poorly written part of my
> .zshrc is to blame.
It will probably be something involving print -P and \a or \007 in
something named preexec. If you change $1 in that to \$1 it is more
likely to work, though it's of course hard to say without seeing the
particular code. If you instead remove any setopt printsubst it should
work fine without modifying the preexec function. (only do one of
these changes). Basically what's happening is you're expanding the
string to put in the title twice, resulting in things like $()
actually being executed which is usually not great.
next prev parent reply other threads:[~2022-05-23 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 16:55 Matt Zagrabelny
2022-05-23 17:01 ` Mikael Magnusson
2022-05-23 17:26 ` Matt Zagrabelny
2022-05-23 17:31 ` Mikael Magnusson [this message]
2022-05-23 17:51 ` Matt Zagrabelny
2022-05-23 17:04 ` Dominik Vogt
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
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).