From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: "James A. Robinson" Date: Sat, 31 Aug 2013 10:23:55 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c23ee2f9775c04e5419c2c Subject: [9fans] reading addr always returns #0,#0? Topicbox-Message-UUID: 77d8958e-ead8-11e9-9d60-3106f5b1d025 --001a11c23ee2f9775c04e5419c2c Content-Type: text/plain; charset=UTF-8 Say I have an acme window with a $winid of 2. If I type the following commands: $ echo -n , | 9p write acme/2/addr $ echo dot=addr | 9p write acme/2/ctl I see the entire text of the window get selected. I had assumed that if I then read addr that I would get back two numbers, 0 and the final byte offset of the file (it is a non-zero length file). However, I get back two zeros: $ 9p read acme/2/addr 0 0 What am I missing? Jim --001a11c23ee2f9775c04e5419c2c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Say I have an acme window with a $winid of 2.
If I typ= e the following commands:

$ echo -n , | 9p writ= e acme/2/addr
$ echo dot=3Daddr | 9p write acme/2/ctl
<= br>
I see the entire text of the window get selected.
I ha= d assumed that if I then read addr that I would
get back two numb= ers, 0 and the final byte offset
of the file (it is a non-zero le= ngth file).

However, I get back two zeros:

$ 9p read acme/2/addr
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0=C2=A0

What= am I missing?

Jim

--001a11c23ee2f9775c04e5419c2c--