9p write acme/acme/edit not coming thru

[Niko Schwarz]

The following command comes back with an error and does nothing:

$ echo 'Edit x/n/ d' | 9p write acme/acme/edit 

9p: fsopen acme/edit: file 'acme/edit' not found

The exact same command is a bit tricky to run inside acmeSAC, so I ran another one. This one behaves as expected (it prints the current window):

cat /mnt/acme/acme/body

But in 9p, nothing works:

$ read acme/acme/body

9p: fsopen acme/body: file 'acme/body' not found

The strangest behavior is this:

$ mackay:acme nes$ echo hi | 9p write /acme/new

9p: mount: dial unix!/tmp/ns.nes._tmp_launch-HARC6z_org.macosforge.xquartz:0/: connect /tmp/ns.nes._tmp_launch-HARC6z_org.macosforge.xquar

This opens a new window in acme, but it does NOT contain the words "hi".

You see, it's all a bit strange :)

[Russ Cox]

When you use the 9p command, the first path element names the server to connect to (here, acme). The rest is passed to the server. The paths you get back in errors will be one element shorter because the server doesn't see that first element. For example '9p read acme/index' asks the acme server for just '/index'. 

acme/new is a directory that, each time you enter it, creates a new window. You can't write directly to the directory but you can write to the window control files inside it. 

    echo hi | 9p write acme/new/body.