From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Shell buffer processes all die when I run "man" Date: Sat, 12 Nov 2016 09:11:58 +0200 Message-ID: <83shqxcgu9.fsf@gnu.org> References: NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1478934777 25877 195.159.176.226 (12 Nov 2016 07:12:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 12 Nov 2016 07:12:57 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Nov 12 08:12:53 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c5SUB-0001cG-1K for geh-help-gnu-emacs@m.gmane.org; Sat, 12 Nov 2016 08:12:23 +0100 Original-Received: from localhost ([::1]:57057 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c5SUA-0003U5-TI for geh-help-gnu-emacs@m.gmane.org; Sat, 12 Nov 2016 02:12:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35894) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c5STk-0003Tp-C2 for help-gnu-emacs@gnu.org; Sat, 12 Nov 2016 02:11:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c5STg-000178-RD for help-gnu-emacs@gnu.org; Sat, 12 Nov 2016 02:11:55 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59238) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c5STg-000171-OD for help-gnu-emacs@gnu.org; Sat, 12 Nov 2016 02:11:52 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3012 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1c5STg-0003zJ-3B for help-gnu-emacs@gnu.org; Sat, 12 Nov 2016 02:11:52 -0500 In-reply-to: (message from David Karr on Fri, 11 Nov 2016 10:41:12 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:111714 Archived-At: > From: David Karr > Date: Fri, 11 Nov 2016 10:41:12 -0800 > > I'm using Emacs 24.5.1 in Cygwin on Windows 7. > > I create multiple shell buffers (using a wrapper package that I > wrote). I've used this basically unchanged for more than 10 years. > > I recently noticed that if I have one or more shell buffers, and I run > the "man" function, I often see a short message saying "Waiting for > process to die", and then I see that all of my shell buffers say > "Process shell hangup" (or "shell<1>", depending on the buffer name). > I've been seeing this consistently for several weeks now. I cannot reproduce this in "emacs -Q", if I manually rename the shell buffers to *shell*<1> etc., and then run "M-x man". "Waiting for process to die" is usually a sign that some problem happened during execution of a subprocess, so you should look into what happens in the pipe run by "M-x man" on your system. E.g., do you see the same message when no shell buffers exist in your session? When Emacs emits the above message, it kills the entire process group of the subprocess with the SIGINT signal, so if your shell processes are by some chance all in the same group as the shell run by "M-x man", they will also be killed (but not by SIGHUP, as you seem to say). This shouldn't normally happen, though, and besides, the message is only shown for processes started synchronously with call-process, whereas on your system "M-x man" should run the pipe asynchronously with start-process. So I think some other factor is at work here, and the key to unlocking this puzzle is somewhere in your customizations and/or that wrapper package you wrote.