public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dawid Ferenczy <ferenczy@volny.cz>
To: cygwin@cygwin.com
Subject: Re: Screen crippled by applications using alternative screen
Date: Sat, 26 Apr 2014 18:49:00 -0000	[thread overview]
Message-ID: <loom.20140426T203354-220@post.gmane.org> (raw)
In-Reply-To: <20140425173617.GB346@ednor.casa.cgf.cx>

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:

> "doesn't send ANSI codes to the console" doesn't make a lot of sense.
> "Cygwin" doesn't send ANSI codes to the windows console since the windows
> console doesn't understand ANSI codes.

I didn't know that. So how does it work, that I'm able to set cmd.exe window 
title with ANSI escape sequences bellow?

\[\033]0;\w\007\]

It sets cmd.exe window title to the current working directory in bash. Also 
colors in bash are set by ANSI escape sequences.

Sorry for maybe stupid questions, but I'm web applications developer not 
system developer. I don't know how that things work.


> 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.
> 
> cgf

Actually I don't want Cygwin to send ANSI escape sequences, I just would 
like to use Cygwin for doing my job, it's really great, but this screen 
crippling makes it really hard. I'm ready to help as much as I can, but I 
just need your help.

Have a nice day.


-- 
 Dawid Ferenczy
 http://twitter.com/DawidFerenczy



--
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

  parent reply	other threads:[~2014-04-26 18:49 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 [this message]
2014-05-01 10:14   ` Maximus5
2014-05-01 22:10     ` Larry Hall (Cygwin)
2014-05-02  5:33       ` Christopher Faylor
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=loom.20140426T203354-220@post.gmane.org \
    --to=ferenczy@volny.cz \
    --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).