Thank you both for the explanation!
On Mon, Sep 2, 2013 at 3:38 AM, dexen deVries wrote:
> On Monday 02 of September 2013 14:13:56 Alexander Sychev wrote:
> > The problem is the "addr" file is closed between your calls. When you
> open
> > the "addr" file next time, an internal address is set to
On Monday 02 of September 2013 14:13:56 Alexander Sychev wrote:
> The problem is the "addr" file is closed between your calls. When you open
> the "addr" file next time, an internal address is set to 0,0.
> But after the writing the address is actual and if you read "data" file you
> will see the t
Hi,
The problem is the "addr" file is closed between your calls. When you open
the "addr" file next time, an internal address is set to 0,0.
But after the writing the address is actual and if you read "data" file you
will see the text according to your address.
I you write the code on C or Go with
On Sat, Aug 31, 2013 at 10:23 AM, James A. Robinson <
j...@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).
>
> H
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
