public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Tackett, Galen" <Galen.Tackett@DynCorp.com>
To: cygwin@cygwin.com
Subject: A proposed change to termcap??
Date: Mon, 22 Jul 2002 07:12:00 -0000	[thread overview]
Message-ID: <CBED705A7FD2D311865500508B10894107EB3F96@chntex02.is.dyncorp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

Although there is a terminfo file for rxvt-cygwin-native, the distribution's
termcap file doesn't have an entry for it. I produced the attached one via
the command:

$ infocmp -uCr rxvt-cygwin-native rxvt

For consistency should something like this be added to the termcap file?

(BTW, doing so has resolved a difficulty I described here a few days ago
under
"After pre-release setup, warning message from less." In brief--less gives a
warning for rxvt-cygwin-native, while the vanilla rxvt doesn't allow use of
line drawing characters as in midnight commander. The problem had nothing
to do with setup at all, as far as I can tell now...)


[-- Attachment #2: native-add --]
[-- Type: application/octet-stream, Size: 245 bytes --]

rxvt-cygwin-native|rxvt terminal emulator (native MS Window System port) on cygwin:\
	:ac=+\257,\256-^0\333`\004a\261f\370g\361h\260j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330~\376:\
	:tc=rxvt:


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-07-22 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22  7:12 Tackett, Galen [this message]
2002-07-22  7:21 ` Nicholas Wourms
2002-07-22  9:22 ` Christopher Faylor
2002-07-22 10:46 Tackett, Galen
2002-07-26  8:16 Tackett, Galen

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=CBED705A7FD2D311865500508B10894107EB3F96@chntex02.is.dyncorp.com \
    --to=galen.tackett@dyncorp.com \
    --cc=cygwin@cygwin.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).