From: Eli Zaretskii <eliz@gnu.org>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: khooyp@cs.umd.edu, tromey@redhat.com, pmuldoon@redhat.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4]: Make "python" start a standard Python prompt
Date: Sat, 28 Jul 2012 15:05:00 -0000 [thread overview]
Message-ID: <831ujwhqoh.fsf@gnu.org> (raw)
In-Reply-To: <B53D4064-D309-4403-A0BE-63EED15F3472@cs.umd.edu>
> From: Khoo Yit Phang <khooyp@cs.umd.edu>
> Date: Sat, 28 Jul 2012 10:34:52 -0400
> Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
> tromey@redhat.com,
> pmuldoon@redhat.com,
> gdb-patches@sourceware.org
>
> >> +@item python-interactive @r{[}@var{code}@r{]}
> >> +@itemx pi @r{[}@var{code}@r{]}
> >
> > Why "code"? Elsewhere you used "command", which is better, IMO.
>
> I had just copied the doc for the old "python" command, which used "code". Shall I change it there too?
Yes, please.
> +Alternatively, a single-line Python command can be given as an
> +argument and evaluated. If the command is an expression, the result
> + will be printed; otherwise, nothing will be printed.
This is good, but please leave two spaces after the period that ends
the first of these two sentences.
Thanks.
next prev parent reply other threads:[~2012-07-28 15:05 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
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 [this message]
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=831ujwhqoh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
--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