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 09:23:00 -0000 [thread overview]
Message-ID: <5704D573.5020909@gmail.com> (raw)
In-Reply-To: <CAFo71_6XkS=3kBAW4eZ3stEYg3g7Ee_yVh0nUCZKATx+bs53Qw@mail.gmail.com>
On 06/04/2016 11:13, Ismail Donmez wrote:
> On Wed, Apr 6, 2016 at 11:59 AM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>>
>>
>> On 05/04/2016 18:35, Ismail Donmez wrote:
>>>
>>> Hi,
>>>
>>> On Tue, Apr 5, 2016 at 6:03 PM, Marco Atzeri <marco.atzeri@gmail.com>
>>> wrote:
>>>>
>>>> New versions 1.6.0-1 of
>>>>
>>>> mutt
>>>>
>>>> is available in the Cygwin distribution:
>>>>
>>>> CHANGES
>>>> Last upstream release. First 1.6.x
>>>
>>>
>>> Thanks for the update! Could you maybe build it with slang? That way
>>> mutt can support 256 colors.
>>>
>>> Regards,
>>> ismail
>>>
>>> --
>>
>>
>> I don't find anything in the mutt documentation that says
>> that 256 color requires slang.
>> Have you some reference ?
>
> Yes, https://superuser.com/questions/695867/not-able-to-use-solarized-in-mutt
> I have the same problem and compiling mutt against slang fixes the issue.
>
> Thanks.
>
A counter example:
http://chbrauner.blogspot.de/2014/02/mutt-compiled-against-ncurses-and.html
try and let me know
Regards
Marco
--
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:[~2016-04-06 9:23 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 [this message]
2016-04-06 9:33 ` Ismail Donmez
2016-04-06 10:43 ` Marco Atzeri
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=5704D573.5020909@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).