From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: "James A. Robinson" Date: Sat, 31 Aug 2013 10:29:31 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d043c7e60f416f504e541b04e Subject: Re: [9fans] reading addr always returns #0,#0? Topicbox-Message-UUID: 77de9678-ead8-11e9-9d60-3106f5b1d025 --f46d043c7e60f416f504e541b04e Content-Type: text/plain; charset=UTF-8 On Sat, Aug 31, 2013 at 10:23 AM, James A. Robinson < jimr@highwire.stanford.edu> wrote: > 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? > I should have said character offset, not byte offset. I was also experimenting with using addr=dot, but didn't see any change in behavior. Jim --f46d043c7e60f416f504e541b04e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Aug 31, 2013 at 10:23 A= M, James A. Robinson <jimr@highwire.stanford.edu> w= rote:
I see t= he 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 fil= e (it is a non-zero length 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?

I should have said character off= set, not byte offset.
I was also experimenting with using addr=3Ddot, = but
didn't see any change in behavior.<= /div>

Jim

--f46d043c7e60f416f504e541b04e--