>> 4. to recall commands typed in an rc session without resorting to the >> middle mouse button (snarf+paste)? > > russ has to useful scripts " and "" one prints the last comand the other > executes it. what they do is grepping /dev/text > >> 5. to make rc auto-scroll for programs that output many pages of text, e. >> g. a du on a deep directory tree, and to not block them after a single >> page? > > middle click, "scroll"
one important difference that may be missed here is that unlike linux, the shell is not responsible for either of these behaviors. rio and acme are the two programs that link against libcomplete thus, when running on the console, there is no completion available. there is a version of rc with research unix-style history. /n/sources/contrib/quanstro/futharc.tgz. it works by saving parsed commands to a file designated by $history. the program history.c can be compiled as - and -p so that "-p x" would print the last command x executed in any window; "- x" would repeat that command. "grep x $history" would search history. > 7. to make rc auto-complete commands and not only file/directory names? > > different OS & paradigm == different behavior again, rc isn't doing the completion. rio/acme don't know what the commands might be. this is why tab is not the completion key. it would be inconvient to be disallowed typing tab in any program (save sam). - erik
