From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Screen crippled by applications using alternative screen
Date: Fri, 02 May 2014 05:33:00 -0000 [thread overview]
Message-ID: <20140502053330.GA3882@ednor.casa.cgf.cx> (raw)
In-Reply-To: <5362C651.9090402@cygwin.com>
On Thu, May 01, 2014 at 06:10:25PM -0400, Larry Hall (Cygwin) wrote:
>On 05/01/2014 06:13 AM, Maximus5 wrote:
>> Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:
>>
>>> I don't see the behavior that you are specifying but I doubt that what
>>> you are seeing has anything to do with the gobbledegook on the above
>>> page. If you do want "Cygwin" to send ANSI escape sequences then you'll
>>> need to make sure that you're using a package which knows how to send
>>> them, i.e., an ncurses-using package, and that the TERM environment
>>> variable is set appropriately.
>>
>> Hi, about gobbledegook
>>
>> Looking into imports of cygwin's shot.exe I can see "cygncursesw-10.dll".
>>
>> Does that mean it is "using a package which knows how to send them"?
>>
>> Checking for environment
>> $ set | grep TERM
>> TERM=xterm
>>
>> Ok?
>>
>> But sh.exe is using Windows console API instead of writing ANSI to stdout.
>>
>> What is wrong?
>
>If you're using the Windows console (cmd.exe, Console2, ConEmu, etc.), then
>you're not going to get complete ANSI code support regardless of what you
>set your TERM environment variable to. If you're saying that you're using
>mintty or xterm and having problems, then you need to provide a clear recipe
>to reproduce the problem so that someone here can try to reproduce it. For
>more details on what's needed, please see the problem reporting guidelines
>found at the link below:
>
><http://cygwin.com/problems.html>
I think I understand now. The request if for Cygwin to "do nothing"
when it sees escape sequences since, apparently, ConEmu will handle
escape sequences on its own. This is not a bug in Cygwin but, a request
for different functionality. And, on rereading, the web page, I see
that I just wasn't getting what was being requested. That was because I
was thinking about this from the point of view of someone reporting this
as an apparent long-standing bug in Cygwin when it was nothing of the
sort.
Anyway, gobbledegook label withdrawn. Sorry.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-02 5:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:21 Dawid Ferenczy
2014-04-25 17:36 ` Christopher Faylor
2014-04-26 18:06 ` Christopher Faylor
2014-04-26 19:09 ` Dawid Ferenczy
2014-04-26 19:35 ` Dawid Ferenczy
2014-05-03 19:52 ` Dawid Ferenczy
2014-05-03 20:02 ` Christopher Faylor
2014-04-26 18:22 ` Dawid Ferenczy
2014-04-26 19:07 ` Christopher Faylor
2014-04-26 20:16 ` Dawid Ferenczy
2014-04-26 22:45 ` Christopher Faylor
2014-04-26 18:49 ` Dawid Ferenczy
2014-05-01 10:14 ` Maximus5
2014-05-01 22:10 ` Larry Hall (Cygwin)
2014-05-02 5:33 ` Christopher Faylor [this message]
2014-05-02 5:37 ` Christopher Faylor
2014-05-02 11:09 ` Maximus5
2014-05-03 5:54 ` Csaba Raduly
2014-04-26 7:38 Houder
2014-04-27 9:11 ` Houder
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=20140502053330.GA3882@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).