Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53902 - [ncurses] Using 'default' as color returns inconsistent results
Attached to Project:
Arch Linux
Opened by David Thurstenson (thurstylark) - Monday, 01 May 2017, 15:17 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 03 May 2017, 15:42 GMT
Opened by David Thurstenson (thurstylark) - Monday, 01 May 2017, 15:17 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 03 May 2017, 15:42 GMT
|
DetailsWhen using an application that uses ncurses, the 'default' color returns inconsistent results.
More in-depth discussion of the bug itself here: https://github.com/vifm/vifm/issues/269 According to the bug-ncurses ML, this should be fixed in the latest release (6.0-20170429): https://lists.gnu.org/archive/html/bug-ncurses/2017-04/msg00037.html Version: 6.0+20170401-1 Steps to reproduce: For vifm: - Use 'default' as a color definition in your color scheme - Launch vifm |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 03 May 2017, 15:42 GMT
Reason for closing: Fixed
Additional comments about closing: ncurses 6.0+20170429-1
Wednesday, 03 May 2017, 15:42 GMT
Reason for closing: Fixed
Additional comments about closing: ncurses 6.0+20170429-1