From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, Yuan Fu <casouri@gmail.com>
Cc: 19080@debbugs.gnu.org, josh@berdine.net
Subject: bug#19080: 24.4; wish: enable show-paren-mode to highlight matching same-level keywords
Date: Thu, 12 May 2022 08:36:18 +0300 [thread overview]
Message-ID: <8335hfqpm5.fsf@gnu.org> (raw)
In-Reply-To: <87lev734ok.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 12 May 2022 03:44:43 +0200)
> Cc: 19080@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 12 May 2022 03:44:43 +0200
>
> > This starts a fresh emacs, loads the tuareg mode, enables
> > show-paren-mode, enters some ocaml code, and puts the point on a 'let'
> > keyword.
> >
> > In this situation, it would be helpful if the 'let' and corresponding
> > 'in' were highlighted in 'show-paren-match-face'. And similarly for
> > "fun", "if", "match", and "try".
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> I think this is rather beyond the scope of show-paren-mode (which is a
> pretty simple mode that just blinks parentheses, and not much more).
Indeed.
> A new different mode that relies on language semantics to identify
> these things would be nice, but I don't think there's anything
> actionable to be done here, so I'm closing this bug report.
We could perhaps add a new feature, based on tree-sitter, to highlight
a block of code, where the block is defined by PL rules, not by
parens, braces, and similar simple syntactic elements.
Yuan, WDYT? Can this be added to the tree-sitter branch perhaps?
next prev parent reply other threads:[~2022-05-12 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:34 bug#19080: 24.4; wish: enable show-paren-mode to highlight matching same-level keywords Josh Berdine
2022-05-12 1:44 ` Lars Ingebrigtsen
2022-05-12 5:36 ` Eli Zaretskii [this message]
2022-05-12 22:52 ` Yuan Fu
2022-05-13 5:52 ` Eli Zaretskii
2022-05-13 11:48 ` Josh Berdine
2022-05-14 5:05 ` Yuan Fu
2022-05-14 8:00 ` Visuwesh
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=8335hfqpm5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19080@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=josh@berdine.net \
--cc=larsi@gnus.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).