help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Weird bug / missing feature with gvim interaction
Date: Mon, 6 Mar 2023 11:35:07 -0800	[thread overview]
Message-ID: <CAH+w=7ZfgisfnsRFH=ud_zB9BCjcv9=wS19QvtcPTN1rJsq-3w@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s03ycwi+5e+o5qKrau9neJXdVG9xsyQGMmBaKONuPf6hQ@mail.gmail.com>

On Mon, Mar 6, 2023 at 6:31 AM Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Sun, Mar 5, 2023 at 10:28 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> >
> > What's not clear is where the HUP is coming from
> >
> > Puzzlingly, using "nohup xdg-open ..." doesn't help.
> That doesn't help, but "setsid nohup xdg-open ..." does help, both in
> bash and zsh. But I believe that's what the vim code essentially tried
> to do.

Sure, but vim is doing it before zsh starts up, whereas when you use
the setsid command it creates the new process group after zsh runs it.
E.g., without the setsid command, I believe the thread would be that
zsh execs nohup which execs xdg-open, all with no forking involved,
but if you add setsid in front then zsh execs setsid which forks
before exec of nohup.

Zsh doesn't use setsid(2) and doesn't mess with the process group by
any other means unless there's a controlling tty to attach to, which
there presumably is not in this case.

Still doesn't explain the source of the HUP signal, or why nohup fails
to ignore it ... unless xdg-open is deliberately unblocking it again.

  reply	other threads:[~2023-03-06 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  1:32 Felipe Contreras
2023-03-06  4:28 ` Bart Schaefer
2023-03-06  4:32   ` Bart Schaefer
2023-03-06 14:31   ` Felipe Contreras
2023-03-06 19:35     ` Bart Schaefer [this message]
2023-03-06 19:47       ` Felipe Contreras
2023-03-06 15:14 ` lilydjwg
2023-03-06 15:54   ` Felipe Contreras

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7ZfgisfnsRFH=ud_zB9BCjcv9=wS19QvtcPTN1rJsq-3w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=felipe.contreras@gmail.com \
    --cc=zsh-workers@zsh.org \


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