Skip to content

Commit 2b45f39

Browse files
authored
Docs: Specify that NXF_SYNTAX_PARSER is an environment variable (#5901)
Not totally clear, especially as other feature toggles use things like nextflow.enable within scripts. Better to be explicit. Signed-off-by: Phil Ewels <[email protected]>
1 parent 39f3c05 commit 2b45f39

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/updating-syntax.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If you are still using DSL1, see {ref}`dsl1-page` to learn how to migrate your N
1313
## Preparing for strict syntax
1414

1515
:::{versionadded} 25.02.0-edge
16-
The strict syntax can be enabled in Nextflow by setting `NXF_SYNTAX_PARSER=v2`.
16+
The strict syntax can be enabled in Nextflow by setting the environment variable `NXF_SYNTAX_PARSER=v2`.
1717
:::
1818

1919
The strict syntax is a subset of DSL2. While DSL2 allows any Groovy syntax, the strict syntax allows only a subset of Groovy syntax for Nextflow scripts and config files. This new specification enables more specific error reporting, ensures more consistent code, and will allow the Nextflow language to evolve independently of Groovy.
@@ -496,7 +496,7 @@ The process `shell` section is deprecated. Use the `script` block instead. The V
496496
### Configuration syntax
497497

498498
:::{versionadded} 25.02.0-edge
499-
The strict config syntax can be enabled in Nextflow by setting `NXF_SYNTAX_PARSER=v2`.
499+
The strict config syntax can be enabled in Nextflow by setting the environment variable `NXF_SYNTAX_PARSER=v2`.
500500
:::
501501

502502
See {ref}`Configuration <config-syntax>` for a comprehensive description of the configuration language.

0 commit comments

Comments
 (0)