From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simark@simark.ca>, Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: Discrepancy between Python and Guile wrt exiting the interpreter
Date: Thu, 23 Jan 2020 17:39:00 -0000 [thread overview]
Message-ID: <d1d2ac0d-45a2-34e5-9109-567ca9d93f1b@redhat.com> (raw)
In-Reply-To: <efc4b988-c931-0be6-f917-ae428821defd@redhat.com>
On 1/23/20 5:32 PM, Pedro Alves wrote:
> On 1/23/20 5:21 PM, Simon Marchi wrote:
>> On 2020-01-23 12:10 p.m., Pedro Alves wrote:
>>> Note that these commands are not direct equivalents. The guile equivalent
>>> to "pi" which is short for "python" would be "guile", or "gu", and with
>>> that command you get the same behavior as "pi", in the sense that ",q"
>>> doesn't bail you out, you have to type some command and finish with
>>> either Ctrl-D or Ctrl-C to abort.
>>
>> "pi" is not a shorthand for "python", it's a shorthand for "python-interactive",
>> which spawns a Python interpreter prompt/repl. So I think that and "guile-repl"
>> are quite similar. It's just that the Python repl doesn't provide a convenient
>> way (other than ctrl-D) so say "exit the repl".
>
> Indeed, I got confused with that.
And I have to add -- wow, "quit()" exiting gdb is really nasty
in that case. It's even suggested if you try "quit" without
parens:
>>> quit
Use quit() or Ctrl-D (i.e. EOF) to exit
Clearly the embedded use case wasn't considered here. I think
this should be reported to Python upstream.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-01-23 17:37 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
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 [this message]
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=d1d2ac0d-45a2-34e5-9109-567ca9d93f1b@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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