Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>,  Eli Zaretskii <eliz@gnu.org>,
	 gdb-patches@sources.redhat.com
Subject: Re: Ping: frozen variable objects
Date: Sun, 15 Apr 2007 11:57:00 -0000	[thread overview]
Message-ID: <200704151546.09530.vladimir@codesourcery.com> (raw)
In-Reply-To: <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


  reply	other threads:[~2007-04-15 11:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25  9:52 Vladimir Prus
2007-03-25 20:17 ` Eli Zaretskii
2007-04-10 19:03 ` Daniel Jacobowitz
2007-04-11 14:44   ` Vladimir Prus
2007-04-11 14:52     ` Daniel Jacobowitz
2007-04-11 18:38       ` Eli Zaretskii
2007-04-13  9:53     ` Eli Zaretskii
2007-04-14 16:14       ` Vladimir Prus
2007-04-14 16:19         ` Daniel Jacobowitz
2007-04-14 23:18           ` Nick Roberts
2007-04-15 10:32             ` Vladimir Prus
2007-04-15 10:35             ` Vladimir Prus
2007-04-15 11:46               ` Nick Roberts
2007-04-15 11:57                 ` Vladimir Prus [this message]
2007-04-15 20:09                   ` Nick Roberts
2007-04-15 20:16                   ` Eli Zaretskii
2007-04-15 20:13               ` Eli Zaretskii
2007-04-14 20:32         ` Eli Zaretskii
2007-04-15 11:42           ` Vladimir Prus
2007-04-15 12:03             ` Nick Roberts
2007-04-16  2:40               ` Eli Zaretskii
2007-04-18  5:38                 ` Vladimir Prus
2007-04-18 10:37                   ` Nick Roberts
2007-04-18 22:23                     ` Eli Zaretskii
2007-04-19  4:41                   ` Eli Zaretskii
2007-04-15 20:14             ` Eli Zaretskii
2007-04-15  8:04         ` Nick Roberts
2007-04-18 10:22         ` [patch] fix insight (was: Re: Ping: frozen variable objects) Brian Dessent
2007-04-18 12:51           ` Maciej W. Rozycki
2007-04-18 13:01             ` Brian Dessent
2007-04-18  5:38   ` Ping: frozen variable objects Michael Snyder
2007-04-18  6:57     ` Vladimir Prus
2007-04-18 22:21       ` Michael Snyder

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=200704151546.09530.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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