From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Display feature request: gud-overlay-arrow
Date: Tue, 21 Mar 2006 22:35:46 +1200 [thread overview]
Message-ID: <17439.55042.159116.120699@kahikatea.snap.net.nz> (raw)
In-Reply-To: <m37j6orvur.fsf@kfs-l.imdomain.dk>
> There is no reason to define the new bitmap as "built-in".
>
> Just use define-fringe-bitmap to define the new bitmap in your
> own Lisp code.
Yes, of course. That's much simpler.
> As an alternative to the hollow triangle, you could use a filled
> triangle (identical to the current bitmap), but give it is less
> prominent color, e.g. medium gray.
>
> You could call the bitmap something like "gud-inactive-arrow", and
> put a face named "gud-inactive-arrow" (inherit from "fringe") on
> it -- then people could customize it to their own liking.
I don't really know how to put a face on a bitmap but I don't mind if
someone more familiar with faces wants to play around with it.
I'm more concerned that it doesn't update properly (perhaps thats what you
alluded to with "post-switch-buffer-hook", but I don't think so):
If you have a program that calls a procedure and you set a breakpoint on that
procedure and then enter "run", the source buffer should display correctly
with the solid arrow.
If you now do "up", the main routine displays, again with a solid arrow, but
this time it should be hollow. Dragging the mode line corrects this.
If you now do "down", the called procedure displays, but with a hollow arrow.
Again dragging the mode line corrects this.
It seems to me that the buffer is not being re-displayed even though I have
deleted (set to nil) and re-computed the marker gud-overlay-arrow-position. I
think this is a display bug, and that Emacs should realise that the appearance
of this buffer has changed. Although this might be hard to do, in practice.
I've committed my changes to gdb-ui.el so you can see what I mean. If the
re-display in Emacs can't be changed, I will back my changes out.
> > It includes some minor corrections
> > to the doco.
>
> Please install that part of the patch.
Done.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-03-21 10:35 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 [this message]
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
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=17439.55042.159116.120699@kahikatea.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 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).