Skip to content

env with -S (string split) breaks code highlighting #83

@onedr0p

Description

@onedr0p

Hi 👋

I would like to condense my shell invocations from two lines to one, however I lose syntax highlighting when I try the example below:

test1:
    #!/usr/bin/env -S bash -Eeuo pipefail
    echo "Highlighting does not work"

test2: 
    #!/usr/bin/env bash
    set -Eeuo pipefail
    echo "Highlighting does work"

test3:
    #!/usr/bin/env bash -Eeuo pipefail
    echo "Highlighting does work but not sure if this is considered best practice"

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions