[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On Dec 30, 7:56pm, Kamil Rytarowski wrote:
} This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
} Content-Type: multipart/mixed; boundary="85Smcsqd4lp0oGdh86kR7TUq2Q6dvAdU4";
} From: Kamil Rytarowski <n54%gmx.com@localhost>
} To: Thomas Dickey <dickey%his.com@localhost>, Valery Ushakov <uwe%stderr.spb.ru@localhost>
} Cc: netbsd-users%netbsd.org@localhost
} Message-ID: <58d4e939-479d-3c35-2f83-223743267b27%gmx.com@localhost>
} Subject: Re: vt100
} References: <1874747553.1486653.1514659173675.JavaMail.root%his.com@localhost>
} In-Reply-To: <1874747553.1486653.1514659173675.JavaMail.root%his.com@localhost>
} On 30.12.2017 19:39, Thomas Dickey wrote:
} > ----- Original Message -----
} > | From: "Valery Ushakov" <uwe%stderr.spb.ru@localhost>
} > | To: netbsd-users%netbsd.org@localhost
} > | Sent: Saturday, December 30, 2017 1:28:53 PM
} > | Subject: Re: vt100
} > |
} > | Kamil Rytarowski <n54%gmx.com@localhost> wrote:
} > ...
} > |
} > | > I've uploaded screen shot of xterm and script(1) recording.
} > | >
} > | > http://netbsd.org/~kamil/vt100/
} > |
} > | The typescript looks strange. Are you sure there was not accidental
} > | conversion(s) to/from utf-8 somewhere along the path?
} > That might be part of it, but the 233's are pretty clear.
} > The host is responding with C1 controls, and that seems to be the main issue.
} > Either make it work properly (I'd do that...) or back off and just be a VT100/VT102.
} I use the default options and I assume that something is wrong on the
} NetBSD side.
Why would you automatically assume that? That's a pessimatic
viewpoint towards NetBSD.
} My only host change in my env(1)/NetBSD-host that might affect something is:
Given what Thomas Dickey said about the 8-bit controls earlier
it sounds like you're failing to tell the OpenVMS side what type
of terminal you have (i.e. it thinks that you have a VT220 or newer
model when you only have a VT100). If this is the case, then it
is user error on your part and not NetBSD's fault at all.
}-- End of excerpt from Kamil Rytarowski
Main Index |
Thread Index |