unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: 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: Tue, 13 Oct 2015 19:11:50 +0200	[thread overview]
Message-ID: <87612asnft.fsf@gnu.org> (raw)
In-Reply-To: <2104732111.3249767.1444755838015.JavaMail.yahoo@mail.yahoo.com> (Mike Gran's message of "Tue, 13 Oct 2015 17:03:57 +0000 (UTC)")

Mike Gran <spk121@yahoo.com> skribis:

>> On Tuesday, October 13, 2015 1:59 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>> > Hello,
>> 
>> 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?
>
> getwin/putwin save and restore a representation of a screen to a file.
> That file format has changed for ncurses 6.  Their binding is
> probably the least robust of the many functions in guile-ncurses.
>
> I'll see what I can do with regards to a fix.

OK.

Any suggestions on how to fix it or work around it in Guix?  Or maybe we
should just wait for whatever fix you come up with?

Thanks!

Ludo’.

  reply	other threads:[~2015-10-13 17:12 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 [this message]
2015-10-13 17:40       ` Mike Gran
2015-10-17 16:50         ` Mike Gran
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=87612asnft.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=21677@debbugs.gnu.org \
    --cc=bug-guile-ncurses@gnu.org \
    --cc=spk121@yahoo.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. 
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).