fish-shell/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(plain_statement)
ELEM(argument_list)
ELEM(arguments_or_redirections_list)
ELEM(argument)
ELEM(redirection)
ELEM(optional_background)
ELEM(optional_newlines)
ELEM(end_command)
ELEM(freestanding_argument_list)
#undef ELEM
Add grammar in type system 2018-01-08 05: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-03 10: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-02 05: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-02 10:30:48 +08:00			`ELEM(job_conjunction_continuation)`
Add grammar in type system 2018-01-08 05: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-03 10:09:16 +08:00			`ELEM(not_statement)`
Add grammar in type system 2018-01-08 05:34:04 +08:00			`ELEM(andor_job_list)`
			`ELEM(decorated_statement)`
			`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-19 06:37:44 +08:00			`ELEM(optional_newlines)`
Add grammar in type system 2018-01-08 05:34:04 +08:00			`ELEM(end_command)`
			`ELEM(freestanding_argument_list)`
			`#undef ELEM`