From: Vitalie Spinu <spinuvit@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 14297@debbugs.gnu.org
Subject: bug#14297: 24.3.50; emacs subprocesses don't exit on "exit"
Date: Tue, 30 Apr 2013 00:36:31 +0200 [thread overview]
Message-ID: <87zjwhrmkw.fsf@gmail.com> (raw)
In-Reply-To: <87d2te3l09.fsf@gmail.com>
Problem does not occur in emacs -nw and as I have just discovered it
doesn't occur with lucid either. Sorry, it took me a while to figure
this out. So it is probably some local glitch with Gtk what happened
after the update. It's pretty non intuitive, how failure of
(process-live-p proc) is connected to window toolkit?
With trunk from last November I cannot open Gtk emacs at all. I will
reinstall Gtk tomorrow to see if that helps.
Thanks for all the input,
Vitalie
>> Glenn Morris <rgm@gnu.org>
>> on Mon, 29 Apr 2013 15:10:21 -0400 wrote:
> Glenn Morris wrote:
>> It's fairly likely to be something in process.c.
> PS which suggests checking these (bzr trunk) revision numbers:
> revno: 111280
> revno: 111258
> revno: 111151
> revno: 111122
> revno: 111081
> revno: 111064
> revno: 111016
> revno: 110931
> revno: 110922
> revno: 110909
> revno: 110889
> revno: 110801
> revno: 110784
next prev parent reply other threads:[~2013-04-29 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 12:19 bug#14297: 24.3.50; emacs subprocesses don't exit on "exit" Vitalie Spinu
2013-04-28 17:26 ` Glenn Morris
2013-04-28 18:30 ` Vitalie Spinu
2013-04-29 0:28 ` Glenn Morris
2013-04-29 0:34 ` Glenn Morris
2013-04-29 12:39 ` Vitalie Spinu
2013-04-29 15:49 ` Glenn Morris
2013-04-29 18:30 ` Glenn Morris
2013-04-29 18:41 ` Vitalie Spinu
2013-04-29 18:53 ` Glenn Morris
2013-04-29 19:10 ` Glenn Morris
2013-04-29 22:36 ` Vitalie Spinu [this message]
2013-04-29 23:42 ` Glenn Morris
2013-05-13 4:38 ` Paul Eggert
2013-05-13 15:59 ` Eli Zaretskii
2013-05-13 16:58 ` Paul Eggert
2013-05-13 17:41 ` Eli Zaretskii
2013-05-13 18:34 ` Paul Eggert
2015-12-25 23:45 ` Lars Ingebrigtsen
2015-12-26 0:19 ` Vitalie Spinu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjwhrmkw.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=14297@debbugs.gnu.org \
--cc=rgm@gnu.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).