From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: bad news about add_setshow_cmd
Date: Thu, 27 Jun 2002 08:56:00 -0000 [thread overview]
Message-ID: <87u1nobt74.fsf@fleche.redhat.com> (raw)
In-Reply-To: <3D1A7765.1060708@ges.redhat.com>
>>>>> "Andrew" == Andrew Cagney <ac131313@ges.redhat.com> writes:
>> My current plan is to go ahead and add the new field and new doc
>> strings everywhere. Any other ideas or preferences?
Andrew> Sorry, you've lost me. Which new doc string? A third string
Andrew> for showing the value?
Yes. Something like:
N_("Argument list to give program being debugged when it is started is \"%s\")
This will let us preserve the same output we have now.
It will be a bit ugly in implementation (if we want to use the rule
"one %s in any string" we'll need to pre-format ints and the like).
Andrew> BTW, grep -e '->doc', arrhg! add_dump_command() for instance?
Oh, man. Nobody understood i18n in 1988. But it still sucks to do
multiple passes over all the code.
Thanks for finding this. If you (or anybody) knows of other problems
like this, feel free to drop me a line.
Tom
prev parent reply other threads:[~2002-06-27 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 14:45 Tom Tromey
2002-06-26 19:25 ` Andrew Cagney
2002-06-27 8:56 ` Tom Tromey [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=87u1nobt74.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@sources.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