This is not a bug.
At any point in time, there is a character position
associated with the upper left corner of the text window.
Text before that position is not shown; text at or after
that position is shown, until it runs off the bottom of
the window. Let's call that upper left character positi
> 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 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.
> 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
* erik quanstrom ([EMAIL PROTECTED]) wrote:
> > > the fact that the tick shows is also a bug. notice the scroll bar.
> >
> > What do you mean? You're showing no characters in the pane, the
> > insertion point is after the last character.
>
> yes, but you're not showing the line which includes th
> > the fact that the tick shows is also a bug. notice the scroll bar.
>
> What do you mean? You're showing no characters in the pane, the
> insertion point is after the last character.
yes, but you're not showing the line which includes the prompt.
either the tick and the prompt need displaying
> the fact that the tick shows is also a bug. notice the scroll bar.
What do you mean? You're showing no characters in the pane, the
insertion point is after the last character.
Or do you want to have the ability to scroll beyond the end of your
text, to have some imaginary scroll advance taking
> > this is a bug. you can see what you've typed but not the prompt.
> > normally acme warps back to the tick when you type. this bug is
> > in acme since if you create a new window and type the prompt
> > manually then continue with step 2, you get the same results.
> >
>
> It's because your cu
On Fri, Oct 3, 2008 at 1:19 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>> > 1. Open a "win" in acme.
>> > 2. Scroll down as far as possible.
>> > 3. Notice that there is no $prompt visible at left.
>> > 4. echo annoying
>> > 5. Now scroll back up and it turns out you entered the echo command at
> > 1. Open a "win" in acme.
> > 2. Scroll down as far as possible.
> > 3. Notice that there is no $prompt visible at left.
> > 4. echo annoying
> > 5. Now scroll back up and it turns out you entered the echo command at
> > a prompt after all!
>
> Not entirely sure what other behaviour you were ex
On Fri, Oct 3, 2008 at 7:14 AM, Michael Brown <[EMAIL PROTECTED]> wrote:
> 1. Open a "win" in acme.
> 2. Scroll down as far as possible.
> 3. Notice that there is no $prompt visible at left.
> 4. echo annoying
> 5. Now scroll back up and it turns out you entered the echo command at
> a prompt after
1. Open a "win" in acme.
2. Scroll down as far as possible.
3. Notice that there is no $prompt visible at left.
4. echo annoying
5. Now scroll back up and it turns out you entered the echo command at
a prompt after all!
12 matches
Mail list logo
