fish-shell - user-friendly command line shell

	Commit message (Collapse)	Author	Age
*	Don't stop job execution on wildcard errors	Kevin Ballard	2014-10-13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Wildcard errors are only reported interactively, and they're also not really errors. Commands with multiple wildcards would in fact continue executing if at least one wildcard matched, which is quite surprising. But they would report an error if there is only one wildcard in the arguments list and the wildcard has no match, even if there are other remaining arguments. Given this inconsistency, and given that sh does not stop execution if a wildcard fails to match, it seems better to allow execution to continue. This is better from a scripting perspective anyway, as it means constructs like `set -l paths foo/*.txt` will actually create the variable (with an empty value) instead of skipping the `set` altogether and perhaps causing subsequent code to read or modify a global or universal variable.
*	Fix for issue where comments are lost in function definitions	ridiculousfish	2014-09-27
\| \| \| \|	Fixes #1710
*	Do not continue execution if argument expansion fails. Fixes #1488	ridiculousfish	2014-05-31
\|
*	Run restyle.sh to enforce style rules.	ridiculousfish	2014-03-31
\|
*	Excise use of parser_t's error() functionality. Thread a	ridiculousfish	2014-03-21
\| \| \| \| \| \|	parse_error_list_t through all of the expand functions, enabling them to report errors more directly. Improve aspects of error reporting for expansion failures.
*	Rewrite parser_t::current_line() to respect new parser	ridiculousfish	2014-03-20
\|
*	Fix line number reporting in new parser	ridiculousfish	2014-03-20
\|
*	Implement status -n (line number) with new parser	ridiculousfish	2014-03-01
\|
*	Partially rework profiling. Fix profiling crash with new parser. Fixes	ridiculousfish	2014-02-09
\| \| \| \|	1295
*	Update style and formatting to conform to fish style guide.	ridiculousfish	2014-01-15
\|
*	Support for "simple block" optimization, where we can run blocks	ridiculousfish	2014-01-07
\| \| \| \|	directly if there are no arguments or redirections to the block itself
*	Support for stack overflow and infinite recursion detection in new	ridiculousfish	2014-01-01
\| \| \| \|	parser
*	Further improvements to error reporting with new parser	ridiculousfish	2014-01-01
\|
*	Clean up and rationalize error handling in parse_execution.cpp	ridiculousfish	2013-12-31
\|
*	Support for implicit cd, no-exec, and the exit builtin. All tests now	ridiculousfish	2013-12-29
\| \| \| \|	pass (!). Error reporting still unsteady.
*	Make eval_node_at_offset return an error indication instead of the exit	ridiculousfish	2013-12-28
\| \| \| \|	status of the last command
*	Fix issues related to redirections and block level IO with new parser	ridiculousfish	2013-12-28
\|
*	Hook up for statements, if statements, and function definition in new	ridiculousfish	2013-12-27
\| \| \| \|	parser
*	Facilities for turning on new AST-based parser.	ridiculousfish	2013-12-26
\|
*	Cleanup thrashing around in parser_t. New parser execution lives in	ridiculousfish	2013-12-26
\| \| \| \|	parse_execution.cpp
*	New ideas about how to use new parser for execution. Beginnings of	ridiculousfish	2013-12-26
\| \| \| \|	implementation.
*	Factor execution aspects from parser_t to parse_execution_context_t .	ridiculousfish	2013-12-24
	Still searching for best way to use new parser for execution.