[9fans] Rc port.

[9fans] Rc port.

[Federico Benavento]

Hola,

I just uploaded a standalone unix (only tested on macOS/Linux) port with edit, history and completion support to GitHub.
I have been using it as my primary shell for months on macOS and it’s seems to be working pretty well.

https://github.com/benavento/rc

Have fun.
—-
Federico G. Benavento
benavento@gmail.com

Re: [9fans] Rc port.

[Calvin Morrison]

On Thu, 24 Jan 2019 at 08:41, Federico Benavento <benavento@gmail.com> wrote:
>
> Hola,
>
> I just uploaded a standalone unix (only tested on macOS/Linux) port with edit, history and completion support to GitHub.
> I have been using it as my primary shell for months on macOS and it’s seems to be working pretty well.

rc is a great shell. It's interface just isn't optimal with a fake TTY
like we use on linux. I think the merits of the shell outweigh that.
I've been using rlwrapper for a while which gives me command history
and thats nice, but completion will be cool too!

btw could'nt get it to compile without adding

diff --git a/unix.c b/unix.c
index 5c89243..1f88f69 100644
--- a/unix.c
+++ b/unix.c
@@ -11,6 +11,7 @@
 #include <errno.h>
 #include <sys/stat.h>
 #include <sys/types.h>
+#include <sys/wait.h>
 #include <dirent.h>
 #include <assert.h>

Re: [9fans] Rc port.

[Federico Benavento]

 I’ve been able to survive quite well on a regular Mac terminal with it.
Thanks for trying it.

> On Jan 23, 2019, at 6:57 PM, Calvin Morrison <mutantturkey@gmail.com> wrote:
> 
> On Thu, 24 Jan 2019 at 08:41, Federico Benavento <benavento@gmail.com> wrote:
>> 
>> Hola,
>> 
>> I just uploaded a standalone unix (only tested on macOS/Linux) port with edit, history and completion support to GitHub.
>> I have been using it as my primary shell for months on macOS and it’s seems to be working pretty well.
> 
> rc is a great shell. It's interface just isn't optimal with a fake TTY
> like we use on linux. I think the merits of the shell outweigh that.
> I've been using rlwrapper for a while which gives me command history
> and thats nice, but completion will be cool too!
> 
> btw could'nt get it to compile without adding
> 
> diff --git a/unix.c b/unix.c
> index 5c89243..1f88f69 100644
> --- a/unix.c
> +++ b/unix.c
> @@ -11,6 +11,7 @@
> #include <errno.h>
> #include <sys/stat.h>
> #include <sys/types.h>
> +#include <sys/wait.h>
> #include <dirent.h>
> #include <assert.h>
> 

—-
Federico G. Benavento
benavento@gmail.com

Re: [9fans] Rc port.

[Calvin Morrison]

On Thu, 24 Jan 2019 at 09:00, Federico Benavento <benavento@gmail.com> wrote:
>
>  I’ve been able to survive quite well on a regular Mac terminal with it.
> Thanks for trying it.
>

feature i would ove: something equiv to a PS1 line so i know what
folder i'm in. Can I do that with $prompt?

Calvin.

Re: [9fans] Rc port.

[Federico Benavento]

Yes, you can, I think I even set the title of the terminal window when I cd. I’m not at home now, i’ll post my rcrc once I get a chance.

> On 23 Jan 2019, at 19:11, Calvin Morrison <mutantturkey@gmail.com> wrote:
> 
> feature i would ove: something equiv to a PS1 line so i know what
> folder i'm in. Can I do that with $prompt?

Re: [9fans] Rc port.

[Federico Benavento]

Here, this is what I have.

