From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] nile, a rio derivative
Date: Thu, 17 Oct 2013 16:00:06 -0400 [thread overview]
Message-ID: <72b93ab89f7f3e824051c84d0cb74ff7@9srv.net> (raw)
In-Reply-To: <CAK4xykUwWxvGO1Jo=CcAg3MsD-K9z2AMzP=7XkHhDhYbvgznJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 102 bytes --]
I don't recall if it's an exact match, but that sounds
roughly like what's in plan9port. I like it.
[-- Attachment #2: Type: message/rfc822, Size: 4510 bytes --]
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nile, a rio derivative
Date: Thu, 17 Oct 2013 13:53:33 -0600
Message-ID: <CAK4xykUwWxvGO1Jo=CcAg3MsD-K9z2AMzP=7XkHhDhYbvgznJg@mail.gmail.com>
nice!
i've been thinking in the past that the scroll dichotomy (some like
noscroll and some don't) can be solved similarly to OSX's terminal --
if you're at the bottom of the page it scrolls down, if you're
anywhere else it does not. the last line of text (the line with the
prompt, or an empty line) at the bottom of the window is normally not
visible, so to switch from noscroll mode to scroll mode you go to the
bottom of the page and hit page-down/arrow down once more to "show"
the last line and enable "scroll" mode. page-up or up-arrow once will
act normally but have the secondary effect that noscroll is enabled.
i've found it useful in terminal, but i've always been a no-noscroll
kind of guy :)
next prev parent reply other threads:[~2013-10-17 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 18:03 a
2013-10-17 19:49 ` Skip Tavakkolian
2013-10-17 19:57 ` a
2013-10-17 21:44 ` Skip Tavakkolian
2013-10-17 22:53 ` Lee Fallat
2013-10-17 19:53 ` andrey mirtchovski
2013-10-17 20:00 ` a [this message]
2013-10-17 20:00 ` Steve Simon
2013-10-17 20:06 ` a
2013-10-17 20:22 ` Skip Tavakkolian
2013-10-18 20:28 ` hiro
2013-10-18 20:32 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72b93ab89f7f3e824051c84d0cb74ff7@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).