@7 (kp_end). As ncurses has the limitation that it returns the first
matched key symbol, you can not use END in ncurses based program under
screen (like ports/misc/mc).
We did similar changes to xterm entry last year for exactly the same reason.
PR: 132199
Submitted by: Timur I. Bakeyev <timur at FreeBSD.org>
MFC after: 2 month
As ncurses has the limitation that it returns the first matched key symbol,
you can not use END in ncurses based program, like mutt, with xterm.
- Add @8 (kp_enter) definition for xterm so you can use ENTER in xterm with
ncurses based program.
I also found that NetBSD's xterm does the same thing.
PR: 100150
Reported by: Arseny Nasokin <tarc at tarc.po.cs.msu.su>
Discussed with: Thomas Dickey, Ulrich Spoerlein <uspoerlein at gmail.com>
Reviewed by: freebsd-arch@
MFC after: 2 month
It can be missed easily that the following blank line formally
belongs to the xterm-basic entry due to the unneeded backslash.
PR: bin/80256 (audit trail)
Now ncurses-based programs such as sysinstall and mc will display the
correct font for graphical lines instead of "-" and "+" characters.
Correct two special characters for cons25l1 in termcap: use real
arrows instead of ">>" and "<<".
Add a lot of additional symbols for line drawing which are taken from
the CP437 font.
Almost all of the ACS symbols are now implemented.
PR: conf/90082
Submitted by: Oliver Fromme <olli@secnetix.de>
MFC after: 1 week
Remove references to termcap@berkeley.edu and uunet!ucbvax!termcap in
favor of send-pr(1).
Add comment about how to use cap_mkdb to build a new termcap db.
Submitted by: Ted Mittelstaedt <tedm@toybox.placo.com>
MFC After: 2 weeks
Style:
o Use tabs instead of 8 spaces
o Space after # beginning comment
o Fix entries lacking ":" after tab
o Removed whitespace at EOL
PR: misc/62749 (the ibm additions)
Submitted by: Gerhard Gonter <gonter@wu-wien.ac.at>
MFC after: 3 days
we don't use two-letters names already many years.
2) Make xterm-color just plain alias to xterm instead of unnecessary
reduplication of color capabilities already exist in xterm entry.
3 bytes (ut:) seems too long for kterm-color. There is a limitation
of buffer size within 1024 bytes in our ncurses.
Submitted by: mistral@imasy.or.jp
Reviewed by: matusita
MFC after: 1 day
(I skipped those in contrib/, gnu/ and crypto/)
While I was at it, fixed a lot more found by ispell that I
could identify with certainty to be errors. All of these
were in comments or text, not in actual code.
Suggested by: bde
MFC after: 3 days
Clarify comment about kind of color emulators for which vt*-co* entries
are for and about saving space.
Use direct \E[m instead of ...;m for dumb emulators.
In the past 2 months or so, after rlogining into another host, the
environment has the geometry wrong. Peter suggested that this behavior
change was most likely caused by the PAM stuff that changed to run a proper
session with a forked child. And that for some reason the window size is
no longer being transferred via an OOB message on the socket.
This change fixes my problem and seems to be a good stopgap measure until
someone has time to ktrace/ktrace -i inetd to catch all the child processes
it spawns while doing an rlogin and change window size a few times to see
how far the change messages are getting.
