From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sun, 7 Apr 2024 13:41:34 -0500
Subject: new repository

---
 devdocs/elisp/syntax-flags.html | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 devdocs/elisp/syntax-flags.html

(limited to 'devdocs/elisp/syntax-flags.html')

diff --git a/devdocs/elisp/syntax-flags.html b/devdocs/elisp/syntax-flags.html
new file mode 100644
index 00000000..b5cb2deb
--- /dev/null
+++ b/devdocs/elisp/syntax-flags.html
@@ -0,0 +1,18 @@
+ <h4 class="subsection">Syntax Flags</h4>  <p>In addition to the classes, entries for characters in a syntax table can specify flags. There are eight possible flags, represented by the characters ‘<samp>1</samp>’, ‘<samp>2</samp>’, ‘<samp>3</samp>’, ‘<samp>4</samp>’, ‘<samp>b</samp>’, ‘<samp>c</samp>’, ‘<samp>n</samp>’, and ‘<samp>p</samp>’. </p> <p>All the flags except ‘<samp>p</samp>’ are used to describe comment delimiters. The digit flags are used for comment delimiters made up of 2 characters. They indicate that a character can <em>also</em> be part of a comment sequence, in addition to the syntactic properties associated with its character class. The flags are independent of the class and each other for the sake of characters such as ‘<samp>*</samp>’ in C mode, which is a punctuation character, <em>and</em> the second character of a start-of-comment sequence (‘<samp>/*</samp>’), <em>and</em> the first character of an end-of-comment sequence (‘<samp>*/</samp>’). The flags ‘<samp>b</samp>’, ‘<samp>c</samp>’, and ‘<samp>n</samp>’ are used to qualify the corresponding comment delimiter. </p> <p>Here is a table of the possible flags for a character <var>c</var>, and what they mean: </p> <ul> <li> ‘<samp>1</samp>’ means <var>c</var> is the start of a two-character comment-start sequence. </li>
+<li> ‘<samp>2</samp>’ means <var>c</var> is the second character of such a sequence. </li>
+<li> ‘<samp>3</samp>’ means <var>c</var> is the start of a two-character comment-end sequence. </li>
+<li> ‘<samp>4</samp>’ means <var>c</var> is the second character of such a sequence. </li>
+<li> ‘<samp>b</samp>’ means that <var>c</var> as a comment delimiter belongs to the alternative “b” comment style. For a two-character comment starter, this flag is only significant on the second char, and for a 2-character comment ender it is only significant on the first char. </li>
+<li> ‘<samp>c</samp>’ means that <var>c</var> as a comment delimiter belongs to the alternative “c” comment style. For a two-character comment delimiter, ‘<samp>c</samp>’ on either character makes it of style “c”. </li>
+<li> ‘<samp>n</samp>’ on a comment delimiter character specifies that this kind of comment can be nested. Inside such a comment, only comments of the same style will be recognized. For a two-character comment delimiter, ‘<samp>n</samp>’ on either character makes it nestable.  <p>Emacs supports several comment styles simultaneously in any one syntax table. A comment style is a set of flags ‘<samp>b</samp>’, ‘<samp>c</samp>’, and ‘<samp>n</samp>’, so there can be up to 8 different comment styles, each one named by the set of its flags. Each comment delimiter has a style and only matches comment delimiters of the same style. Thus if a comment starts with the comment-start sequence of style “bn”, it will extend until the next matching comment-end sequence of style “bn”. When the set of flags has neither flag ‘<samp>b</samp>’ nor flag ‘<samp>c</samp>’ set, the resulting style is called the “a” style. </p> <p>The appropriate comment syntax settings for C++ can be as follows: </p> <dl compact> <dt>‘<samp>/</samp>’</dt> <dd><p>‘<samp>124</samp>’ </p></dd> <dt>‘<samp>*</samp>’</dt> <dd><p>‘<samp>23b</samp>’ </p></dd> <dt>newline</dt> <dd><p>‘<samp>&gt;</samp>’ </p></dd> </dl> <p>This defines four comment-delimiting sequences: </p> <dl compact> <dt>‘<samp>/*</samp>’</dt> <dd>
+<p>This is a comment-start sequence for “b” style because the second character, ‘<samp>*</samp>’, has the ‘<samp>b</samp>’ flag. </p> </dd> <dt>‘<samp>//</samp>’</dt> <dd>
+<p>This is a comment-start sequence for “a” style because the second character, ‘<samp>/</samp>’, does not have the ‘<samp>b</samp>’ flag. </p> </dd> <dt>‘<samp>*/</samp>’</dt> <dd>
+<p>This is a comment-end sequence for “b” style because the first character, ‘<samp>*</samp>’, has the ‘<samp>b</samp>’ flag. </p> </dd> <dt>newline</dt> <dd><p>This is a comment-end sequence for “a” style, because the newline character does not have the ‘<samp>b</samp>’ flag. </p></dd> </dl> </li>
+<li> ‘<samp>p</samp>’ identifies an additional prefix character for Lisp syntax. These characters are treated as whitespace when they appear between expressions. When they appear within an expression, they are handled according to their usual syntax classes. <p>The function <code>backward-prefix-chars</code> moves back over these characters, as well as over characters whose primary syntax class is prefix (‘<samp>'</samp>’). See <a href="motion-and-syntax">Motion and Syntax</a>. </p>
+</li>
+</ul><div class="_attribution">
+  <p class="_attribution-p">
+    Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
+    <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Syntax-Flags.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Syntax-Flags.html</a>
+  </p>
+</div>
-- 
cgit v1.2.3