Skip to content

Escaped whitespace is treated as as whitespace, rather than literals #284

Open
@Xophmeister

Description

@Xophmeister

The grammar, as of d1a1a3f, swallows any escaped horizontal whitespace, treating them as actual whitespace rather than literals. For example:

# This should output:
# <x>
# < >
# <	>
# <x>
printf "<%s>\n" x \  \	 x

The parse tree for the above looks like this:

program [0, 0] - [1, 0]
  command [0, 0] - [0, 25]
    name: command_name [0, 0] - [0, 6]
      word [0, 0] - [0, 6]
    argument: string [0, 7] - [0, 15]
      string_content [0, 8] - [0, 14]
    argument: word [0, 16] - [0, 17]
    argument: word [0, 24] - [0, 25]

We see only three arguments -- the printf format string and the two xs -- rather than five, including the escaped space and tab between the xs.

Whitespace literals are semantically different from whitespace used in tokenisation. For example:

echo \ # this is not a comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions