zsh-users
 help / color / mirror / code / Atom feed
From: Dominik Vogt <dominik.vogt@gmx.de>
To: zsh-users@zsh.org
Subject: Re: Frozen command substitution
Date: Sat, 11 Feb 2023 21:28:43 +0100	[thread overview]
Message-ID: <Y+f6e75KQM4/kFhR@localhost> (raw)
In-Reply-To: <CAH+w=7aSWR5iVZFv0vARVy6Ssk-cHMo5+W5emMXaac+Ot_k9MQ@mail.gmail.com>

On Sat, Feb 11, 2023 at 09:36:01AM -0800, Bart Schaefer wrote:
> On Sat, Feb 11, 2023 at 9:03 AM Dominik Vogt <dominik.vogt@gmx.de> wrote:
> >
> > On Sat, Feb 11, 2023 at 10:41:07AM +0100, Dominik Vogt wrote:
> > > foo freezes in a call of bar and won't wake up anymore when bar
> > > terminates:
> >
> > >               R="$(bar some arguments)"  <------- hangs in this line
> >
> > Apparingly this does not happen if the line is rewritten to
> >
> > >               bar some arguments | read R
>
> Look for a file or pipe that's been opened in foo to which the
> subshell for bar might still have a descriptor (obviously other than
> the fd to return bar's output).

Hm, either script may restart the browser if the browser hangs.
After killing it I use this to restart it:

  start-browser () {
          ( set -m; "$BROWSER" <options> <url> &! )
  }

Does this have some side effect that I'm not aware of?  The idea
was to decouple the browser from the script so that it won't be
killed when the script ends.

(This is all a bit more complicated because the browser runs
inside a sandbox (firjail) and killing the browser actually means
terminating the sandbox.  But I think that's not part of the
problem.)

Ciao

Dominik ^_^  ^_^

--

Dominik Vogt


      reply	other threads:[~2023-02-11 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  9:41 Dominik Vogt
2023-02-11 17:02 ` Dominik Vogt
2023-02-11 17:36   ` Bart Schaefer
2023-02-11 20:28     ` Dominik Vogt [this message]

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=Y+f6e75KQM4/kFhR@localhost \
    --to=dominik.vogt@gmx.de \
    --cc=zsh-users@zsh.org \
    /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
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

	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).