unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: Two changes to tooltip.el (proposal)
Date: Wed, 20 Nov 2002 23:33:32 +0000	[thread overview]
Message-ID: <15836.7116.848080.301463@nick.uklinux.net> (raw)
In-Reply-To: <5xfztwzcno.fsf@kfs2.cua.dk>


 > > 
 > > (defun tooltip-identifier-from-point (point)
 > >   "Extract the identifier at POINT, if any."
 > >   (save-excursion
 > >     (goto-char point)
 > >     (gud-find-c-expr)))
 > 
 > Maybe this would be safer:
 > 
 >         (if (fboundp 'gud-find-c-expr)
 >             (gud-find-c-expr)
 >           ... old tooltip-identifier-from-point code goes here ...
 >           )
 > 

`tooltip-identifier-from-point' is only used by gud so `gud-find-c-expr'
will always be defined. Actually, I think the functions that provide
the tooltips for gud should be should really be in gud.el.

 > I haven't been able to find any documentation on the "server" prefix;
 > what does it mean?  Is it related to the gdbserver program?  In that
 > case, does it change the semantics of the print command so that
 > debugging a program via gdbserver may not work properly with the change?
 > 
 > Even if it is harmless, are you sure "server print" is supported by
 > all gdb versions (do we care -- probably most systems running emacs 21.x
 > also have a fairly new version of gdb ?)

The server prefix is described in the Annotations section of the Gdb info
pages.  Annotations have been around for a long time so I presume the server
prefix has too. Eli could probably tell you more.

It has nothing to do with the gdbserver program as far as I know.

Nick

  reply	other threads:[~2002-11-20 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 19:24 Two changes to tooltip.el (proposal) Nick Roberts
2002-11-20 11:46 ` Kim F. Storm
2002-11-20 23:33   ` Nick Roberts [this message]
2002-11-25 12:37 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15836.7116.848080.301463@nick.uklinux.net \
    --to=nick@nick.uklinux.net \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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