Re: [9fans] reading addr always returns #0,#0?

2013-09-02 Thread Alexander Sychev
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

Re: [9fans] [plan9] acme noscrool feature enable

2013-09-02 Thread Alexander Sychev
Hi, As far as I know Acme doesn't have the "noscroll" feature at all. Best regards, santucco On Mon, Sep 2, 2013 at 10:57 AM, Giovanni Casano wrote: > Hello all, I do not remember, and I can't find it on the web, how to > enable the noscroll feature > on acme from plan9port. > > I wrote Nosc

Re: [9fans] reading addr always returns #0,#0?

2013-09-02 Thread dexen deVries
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

Re: [9fans] Any Israeli Plan 9 users?

2013-09-02 Thread Erez Schatz
Mostly Sam and now ACME user with interest in learning more about Plan9, but from Israel. On 1 September 2013 17:02, wrote: > So, in the same spirit as the earlier mail... Are there any Plan 9 > users in Israel? I live near Modi'in and work in Jerusalem, so those > are the most convenient area

Re: [9fans] [plan9] acme noscrool feature enable

2013-09-02 Thread dexen deVries
On Monday 02 of September 2013 14:19:17 Alexander Sychev wrote: > Hi, > As far as I know Acme doesn't have the "noscroll" feature at all. if `win' is of any help, it has the following property: > Win windows follow the > same scrolling heuristic as in 9term(1): the window scrolls > on output only

Re: [9fans] [plan9] acme noscrool feature enable

2013-09-02 Thread Giovanni Casano
9term windows default behaviour does not scroll when output reaches the end of the window: this is what I am trying to do. Few months ago I succeded in that... now I do not remember how I did :( 2013/9/2 dexen deVries : > On Monday 02 of September 2013 14:19:17 Alexander Sychev wrote: >> Hi, >> As

Re: [9fans] [plan9] acme noscrool feature enable

2013-09-02 Thread dexen deVries
On Monday 02 of September 2013 12:58:28 Giovanni Casano wrote: > 9term windows default behaviour does not scroll when output reaches > the end of the window: this is what I am trying to do. > Few months ago I succeded in that... now I do not remember how I did :( when executed in Acme, the follow

Re: [9fans] reading addr always returns #0,#0?

2013-09-02 Thread James A. Robinson
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

Re: [9fans] [plan9] acme noscrool feature enable

2013-09-02 Thread Giovanni Casano
ops, I use bash as default shell... maybe should I use rc? 2013/9/2 dexen deVries : > On Monday 02 of September 2013 12:58:28 Giovanni Casano wrote: >> 9term windows default behaviour does not scroll when output reaches >> the end of the window: this is what I am trying to do. >> Few months ago I

Re: [9fans] Building Go/386

2013-09-02 Thread Nick Owens
hello 9fans and gophers, i have been using go on 9front for a while now. however, an issue with 8c's inclusion mechanism was recently introduced. the commit was https://codereview.appspot.com/12568043 which assumes that includes will be resolved relative to the file that included them, not the wd

Re: [9fans] Building Go/386

2013-09-02 Thread Rob Pike
I'm pretty sure C defines the include path to be relative to the file that includes it. The compiler's working directory should be irrelevant. I'm also pretty sure Plan 9's compiler gets this right, or at least used to. So more information is required. -rob

Re: [9fans] Building Go/386

2013-09-02 Thread erik quanstrom
On Mon Sep 2 16:51:31 EDT 2013, robp...@gmail.com wrote: > I'm pretty sure C defines the include path to be relative to the file > that includes it. The compiler's working directory should be > irrelevant. I'm also pretty sure Plan 9's compiler gets this right, or > at least used to. So more infor

Re: [9fans] Building Go/386

2013-09-02 Thread Nick Owens
On Mon, Sep 02, 2013 at 05:51:15PM -0400, erik quanstrom wrote: > On Mon Sep 2 16:51:31 EDT 2013, robp...@gmail.com wrote: > > I'm pretty sure C defines the include path to be relative to the file > > that includes it. The compiler's working directory should be > > irrelevant. I'm also pretty sure

Re: [9fans] Building Go/386

2013-09-02 Thread erik quanstrom
> the trouble here is that go's src/libmach/8obj.c has '#include > "../cmd/8l/8.out.h"', and 8.out.h now has the newly added '#include > "../ld/textflag.h"'. > > i see now that the kernel source has an instance of this, in > /sys/src/9/pc: 'fns.h:1: #include "../port/portfns.h"', but i'm not sure