zsh-users
 help / color / mirror / code / Atom feed
From: Ronan Pigott <rpigott314@gmail.com>
To: Zsh Users <zsh-users@zsh.org>, stephane@chazelas.org
Subject: Re: zsh mysteriously suspending job with sudo
Date: Thu, 14 May 2020 14:15:03 -0700	[thread overview]
Message-ID: <CAG4d5BgYa3oC4TV2=0_DjpBON=U2MStLr_sR72J-GkiMZaYJww@mail.gmail.com> (raw)
In-Reply-To: <CAG4d5BgKOghaqM5u7cz8iqTv0Nkjtd1_=maG+f1HpyWRVAPCPA@mail.gmail.com>

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

Is it possible to apply Peter's ESRCH patch to master?

I've run this patch for a while and I think many pacman users could benefit.

On Sun, Feb 23, 2020 at 4:57 PM Ronan Pigott <rpigott314@gmail.com> wrote:

> Brilliant! Thank you Peter for the patch.
>
> I have applied it to my zsh and pacman is working again.
>
> On Sun, Feb 23, 2020 at 11:53 AM Ronan Pigott <rpigott314@gmail.com>
> wrote:
>
>> Wow! Thank you Stephane for your analysis.
>>
>> So you think that a patch checking for ESRCH is not suitable?
>>
>> I tried poking around in Src/jobs.c in update_job where
>> it sounds like this issue originates, but I'm not quite sure
>> how the logic should be revised.
>>
>> Is there somewhere else where this bug should be reported?
>>
>> Thanks again for your help!
>>
>

  reply	other threads:[~2020-05-14 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG4d5Bg=vkj6PYYGVyNO3pWTh=RkT=2rTFdE_hPBj1xxz6YTSw__29611.299622205$1582420251$gmane$org@mail.gmail.com>
2020-02-23 14:03 ` Stephane Chazelas
2020-02-23 18:53   ` Ronan Pigott
2020-02-23 23:57     ` Ronan Pigott
2020-05-14 21:15       ` Ronan Pigott [this message]
2020-05-15  9:08         ` Peter Stephenson
2020-05-15  9:20           ` Ronan Pigott
2020-02-23 20:18   ` Peter Stephenson
2020-02-23  1:09 Ronan Pigott

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='CAG4d5BgYa3oC4TV2=0_DjpBON=U2MStLr_sR72J-GkiMZaYJww@mail.gmail.com' \
    --to=rpigott314@gmail.com \
    --cc=stephane@chazelas.org \
    --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).