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 17:55:00 -0000 [thread overview]
Message-ID: <9DB9F174-129C-4C4A-9708-53A1D521251A@cs.umd.edu> (raw)
In-Reply-To: <874novivob.fsf@fleche.redhat.com>
Hi,
Just to throw out another suggestion: make the new command "python-interactive" and alias it to "pi", and leave the old "python" and alias it to "py". Best of both worlds?
Yit
July 25, 2012
On Jul 25, 2012, at 1:43 PM, Tom Tromey wrote:
>>>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:
>
> Yit> My original patch back in January tried to preserve the behavior of
> Yit> "python" based "from_tty": if it was true, "python" would be
> Yit> interactive; otherwise, it would not. But there were several
> Yit> objections to that, I guess since "from_tty" is hard to track (see
> Yit> http://thread.gmane.org/gmane.comp.gdb.patches/71971). The current
> Yit> implementation is based on the discussion then.
>
> I vaguely remember it. I have a suspicion that I've changed my mind
> since the old thread, but I didn't go back and read to see :)
>
> I don't know what would make from_tty hard to track, but ok.
>
> I just think it is very likely that "python" commands are in .gdbinits
> and other places, and that breaking these would be bad.
>
> Yit> One more option is to move the Python REPL to "python-repl" and alias
> Yit> it to "py", and leave the old "python" as is. The "py" alias gives a
> Yit> convenient short command, "python-repl" can be used from a script to
> Yit> start a REPL, and the old "python" remains as is.
>
> Like Matt says, "py" is probably already in use (I feel certain I've
> seen it) and if anything we should do the converse -- alias "py" to
> "python" if a new command goes in.
>
> "python-repl" would be fine by me.
>
> Tom
next prev parent reply other threads:[~2012-07-25 17:55 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
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 [this message]
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=9DB9F174-129C-4C4A-9708-53A1D521251A@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