This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Ping: frozen variable objects


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]