From owner-freebsd-hackers Fri Feb 20 18:13:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01141 for freebsd-hackers-outgoing; Fri, 20 Feb 1998 18:13:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA01115; Fri, 20 Feb 1998 18:13:25 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Fri, 20 Feb 1998 21:12:22 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA07533; Fri, 20 Feb 98 21:12:21 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id VAA20168; Fri, 20 Feb 1998 21:11:36 -0500 Message-Id: <19980220211135.62939@ct.picker.com> Date: Fri, 20 Feb 1998 21:11:35 -0500 From: Randall Hopper To: James Van Artsdalen , Robert Beer Cc: freebsd-questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: emacs & less bug (process disowned) References: <000901bd3c41$d704f8d0$9ba9a68f@pest.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <000901bd3c41$d704f8d0$9ba9a68f@pest.us.dell.com>; from James Van Artsdalen on Wed, Feb 18, 1998 at 01:50:11AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Van Artsdalen: | $ EDITOR=emacs less foo.c | |and type "v" in less, less invokes emacs to edit the file. |If I then press ^G in emacs, both less and emacs see |the SIGINT, not just emacs. Robert Beer: |I have been (slowly) investigating something much like you describe with |emacs in a telnet session. I think you will find that emacs is receiving a |SIGSTOP and not a SIGINT. | |This appears to be a bad telnet client and server interaction. Does anyone |have any further insight(s) into this problem? I'm seeing the same thing inside a mailer I've been using (Mutt) on 3.0-971208-SNAP. I have "emacs -nw" set up to be my message editor. When I go off to edit a message, all is fine until I hit ^G in Emacs. Then it appears that somehow Mutt wakes up and takes control of the terminal as if I'd exited Emacs, but Emacs of course is still running and attached to the terminal. Hitting ^L to refresh the screen results in both Emacs and Mutt refreshing their displays; sometimes mutt will be last, sometimes Emacs; and their both hooked in looking at the keys being hit. Pretty ugly. Doing a ps listing, it appears that somehow the editing Emacs process is no longer a child process of Mutt, but has been disowned and is now owned by init. Why this is happening I don't know but it at least this process parenting change explains why Mutt seems to wake up and take control of the terminal. Its child process is no longer its child. > ps -auwx | egrep 'mutt|emacs' | grep -v grep 2965 325 rhh mutt rhh 2965 0.0 1.4 868 628 p0 S+ 9:02PM 0:00.17 mutt 2967 1 rhh emacs -nw /usr/t rhh 2967 0.0 4.6 2472 2156 p0 I+ 9:02PM 0:00.39 emacs -nw /usr/tmp/mutt-stealth-2965- Any thoughts? Randall Hopper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message