All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miguel González Castaños" <mgc@tid.es>
To: linux-admin@vger.kernel.org
Subject: Re: terminal problems with escape characters
Date: Tue, 10 Dec 2002 18:21:51 +0100	[thread overview]
Message-ID: <3DF622AF.A90C9263@tid.es> (raw)
In-Reply-To: Pine.LNX.4.44.0212101255080.2146-100000@bak.amgad.org


Many thanks for the fancy telnet client.

I am going to specify my problem a little bit more:

I have set TERM to 'linux'.

When I edit with the vi program (or the bash prompt) delete and backspace works fine,
but not control characters, like
the Up, Down, Left,Right arrow keys, instead of that I get:

^[[B ,  ^[[A , ^[[C , ^[[D

I hope this is a more specific information on this issue. I have looked around in some
web sites, but I still cant figure
out how to fix it.

Many thanks

Miguel


amgad fahmy ha escrito:

> Hello
> Dave telnet is my friend
> it is very flexible & open source
> try it & let se if you still having any problems
>
> http://prdownloads.sourceforge.net/dtelnet/dt118b16.zip?download
>
> On Tue, 10 Dec 2002,
> Miguel González
> Castaños
> wrote:
>
> > Date: Tue, 10 Dec 2002 17:19:34 +0100
> > From: Miguel González Castaños <mgc@tid.es>
> > To: linux-admin@vger.kernel.org
> > Subject: terminal problems with escape characters
> >
> > I have a RedHat 7.3 linux box. I have enabled the telnet server.
> >
> > I am trying to telnet my linux box from a unix-like system where the default
> > terminal setting is set to ansi.
> >
> > I have succesfully changed the setting for the TERM variable to 'linux' or 'vt100'
> > or even 'xterm' (as I have found in several news).
> >
> > But I am still experiencing when I edit files with the vi program, because of the
> > escape characters like the ones to move the cursor dont work...That´s my main
> > problem.
> >
> > Anyway, I have thought that maybe it was due that I was telneting to the Unix box
> > using  the Windows 2000 telnet, but I have tried to use other telnet programs
> > (like putty), but I cant figure out what I have to change in the linux box
> > settings (or the telnet client)...
> >
> > Many thanks in advance...
> >
> > Miguel
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
>
> --
> Amgad Fahmy
> >From the Server

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2002-12-10 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0212101255080.2146-100000@bak.amgad.org>
2002-12-10 17:21 ` Miguel González Castaños [this message]
2002-11-18  8:01 difference btw CGI and HTML scripts simon Shaw
2002-11-18 16:42 ` Tyler
2002-11-19 17:09   ` Geoff Torres
2002-11-19 20:34     ` Linux Backups Ed Walsh
2002-11-20  9:06       ` Agus Budy Wuysang
2002-12-10 16:19         ` terminal problems with escape characters Miguel González Castaños
2002-12-11  1:04           ` dashielljt
2002-12-11  8:54             ` Miguel González Castaños
2002-12-12  1:11               ` dashielljt

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=3DF622AF.A90C9263@tid.es \
    --to=mgc@tid.es \
    --cc=linux-admin@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.