From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-return-43517-ml=inbox.vuxu.org@zsh.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id dc2f17ee for ; Sat, 22 Sep 2018 05:52:15 +0000 (UTC) Received: (qmail 10350 invoked by alias); 22 Sep 2018 05:51:58 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 43517 Received: (qmail 29600 invoked by uid 1010); 22 Sep 2018 05:51:58 -0000 X-Qmail-Scanner-Diagnostics: from mail-pg1-f174.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.215.174):SA:0(1.1/5.0):. Processed in 3.139255 secs); 22 Sep 2018 05:51:58 -0000 X-Envelope-From: joeypabalinas@gmail.com X-Qmail-Scanner-Mime-Attachments: |signature.asc| X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=dVx6eAX2BQGPyHex5gV8xkDciDdJbS37g5dn762xsc0=; b=LPFItbo2xETB7P2xeEznLQcOFSXUNKQNkEbGYfZZxVIUQyOOjKcsFpr8qyoIueghGv eXe3yUc1UckmlmylWi9MDRNoTNrg8lefo0gTbWL2klcvSOpsue/oJy+QiARvlfcAz41h j03xkRthbPCHJLgAZVq2ciFiFVyjylttA48J2U5TTs510U2kSNyPAOKaCF0a8qL7Yjb6 hjgY+H07GqPQB06mhYzlfeZkbQxadU31nyop9UIMNEwKBRbxhxzo7Vbh1/woJVd1X7ZM dWXWzKv0KJRmdPbPToywyLyqPwh0tGOmHs4FP0YeOj0zCnqVAoDDIQmkwvaCwWRdOKaG fWUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=dVx6eAX2BQGPyHex5gV8xkDciDdJbS37g5dn762xsc0=; b=ig3LORYnl6w70XqkuaV7lYutC3386tRU8nSgR478+KL2AEj3LiTcr3Ne++9QiNyKs2 VlmgUvGUxwb9NJXrALkiHgcqJwjcLnGSRxWavQHJgJDRhgJogdwlE91C0Zj9FwLAxPKH /G2KW5AmwN+Eg5y2UxkMGvDCpjHFvdXrIn5UPHw0qGmLKxi4jNezYICb7U/0i5BLzWN3 4iRw7Pwy6kfhd/n5IPo9Hno4rjnUXYgEv33C7qOrzuDUpueb7DXlyzk/zgSW4BzSUaHy eAfzOj5w2m00yj4K8VVm6bPCCx+3WgZ2a5faJE1254+97ZwEYGRUUjZMQ4U3f2tSzJP3 0lQg== X-Gm-Message-State: APzg51AZ9hJyl2Q9S00TZTAhbMQ5dNnsd9Ga2QIgkdCrEvw3rBL1HbJw vu0EKGtru7yHcur9uYEzvuY= X-Google-Smtp-Source: ANB0VdbBXHfWq0VSCUcR2pl9SAqcgkE1/k91speAPuNj6rHcMe2HxOKN+K8ClxLqsakdxSRLvv0KpQ== X-Received: by 2002:a62:cc83:: with SMTP id j3-v6mr1047481pfk.255.1537595511197; Fri, 21 Sep 2018 22:51:51 -0700 (PDT) Date: Fri, 21 Sep 2018 19:51:48 -1000 From: Joey Pabalinas To: Bart Schaefer Cc: Peter Stephenson , "zsh-workers@zsh.org" , Joey Pabalinas Subject: Re: long-standing tty related issue: wrapped Emacs not suspended Message-ID: <20180922055148.dvmf7kvknnez3cvd@gmail.com> Mail-Followup-To: Joey Pabalinas , Bart Schaefer , Peter Stephenson , "zsh-workers@zsh.org" References: <20180920123005.GA20647@zira.vinc17.org> <20180921175740.6ab97a81@pws-HP.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xsfyqk3ozvwfiiag" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 --xsfyqk3ozvwfiiag Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 21, 2018 at 06:17:47PM -0700, Bart Schaefer wrote: > FWIW I can't get what Vincent describes to happen at all with the > above example and the current git checkout, even after assorted > bg/fg/^Z/etc. But the system on which I can currently test doesn't > have an X-enabled emacs. This did confuse me a bit earlier in Peter's email, as I also had this exact behavior on 5.5.1.r143.g225b35c9070f94cf79 where -CONT didn't even seem to work regardless of which child process I sent it to. I had just chalked it up to one of my weird configs, but I guess this is pretty much happening to everyone running the development versions? > Also, the parent shell should probably be sending a SIGCONT to all > those jobs whenever they are fg'd, even if it believes they are > already running. SIGCONT is harmless for a job that is not stopped, > and trusting the job table idea of the process state is an unnecessary > optimization. Interestingly enough I did once run into a program that used a SIGCONT handler, reset to default disposition in SIGTSTP handler, for some internal callback-ish stuff. My guess was it assumed SIGCONT to be a "safe" sentinel signal (while completely forgetting about its uncatchable brother SIGSTOP), but cases like that are mostly just broken curiosities and definitely not worth worrying about :) --=20 Cheers, Joey Pabalinas --xsfyqk3ozvwfiiag Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKlZXrihdNOcUPZTNruvLfWhyVBkFAlul2HMACgkQruvLfWhy VBmyZxAAlJ5yMwgSogd8IQVdPjADR8rq/LNcb3bUlQgkeF9fXxrccseZx0oSD1Vn AkUurrjAWjqImF3vNZBbBNAAZedsasmi+YSf/vgRc/a7tOEcG/7Z2/R4/sTC8G+p tCTdZpsF7VRWWNBZjc/Yy7TrgjJiQU01X3/RUkZ/QyXRp7HxEMdQykeag631WE2W uRc0Pu2xBR/tg2H/ouH60Wj7Z0hP292jk9T+bhqoi1pMr+1NrP8ASBx6X/xDtwob mfQF5BR6EPcjUJD+HGNaHk9/pMfI2zcMbEOrIzjuRqylPSAJPh2CohGKCB2dsGee pBGhZRmdRh2nuQgq2wx326BcUksIVnLOTqdfRjsvZbyim+Z8aRZ9mlrK24g5Ls2y TcN2C6vBgD6Eq61IXPnzv+ZmGnXuJKEQqxjMd2B3JKOy108BNV7tKKApt5BaMB+K p1J44uXnH4lK2YqAtvwj3v9085MOpoIp1H8IJ+rOWDQV7RlSUqEYM9qxgm9dv3GI 501mA7gk0E9hTXIr1oApQcg2vEWwfrpmyrDBGd/X5/pLSdkyjPyysJmVG99zkY6g RA0ANY14P7NBaTdJGu0V01m4OKaqwki7evkGwvFuueLv97CSr1DxAnGRWKiKceNK ef6XEGUeJuQrU813ZNuaBXDfUccObEsKakF8qhYEmKVTeND4upI= =0/rb -----END PGP SIGNATURE----- --xsfyqk3ozvwfiiag--