Some thoughts on designing a shell experience for PISC
- Most shells flow in a cmd args fasion, but doing this in PISC is difficult, unless some sort of delimiter is used
- Having a delimiter that is forced makes for a very interesting oppurtunity to have an interactive/exploratory shell line for dealing with flags that are usually arcane, by exposing what options have already been set in the stack display.
.seems like a natural delimiter for this,
&&could also be used for pipelines and chains?
.could be a shortand for .exec
Vet with shell users?
cd ".." .
grep -n 5 <-A 5<-B "pattern" "filepath" .