l terminal and have tried
vt100 and vt102 with about the same degree of mostly weirdness.
It seemed like older versions of make menuconfig didn't have
this problem. Any ideas as to how I can make it work correctly?
Other screen functions such as the shell and when I run
vi are fine. comm
hi,
I'm looking for vt100 font for my debian box and so far I've been unable
to locate it. Yes I did google it w/ no avail.
Is anyone using this font? If so, can you point me in the right
direction so I can get it.
tia,
regards,
/virendra
--
To UNSUBSCRIBE, email to [EMAIL
I have upgraded 3 systems to Sarge and each one exhibits a
peculiar behavior when running dselect. It occurs only in the main
and conflict resolution menus and looks like:
Help:pIntroductionptopconflict/dependencypresolutionpsub-listppp
Tupu~tu~sys~v|ystprus|uty~p}py~trt
On Sun, 2002-10-13 at 20:06, Russell wrote:
> Lukas Ruf wrote:
> >
> > Dear all,
> >
> > trying to launch:
> >
> > uccellina:~!63> minicom -o -l -m -t VT100
> >
> > resulted in:
> >
> > No termcap entry for VT100
> &
Lukas Ruf <[EMAIL PROTECTED]> writes:
> uccellina:~!63> minicom -o -l -m -t VT100
try "vt100" (ie, lowercase)
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
"Oh give me a home, where the aardvarks do roam..."
--
To UNSUBSCRIBE, emai
Lukas Ruf wrote:
>
> Russell,
>
> On Mon, 14 Oct 2002, Russell wrote:
>
...
> > Try:
> > uccellina:~!63> minicom -o -l -m
> >
> This does not help. I need to use VT100, minicom tries to make use of
> VT102 -- which results in garbage on screen.
Russell,
On Mon, 14 Oct 2002, Russell wrote:
> Lukas Ruf wrote:
> >
> > Dear all,
> >
> > trying to launch:
> >
> > uccellina:~!63> minicom -o -l -m -t VT100
> >
> > resulted in:
> >
> > No termcap entry for VT100
> &
Lukas Ruf wrote:
>
> Dear all,
>
> trying to launch:
>
> uccellina:~!63> minicom -o -l -m -t VT100
>
> resulted in:
>
> No termcap entry for VT100
>
> How can I configure the VT100 terminal emulation in the termcap(?) ?
man minicom
-t VT100 overi
Dear all,
trying to launch:
uccellina:~!63> minicom -o -l -m -t VT100
resulted in:
No termcap entry for VT100
How can I configure the VT100 terminal emulation in the termcap(?) ?
Thanks for any help!
--
Lukas Ruf
http://www.lpr.ch http://www.maremma
t;(S)elect" mode and go back to the menu, I'll
often get a whole page full of flashing characters. I can still type letters
("I" for Install, etc) to get to what I need... but the menu navigation just
becomes useless.
Is "vt100" suddenly deprecated or something?
- Jo
Thanks. I discovered I was using the NT telnet client from work the wrong
way. Problem solved now.
Patrick
- Original Message -
From: Marc Mongeon <[EMAIL PROTECTED]>
To:
Sent: Monday, July 12, 1999 1:43 PM
Subject: Re: TERM=vt100 for telnet
> Patrick:
>
> Telnet is
It's such a fine line between clever and stupid."
-- David St. Hubbins and Nigel Tufnel of "Spinal Tap"
>>> "Patrick Kirk" <[EMAIL PROTECTED]> 07/11 4:03 PM >>>
Hi all,
Why does vi simply not work unless I have entered the command TERM=vt100
w
Hi all,
Why does vi simply not work unless I have entered the command TERM=vt100
when I use telnet? What is vt100? Is there anything better?
Would putting TERM=vt100 or whatever is better in my .bashrc be of benefit?
Patrick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 14 Jan 1999 21:54:37 + (GMT), Nidge Jones wrote:
>So what is broken here, how do I make the CR work again when the term type
>is set to VT100. And why is it OK in Screen.. Is Screen setting some sort of
>stty variable or someth
Since upgrading to 2.0 from 1.3.1 I have a problem with remote VT100
terminals and the Carriage Return Key.
That is too say, if you access Debian 2.0 from a VT100 terminal (Not
Console), or VT100 emulators via Ethernet, the CR fails to work in such
things as JOE etc.
However, if one was to
Since upgrading to 2.0 from 1.3.1 I have a problem with remote VT100
terminals and the Carriage Return Key.
That is too say, if you access Debian 2.0 from a VT100 terminal (Not
Console), or VT100 emulators via Ethernet, the CR fails to work in such
things as JOE etc.
However, if one was to
On Mon, Dec 21, 1998 at 12:10:24PM +, Nuno Carvalho wrote:
> - how can I do for not echo charaters to the remote machine(probabily
> using vt100 escape codes) !?
Jump the cursor to some realative position, ask for that position from
the remote terminal.
--
S
Hi,
Could someone help me on:
- check, using socket programming, if the remote machine support vt100!
I'm trying on using escape codes sending a string ("\e[c") to the
remote machine. Unfortunally it writes the result to the remote machine.
Is there any way for I
set is used for csh or tcsh. export is used for sh (bourne shell)
derivatives, like bash.
-brad
On Sun, 22 Nov 1998, Sibuyas Bombay wrote:
> hi!
> i once had an ISP where in order to be able to run elm (when telnet`ing to
> it) you have to invoke _$ set TERM=v100_ , they were running RedHat
hi!
i once had an ISP where in order to be able to run elm (when telnet`ing to
it) you have to invoke _$ set TERM=v100_ , they were running RedHat.
on another ISP, in order for you to run pine, you have to invoke _$ export
TERM=vt100_ , they ran BSDI.
now, on my debian system, (when i teln
ve to hear from
>> you Oh yeah.. Im using vt100 for the terminal.
>> BTW: I am not currently on the mailing list so please email me a reply. :)
>
>What model Wyse and what emulation is it running? Your TERM variable
>would need to be set to wyse??? if you're running i
, {ESC}OR etc. The place I found
>> these had {ESC}[H for Home and {ESC}[K for End. But they dont work. can
>> anybody shine some light on this subject??? I would love to hear from
>> you Oh yeah.. Im using vt100 for the terminal.
>> BTW: I am not currentl
aritively
> easy. strings like {ESC}OP, {ESC}OQ, {ESC}OR etc. The place I found
> these had {ESC}[H for Home and {ESC}[K for End. But they dont work. can
> anybody shine some light on this subject??? I would love to hear from
> you.... Oh yeah.. Im using vt100 for the term
easy. strings like {ESC}OP, {ESC}OQ, {ESC}OR etc. The place I found
> these had {ESC}[H for Home and {ESC}[K for End. But they dont work. can
> anybody shine some light on this subject??? I would love to hear from
> you.... Oh yeah.. Im using vt100 for the terminal.
> BTW: I a
these had {ESC}[H for Home and {ESC}[K for End. But they dont work. can
anybody shine some light on this subject??? I would love to hear from
you Oh yeah.. Im using vt100 for the terminal.
BTW: I am not currently on the mailing list so please email me a reply. :)
Michael Beattie
--
TO
On Wed, 20 Aug 1997 [EMAIL PROTECTED] wrote:
> > how do i get a vc or an xterm to recognize and print vt100 print
> > sequences?
> > this is what i want to be able to do, in a nutshell:
> > my.debian.machine% rsh other.debian.machine vtprint foo.txt
> > thus causin
how do i get a vc or an xterm to recognize and print vt100 print
sequences?
this is what i want to be able to do, in a nutshell:
my.debian.machine% rsh other.debian.machine vtprint foo.txt
thus causing foo.txt to be printed on the printer which is physically
connected to "my.debian.ma
On Thu, 19 Dec 1996, Pete Templin wrote:
>
> -> This is to make the office gag gift really work...<-
>
> I was "given" a VT100 terminal as a gag gift. Is there any way to
> interface it with a Linux box? Keep it simple, so I can do it in one
> night and
On Thu, 19 Dec 1996, Pete Templin wrote:
> -> This is to make the office gag gift really work...<-
>
> I was "given" a VT100 terminal as a gag gift. Is there any way to
> interface it with a Linux box? Keep it simple, so I can do it in one
> night and really get
-> This is to make the office gag gift really work...<-
I was "given" a VT100 terminal as a gag gift. Is there any way to
interface it with a Linux box? Keep it simple, so I can do it in one
night and really get some laughs around here.
(Normally, we get one machine "
30 matches
Mail list logo
