unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: gdb-ui.el assumes images support
Date: Tue, 09 Nov 2004 06:28:50 +0200	[thread overview]
Message-ID: <01c4c614$Blat.v2.2.2$c1e9ff40@zahav.net.il> (raw)
In-Reply-To: <E1CRCrm-0004st-81@fencepost.gnu.org> (message from Richard Stallman on Mon, 08 Nov 2004 11:59:42 -0500)

> From: Richard Stallman <rms@gnu.org>
> CC: nickrob@snap.net.nz, emacs-devel@gnu.org
> Date: Mon, 08 Nov 2004 11:59:42 -0500
> 
> Maybe we should include fringe.c unconditionally, so that defining and
> looking up fringe bitmaps will always work, whether or not Emacs
> can actually display them.

I don't know if fringe.c will compile and link when no X libraries and
no window-system code is present (Kim?).  In any case, the bodies of
some of the functions should probably be conditioned on window-system,
either via #ifdef or a run-time check, if we include fringe.c.  And if
there's already code that tests whether the primitives defined by
fringe.c are fboundp, that code should now be changed to use some
other predicate.

Otherwise, this could be a solution.

  reply	other threads:[~2004-11-09  4:28 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
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 [this message]
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

  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='01c4c614$Blat.v2.2.2$c1e9ff40@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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.
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).