From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#23468: Feature request: highlight Edebug breakpoints Date: Sun, 20 Oct 2019 19:18:11 +0200 Message-ID: <87blube3os.fsf@gnus.org> References: <87tv83hgqi.fsf@gnus.org> <83lftf65dn.fsf@gnu.org> <8736fnhdqs.fsf@gnus.org> <83eez763kl.fsf@gnu.org> <87zhhvei0h.fsf@gnus.org> <837e4z60qu.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="67031"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 23468@debbugs.gnu.org, pogonyshev@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Oct 20 19:19:21 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iMErO-000HDc-TE for geb-bug-gnu-emacs@m.gmane.org; Sun, 20 Oct 2019 19:19:19 +0200 Original-Received: from localhost ([::1]:41704 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMErN-0000K4-0R for geb-bug-gnu-emacs@m.gmane.org; Sun, 20 Oct 2019 13:19:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37377) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMErA-0000Jb-Db for bug-gnu-emacs@gnu.org; Sun, 20 Oct 2019 13:19:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMEr9-0002LO-Dc for bug-gnu-emacs@gnu.org; Sun, 20 Oct 2019 13:19:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46393) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iMEr8-0002LE-P2 for bug-gnu-emacs@gnu.org; Sun, 20 Oct 2019 13:19:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iMEr8-00089L-EV for bug-gnu-emacs@gnu.org; Sun, 20 Oct 2019 13:19:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 20 Oct 2019 17:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23468 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 23468-submit@debbugs.gnu.org id=B23468.157159189831274 (code B ref 23468); Sun, 20 Oct 2019 17:19:02 +0000 Original-Received: (at 23468) by debbugs.gnu.org; 20 Oct 2019 17:18:18 +0000 Original-Received: from localhost ([127.0.0.1]:55214 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iMEqQ-00088M-2i for submit@debbugs.gnu.org; Sun, 20 Oct 2019 13:18:18 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:52184) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iMEqO-00088A-0P for 23468@debbugs.gnu.org; Sun, 20 Oct 2019 13:18:16 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iMEqJ-0001TS-SL; Sun, 20 Oct 2019 19:18:14 +0200 In-Reply-To: <837e4z60qu.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Oct 2019 15:48:57 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:169841 Archived-At: Eli Zaretskii 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