Use acme.rc with acme (p9p)

[d***@gmail.com]

I know that there should be a way to use the functions defined in acme.rc, but I cannot seem to figure out how to load it. Any help would be appreciated.

Up to this point every time I've created new commands I've added them each as a separate command in my PATH which I don't care for.

Thanks.

[Rubén Berenguel]

I run acme (in Mac OS X with zsh) as:

SHELL=$PLAN9/bin/rc acme -a -f /mnt/font/Monaco/16a/font &

to be able to use rc in Win. I guess this also loads all the stuff in
profile.rc (I think I had tried this already a few weeks ago) and probably
also acme.rc (didn't know about acme.rc, makes more sense than clobbering
profile.rc!)

Ruben

Post by d***@gmail.com
I know that there should be a way to use the functions defined in acme.rc,
but I cannot seem to figure out how to load it. Any help would be
appreciated.
Up to this point every time I've created new commands I've added them each
as a separate command in my PATH which I don't care for.
Thanks.

[Sergio Perticone]

Post by d***@gmail.com
I know that there should be a way to use the functions defined in acme.rc,
but I cannot seem to figure out how to load it. Any help would be
appreciated.

dot:

. $PLAN9/lib/acme.rc
newwindow

Post by d***@gmail.com
Up to this point every time I've created new commands I've added them each
as a separate command in my PATH which I don't care for.
Thanks.

[Mathieu Lonjaret]

if you start acme with your SHELL being $PLAN9/bin/rc, then the wins you'll
open will run rc -l, which reads $HOME/lib/profile.
So whatever functions you define in there will be known to your wins in
acme. Not sure that answers your questions though.

Post by Sergio Perticone

Post by d***@gmail.com
I know that there should be a way to use the functions defined in
acme.rc, but I cannot seem to figure out how to load it. Any help would be
appreciated.

. $PLAN9/lib/acme.rc
newwindow

Post by d***@gmail.com
Up to this point every time I've created new commands I've added them
each as a separate command in my PATH which I don't care for.
Thanks.