And then I found it's barely reasonable to run Windows batch files from 9pm rc.
Despite rc using Windows path syntax, changes to $path made in rc don't get
propagated to the batch file. Also, rc doesn't find batch files in the path.
*And* I can't remember why I started trying to use 9pm! I
Not an important subject, I have other tools, but just in case anyone knows,
how do you write scripts for 9pm?
On Fri, Jan 25, 2019, at 11:11 PM, Ethan Gardener wrote:
> 9pm rc is a bit
> broken anyway. There doesn't seem to be a way to make an executable
> script
I set $path wrong, 9pm uses
I'm messing around with /sys/src/9/port/sysproc.c and I may have
distorted it beyond recovery, but I have a feeling this problem isn't
of my own making.
I have:
; cat /bin/ll
#!/bin/ls -l
;
If I invoke ll
; ll
--rwxrwxr-x M 9 lucio lucio 13 Jan 31 09:30
See exec(2):
For a file beginning #!, the arguments passed to the program
(/bin/rc in the example above) will be the name of the file
being executed, any arguments on the #! line, the name of
the file again, and finally the second and subsequent argu-
See exec(2):
For a file beginning #!, the arguments passed to the program
(/bin/rc in the example above) will be the name of the file
being executed, any arguments on the #! line, the name of
the file again, and finally the second and subsequent argu-
