Acme.exe is the same (mostly) as emu(1) so the command line arguments
are the same (except for -I). Acme.exe reads the EMU environment
variable for options first, then processes the command line options.
If no dis command is given on the command line to Acme.exe then the
default command is 'sh -l', see sh(1). The -l option will cause the
shell to run as a login shell, which means it first runs the file
/lib/sh/profile, and then lib/profile if that file exists.
/lib/sh/profile is mostly concerned with making sure a home directory
exists for the current user, then changing to that directory, so the
lib/profile in that users directory will be run.
it is your $home/lib/profile where most of the action is. It sets up
various things, namespace, factotum, environment variables (e.g. for
fonts), and finally it launches acme.
If you want to change the arguments that start the actual acme editor
then edit your $home/lib/profile.
If you want to change the command line arguments the Acme.exe, the
emulator, then either modify EMU environment var, or on Nt create a
shortcut, modify its properties changing the command line with the
options you want.
I don't know about an -r option to acme. Its not there on acme-sac.
Caerwyn
Is there a solution floating around?
For what it's worth, I'm most of the way through enough automation
(through MS's PowerShell) to be able to drive a real debugger out of
Acme. It won't be acid, but it will (incrementally) handle most of
my tasks.
Thanks,
Paul