From: Neil Zanella <nzanella@cs.mun.ca>
To: Marc Fortier <mfortier@site.uottawa.ca>
Cc: Cygwin Mailing List <cygwin@sources.redhat.com>
Subject: Re: Colors mess up terminal
Date: Thu, 23 Aug 2001 08:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0108231247080.5313-100000@garfield.cs.mun.ca> (raw)
In-Reply-To: <Pine.WNT.4.33.0108231017100.1584-100000@admin2>
On Thu, 23 Aug 2001, Marc Fortier wrote:
> On Thu, 23 Aug 2001 08:58:15 +0200, Corinna Vinschen wrote:
>
> > On Wed, Aug 22, 2001 at 05:52:14PM -0400, Marc Fortier wrote:
> >> Hello,
> >>
> >> I'm also using pine via cygwin/ssh and am getting strange display
> >> behaviour when colours are used. Is there a solution to this problem?
To implement colors portably you must use tput instead of the bash
escape sequences.
> >> In the meantime, I'll try to come up with a script that detects
> >> whether the term type is cygwin and run pine with no colour in that
> >> case.
tput knows about terminal capabilities and displays the colors only when
the given terminal supports them.
> > I'm running `mutt' in a console window using TERM=cygwin and have no
> > problems with it. Also `ls --color' works fine. What exactly means
> > "strange display behaviour"? Are you actually working in a console
> > window?
> >
> > Corinna
>
> Hello,
>
> I'll try to explain better.
>
> I'm running W2K with all the latest cygwin stuff, including
> openssh2.9p2. I ssh from cygwin to a linux box. echo $TERM replies
> cygwin. If I run pine without specifying to turn off colours, extra line
> feeds are added at the bottom of the screen, whether I'm in the menu,
> message index, or reading messages. In the index, this means I have to
> guess what message the cursor is over before I can open it. Also, some
> lines don't get updated properly a the top and bottom of the screen.
Try CTRL-L to update the screen.
>
> If I run pine with -color-style=no-colors, all is well. But it would
> be nice not to have to turn off colours.
>
> Marc
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-08-23 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 7:39 Marc Fortier
2001-08-23 7:54 ` Andrew Markebo
2001-08-23 9:35 ` Marc Fortier
2001-08-23 7:55 ` Corinna Vinschen
2001-08-23 8:19 ` Neil Zanella [this message]
2001-08-23 9:37 ` Marc Fortier
2001-08-23 10:16 ` Louis Bohm
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 12:20 Marc Fortier
2001-08-23 9:49 Marc Fortier
2001-08-22 14:47 Marc Fortier
2001-08-22 23:58 ` Corinna Vinschen
2001-05-30 14:57 Greg Bell
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=Pine.LNX.4.30.0108231247080.5313-100000@garfield.cs.mun.ca \
--to=nzanella@cs.mun.ca \
--cc=cygwin@sources.redhat.com \
--cc=mfortier@site.uottawa.ca \
/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).