unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to gdb-ui.el
Date: Mon, 21 Mar 2005 07:39:59 +0900	[thread overview]
Message-ID: <fc339e4a0503201439393fd94f@mail.gmail.com> (raw)
In-Reply-To: <16958.302.32187.274750@farnswood.snap.net.nz>

On Mon, 21 Mar 2005 11:03:10 +1200, Nick Roberts <nickrob@snap.net.nz> wrote:
> I don't think using breakpoint faces in text-mode quite works. On a basic
> xterm, an enabled breakpoint (letter 'B') stands out clearly in red, but
> as disabled breakpoint (letter 'b') disappears completely.

It works correclty on the linux console; it may be face definitions
need tweaking for "low-color" terminals (this can be done using the
conditional facility of the face definition language).

> the subtleties of faces but maybe grey60 gets 'rounded' to white on an xterm
> with 8/16 colours.

Yes, this is probably what's happening.

> Also the background of the face doesn't always match the
> background of the terminal (I have found particularly so for a gnome-terminal).

Ok; probably the `:inherit fringe' should be used only for bitmaps (is
it even useful for them?  I though fringe stuff would get merged with
the fringe face anyway).

> In X, enabled/disabled breakpoints are distinguished by colour alone, the
> icons having the same shape both in the margin and in the fringe. In text
> mode the breakpoint state is already distinguished by the case of the letter
> (B/b) so the same colour can be used. To help it stand out from the text,
> I guess this color could be red in both cases, a color which I presume is
> available on many terminals.

Note that I made this change because I was setting breakpoints on a
tty and couldn't see them very well; having them displayed in bold red
_really_ helps.

I'll give the faces a tweak to reflect the above points.

-Miles
-- 
Do not taunt Happy Fun Ball.

  reply	other threads:[~2005-03-20 22:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 23:03 Changes to gdb-ui.el Nick Roberts
2005-03-20 22:39 ` Miles Bader [this message]
2005-03-21 17:29 ` Richard Stallman
2005-03-21 22:10   ` Nick Roberts
2005-03-22  5:16 ` Miles Bader
2005-03-22 20:45   ` Richard Stallman
2005-03-22 23:31     ` Kim F. Storm

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=fc339e4a0503201439393fd94f@mail.gmail.com \
    --to=snogglethorpe@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).