From: John Cook <john.cook@kla-tencor.com>
To: "'gnuwin32'" <gnu-win32@cygnus.com>
Subject: which TERM to use for vim?
Date: Mon, 27 Oct 1997 18:18:00 -0000 [thread overview]
Message-ID: <c=US%a=_%p=KLA_Instruments_%l=SJEXCHANGE3-971028021319Z-21729@sjexchange.kla-tencor.com> (raw)
Despite my problems with 'make install' for ncurses-4.1,
I am able to compile vim-5.0p under gnuwin32 bash (this
may be an anomaly; I can't tell). Vim does not recognize
the TERM value of 'linux', however, and gives only a few
choices that it _does_ recognize, such as 'builtin_ansi'
and 'builtin_dumb'. What is the correct TERM to use for
vim under gnuwin32 bash?
Anyone who has built Vim-5.0p under gnuwin32, please pass
along what (if any) changes you had to make to the Makefile
or the build procedure.
Thanks,
John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
reply other threads:[~1997-10-27 18:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='c=US%a=_%p=KLA_Instruments_%l=SJEXCHANGE3-971028021319Z-21729@sjexchange.kla-tencor.com' \
--to=john.cook@kla-tencor.com \
--cc=gnu-win32@cygnus.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).