Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Discrepancy between Python and Guile wrt exiting the interpreter
Date: Thu, 23 Jan 2020 18:20:00 -0000	[thread overview]
Message-ID: <83zheerq9g.fsf@gnu.org> (raw)
In-Reply-To: <9684975c-324f-b26b-de87-6d37c0d8d08a@redhat.com> (message from	Pedro Alves on Thu, 23 Jan 2020 17:10:10 +0000)

> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 23 Jan 2020 17:10:10 +0000
> 
> 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.
> 
> "gr" is an alias for "guile-repl", and with that command, it's the Guile
> repl that implements the ",q", not GDB.  With the "python" and "guile"
> commands, it's GDB that implements the secondary prompt handling and
> command line reading (the ">", etc.).  Compare guile_repl_command and
> guile_command.

Thanks.

Is there a Python equivalent of "gr"?


  parent reply	other threads:[~2020-01-23 18:18 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
2020-01-24 10:26         ` Eli Zaretskii
2020-01-23 18:20   ` Eli Zaretskii [this message]
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=83zheerq9g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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