public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mutt-1.6.0-1
Date: Wed, 06 Apr 2016 10:43:00 -0000	[thread overview]
Message-ID: <5704E829.1060808@gmail.com> (raw)
In-Reply-To: <CAFo71_5C4stSvWjkTcN7N6pzFfGF=BY4d1hH+4TP7xtO3_5G9g@mail.gmail.com>

On 06/04/2016 11:32, Ismail Donmez wrote:
> Hi,
>
> On Wed, Apr 6, 2016 at 12:22 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>> A counter example:
>> http://chbrauner.blogspot.de/2014/02/mutt-compiled-against-ncurses-and.html
>>
>> try and let me know
>
> I am not using a mutt colorscheme but a mintty one which mutt fails to
> render. I will, however, try the change but a quote from the page
>
> "The solution is to replace a lot of the very specific color
> specifications of the colorscheme by the value default. "
>
> This proves the point that mutt is unable to use 256-color specifications.
>
> Thanks,
> Ismail

ncurse can handle 256 color.
I doubt that mutt is different from other programs.


which TERM variable are you using ?

  $ TERM="xterm"
  $ tput colors
8

$ TERM="xterm-256color"
$ tput colors
256




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

  reply	other threads:[~2016-04-06 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 15:11 Marco Atzeri
2016-04-05 16:35 ` Ismail Donmez
2016-04-06  8:59   ` Marco Atzeri
2016-04-06  9:14     ` Ismail Donmez
2016-04-06  9:23       ` Marco Atzeri
2016-04-06  9:33         ` Ismail Donmez
2016-04-06 10:43           ` Marco Atzeri [this message]
2016-04-06 12:16             ` Ismail Donmez
2016-04-10 12:01               ` Ismail Donmez

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=5704E829.1060808@gmail.com \
    --to=marco.atzeri@gmail.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).