From: Miles Bader <miles.bader@necel.com>
Cc: "Kim F. Storm" <storm@cua.dk>,
emacs-devel@gnu.org, "John S. Yates, Jr." <john@yates-sheets.org>
Subject: Re: Display feature request: gud-overlay-arrow
Date: Thu, 23 Mar 2006 15:26:24 +0900 [thread overview]
Message-ID: <buolkv1llrj.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <17442.14184.526075.771249@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu, 23 Mar 2006 17:51:36 +1200")
Nick Roberts <nickrob@snap.net.nz> writes:
> For this case of co-incidence, I've thought about changing the colour of the
> arrow to that of the underlying breakpoint and omitting the breakpoint icon
> altogether, but I'm sure this would be hard to do.
BTW, the aforemention commercial debuggers used multicolor icons so that
a mostly invisible arrow behind a octagon is much more obvious if it's
white and the octagon is red ... i guess we can't do that with fringe
icons though.
-Miles
--
Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
next prev parent reply other threads:[~2006-03-23 6:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 22:59 Display feature request: gud-overlay-arrow Nick Roberts
2006-03-20 23:42 ` Kim F. Storm
2006-03-21 3:55 ` Nick Roberts
2006-03-21 9:27 ` Kim F. Storm
2006-03-21 10:35 ` Nick Roberts
2006-03-21 13:43 ` Kim F. Storm
2006-03-22 3:20 ` Nick Roberts
2006-03-22 20:43 ` Kim F. Storm
2006-03-23 5:15 ` John S. Yates, Jr.
2006-03-23 5:04 ` Miles Bader
2006-03-23 5:51 ` Nick Roberts
2006-03-23 6:26 ` Miles Bader [this message]
2006-03-23 21:28 ` Nick Roberts
2006-03-23 8:59 ` Nick Roberts
2006-03-23 10:23 ` Kim F. Storm
2006-03-23 21:59 ` Nick Roberts
2006-03-21 19:26 ` Richard Stallman
2006-03-21 19:40 ` Masatake YAMATO
2006-03-21 22:01 ` Stefan Monnier
2006-03-21 21:58 ` Kim F. Storm
2006-03-22 13:44 ` Richard Stallman
2006-03-22 17:50 ` Kim F. Storm
2006-03-23 19:47 ` 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=buolkv1llrj.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=miles@gnu.org \
--cc=storm@cua.dk \
/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).