From: Mike Gran <spk121@yahoo.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "21677@debbugs.gnu.org" <21677@debbugs.gnu.org>,
"bug-guile-ncurses@gnu.org" <bug-guile-ncurses@gnu.org>
Subject: bug#21677: [Bug-guile-ncurses] Guile-NCurses test failure when built against NCurses 6.0
Date: Sat, 17 Oct 2015 16:50:16 +0000 (UTC) [thread overview]
Message-ID: <1933042933.1958255.1445100616496.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <1683863730.3263018.1444758001236.JavaMail.yahoo@mail.yahoo.com>
>>>> Guile-NCurses 1.6 has one test failure when built against NCurses
> 6.0:
>>>>
>>>
>>>> FAIL: getwin/putwin: putwin
>>>> ERROR: getwin/putwin: getwin - arguments: ((srfi-34 #<condition
>
>>>> &curses-wrong-type-arg-error [arg: #f expected-type: window]
>> e7d210>))
>>>
>>>> Any ideas?
Okay. I've tried some of the combinations of Guile, Ncurses and OS
and getwin/putwin is broken in different ways with different combinations.
No one uses those functions anyway, as far as I can tell.
I think the plan is to put out a guile-ncurses 1.7 that just eliminates
it. And then soon, put out a guile-ncurses 2.0 that will require guile-2.0.11+
and ncurses 6.0+, and re-evaluate whether it is worth it to fix
those functions.
I'll try to put out guile-ncurses 1.7 this week.
-Mike
next prev parent reply other threads:[~2015-10-17 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:54 bug#21677: Guile-NCurses 1.6 test failure with ncurses 6.0 Ludovic Courtès
2015-10-13 8:59 ` bug#21677: Guile-NCurses test failure when built against NCurses 6.0 Ludovic Courtès
2015-10-13 17:03 ` bug#21677: [Bug-guile-ncurses] " Mike Gran
2015-10-13 17:11 ` Ludovic Courtès
2015-10-13 17:40 ` Mike Gran
2015-10-17 16:50 ` Mike Gran [this message]
2015-10-18 10:20 ` Ludovic Courtès
2015-11-03 23:15 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1933042933.1958255.1445100616496.JavaMail.yahoo@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=21677@debbugs.gnu.org \
--cc=bug-guile-ncurses@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).