From: "Berek Half-hand" <berek@usa.net>
To: "Worik" <worik@jungledrum.co.nz>, <sourcenav@sources.redhat.com>
Subject: Re: X-Ref broke....
Date: Mon, 24 Sep 2001 17:21:00 -0000 [thread overview]
Message-ID: <001e01c14557$f1eee0c0$c42f5b18@ne.mediaone.net> (raw)
In-Reply-To: <3BAF946A.459D4095@jungledrum.co.nz>
No. Problem's with the parsers. Buggy. Ask RedHat.
----- Original Message -----
From: "Worik" <worik@jungledrum.co.nz>
To: <sourcenav@sources.redhat.com>
Sent: Monday, September 24, 2001 16:15
Subject: Re: X-Ref broke....
> Is there a workaround?
>
> Worik
>
> Berek Half-hand wrote:
> >
> > This is an old problem that's been around for years. The problem is with
the
> > parsers. The fix doesn't seem to be a high priority with Red Hat.
> >
> > ----- Original Message -----
> > From: "Dalton, Barnaby" <Barnaby.Dalton@radioscape.com>
> > To: "'Worik'" <worik@jungledrum.co.nz>; <sourcenav@sources.redhat.com>
> > Sent: Monday, September 24, 2001 4:26 AM
> > Subject: RE: X-Ref broke....
> >
> > >
> > > I have experienced the same problem - and it hasn't magically fixed
itself
> > > yet!
> > > Barney
> > >
> > > > -----Original Message-----
> > > > From: Worik [ mailto:worik@jungledrum.co.nz ]
> > > > Sent: 24 September 2001 6:19 AM
> > > > To: sourcenav@sources.redhat.com
> > > > Subject: Re: X-Ref broke....
> > > >
> > > >
> > > > Please ignore my last message.
> > > >
> > > > I have no idea what I have done, but it is working again.
> > > >
> > > > Since I have no idea of what happened I cannot report a bug.
> > > >
> > > > Such is life
> > > >
> > > > Worik
> > > >
> > > > Worik wrote:
> > > > >
> > > > > Friends
> > > > >
> > > > > When I select a C++ method and do a X-Ref for it I get all
> > > > the methods
> > > > > and functions it calls but not the methods and functions
> > > > that call it.
> > > > >
> > > > > The 'referred by' menu item in the right mouse menu is greyed out.
> > > > >
> > > > > I am sure this was working last week. Is there some
> > > > setting that I may
> > > > > have inadvertently changed that controls this
> > > > >
> > > > > Worik
> > > >
> > >
> > >
> > > **********************************************************************
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity to whom they
> > > are addressed. If you have received this email in error please notify
> > > postmaster@radioscape.com.
> > >
> > > This footnote also confirms that this email message has been scanned
> > > for the presence of computer viruses known at the time of sending.
> > >
> > > www.radioscape.com
> > > **********************************************************************
> > >
> > >
> > >
>
>
next prev parent reply other threads:[~2001-09-24 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 1:25 Dalton, Barnaby
2001-09-24 7:13 ` Berek Half-hand
2001-09-24 13:15 ` Worik
2001-09-24 17:21 ` Berek Half-hand [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-23 20:31 Worik
2001-09-23 22:18 ` Worik
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='001e01c14557$f1eee0c0$c42f5b18@ne.mediaone.net' \
--to=berek@usa.net \
--cc=sourcenav@sources.redhat.com \
--cc=worik@jungledrum.co.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).