From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: simark@simark.ca, gdb-patches@sourceware.org
Subject: Re: Discrepancy between Python and Guile wrt exiting the interpreter
Date: Tue, 21 Jan 2020 19:57:00 -0000 [thread overview]
Message-ID: <83k15kvb05.fsf@gnu.org> (raw)
In-Reply-To: <874kwoa8rc.fsf@tromey.com> (message from Tom Tromey on Tue, 21 Jan 2020 12:51:03 -0700)
> From: Tom Tromey <tom@tromey.com>
> Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
> Date: Tue, 21 Jan 2020 12:51:03 -0700
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Eli> The context of these questions is the Emacs's front-end for GDB, which
> Eli> uses MI, and that adds even more complexities to this already quite
> Eli> complex situation, in particular because Emacs until now didn't know
> Eli> (nor care) whether the user invoked Python or Guile interpreter.
>
> I wonder if Emacs could use the "new-ui" command to create a separate MI
> channel just for its use.
It would only work on some platforms, but in any case I don't think I
understand how that would help with the issue of exiting the Python
interpreter. What did I miss?
next prev parent reply other threads:[~2020-01-21 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 14:46 Eli Zaretskii
2020-01-19 16:11 ` Simon Marchi
2020-01-19 16:42 ` Eli Zaretskii
2020-01-19 17:20 ` Simon Marchi
2020-01-19 19:13 ` Eli Zaretskii
2020-01-21 19:53 ` Tom Tromey
2020-01-21 19:57 ` Eli Zaretskii [this message]
2020-01-23 17:21 ` Pedro Alves
2020-01-23 17:37 ` Simon Marchi
2020-01-23 17:50 ` Pedro Alves
2020-01-23 17:39 ` Pedro Alves
2020-01-24 10:26 ` Eli Zaretskii
2020-01-23 18:20 ` Eli Zaretskii
2020-01-23 18:30 ` Pedro Alves
2020-01-23 18:46 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k15kvb05.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox