all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Josh Berdine <josh@berdine.net>
Cc: 19080@debbugs.gnu.org
Subject: bug#19080: 24.4; wish: enable show-paren-mode to highlight matching same-level keywords
Date: Thu, 12 May 2022 03:44:43 +0200	[thread overview]
Message-ID: <87lev734ok.fsf@gnus.org> (raw)
In-Reply-To: <878ujat60c.fsf@berdine.net> (Josh Berdine's message of "Mon, 17 Nov 2014 11:34:43 +0000")

Josh Berdine <josh@berdine.net> writes:

> emacs -Q
> M-x load-file
> ~/.opam/4.02.1/share/tuareg/tuareg.el
> M-x tuareg-mode
> M-x show-paren-mode
> let f () =
>   let x = 0 in
>   ()
> C-u 17 C-b
>
> 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).  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.

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





  reply	other threads:[~2022-05-12  1:44 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 [this message]
2022-05-12  5:36   ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lev734ok.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19080@debbugs.gnu.org \
    --cc=josh@berdine.net \
    /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.