From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23468@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#23468: Feature request: highlight Edebug breakpoints
Date: Sun, 20 Oct 2019 14:47:54 +0300 [thread overview]
Message-ID: <83eez763kl.fsf@gnu.org> (raw)
In-Reply-To: <8736fnhdqs.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 20 Oct 2019 13:12:43 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: pogonyshev@gmail.com, 23468@debbugs.gnu.org
> Date: Sun, 20 Oct 2019 13:12:43 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I've now added highlights for the breakpoints in Emacs 27.
> >
> > Thanks, but why isn't this in NEWS and in the ELisp manual?
>
> I didn't think it was NEWS-worthy (or documentation-worthy): It just
> a visual signifier that should have been there all along.
I think it should be documented because it presents a visual artifact
that users will need to understand.
And now that I see it in action, I think its visual appearance could
be improved. What I see is the opening parenthesis of the form
highlighted in the 'highlight' face. I think we should use a distinct
face, so that it doesn't "disappear" if the user has hl-line mode
enabled and so that users could customize it independently, and also I
think an indication similar to GUD (on the fringe etc.) would be
better: more prominent and much more self-explanatory.
Thanks.
next prev parent reply other threads:[~2019-10-20 11:47 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 [this message]
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
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=83eez763kl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23468@debbugs.gnu.org \
--cc=larsi@gnus.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).