LSH, Version 1.10 Update August 25, 1991 FIXED LOG VERSION There is now a separate version of LSH which uses a fixed size history file. Its purpose is to speed up operation on floppy disks, or even hard disks, by allowing you to place the history file on the outer disk tracks (i.e. it will be one of the first files on the disk) and know that it will STAY there. The Variable Log version keeps adding to the history indefinitely, so you will eventually end up reading from the inner tracks. A new history file, or an old one which is shorter than the nominal length, is padded to the full size. When the history is full, only the end of the file is written to disk. You lose the first command lines. The file size is installed with LSHINST. The distributed version reserves 4k, but 2k may be all you need. CAUTION: If you edit a history file independently, the text editor will probably truncate it. However, if LSH runs immediately afterward, it will pad the file back out to its reserved length when you execute the next command. COMMAND COMPLETION Idea taken from PCED: When completing the first token on the line, only .COM types are matched (along the path), and a trailing space is appended. Then you are immediately ready to add command arguments. For example: c cl crunch then... crunch f crunch foo.com crunch foo.z80 Command Complete now recognizes "=" and "," as token separators, so it works on argument lists and for CP, REN, etc. It also now handles lines starting with ":" or "." to force search of current directory on first token. LINE SEQUENCING A review of old messages about LSH reminded me that someone wanted the automatic line sequencing command to return to the same line rather than go to the next line. LSHINST can now configure that choice. It cannot be toggled within LSH. SINGLE INVOCATION The command line now has a /C option to run LSH once. This is a convenience when you want to dig up an old command line, but don't want the shell running. USER ROUTINE A small user's routine can be installed in a 32 byte patch area. The code there is run when the User Patch key is pressed. The patch must end with RET if LSH is to keep running. All registers are available for your use. Code can be assembled to an object file and overlayed on LSH with BCOMP. The patch area is surrounded by "USR> ..patch..