fn setprompt {
	# delete old function
	fn $ps1
	PWD=`{pwd}
	ps1='['^$sysname^':'^`{basename $PWD}^']%'
	prompt=($ps1^' ' '	')
	fn $ps1 { if(! ~ $#* 0) $* }

	# macOS Terminal Title
	printf '\033]7;%s\007'	file://^`{hostname}^$PWD
}

fn cd {
	builtin cd $* &&
	setprompt
}



> On Jan 23, 2019, at 7:32 PM, Federico Benavento <benavento@gmail.com> wrote:
> 
> Yes, you can, I think I even set the title of the terminal window when I cd. I’m not at home now, i’ll post my rcrc once I get a chance.
> 
>> On 23 Jan 2019, at 19:11, Calvin Morrison <mutantturkey@gmail.com> wrote:
>> 
>> feature i would ove: something equiv to a PS1 line so i know what
>> folder i'm in. Can I do that with $prompt?

—-
Federico G. Benavento
benavento@gmail.com

Re: [9fans] Rc port.

[Stuart Morrow]

> feature i would ove: something equiv to a PS1 line so i know what
> folder i'm in. Can I do that with $prompt?

IIRC, with es you can get persistent history, and control your prompts
with arbitrarily complex logic, all without building stuff into
/bin/es. You can do it with es code in esmain or your user profile
(Again, IIRC.)

I might have imagined that, but I'm even more sure you can set it up
so that if a first refers to a directory, then it's the same as cd
that directory. So a prompt could be

/place;

and you can click and resend the whole thing and the result is it goes
to /place for you (then does the stuff after the semicolon).

Finally, I'm most sure of all that if the above is correct then you
can also make it so that

/place {

is the prompt and it executes the actual command only if the /place is
successful. You'd have to finish off all your commands with a },
though...

-Morrow

Re: [9fans] Rc port.

[erik quanstrom]

[-- Attachment #1: Type: text/html, Size: 457 bytes --]

Re: [9fans] Rc port.

[Stuart Morrow]

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

I take back the stuff where a directory can be a command  - it interacts weird with $path:
you’d do `..’ thinking it’s the same as `cd ..’, except it’s actually `cd /bin/..’.

> is there a buildable version of es any longer?

I just found
	http://wryun.github.io/es-shell/

I’ve never actually used es, this or any other version; this is the first I’ve heard you
couldn’t just use the original.

Hey, does anybody know if Tom Duff really invented process substitution? ( <{} )
There’s a comment in ‘A Retrospective’ (1978, I think - it’s in the 1978 BSTJ edition
`UNIX Time-Sharing System’; I have a tenth-anniversary reprint called ‘UNIX System
Readings And Applications’) by Dennis Ritchie about how a syntax for non-linear
pipelines has already been proposed. /dev/fd wouldn’t have existed yet, so does
anybody know what he’s referring to here?

Whoever it was, I bet it was Doug.

-Morrow


[-- Attachment #2: Type: text/html, Size: 7096 bytes --]

Re: [9fans] Rc port.

[erik quanstrom]

[-- Attachment #1: Type: text/html, Size: 1693 bytes --]

Re: [9fans] Rc port.

[Ethan Gardener]

On Wed, Jan 23, 2019, at 9:59 PM, Federico Benavento wrote:
>  I’ve been able to survive quite well on a regular Mac terminal with it.

I remember thinking regular rc was tolerable on a Mac terminal thanks to the terminal copy/pasting with normal keybindings, but this would be better.

I've been trying 9pm a little bit; found Windows command window handles command history.  It doesn't handle completion though.  9pm rc is a bit broken anyway.  There doesn't seem to be a way to make an executable script, and rc crashes on startup if it would inherit functions.  I just thought about trying to build es or your rc in MinGW, but I'm lazy and have AcmeSAC.

[9fans] Scripts in 9pm

[Ethan Gardener]

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.

Re: [9fans] Scripts in 9pm

[Ethan Gardener]

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 do like the black and white Sam, but the lack of support for even left and right arrow keys is not fun at all.  After using Acme SAC for a while, I've found myself trying to use up and down arrows too.  I'm going soft.

Re: [9fans] Rc port.

[Mayuresh Kathe]

On 2019-01-24 03:09 AM, Federico Benavento wrote:
> Hola,
> 
> I just uploaded a standalone unix (only tested on macOS/Linux) port
> with edit, history and completion support to GitHub.
> I have been using it as my primary shell for months on macOS and it’s
> seems to be working pretty well.

not undermining your efforts, but isn't a port of "rc" a part of 
plan9ports?

~mayuresh

Re: [9fans] Rc port.

[Federico Benavento]

I just wanted the shell, not the whole thing, it’s a port, because I started from the copy in /sys/src/cmd/,
I didn’t want to use es either.

> On Jan 24, 2019, at 12:01 AM, Mayuresh Kathe <mayuresh@kathe.in> wrote:
> 
> On 2019-01-24 03:09 AM, Federico Benavento wrote:
>> Hola,
>> I just uploaded a standalone unix (only tested on macOS/Linux) port
>> with edit, history and completion support to GitHub.
>> I have been using it as my primary shell for months on macOS and it’s
>> seems to be working pretty well.
> 
> not undermining your efforts, but isn't a port of "rc" a part of plan9ports?
> 
> ~mayuresh
> 

—-
Federico G. Benavento
benavento@gmail.com

Re: [9fans] Rc port.

[Federico Benavento]

Oh, maybe it wasn’t so obvious, but this copy has edit, history and completion which can be customized by defining a fn complete{} function.

> On Jan 24, 2019, at 1:25 PM, Federico Benavento <benavento@gmail.com> wrote:
> 
> I just wanted the shell, not the whole thing, it’s a port, because I started from the copy in /sys/src/cmd/,
> I didn’t want to use es either.
> 
>> On Jan 24, 2019, at 12:01 AM, Mayuresh Kathe <mayuresh@kathe.in> wrote:
>> 
>> On 2019-01-24 03:09 AM, Federico Benavento wrote:
>>> Hola,
>>> I just uploaded a standalone unix (only tested on macOS/Linux) port
>>> with edit, history and completion support to GitHub.
>>> I have been using it as my primary shell for months on macOS and it’s
>>> seems to be working pretty well.
>> 
>> not undermining your efforts, but isn't a port of "rc" a part of plan9ports?
>> 
>> ~mayuresh
>> 
> 
> —-
> Federico G. Benavento
> benavento@gmail.com
> 
> 
> 
> 

—-
Federico G. Benavento
benavento@gmail.com

Re: [9fans] Rc port.

[Mayuresh Kathe]

okay, in that case, would you be in a position to add-in the excellent 
enhancements you made to your copy to the "rc" in plan9port?

On 2019-01-24 10:02 PM, Federico Benavento wrote:
> Oh, maybe it wasn’t so obvious, but this copy has edit, history and
> completion which can be customized by defining a fn complete{}
> function.
> 
>> On Jan 24, 2019, at 1:25 PM, Federico Benavento <benavento@gmail.com> 
>> wrote:
>> 
>> I just wanted the shell, not the whole thing, it’s a port, because I 
>> started from the copy in /sys/src/cmd/,
>> I didn’t want to use es either.
>> 
>>> On Jan 24, 2019, at 12:01 AM, Mayuresh Kathe <mayuresh@kathe.in> 
>>> wrote:
>>> 
>>> On 2019-01-24 03:09 AM, Federico Benavento wrote:
>>>> Hola,
>>>> I just uploaded a standalone unix (only tested on macOS/Linux) port
>>>> with edit, history and completion support to GitHub.
>>>> I have been using it as my primary shell for months on macOS and 
>>>> it’s
>>>> seems to be working pretty well.
>>> 
>>> not undermining your efforts, but isn't a port of "rc" a part of 
>>> plan9ports?

Re: [9fans] Rc port.

[Stuart Morrow]

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

> I just wanted the shell, not the whole thing

You should post it to suckless.  I recall a thread years ago discussing what
the ‘official’ shell of the suckless project ought to be.  Rc went completely
unmentioned for at least about half of the thread, although they can’t
possibly have been unaware of it... They either want to avoid p9p as a
dependency, or else can’t live without the usual interactive features
of Linux shells.

Now they have no excuse.

As long as we’re discussing Linux stuff in shells, I think the new shell
mpsh[1] has a neat way to set prompt, neat because the mechanism
can also be used to do those variables like OLDPWD that /bin/bash has
built-in knowledge of.
(I wonder what the security implications might be.)

[1] https://www.cca.org/mpsh/docs-05.html

-Morrow


[-- Attachment #2: Type: text/html, Size: 7546 bytes --]

Re: [9fans] Rc port.

[arnold]

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

Federico Benavento <benavento@gmail.com> wrote:

> Hola,
>
> I just uploaded a standalone unix (only tested on macOS/Linux) port with edit, history and completion support to GitHub.
> I have been using it as my primary shell for months on macOS and it???s seems to be working pretty well.
>
> https://github.com/benavento/rc
>
> Have fun.
> ???-
> Federico G. Benavento
> benavento@gmail.com

On Ubuntu 18.04, doing make, I get errors on several files. See attached.

Thanks,

Arnold

[-- Attachment #2: ERRS --]
[-- Type: application/octet-stream, Size: 2809 bytes --]

cc  -g -Wall -Wextra -Wno-parentheses -Wno-missing-braces -Wno-missing-field-initializers  -Wno-comment -Wno-sign-compare -Wno-unused-parameter -Werror -DPREFIX=\"/usr/local\" -c lex.c
lex.c: In function ‘yylex’:
lex.c:225:5: error: this statement may fall through [-Werror=implicit-fallthrough=]
   if(nextis(c)){
     ^
lex.c:230:2: note: here
  case '<':
  ^~~~
cc1: all warnings being treated as errors
Makefile:40: recipe for target 'lex.o' failed
make: *** [lex.o] Error 1
cc  -g -Wall -Wextra -Wno-parentheses -Wno-missing-braces -Wno-missing-field-initializers  -Wno-comment -Wno-sign-compare -Wno-unused-parameter -Werror -DPREFIX=\"/usr/local\" -c pcmd.c
pcmd.c: In function ‘pcmd’:
pcmd.c:111:4: error: this statement may fall through [-Werror=implicit-fallthrough=]
    pchr(f, '<');
    ^~~~~~~~~~~~
pcmd.c:112:3: note: here
   case READ:
   ^~~~
pcmd.c:121:4: error: this statement may fall through [-Werror=implicit-fallthrough=]
    pchr(f, '>');
    ^~~~~~~~~~~~
pcmd.c:122:3: note: here
   case WRITE:
   ^~~~
cc1: all warnings being treated as errors
Makefile:40: recipe for target 'pcmd.o' failed
make: *** [pcmd.o] Error 1
cc  -g -Wall -Wextra -Wno-parentheses -Wno-missing-braces -Wno-missing-field-initializers  -Wno-comment -Wno-sign-compare -Wno-unused-parameter -Werror -DPREFIX=\"/usr/local\" -c simple.c
simple.c: In function ‘execexit’:
simple.c:205:3: error: this statement may fall through [-Werror=implicit-fallthrough=]
   pfmt(err, "Usage: exit [status]\nExiting anyway\n");
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
simple.c:206:2: note: here
  case 2:
  ^~~~
simple.c:207:3: error: this statement may fall through [-Werror=implicit-fallthrough=]
   setstatus(runq->argv->words->next->word);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
simple.c:208:2: note: here
  case 1: Xexit();
  ^~~~
simple.c: In function ‘execflag’:
simple.c:405:5: error: this statement may fall through [-Werror=implicit-fallthrough=]
   if(strlen(letter)==1){
     ^
simple.c:415:2: note: here
  default:
  ^~~~~~~
cc1: all warnings being treated as errors
Makefile:40: recipe for target 'simple.o' failed
make: *** [simple.o] Error 1
cc  -g -Wall -Wextra -Wno-parentheses -Wno-missing-braces -Wno-missing-field-initializers  -Wno-comment -Wno-sign-compare -Wno-unused-parameter -Werror -DPREFIX=\"/usr/local\" -c unix.c
unix.c: In function ‘Waitfor’:
unix.c:224:10: error: implicit declaration of function ‘wait’; did you mean ‘Exit’? [-Werror=implicit-function-declaration]
   wpid = wait(&wstat);
          ^~~~
          Exit
cc1: all warnings being treated as errors
Makefile:40: recipe for target 'unix.o' failed
make: *** [unix.o] Error 1
make: Target 'all' not remade because of errors.

Re: [9fans] Rc port.

[Federico Benavento]

Fixed, thanks.

> On Jan 28, 2019, at 12:22 PM, arnold@skeeve.com wrote:
> 
> Federico Benavento <benavento@gmail.com> wrote:
> 
>> Hola,
>> 
>> I just uploaded a standalone unix (only tested on macOS/Linux) port with edit, history and completion support to GitHub.
>> I have been using it as my primary shell for months on macOS and it???s seems to be working pretty well.
>> 
>> https://github.com/benavento/rc
>> 
>> Have fun.
>> ???-
>> Federico G. Benavento
>> benavento@gmail.com
> 
> On Ubuntu 18.04, doing make, I get errors on several files. See attached.
> 
> Thanks,
> 
> Arnold
> <ERRS>

—-
Federico G. Benavento
benavento@gmail.com