Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Artifact ID: | c7db0d51caac1a5cba2218f595f3871dd744eb57 |
---|---|
Page Name: | InteractiveShell |
Date: | 2017-08-14 17:23:16 |
Original User: | yumaikas |
Mimetype: | text/x-markdown |
Parent: | ee2f11b8fa5d7428e491bef218c1c84d74f0c071 |
Content
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,|
and&&
could also be used for pipelines and chains?.
could be a shortand for .execVet with shell users?
cd ".." .
grep -n 5 <-A 5<-B "pattern" "filepath" .