From: Charles Hallenbeck <2ndsight@taconic.net>
To: blinux-list@redhat.com
Subject: Re: Editing through a Terminal?
Date: Fri, 11 Dec 1998 08:54:00 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.981211083514.181A-100000@darkstar.taconic.net> (raw)
In-Reply-To: <3.0.5.32.19981210224309.007cd9d0@pop.mw.mediaone.net>
The problem is not intrinsic to Linux or to the use of terminals... I
access my Linux box through a serial terminal connection and use VI with
no difficulty. However my serial terminal is hard wired and does not need
a telnet connection. Telix is the software on the terminal, with our
provox screen reader.
You might try occasionally entering "control L" to "repaint the screen"
and see if that gets things back into synch.
Chuck -- Second Sight Software
Now using Linux and PINE
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
printing linux files Charles Hallenbeck
` Jude Dashiell
` Fredrik Larsson
` wlestes
` Charles Hallenbeck
` Jason Castonguay
` Charles Hallenbeck
` wlestes
` Luke Davis
` Charles Hallenbeck
` Editing through a Terminal? Alfred Puzzuoli
` Charles Hallenbeck [this message]
hall003
` Jude Dashiell
Martin McCormick
` Alfred Puzzuoli
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=Pine.LNX.3.96.981211083514.181A-100000@darkstar.taconic.net \
--to=2ndsight@taconic.net \
--cc=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).