all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23468@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#23468: Feature request: highlight Edebug breakpoints
Date: Mon, 21 Oct 2019 22:29:27 +0200	[thread overview]
Message-ID: <878spdq1ug.fsf@gnus.org> (raw)
In-Reply-To: <83tv8344os.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Oct 2019 22:06:43 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> No, that's not it.  Sorry, I've misled you: you need to look at
> gdb-mi.el, where it puts on an overlay string a display property whose
> value includes 'left-fringe.  See, e.g., gdb-put-string.

Ah, I see.  I've never used fringe stuff before and how it interacts
with overlays isn't self-evident.  Perhaps there should be an example in
the manual?

By cargo-culting the code from gdb-mi, I get the following way to make
an overlay that's not hiding anything in the buffer, but just showing a
fringe bitmap:

 (let ((fringe (make-overlay pos pos)))
   (overlay-put fringe 'before-string
                (propertize "x" 'display `(left-fringe breakpoint ,face)))))))))


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-21 20:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 17:10 bug#23468: Feature request: highlight Edebug breakpoints Paul Pogonyshev
2019-10-20 10:08 ` Lars Ingebrigtsen
2019-10-20 11:08   ` Eli Zaretskii
2019-10-20 11:12     ` Lars Ingebrigtsen
2019-10-20 11:47       ` Eli Zaretskii
2019-10-20 12:08         ` Lars Ingebrigtsen
2019-10-20 12:48           ` Eli Zaretskii
2019-10-20 17:18             ` Lars Ingebrigtsen
2019-10-20 19:06               ` Eli Zaretskii
2019-10-21 20:29                 ` Lars Ingebrigtsen [this message]
2019-10-22  2:29                   ` Eli Zaretskii
2019-10-22 14:21                     ` Lars Ingebrigtsen

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=878spdq1ug.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=23468@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=pogonyshev@gmail.com \
    /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.