This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Ping: frozen variable objects
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: Nick Roberts <nickrob at snap dot net dot nz>
- Cc: Daniel Jacobowitz <drow at false dot org>, Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sources dot redhat dot com
- Date: Sun, 15 Apr 2007 15:46:08 +0400
- Subject: Re: Ping: frozen variable objects
- References: <200703251351.43195.vladimir@codesourcery.com> <200704151431.58128.vladimir@codesourcery.com> <17954.3880.907830.606565@farnswood.snap.net.nz>
On Sunday 15 April 2007 15:40, Nick Roberts wrote:
> > > Also the name that is displayed shouldn't change, so pxref needs to be
> > > called with two arguments:
> > >
> > >
> > > @code{in_scope} (@pxref{-var-update fields, -var-update}) may be extended.
> >
> > That does not seem to work in a sensible way. In PDF, you get "-var-update
> > fields" only, and info has:
> >
> > (*note -var-update: -var-update fields.)
> >
> > which makes no sense whatsoever.
>
> It does to me because the first refers to the destination (the entry for
> -var-update), while the second is just the name of the anchor which is not
> visible to the reader.
It is visible to the reader -- both in printed documented and in info (as viewed
by 'info' command).
> Info in Emacs reflects the importance of the first
> argument by just displaying:
>
> (*note -var-update.)
>
> Currently Emacs displays:
>
> (*note -var-update-fields.)
>
> but there is no such (visible) location.
Should we really cater to the way Emacs displays something?
- Volodya