We used to use the lformat option of the list command to generate temporary scripts working on a set of files. I had written an 'expand' command which would do ENV var expansion and globbing (if I am remembering correctly - it was a while ago :) ).
AmigaDOS taught me so much about computing. For whatever reason I was drawn to using Ed for writing C on the Amiga, which prepared me for vi later on. And the fact that AmigaDOS was a preemptive multitasking OS got me thinking about race conditions between tasks early on. I still fondly recall spending many hours with a debugger disassembling code in the ROM to better learn how things worked. I even ended up writing my own version of exec.library later on that ran in real mode on x86 (with preemptive task switching) along with a few device drivers for the serial port, console and floppy. Ah, the good times learning how to program as a kid!
Nice, I don't remember this!
We used to use the lformat option of the list command to generate temporary scripts working on a set of files. I had written an 'expand' command which would do ENV var expansion and globbing (if I am remembering correctly - it was a while ago :) ).
AmigaDOS taught me so much about computing. For whatever reason I was drawn to using Ed for writing C on the Amiga, which prepared me for vi later on. And the fact that AmigaDOS was a preemptive multitasking OS got me thinking about race conditions between tasks early on. I still fondly recall spending many hours with a debugger disassembling code in the ROM to better learn how things worked. I even ended up writing my own version of exec.library later on that ran in real mode on x86 (with preemptive task switching) along with a few device drivers for the serial port, console and floppy. Ah, the good times learning how to program as a kid!
> the parser for shell scripts, or sequence files as they're called in TRIPOS
I didn't know that was the official name. Hence the startup-sequence.