rouge-carve 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fbeb1c2fa0f572f138c6a89a23bafcae682051c9e10474951b5cba9de3bc0aa3
-  data.tar.gz: 7d089e544a959be5c208ef4e1cc523feda2b1d8cf6632b99086ae41c5cb13c31
+  metadata.gz: c4006805a5023dc8b016745f1ab3dc73bf29fa24de27acc46c19696658a9ee36
+  data.tar.gz: 85965e83d476add300683d7e5ce7464d6affb784b067b3797318ef45575d5c78
 SHA512:
-  metadata.gz: 439cc10aa425adaec2fed2e19e6af9aab75ffec47b699c3a3dff0632ee2503ca6240d7d4f869db0c93f907fee29f43b351ba9a507f89cff5b0a3a11ddb257e72
-  data.tar.gz: b93c04c6c832959f1a58e238efb161b5d6a7283b104cec5deae971e62065f18b8bf88abf03fc61fdf7cc29da54bac7d3cddaa384f267c7e6e91478cd124f8a59
+  metadata.gz: eb1fb40ca27583ebb19f1af32bf208efcdd5d21c2f880f5e400f4c06562d4a79a977988008ec054d448d1e7ac9c0020acdce83db8b2cd19d0bcb6912878896dd
+  data.tar.gz: 7bf48fae5c12930737941c834ec4347dcd5f1a30a77e4cbcbdf99e8fa20c4d90c39d9f45bfaa9d1be3a2edea3d1025ef1f31f5ffa3ecbfade9212e0a4a4811ff

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## [0.1.1] - 2026-09-21
+
+- The reserved include directive `{{ path #section @key:value }}` (PART 9
+  section 19, markup-carve/carve#291) is lexed BY PART: the path as
+  `Name.Namespace`, the selector as `Name.Label`, and each option as
+  `Name.Attribute` plus its value. It used to shred into the constructs its own
+  selector is spelled with, so `#intro` in a path was colored as a hashtag.
+
 ## [0.1.0] - 2026-08-27
 
 First release.

data/README.md

@@ -66,23 +66,6 @@ shared with the Prism, highlight.js and Pygments grammars, so the four agree:
 it over-colours an indented-at-document-level opener rather than
 under-colouring the far more common indented construct inside a list item.
 
-## Testing
-
-```bash
-bundle install
-bundle exec rspec
-```
-
-Two gates, and the second is the one that finds things:
-
-- `spec/carve_spec.rb` pins the constructs, including each inverted delimiter.
-- `script/corpus_check.rb` lexes every `.crv` document in the Carve spec
-  repository and fails on a single `Error` token. A lexer emitting `Error` is
-  telling the reader its own rules ran out. Both bugs found during development -
-  a blank line inside a comment fence, and a `---` thematic break opening
-  frontmatter that never closed - came from this and not from an example
-  anybody thought to write.
-
 ## Related
 
 - [carve](https://github.com/markup-carve/carve) - the language and its spec
@@ -93,6 +76,6 @@ Two gates, and the second is the one that finds things:
 - [carve-css](https://github.com/markup-carve/carve-css) - styles for the HTML
   Carve renders
 
-## License
+## Development
 
-MIT.
+Contributor setup, testing, and maintenance notes are in the [development guide](docs/development.md).

data/lib/rouge/lexers/carve.rb

@@ -359,6 +359,26 @@ module Rouge
           groups Punctuation, Str::Backtick, Punctuation
         end
 
+        # The reserved include directive `{{ path #section @key:value }}`
+        # (PART 9 section 19, grammar.ebnf `include_directive`). The core
+        # leaves it literal; a processor expands it only when a host supplies a
+        # resolver.
+        #
+        # One directive rule, because its own selector is spelled with constructs this
+        # lexer already knows: `#section` is the tag rule below and an option
+        # slot is the mention rule, so without this `#intro` came out coloured
+        # as a hashtag inside a path. After the verbatim family, so a directive
+        # in a code span stays literal; before every other brace rule, none of
+        # which can spell `{{`.
+        # THE CLOSER IS IN THE LOOKAHEAD, so an unterminated `{{` never opens
+        # the state at all and stays the ordinary text the processor treats it
+        # as. Without it the opener scoped and only the newline rule below
+        # stopped the damage.
+        rule %r/(\{\{)(?=[ \t]+[^\n]*?[ \t]+\}\})([ \t]+)((?:"(?:\\.|[^"\\])*"|[^#@}\s"][^#@}\s]*))/ do
+          groups Punctuation, Text, Name::Namespace
+          push :includeparts
+        end
+
         # CriticMarkup substitution and comment, before the forced family:
         # `{~old~>new~}` also matches the forced-strike shape.
         rule %r/(\{~)([^\n]*?)(~>)([^\n]*?)(~\})/ do
@@ -496,6 +516,27 @@ module Rouge
         rule %r/\.\.\./, Punctuation
       end
 
+      # The tail of an include directive: its selector, option slots, and
+      # anything else written there. Scoped BY PART - the opener rule is what
+      # keeps the tag and mention rules out, so painting one token buys nothing,
+      # and a reader wants the path to look like a path.
+      #
+      # A part that is neither a section nor an option stays plain text rather
+      # than being refused, matching the processor, which leaves a malformed
+      # directive alone. A newline pops: the directive requires its closer on
+      # the same line, so anything else is not one.
+      state :includeparts do
+        rule %r/[ \t]+/, Text
+        rule %r/\}\}/, Punctuation, :pop!
+        rule %r/#[A-Za-z_][\w-]*/, Name::Label
+        rule %r/(@[A-Za-z_][\w-]*)(:)([^\s}]+)/ do
+          groups Name::Attribute, Punctuation, Literal
+        end
+        rule %r/[^\s}]+/, Text
+        rule %r/\}/, Text
+        rule %r/\n/, Text, :pop!
+      end
+
       state :inlinefootnote do
         rule %r/\]/, Punctuation, :pop!
         mixin :inlinecontent

data/lib/rouge-carve.rb

@@ -9,5 +9,5 @@ require_relative 'rouge/lexers/carve'
 # registers it, so `Rouge::Lexer.find('carve')` and
 # `Rouge::Lexer.guess(filename: 'x.crv')` work from that point on.
 module RougeCarve
-  VERSION = '0.1.0'
+  VERSION = '0.1.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rouge-carve
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Mark Scherer
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-27 00:00:00.000000000 Z
+date: 2026-09-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rouge