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

From: Nick Roberts <nickrob at snap dot net dot nz>
To: Vladimir Prus <vladimir at codesourcery dot com>
Cc: Daniel Jacobowitz <drow at false dot org>, Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sources dot redhat dot com
Date: Mon, 16 Apr 2007 00:01:03 +1200
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> <200704151546.09530.vladimir@codesourcery.com>

 > > 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).

The *anchor* isn't visible.  Well I can't see it.

 > > 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?

Yes.  GDB and Emacs are both part of the GNU Project, and it makes sense to
integrate tools, in any case.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

References:
- Re: Ping: frozen variable objects
  - From: Vladimir Prus
- Re: Ping: frozen variable objects
  - From: Nick Roberts
- Re: Ping: frozen variable objects
  - From: Vladimir Prus

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