> To me it looks more like a consequence of Plan 9's treatment of files as
> sequences of bytes/chars/runes rather then sequences of lines as is common
> in Unix. Basically, you can't scroll beyond the end of the file, and if the
unix and plan 9 agree: a file is an ordered sequence of bytes. unix
On Oct 5, 2008, at 9:52 AM, erik quanstrom wrote:
indicating exactly where to look. (libframe.)
I don't think so, as libframe doesn't provide a scroll function. Maybe
(rio sam acme) use a common scroll function? I'll look into it.
> On Oct 5, 2008, at 9:52 AM, erik quanstrom wrote:
> > indicating exactly where to look. (libframe.)
>
> I don't think so, as libframe doesn't provide a scroll function. Maybe
> (rio sam acme) use a common scroll function? I'll look into it.
i don't think the callback Frame.scroll would exist
On Sat, Oct 4, 2008 at 3:18 AM, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
> it appears that I'm missing something fundamental in how
> 9pfuse (the one written by Russ) works when it is given
> "-" as an address.
Seems to work here on linux after:
#include
#include
+#include
void socke
> Sorry about that. We're soaking a version of the kernel that includes
> a reference count in the Block struct. It's so far used by the
> Ethernet drivers, IP stack and USB code, and usbohci.c escaped a
> little too early.
>
> I've just pushed out a newer allocb.c to sources that initializes th
Hi!
Thanks for replying. You're the only one so far, which makes
me wonder whether there's a more appropriate place for
plan9port discussions.
On Sun, 2008-10-05 at 23:35 +0800, sqweek wrote:
> On Sat, Oct 4, 2008 at 3:18 AM, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
> > it appears that I'm
On Mon, Oct 6, 2008 at 11:46 AM, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
> Thanks for replying. You're the only one so far, which makes
> me wonder whether there's a more appropriate place for
> plan9port discussions.
Not that I'm aware of. I think we're just seeing the effect of a
small c
