all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: gdb-ui.el assumes images support
Date: Sun, 7 Nov 2004 13:23:14 +1300	[thread overview]
Message-ID: <16781.27378.713504.174297@farnswood.snap.net.nz> (raw)
In-Reply-To: <01c4c422$Blat.v2.2.2$ae5429e0@zahav.net.il>


 > ...(why does tooltip.el need to require gdb-ui, anyway?).

tooltip.el doesn't require gdb-ui. 

emacs -q

`C-h v' features

features's value is 
(help-fns help-mode view button tooltip image tool-bar disp-table mwheel x-dnd fontset ediff-hook vc-hooks lisp-float-type lisp-mode register page menu-bar timer select scroll-bar mldrag mouse facemenu font-core frame ucs-tables georgian utf-8-lang misc-lang vietnamese tibetan thai lao korean japanese hebrew greek romanian slovak czech european ethiopic kannada tamil malayalam devanagari indian cyrillic chinese case-table help simple faces cus-face text-properties overlay md5 base64 format mule env custom widget backquote make-network-process x-toolkit)

tooltip is present, while gdb-ui isn't.

You are probably referring to the fact that tooltip does require gdb-ui for
compilation (eval-when-compile). tooltip.el contains lisp functions from
gdb-ui.el like gdb-enqueue-input and as someone had already `required' gud for
compilation I followed suit and added gdb-ui. Is this what is causing the
problem?

I'm not a lisp expert but there is only one macro in tooltip.el
(tooltip-region-active-p) which doesn't use functions from gud or gdb-ui, so
perhaps these requires aren't necessary? Anyone?

Nick

  reply	other threads:[~2004-11-07  0:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 17:03 gdb-ui.el assumes images support Eli Zaretskii
2004-11-07  0:23 ` Nick Roberts [this message]
2004-11-07  4:48   ` Eli Zaretskii
2004-11-07 10:35     ` Andreas Schwab
2004-11-07 22:12       ` Eli Zaretskii
2004-11-08 10:15         ` Andreas Schwab
2004-11-08 12:11           ` Eli Zaretskii
2004-11-08 16:58         ` Richard Stallman
2004-11-08 20:38           ` Nick Roberts
2004-11-08 21:23             ` Kim F. Storm
2004-11-08 22:05               ` Kevin Rodgers
2004-11-08 23:54                 ` Nick Roberts
2004-11-09  0:12                   ` Luc Teirlinck
2004-11-09  0:35                   ` Luc Teirlinck
2004-11-09  1:27                   ` Luc Teirlinck
2004-11-09 14:11                 ` Kim F. Storm
2004-11-09 17:55                   ` Kevin Rodgers
2004-11-10 16:09                     ` Richard Stallman
2004-11-09 21:29               ` Richard Stallman
2004-11-09 22:58                 ` Luc Teirlinck
2004-11-10  0:02                   ` Stefan Monnier
2004-11-10  0:08                     ` Luc Teirlinck
2004-11-11  3:14                   ` Richard Stallman
2004-11-09 23:22                 ` Kim F. Storm
2004-11-09 21:29             ` Richard Stallman
2004-11-10 11:45               ` Nick Roberts
2004-11-08 16:59     ` Richard Stallman
2004-11-09  4:28       ` Eli Zaretskii
2004-11-09 14:20         ` Kim F. Storm
2004-11-10 16:08           ` Richard Stallman
2004-11-09 21:30         ` Richard Stallman
2004-11-07 18:04 ` Richard Stallman
2004-11-08 12:47   ` Kim F. Storm
2004-11-08 14:55     ` Stefan

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=16781.27378.713504.174297@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.