From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: stanshebs@earthlink.net, tromey@redhat.com,
stan@codesourcery.com, brobecker@adacore.com,
msnyder@vmware.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Let "gcore" command accept a suffix argument
Date: Wed, 06 Jan 2010 10:13:00 -0000 [thread overview]
Message-ID: <E1NSStB-0001gT-OG@fencepost.gnu.org> (raw)
In-Reply-To: <daef60381001052257q2068a8fbmaacd026b8d5cef49@mail.gmail.com> (message from Hui Zhu on Wed, 6 Jan 2010 14:57:32 +0800)
> From: Hui Zhu <teawater@gmail.com>
> Date: Wed, 6 Jan 2010 14:57:32 +0800
> Cc: gdb-patches ml <gdb-patches@sourceware.org>
>
> I make a new patch that eval command use "" to point out the simple command.
> If want add " in normal string. Use \"
> If we want add \ in normal string. Use \\
> It can be use like:
> (gdb) eval "echo \""$a++"\""
> "7"(gdb) eval "echo \""$a++"\""
> "8"(gdb) eval "echo \""$a++"\""
> "9"(gdb) eval "echo \""$a++"\""
> "10"(gdb) eval "echo \""$a++"\""
> "11"(gdb) eval "echo \""$a++"\""
> "12"(gdb) eval "echo \""$a++"\""
> "13"(gdb) eval "echo \""$a++"\""
>
> Please help me review it.
Thanks. This doc string:
> + add_com ("eval", no_class, eval_command, _("\
> +Call command with variable."));
Should be much more detailed, and in particular say when quotes should
be used and how to specify a literal quote character.
It also needs an update for the manual.
TIA
prev parent reply other threads:[~2010-01-06 10:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B11DA3C.3000203@vmware.com>
[not found] ` <daef60380911300437o4c616eb2v5ad7bfe99bd3c5e9@mail.gmail.com>
[not found] ` <20091130162246.GE4034@adacore.com>
[not found] ` <4B141157.3070709@vmware.com>
[not found] ` <20091130185341.GI4034@adacore.com>
[not found] ` <4B141469.5030402@vmware.com>
[not found] ` <20091130190619.GJ4034@adacore.com>
[not found] ` <4B1428F0.7090608@vmware.com>
[not found] ` <daef60380912091827u6ff7127bp1d03998a40932914@mail.gmail.com>
2009-12-10 2:32 ` Hui Zhu
2009-12-10 17:08 ` Tom Tromey
2009-12-11 10:06 ` Joel Brobecker
2009-12-11 18:25 ` Tom Tromey
2009-12-12 8:33 ` Hui Zhu
2009-12-13 4:05 ` Hui Zhu
2009-12-14 17:09 ` Tom Tromey
2009-12-15 1:57 ` Hui Zhu
2009-12-15 19:21 ` Tom Tromey
2009-12-16 3:58 ` Hui Zhu
2009-12-16 15:49 ` Stan Shebs
2009-12-17 2:45 ` Hui Zhu
2009-12-17 4:26 ` Joel Brobecker
2009-12-17 4:29 ` Michael Snyder
2009-12-17 9:32 ` Andreas Schwab
2009-12-21 20:15 ` Tom Tromey
2009-12-31 0:18 ` Stan Shebs
2010-01-04 14:42 ` Hui Zhu
2010-01-06 6:57 ` Hui Zhu
2010-01-06 7:58 ` Joel Brobecker
2010-01-09 9:55 ` Hui Zhu
2010-01-09 10:56 ` Joel Brobecker
2010-01-09 15:18 ` Hui Zhu
2010-01-10 5:43 ` Joel Brobecker
2010-01-10 13:30 ` Hui Zhu
2010-01-10 14:00 ` Joel Brobecker
2010-01-10 14:16 ` Hui Zhu
2010-06-21 15:05 ` Hui Zhu
2010-06-21 16:57 ` Joel Brobecker
2010-06-21 21:34 ` Joel Brobecker
2010-06-21 21:40 ` Tom Tromey
2010-06-22 7:29 ` Hui Zhu
2010-06-22 9:50 ` Pedro Alves
2010-06-22 15:21 ` Joel Brobecker
2010-06-22 18:05 ` Eli Zaretskii
2010-06-23 2:03 ` Hui Zhu
2010-06-23 16:59 ` Joel Brobecker
2010-06-24 6:13 ` Hui Zhu
2010-01-06 10:13 ` Eli Zaretskii [this message]
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=E1NSStB-0001gT-OG@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=stan@codesourcery.com \
--cc=stanshebs@earthlink.net \
--cc=teawater@gmail.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