unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: tomas@tuxteam.de
To: carlmarcos@tutanota.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ektending rainbow-delimiters to colour {}
Date: Tue, 19 Jul 2022 11:45:44 +0200	[thread overview]
Message-ID: <YtZ9SMvKteNQarqS@tuxteam.de> (raw)
In-Reply-To: <N7Kn8wa--3-2@tutanota.com>

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

On Tue, Jul 19, 2022 at 11:31:48AM +0200, carlmarcos@tutanota.com wrote:
> 
> Jul 19, 2022, 08:39 by tomas@tuxteam.de:
> 
> > On Tue, Jul 19, 2022 at 10:21:15AM +0200, carlmarcos@tutanota.com wrote:
> >
> >>
> >> Jul 19, 2022, 07:34 by tomas@tuxteam.de:
> >>
> >
> > [...]
> >
> >> > Look up the documentation for `skip-syntax-forward'. Then read on
> >> > syntax classes. Then, be enlightened :)
> >> >
> >> >From the help for skip-syntax-forward, if syntax starts with ^, skip characters whose syntax is not in syntax.
> >>
> >
> > Nearly.
> >
> > Dig deeper: what could that "syntax" thing mean? Did you read on syntax
> > classes in the manual? Does this answer your question?
> >
> I have read.  Looks as if emacs has internal functionality to determine start and end of elisp
> expressions, which rainbow-delimiters relies of.  It does actually also follow [], not so for {}.    

Read again:

  The “syntax class” of a character describes its syntactic role.  Each
  syntax table specifies the syntax class of each character.  There is no
  necessary relationship between the class of a character in one syntax
  table and its class in any other table.

So whether { resp } have the syntax class symbolised by ( resp. ) depends
on how you set up your syntax class table. Major modes set that up to match
the expectations of the language in question. In theory you could even set
# . up as opening and closing parentheses whenever it makes sense.

The answer is: Emacs _already does_ what you want.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-07-19  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  7:29 Ektending rainbow-delimiters to colour {} carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-19  7:34 ` tomas
2022-07-19  8:21   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-19  8:39     ` tomas
     [not found]     ` <YtZt0b/KBWW/CNV5@tuxteam.de-N7KbPIc----2>
2022-07-19  9:31       ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-19  9:45         ` tomas [this message]
     [not found]         ` <YtZ9SMvKteNQarqS@tuxteam.de-N7KqPqW----2>
2022-07-19 10:15           ` carlmarcos--- 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=YtZ9SMvKteNQarqS@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=carlmarcos@tutanota.com \
    --cc=help-gnu-emacs@gnu.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.
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).