unofficial mirror of bug-gnu-emacs@gnu.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: Sun, 20 Oct 2019 19:18:11 +0200	[thread overview]
Message-ID: <87blube3os.fsf@gnus.org> (raw)
In-Reply-To: <837e4z60qu.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Oct 2019 15:48:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> As for a fringe indication -- there may be a bunch of breakpoints.  Do
>> we want to have something in the fringe for all of them?
>
> GUD puts a bitmap on the fringe for each breakpoint, yes.

Hm.  This is all pretty new to me...  but...
overlay-arrow-variable-list is a list of variables, each of which can
have one single position.

So to have more than a single fringe indication, we'd have to generate
one variable per breakpoint?

And you can't just put the positions into the list, either:

(setq overlay-arrow-variable-list
      (list (set-marker (make-marker) (point-min))
            (set-marker (make-marker) 100)))

Am I missing something, or does this mechanism just not support an
arbitrary number of fringe indicators?  (Well, without generating
variables dynamically, which I'm guessing we don't want to.)

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





  reply	other threads:[~2019-10-20 17:18 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 [this message]
2019-10-20 19:06               ` Eli Zaretskii
2019-10-21 20:29                 ` Lars Ingebrigtsen
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

  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=87blube3os.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 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).