From: carlmarcos--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ektending rainbow-delimiters to colour {}
Date: Tue, 19 Jul 2022 11:31:48 +0200 (CEST) [thread overview]
Message-ID: <N7Kn8wa--3-2@tutanota.com> (raw)
In-Reply-To: <YtZt0b/KBWW/CNV5@tuxteam.de-N7KbPIc----2>
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 {}.
next prev parent reply other threads:[~2022-07-19 9:31 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 [this message]
2022-07-19 9:45 ` tomas
[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=N7Kn8wa--3-2@tutanota.com \
--to=help-gnu-emacs@gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=tomas@tuxteam.de \
/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).