unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: wilnerthomas--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Rainbow-delimiters highlighting { and } for tex and latex
Date: Wed, 7 Sep 2022 17:03:50 +0200 (CEST)	[thread overview]
Message-ID: <NBNTdD6--3-2@tutanota.com> (raw)
In-Reply-To: <jwvleqvmhqj.fsf-monnier+emacs@gnu.org-NBNA5jg----2>


Sep 7, 2022, 13:34 by monnier@iro.umontreal.ca:

> wilnerthomas@tutanota.com [2022-09-07 15:23:57] wrote:
>
>> Sep 7, 2022, 13:14 by help-gnu-emacs@gnu.org:
>>
>>>> Stefan, you are right.  But it handles only lisp commands, colouring
>>>> initial  "("  and final  ")".  But
>>>> not for highlighting  "{"  and  "}"  for  "tex"  and  "latex".
>>>>
>>>
>>> That is not my experience (from a few seconds before sending my
>>> previous message).
>>>
>> What do I have to do exactly?
>>
>
> I don't know.  For me it just works (I don't use rainbow-delimiters,
> I simply turned it on to double-check my intuition before replying to
> you, and it worked for (..), {..} and [..] in a `latex-mode` buffer).
>

What version are you using?  Do you know where in the code the checking for "{ }" is performed?

I see 

rainbow-delimiters--propertize 

which only has 

(while (> end (progn (skip-syntax-forward "^()" end)

I can see that "( )" and "[ ]" get highlighted, but not "{ }".




  parent reply	other threads:[~2022-09-07 15:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 11:07 Rainbow-delimiters highlighting { and } for tex and latex wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-07 13:10   ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:14     ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-07 13:23       ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 13:34         ` Stefan Monnier
2022-09-07 19:29           ` Christopher Dimech
2022-09-08  4:13             ` tomas
2022-09-08 10:13               ` Christopher Dimech
2022-09-08 12:08             ` Alessandro Bertulli
2022-09-08 13:25               ` Christopher Dimech
2022-09-08 13:58                 ` Alessandro Bertulli
2022-09-08 15:02                   ` Christopher Dimech
2022-09-08 15:04                     ` Alessandro Bertulli
2022-09-09  8:41                     ` Arash Esbati
2022-09-09 12:33                       ` Christopher Dimech
2022-09-09 19:36                         ` Arash Esbati
2022-09-09 20:13                           ` Christopher Dimech
2022-09-09 20:45                           ` Christopher Dimech
     [not found]         ` <jwvleqvmhqj.fsf-monnier+emacs@gnu.org-NBNA5jg----2>
2022-09-07 15:03           ` wilnerthomas--- via Users list for the GNU Emacs text editor [this message]
2022-09-07 15:16             ` tomas
2022-09-07 15:29               ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-09-07 15:59                 ` tomas
2022-09-07 16:43             ` Stefan Monnier
     [not found]             ` <jwvczc7b0jf.fsf-monnier+emacs@gnu.org-NBNqAf0----2>
2022-09-08 10:35               ` wilnerthomas--- via Users list for the GNU Emacs text editor

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=NBNTdD6--3-2@tutanota.com \
    --to=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=wilnerthomas@tutanota.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.
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).