From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: [9fans] Scripts in 9pm
Date: Sat, 26 Jan 2019 13:23:08 +0000 [thread overview]
Message-ID: <1548508988.474626.1644046040.52A10C14@webmail.messagingengine.com> (raw)
In-Reply-To: <1548457862.289354.1643744416.5CA9302E@webmail.messagingengine.com>
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 Windows convention, but fixing it didn't help.
% pwd; echo $path
C:/Users/aGeek_Second_User/prog/9/rc
C:/Users/aGeek_Second_User/prog/9/rc;[snip]
% cat lc
#!C:/Users/aGeek_Second_User/prog/9/9pm/bin/rcsh.exe
ls -Fp $* | mc
# verified path correct, shouldn't use a / at start, but it still won't run.
% lc
lc: file not found
% ./lc
./lc: file not found
% cp lc lc.rc
% lc
lc: file not found
% lc.rc
lc.rc: windows error 193
% ./lc.rc
./lc.rc: windows error 193
% touch foo.exe
% ./foo
./foo: windows error 193
193 evidently means invalid executable.
File permissions include execution, both ls -l and Windows file properties show that.
next prev parent reply other threads:[~2019-01-26 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 21:39 [9fans] Rc port Federico Benavento
2019-01-23 21:57 ` Calvin Morrison
2019-01-23 21:59 ` Federico Benavento
2019-01-23 22:11 ` Calvin Morrison
2019-01-23 22:32 ` Federico Benavento
2019-01-24 16:23 ` Federico Benavento
2019-01-24 14:31 ` Stuart Morrow
2019-01-24 16:13 ` erik quanstrom
2019-01-25 15:13 ` Stuart Morrow
2019-01-25 16:02 ` erik quanstrom
2019-01-25 23:11 ` Ethan Gardener
2019-01-26 13:23 ` Ethan Gardener [this message]
2019-01-26 14:09 ` [9fans] Scripts in 9pm Ethan Gardener
2019-01-24 3:01 ` [9fans] Rc port Mayuresh Kathe
2019-01-24 16:25 ` Federico Benavento
2019-01-24 16:32 ` Federico Benavento
2019-01-24 16:54 ` Mayuresh Kathe
2019-01-25 14:49 ` Stuart Morrow
2019-01-28 15:22 ` arnold
2019-01-30 16:02 ` Federico Benavento
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1548508988.474626.1644046040.52A10C14@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).