From: Eliot Moss <moss@cs.umass.edu>
To: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Subject: Re: Readline not working correctly with cygwin1.dll in same directory
Date: Sun, 5 Jun 2022 12:38:22 -0400 [thread overview]
Message-ID: <b61a9a6d-bc80-4dba-8ac0-5cd0254e681b@cs.umass.edu> (raw)
In-Reply-To: <20220606000459.ff0ea9ccbe025d8a4022de25@nifty.ne.jp>
On 6/5/2022 11:04 AM, Takashi Yano wrote:
> 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.
I would add that the escape sequences needed to cause the
proper editing on the screen depend on the terminal type,
and the information for each kind of terminal is in the
terminfo folder. So unless you assume a specific terminal
and can properly inform readline, it would seem to me to
be necessary to include terminfo. Takashi may know more
on this point, of course ...
Best - Eliot Moss
next prev parent reply other threads:[~2022-06-05 16:38 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
2022-06-05 16:38 ` Eliot Moss [this message]
-- 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=b61a9a6d-bc80-4dba-8ac0-5cd0254e681b@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).