From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31044 invoked from network); 21 May 2020 03:33:57 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 21 May 2020 03:33:57 -0000 Received: (qmail 7651 invoked by alias); 21 May 2020 03:33:47 -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: 45872 Received: (qmail 8049 invoked by uid 1010); 21 May 2020 03:33:47 -0000 X-Qmail-Scanner-Diagnostics: from out1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25814. spamassassin: 3.4.4. Clear:RC:0(66.111.4.25):SA:0(-2.6/5.0):. Processed in 4.968756 secs); 21 May 2020 03:33:47 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddutddgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkjghfofggtgfgsehtqh dttdertdejnecuhfhrohhmpeffrghnihgvlhcuufhhrghhrghfuceougdrshesuggrnhhi vghlrdhshhgrhhgrfhdrnhgrmhgvqeenucggtffrrghtthgvrhhnpefhfeehvddtvdefvd fffefgudduteekheejffefleevieduleefleevheduhfduteenucffohhmrghinhepphhr ohguuhgtihhnghhoshhsrdgtohhmnecukfhppeejledrudejjedrudefgedrfeenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghn ihgvlhdrshhhrghhrghfrdhnrghmvg X-ME-Proxy: Date: Thu, 21 May 2020 03:33:01 +0000 From: Daniel Shahaf To: "zsh-workers@zsh.org" Subject: A bug tracker (was: Re: [Bug] Unexpected process suspension) Message-ID: <20200521033301.35393ae9@tarpaulin.shahaf.local2> In-Reply-To: References: <20200513062902.gf6e22g4sqni75x4@chazelas.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Rudi C wrote on Thu, 21 May 2020 03:02 +0430: > Considering this bug (or a very similar variant) was reported before and > the issue just died a silent death, I think it's a good idea to create a > Github repo for tracking zsh issues. Github issue tracker is a lot better > than mailing lists, as things have a dichotomy of being open/closed, and > can be labeled. It is harder for issues to die a silent death there. I'm not opposed to adding a proper issue tracker, but github is not the only fish in the sea; it is one option among many. IIRC, last time this was discussed, it was requested to have bidirectional integration with the mailing list. Do I recall correctly? If we opt for an issue tracker, there'll be the question of whether we'll use the issue tracker to receive/triage bug reports, or keep triage on the mailing lists like today and only use the tracker to record known defects and conclusions of discussions. The latter would be the smaller change compared to the status quo. Another way to solve this is to have a "bug reports manager", who would be a volunteer who'd scan the lists regularly=C2=A0=E2=80=94 say, once a we= ek=C2=A0=E2=80=94 for any bug report threads that have petered out without a solution, and ping those. (The volunteer needn't be a developer.) I filled a similar role myself, years ago at $OTHERPROJECT. Compare https://producingoss.com/en/share-management.html#manager-is-not-owner (particularly its first subsection, read with s/patch/bug report/g). Finally, I have been using Etc/BUGS in git to track bugs. If someone'd like to add an entry there for this set of related bugs, please do. > It is also easier to contribute to that, and easier to unsubscribe > (I don't think one can unsubscribe from a mailing list post one > participated in, as people (wisely) use reply-all.). No, it's not possible to unsubscribe from being directly Cc'd, but the responses generally peter out after a few days, and there are plenty of ways to deduplicate or otherwise flag responses that were Cc'd both to oneself and to the list. Cheers, Daniel > On Wed, May 13, 2020 at 10:59 AM Stephane Chazelas > wrote: >=20 > > 2020-05-12 10:38:38 -0700, Bart Schaefer: =20 > > > On Tue, May 12, 2020 at 12:03 AM Rudi C =20 > > wrote: =20 > > > > > > > > mdoc-test () { > > > > > > > > sleep 0 | sleep 0 =20 > > > > cat} =20 > > > > > > > > echo start |VISUAL=3Dvim command vipe|mdoc-test > > > > > > > > # zsh: suspended (tty output) =20 > > > > > > Putting an interactive command in the middle of a pipeline is > > > generally not going to work. Vim in particular is pretty aggressive > > > about trying to grab a terminal, which will result in processes > > > getting SIGTT* because they don't have foreground control of the > > > terminal they're trying to use. =20 > > [...] > > > > The thing is vim *should* be in the foreground, all the > > processes started in pipeline should be in the same process > > group which should be in foreground (so it gets > > SIGINT/SIGQUIT/SIGTSTP upon ^C/^\/^Z, so it can read the > > terminal, etc) but under some circumstances, zsh fails to put > > some processes in that group, which is a bug. > > > > $ &2 > > 127235 127235 > > $ &2 | = ps > > -o pid,pgid,comm > > 131569 131569 > > PID PGID COMMAND > > 124948 124948 zsh > > 131569 131569 awk > > 131570 131569 ps > > 131571 131569 sleep > > $ &2 | { :; } > > 127410 127410 > > $ &2 | { : | :; } > > 127496 124948 > > > > In that latter case, awk is in a different process group > > (127496) from the terminal foreground process group (124948 > > which here is the process group of the main shell process!). > > > > -- > > Stephane > > =20