From: Alfred Puzzuoli <alpuzz@mediaone.net>
To: blinux-list@redhat.com
Subject: Editing through a Terminal?
Date: Thu, 10 Dec 1998 22:43:09 -0500 [thread overview]
Message-ID: <3.0.5.32.19981210224309.007cd9d0@pop.mw.mediaone.net> (raw)
In-Reply-To: <199812091421.JAA00299@wlestes.uncg.edu>
Hi,
I'm a relative newbie to Linux so may be covering ground that has already
been dealt with here. I don't have a linux box of my own as of yet but do
have access to a couple on the net. The problem that I'm having is that
when I'm connected to one of these via telnet, I'm finding that it's almost
impossible to accurately edit any files. I am doing this from dos, with
artic Business vision for access. I have used two terminal programs, Cutcp
telnet, and Mskermit. i have checked my local and remote terminal
settings and to the best of my knowledge, they're both correctly set to
vt100. The editor with which I have been working is Pico. The problem is
that if I arrow accross a line of text, Artic will not accurately track
the cursor. As I arrow, characters are spoken; However the last character
spoken, is usually not the last character upon which the cursor is resting.
Does anyone have any ideas as to how I might get around this? I've
resorted to downloading files to my machine, editing them and then
uploading them to the linux box once again. Any help would be appreciated.
REgards,
Al
Regards,
Al
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
` Alfred Puzzuoli [this message]
` Editing through a Terminal? Charles Hallenbeck
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=3.0.5.32.19981210224309.007cd9d0@pop.mw.mediaone.net \
--to=alpuzz@mediaone.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).