rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Gert-Jan Vons <vons@ocegr.fr>
To: "rc" <rc@hawkwind.utcs.toronto.edu>, "Sam Roberts" <sam@cogent.ca>
Subject: Re: vrl (was: Re: building rc on QNX4)
Date: Fri, 28 Apr 2000 03:28:36 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <002701bfb089$027826a0$1403a8c0@cogent.ca>

Sam Roberts wrote:

>Speaking of which, is this an appropriate place to talk about
>vrl? I posted some diffs to the author, no response yet (only
>been a day or so -- I'm just mentioning, not griping).

That would be me, since I'm the author :-) I assume you sent it to my 
(old) usa.net address, I'll check my inbox there.

>I had some trubles with it's termcap usage. It seems to
>think that @7 is the keypad END key/capability. This wasn't
>defined on my system, and while I found it defined in a bunch
>of Linux termcap entries (mostly in what looked like old PC
>consoles), it wasn't in the ansi entries.
>Poking around it seemed the right thing was to use kh for HOME
>and kH for END (vrl was using kh for HOME and @7 for END).

kH is the "last-line" key according to FreeBSD's termcap(5). What is the 
OS you are using, what is the tty type, and on what hardware? (please 
mail me the termcap entry for your tty)

"last-line" for going to the end of a line seems a bit strange, but if 
that is what your tty sends when you hit the End key... I could fall back 
to kH if there is no @7 defined.

>Also, I can't call 'login' from an rc shell, strangely, it
>complains about not being session leader. I'm quite baffled.

What kind of OS are you using? I can use "login" under solaris and 
freebsd without any problems.

>Also, I just noticed ^L doesn't clear the screen. I'll look
>into that sometime.

Nope. When you use vrl, ^L redisplays the line, useful in case it got 
garbled by the output of some background process. Note also that vrl is 
about lines, it doesn't (want/need to) know about the screen. The unix 
'clear' command handles that very well.

"If you are good, you will be assigned all the work. If you
  are really good, you will get out of it."
     - Dilbert

  reply	other threads:[~2000-04-28 20:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sroberts@uniserve.com>
2000-04-26 15:02 ` building rc on QNX4 Sam Roberts
2000-04-27 16:56   ` Scott Schwartz
2000-04-27 20:41     ` Sam Roberts
2000-04-28  7:28       ` Gert-Jan Vons [this message]
2000-04-28 18:38         ` vrl (was: Re: building rc on QNX4) Sam Roberts
2000-05-02  8:16           ` Gert-Jan Vons
2000-04-28 19:03         ` rc not session leader? Sam Roberts
2000-04-27 17:39   ` building rc on QNX4 Carlo Strozzi
2000-05-02 14:41     ` Tim Goodwin
2000-05-04 15:18       ` Carlo Strozzi
2000-05-08  8:29         ` Tim Goodwin
2000-05-08  8:58           ` Chris Siebenmann
2000-05-08  9:15             ` Tim Goodwin
2000-05-08 23:25               ` Stephen Tell
2000-05-10  0:37                 ` builtins Scott Schwartz
2000-05-12  7:22                   ` builtins Carlo Strozzi
2000-05-08 11:50           ` building rc on QNX4 David Luyer
2000-05-08 13:28           ` Carlo Strozzi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to= \
    --to=vons@ocegr.fr \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=sam@cogent.ca \


* 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).