examples/block-names.md in markdown_exec-2.2.0 vs examples/block-names.md in markdown_exec-2.3.0
- old
+ new
@@ -1,10 +1,34 @@
## Demonstrate handling of special characters in block names
-The hidden block "(success)" is required below. It prints "Success".
-```bash :(success)
-echo "Success"
-```
+
+::: Click below to trigger. If it prints "1","2","3","4", the Link blocks were required.
+Long block names can be required by a Bash block.
+ ```bash :calling-block +long_block_name_12345678901234567890123456789012345678901234567890 +(long_block_name_12345678901234567890123456789012345678901234567890) +[long_block_name_12345678901234567890123456789012345678901234567890]
+ echo '1'
+ ```
+Long block names can be used in Link blocks.
+ ```link
+ block: long_block_name_12345678901234567890123456789012345678901234567890
+ ```
+ ```link
+ block: "(long_block_name_12345678901234567890123456789012345678901234567890)"
+ ```
+ ```link
+ block: "[long_block_name_12345678901234567890123456789012345678901234567890]"
+ ```
+
+ Do not call these blocks directly.
+ ```bash :long_block_name_12345678901234567890123456789012345678901234567890
+ echo '2'
+ ```
+ ```bash :(long_block_name_12345678901234567890123456789012345678901234567890)
+ echo '3'
+ ```
+ ```bash :[long_block_name_12345678901234567890123456789012345678901234567890]
+ echo '4'
+ ```
+
Block names with all chars.
/ UTF-8
/ !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
/ ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ
::: Click below to trigger. If it prints "Success", the Link block was processed.
@@ -23,5 +47,16 @@
file: examples/linked2.md
block: show_vars
vars:
page2_var_via_environment: for_page2_from_page1_via_current_environment
```
+The hidden block "(success)" is required above. It prints "Success".
+```bash :(success)
+echo "Success"
+```
+
+```opts :(document_options)
+execute_in_own_window: false
+output_execution_report: false
+output_execution_summary: false
+pause_after_script_execution: true
+```