From: Hadrien Lacour <hadrien.lacour@posteo.net>
To: 39277@debbugs.gnu.org
Subject: bug#39277:
Date: Tue, 27 Oct 2020 16:24:48 +0100 [thread overview]
Message-ID: <20201027152448.ddkpa6oelcql22rb@gentoo-zen2700x> (raw)
In-Reply-To: <20200125100009.33e3cpgmjszmpwzq@gentoo-zen2700x>
Sorry for not really contributing, I must provid the excuse that I don't have
enough time or energy right now.
About Tcl syntax rules, Tcl(3tcl) (or Tcl(n) on gentoo) explains it simply:
...
[4] Double quotes.
If the first character of a word is double-quote (“"”) then the word is
terminated by the next double-quote character. If semi-colons, close
brackets, or white space characters (including newlines) appear between the
quotes then they are treated as ordinary characters and included in the
word. Command substitution, variable substitution, and backslash
substitution are performed on the characters between the quotes as
described below. The double-quotes are not retained as part of the word.
...
[6] Braces.
If the first character of a word is an open brace (“{”) and rule [5] does
not apply, then the word is terminated by the matching close brace (“}”).
Braces nest within the word: for each additional open brace there must be
an additional close brace (however, if an open brace or close brace within
the word is quoted with a backslash then it is not counted in locating the
matching close brace). No substitutions are performed on the characters
between the braces except for backslash-newline substitutions described
below, nor do semi-colons, newlines, close brackets, or white space receive
any special interpretation. The word will consist of exactly the
characters between the outer braces, not including the braces themselves.
...
To put simply, braces act like sh's single quotes and double quotes are
basically the same (only $ or [] is substituted).
prev parent reply other threads:[~2020-10-27 15:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 10:00 bug#39277: 26.3; Tcl font lock does not understand quoting Hadrien Lacour
2020-01-25 10:12 ` bug#39277: tcl-mode " Hadrien Lacour
2020-01-25 10:53 ` Hadrien Lacour
2020-10-26 20:44 ` bug#39277: 26.3; Tcl font lock " mvar
2020-10-27 8:31 ` bug#39277: (no subject) Lars Ingebrigtsen
2020-10-27 8:51 ` bug#39277: 26.3; Tcl font lock does not understand quoting Andreas Schwab
2020-10-27 8:56 ` Lars Ingebrigtsen
2020-10-27 13:27 ` Stefan Monnier
2020-10-27 17:45 ` Lars Ingebrigtsen
2020-10-27 20:42 ` mvar
2020-10-27 20:47 ` Lars Ingebrigtsen
2020-10-27 22:48 ` Stefan Monnier
2020-10-29 17:39 ` Stefan Monnier
2020-10-30 12:02 ` Lars Ingebrigtsen
2020-10-31 11:01 ` mvar
2020-10-31 13:20 ` Stefan Monnier
2020-11-03 19:47 ` mvar
2020-11-03 21:45 ` Stefan Monnier
2020-11-05 12:38 ` mvar
2020-10-27 15:24 ` Hadrien Lacour [this message]
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=20201027152448.ddkpa6oelcql22rb@gentoo-zen2700x \
--to=hadrien.lacour@posteo.net \
--cc=39277@debbugs.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.
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).