From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Readline not working correctly with cygwin1.dll in same directory
Date: Mon, 6 Jun 2022 00:04:59 +0900 [thread overview]
Message-ID: <20220606000459.ff0ea9ccbe025d8a4022de25@nifty.ne.jp> (raw)
In-Reply-To: <ec232cef41cc494082e6229063534d57@ads.uni-passau.de>
On Sun, 5 Jun 2022 14:17:27 +0000
"Mexis, Nico" wrote:
> However, I still have one follow-up question about this:
>
> Is there a way to get rid of the need for the terminfo folder or change its location?
>
> It would be ideal to not need to include it in the distribution at all or such that it will be in the same folder as cygwin1.dll.
If environment variable TERMINFO is set, cygncurses*.dll searches
terminfo from TERMINFO. So it is possible if you have chance to
set environment variable TERMINFO.
Please refer to 'man terminfo' for more detail.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-06-05 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 14:17 Mexis, Nico
2022-06-05 15:04 ` Takashi Yano [this message]
2022-06-05 16:38 ` Eliot Moss
-- strict thread matches above, loose matches on Subject: below --
2022-06-03 18:37 Mexis, Nico
2022-06-03 23:53 ` Takashi Yano
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=20220606000459.ff0ea9ccbe025d8a4022de25@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).