Skip to content

snippets: shell parameter expansion syntax conflicts with snippet placeholders #24

@AndrewDDavis

Description

@AndrewDDavis

The syntax for snippet placeholders is identical to some shell parameter expansions of the positional arguments in a script. If you want to put such shell expansions in a snippet, the snippet is mangled when it's inserted.

Fixed in PR #23, which allows shell snippets to have an escape syntax like ${\1:?message} to produce ${1:?message} when the snippet is inserted. Other common shell expansions work too, like ${\1:-default} and ${\1:+alt-txt}.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions