From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
Phil Muldoon <pmuldoon@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4]: Make "python" start a standard Python prompt
Date: Wed, 25 Jul 2012 16:58:00 -0000 [thread overview]
Message-ID: <1C2FC4AD-E6FE-4857-9DE5-FDE5BE006E95@cs.umd.edu> (raw)
In-Reply-To: <87zk6nizl6.fsf@fleche.redhat.com>
Hi,
On Jul 25, 2012, at 12:18 PM, Tom Tromey wrote:
>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>
> Phil> If a user has a script (or some code in .gdbinit, or whatever )
> Phil> that uses "python" will it break that user's script?
>
> This is my question as well.
>
> I think it is ok to change the interactive behavior of the "python"
> command, but not the behavior in a script.
>
> Tom
My original patch back in January tried to preserve the behavior of "python" based "from_tty": if it was true, "python" would be interactive; otherwise, it would not. But there were several objections to that, I guess since "from_tty" is hard to track (see http://thread.gmane.org/gmane.comp.gdb.patches/71971). The current implementation is based on the discussion then.
One more option is to move the Python REPL to "python-repl" and alias it to "py", and leave the old "python" as is. The "py" alias gives a convenient short command, "python-repl" can be used from a script to start a REPL, and the old "python" remains as is.
Yit
July 25, 2012
next prev parent reply other threads:[~2012-07-25 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 20:47 Khoo Yit Phang
2012-07-24 21:19 ` Khoo Yit Phang
2012-07-25 6:45 ` Phil Muldoon
2012-07-25 16:18 ` Tom Tromey
2012-07-25 16:58 ` Khoo Yit Phang [this message]
2012-07-25 17:20 ` Matt Rice
2012-07-25 17:29 ` Khoo Yit Phang
2012-07-25 17:43 ` Tom Tromey
2012-07-25 17:55 ` Khoo Yit Phang
2012-07-25 17:59 ` Tom Tromey
2012-07-25 21:07 ` Khoo Yit Phang
2012-07-26 17:38 ` Tom Tromey
2012-07-26 17:52 ` Khoo Yit Phang
2012-07-26 18:06 ` Eli Zaretskii
2012-07-26 18:10 ` Khoo Yit Phang
2012-07-27 2:32 ` Khoo Yit Phang
2012-07-27 19:23 ` Tom Tromey
2012-07-28 6:53 ` Eli Zaretskii
2012-07-28 14:35 ` Khoo Yit Phang
2012-07-28 15:05 ` Eli Zaretskii
2012-07-28 15:14 ` Khoo Yit Phang
2012-07-31 22:04 ` Khoo Yit Phang
2012-08-01 15:46 ` Tom Tromey
2012-08-10 17:28 ` Khoo Yit Phang
2012-08-22 17:44 ` Khoo Yit Phang
2012-08-22 17:59 ` 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=1C2FC4AD-E6FE-4857-9DE5-FDE5BE006E95@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@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