From: Andreas Schwab <schwab@suse.de>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: -var-show-attributes response syntax
Date: Fri, 10 Nov 2006 17:02:00 -0000 [thread overview]
Message-ID: <jehcx7qlph.fsf@sykes.suse.de> (raw)
In-Reply-To: <17748.43269.740800.782628@kahikatea.snap.net.nz> (Nick Roberts's message of "Sat, 11 Nov 2006 05:29:57 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> Vladimir Prus writes:
> >
> > Hello!
> >
> > Here's the docs for -var-show-attributes MI command:
> >
> > Synopsis
> > -var-show-attributes name
> >
> > List attributes of the specified variable object name:
> > status=attr [ ( ,attr )* ]
> > where attr is { { editable | noneditable } | TBD }.
> >
> > What is the reason for using "non" instead of "attribute_name=attribute_value"
> > syntax? The above assumes all attributes are boolean, which is not very
> > extensible.
>
> I think the above means output may be something like:
>
> ^done,attr={"editable","yellow","big"}
In which case I think status is a typo and should actually have been attr,
like this:
attr=ATTR [ ( ,ATTR )* ]
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-11-10 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 13:55 Vladimir Prus
2006-11-10 16:34 ` Nick Roberts
2006-11-10 16:53 ` Vladimir Prus
2006-11-10 20:47 ` Nick Roberts
2006-11-10 21:06 ` Vladimir Prus
2006-11-10 21:23 ` Nick Roberts
2006-11-10 17:02 ` Andreas Schwab [this message]
2006-11-10 21:46 ` Eli Zaretskii
2006-11-10 21:54 ` Nick Roberts
2006-11-10 23:10 ` Eli Zaretskii
2006-11-10 23:33 ` Nick Roberts
2006-11-11 9:26 ` Eli Zaretskii
2006-11-11 10:03 ` Nick Roberts
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=jehcx7qlph.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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