src/parse_grammar_elements.inc

// Define ELEM before including this file.
ELEM(job_list)
ELEM(job)
ELEM(job_decorator)
ELEM(job_conjunction)
ELEM(job_conjunction_continuation)
ELEM(job_continuation)
ELEM(statement)
ELEM(if_statement)
ELEM(if_clause)
ELEM(else_clause)
ELEM(else_continuation)
ELEM(switch_statement)
ELEM(case_item_list)
ELEM(case_item)
ELEM(block_statement)
ELEM(block_header)
ELEM(for_header)
ELEM(while_header)
ELEM(begin_header)
ELEM(function_header)
ELEM(not_statement)
ELEM(andor_job_list)
ELEM(decorated_statement)
ELEM(variable_assignment)
ELEM(variable_assignments)
ELEM(plain_statement)
ELEM(argument_list)
ELEM(arguments_or_redirections_list)
ELEM(argument)
ELEM(redirection)
ELEM(optional_background)
ELEM(optional_newlines)
ELEM(optional_time)
ELEM(end_command)
ELEM(freestanding_argument_list)
#undef ELEM
Add grammar in type system 2018-01-07 13:34:04 -08:00			`// Define ELEM before including this file.`
			`ELEM(job_list)`
			`ELEM(job)`
Rework 'and' and 'or' to be "job decorators" This promotes "and" and "or" from a type of statement to "job decorators," as a possible prefix on a job. The point is to rationalize how they interact with && and \|\|. In the new world 'and' and 'or' apply to a entire job conjunction, i.e. they have "lower precedence." Example: if [ $age -ge 0 ] && [ $age -le 18 ] or [ $age -ge 75 ] && [ $age -le 100 ] echo "Child or senior" end 2018-03-02 18:09:16 -08:00			`ELEM(job_decorator)`
Add && and \|\| to fish grammar This teaches the parser about && and \|\|, implemented via a new production "job_conjunction". These do not yet have execution support. 2018-03-01 13:39:39 -08:00			`ELEM(job_conjunction)`
Implement execution of && and \|\| This adds support for basic constructs. if and while is not yet supported. 2018-03-01 18:30:48 -08:00			`ELEM(job_conjunction_continuation)`
Add grammar in type system 2018-01-07 13:34:04 -08:00			`ELEM(job_continuation)`
			`ELEM(statement)`
			`ELEM(if_statement)`
			`ELEM(if_clause)`
			`ELEM(else_clause)`
			`ELEM(else_continuation)`
			`ELEM(switch_statement)`
			`ELEM(case_item_list)`
			`ELEM(case_item)`
			`ELEM(block_statement)`
			`ELEM(block_header)`
			`ELEM(for_header)`
			`ELEM(while_header)`
			`ELEM(begin_header)`
			`ELEM(function_header)`
Rework 'and' and 'or' to be "job decorators" This promotes "and" and "or" from a type of statement to "job decorators," as a possible prefix on a job. The point is to rationalize how they interact with && and \|\|. In the new world 'and' and 'or' apply to a entire job conjunction, i.e. they have "lower precedence." Example: if [ $age -ge 0 ] && [ $age -le 18 ] or [ $age -ge 75 ] && [ $age -le 100 ] echo "Child or senior" end 2018-03-02 18:09:16 -08:00			`ELEM(not_statement)`
Add grammar in type system 2018-01-07 13:34:04 -08:00			`ELEM(andor_job_list)`
			`ELEM(decorated_statement)`
Support FOO=bar syntax for passing variables to individual commands This adds initial support for statements with prefixed variable assignments. Statments like this are supported: a=1 b=$a echo $b # outputs 1 Just like in other shells, the left-hand side of each assignment must be a valid variable identifier (no quoting/escaping). Array indexing (PATH[1]=/bin ls $PATH) is not yet supported, but can be added fairly easily. The right hand side may be any valid string token, like a command substitution, or a brace expansion. Since `a=* foo` is equivalent to `begin set -lx a ; foo; end`, the assignment, like `set`, uses nullglob behavior, e.g. below command can safely be used to check if a directory is empty. x=/nothing/{,.} test (count $x) -eq 0 Generic file completion is done after the equal sign, so for example pressing tab after something like `HOME=/` completes files in the root directory Subcommand completion works, so something like `GIT_DIR=repo.git and command git ` correctly calls git completions (but the git completion does not use the variable as of now). The variable assignment is highlighted like an argument. Closes #6048 2019-10-23 03:13:29 +02:00			`ELEM(variable_assignment)`
			`ELEM(variable_assignments)`
Add grammar in type system 2018-01-07 13:34:04 -08:00			`ELEM(plain_statement)`
			`ELEM(argument_list)`
			`ELEM(arguments_or_redirections_list)`
			`ELEM(argument)`
			`ELEM(redirection)`
			`ELEM(optional_background)`
Reflect newlines after pipes in fish grammar The previous attempt to support newlines after pipes changed the lexer to swallow newlines after encountering a pipe. This has two problems that are difficult to fix: 1. comments cannot be placed after the pipe 2. fish_indent won't know about the newlines, so it will erase them Address these problems by removing the lexer behavior, and replacing it with a new parser symbol "optional_newlines" allowing the newlines to be reflected directly in the fish grammar. 2018-02-18 14:37:44 -08:00			`ELEM(optional_newlines)`
Make "time" a job prefix In particular, this allows `true && time true`, or `true; and time true`, and both `time not true` as well as `not time true` (like bash). time is valid only as job _prefix_, so `true \| time true` could call `/bin/time` (same in bash) See discussion in #6442 2019-12-21 11:45:07 +01:00			`ELEM(optional_time)`
Add grammar in type system 2018-01-07 13:34:04 -08:00			`ELEM(end_command)`
			`ELEM(freestanding_argument_list)`
			`#undef ELEM`