ncurses attrset colour pair ignored in favour of bkgd

  • Done
  • quality assurance status badge
Details
2 participants
  • Liliana Marie Prikler
  • Roman Riabenko
Owner
unassigned
Submitted by
Roman Riabenko
Severity
normal
R
R
Roman Riabenko wrote on 28 Mar 2022 14:00
(address . bug-guix@gnu.org)
cfc762b6bc42fc574b0dad64319c4e566a8a136d.camel@riabenko.com
Hello

With ncurses, the "attrset" colour pair is ignored when the background
colour pair is set with "bkgd".

I ran into this issue when compiling robotfindskitten, but it is not
specific to that program and can be reproduced with the attached small
test code. When compiled with "gcc test.c -lncurses", "./a.out" is
expected to display the sample text in yellow (the brownish curses
equivalent of yellow), which is set with "attrset". It does so when
compiled as usual without guix. If compiled in guix, the sample text is
blue instead, which is set with "bkgd" for background and for some
reason is not overridden by "attrset". If the "bkgd" line is removed,
"attrset" works as usual.

This affects software compiled in a guix shell (guix environment), or
on a guix system, or with "guix build" and "guix install".

It does not seem to be caused by the terminal properties or environment
variables because it can be reproduced on the same Debian machine after
compiling (1) with guix (in a guix environment) and (2) without guix.

I tried compiling with guix having ncurses 6.2.20210619 (current guix)
and 6.2.20200212 (from the older guix image from the website and in
Debian bullseye). I tried compiling without guix on Debian with
development packages for ncurses 6.2+20201114-2 (bullseye) and 6.3-2
(bookworm) and on Fedora with its development package for ncurses
6.2.20210508.

I was pointed in a forum to "render_char" function in lib_addch.c, [1]
which defines how colour is applied. But there seem to be no
modifications to that in guix as far as I can see.

[1]:

Roman
#include <ncurses.h>

int main() {
initscr();
start_color();
init_pair ( 1, COLOR_BLUE, COLOR_BLACK );
init_pair ( 2, COLOR_YELLOW, COLOR_BLACK );
bkgd ( (chtype) COLOR_PAIR(1) );
attrset ( COLOR_PAIR(2) );
printw ( "NO WAR!" );
refresh();
getch();
endwin();
return 0;
}
L
L
Liliana Marie Prikler wrote on 29 Mar 2022 14:29
e2474a1c7e3efb4b3dc46ffb284aba98541bd1bc.camel@ist.tugraz.at
Am Montag, dem 28.03.2022 um 15:00 +0300 schrieb Roman Riabenko:
Toggle quote (1 lines)
> gcc test.c -lncurses
This is not a sufficient invocation to get ncurses working correctly.

$ ncursesw6-config --cflags
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -
I/gnu/store/9rrnm5hdjw7cy96a2a9rfgh6y08wsbmf-ncurses-
6.2.20210619/include

$ ncursesw6-config --libs
-L/gnu/store/9rrnm5hdjw7cy96a2a9rfgh6y08wsbmf-ncurses-6.2.20210619/lib
-Wl,-rpath=/gnu/store/9rrnm5hdjw7cy96a2a9rfgh6y08wsbmf-ncurses-
6.2.20210619/lib -lncursesw

$ pkg-config --cflags ncurses
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -
I/gnu/store/9rrnm5hdjw7cy96a2a9rfgh6y08wsbmf-ncurses-
6.2.20210619/include

$ pkg-config --libs ncurses
-Wl,-rpath=/gnu/store/9rrnm5hdjw7cy96a2a9rfgh6y08wsbmf-ncurses-
6.2.20210619/lib -lncursesw

Cheers
R
R
Roman Riabenko wrote on 7 Apr 2022 14:50
e5074a2c285b3eced54c06d4ff2a0e9620f236e3.camel@riabenko.com
Hello

Thank you for directing me to those options.

Setting _XOPEN_SOURCE to 500 or higher seems to restore the expected
functionality of attrset in ncurses for colour. _XOPEN_SOURCE is a
feature test macro, so it just determines that some functionality from
X/Open is used (X/OPEN 5 for _XOPEN_SOURCE 500, X/OPEN 6 for
_XOPEN_SOURCE 600, etc.). The program that is being compiled can have
its own tests for functionality that it needs. I can add "#define
_XOPEN_SOURCE 500" to the beginning of test.c from my previous email to
make it work as it should when built with guix. So, this is something,
the program could normally figure out itself without relying on curses
being implemented in a specific way.

There is a section on alternate configurations of ncurses in its manual
[1] noting that it may be necessary for some functionality of ncurses
to specify _XOPEN_SOURCE up to 600 for programs compiled against
ncurses when the latter was built with --enable-widec. Since this
option was chosen for ncurses in guix, it is fair enough that some
functionality may need _XOPEN_SOURCE 600, even if I am not sure how my
case is related to wide character support or what functionality from
X/Open is used.

[1]:

I believe that the above is enough to close this issue.

Roman
L
L
Liliana Marie Prikler wrote on 7 Apr 2022 14:52
a2859263b68659284f78d87252383547c5a3ff6c.camel@ist.tugraz.at
Am Donnerstag, dem 07.04.2022 um 15:50 +0300 schrieb Roman Riabenko:
Toggle quote (1 lines)
> I believe that the above is enough to close this issue.
Consider it closed.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 54607@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 54607
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch