Default Bash;

Should work fine on the command line.

 Default will be generating bash command sequences.  It appears like pass through to default, but bash can leave a residue on args list and bash can update the console symbol table;

We have sequences like:
Default
i=3;
while(i){ i--;
bash function1 sequence;
function2 sequence;  # note, we do not repeat bash each statement
exit; #  this is some sort of bash exit
}
# still in default.


The Default will defer the syntax position to bash as a terminal in a Default expression tree, and default expressions include valid liinux command sequences.  Console loop has manageable pointers that set a heap pointer in args list and overlap is eliminated. Most of the syntax engines will adapt, it is a few lines of code. Typically we might see:

Default;
names = ./xchars;  # setting the set selection anchor

{ # then all the xchars entry points
# act like built ins and get short look ups.
NewWin, NewGC,...
including
XCBind; # the new all binary interface to xcb
}
exit; # default exits

 The cost of default is a validation routine that checks for default syntax, and otherwise passes, a filter.  But that is OK, Default can exit, any nested syntax can reserve args list space on its own, and the symbol table retains state.   This is all doable, as long as the engines and snippets know to unfold, fold, then  exit, and restart. In other words, emulate the control C key to back up one node on the total expression tree, that is built in to args, like a stack fix up.