Don cohen wrote:
>These seem not to work in 2.38 downloaded from
>http://sourceforge.net/project/showfiles.php?group_id=1355
>e.g., clisp-2.38-x86_64-unknown-linux-gnu-2.6.9.tar.gz
Do you mean working as functional or available?
>I notice that they do seem to work in clisp.i386 2.38-1.fc4
>I do notice that working with-keyboard seems to correlate with
>#+screen. Is that coincidence? Can it be made to work even when
>#-screen?
lispbibl.d shows that they share the same conditions for availability:
#if ((defined(UNIX) && !defined(NEXTAPP) || defined(MAYBE_NEXTAPP)) && !defined\
(NO_TERMCAP_NCURSES)) || defined(WIN32_NATIVE)
Alas, there's #+SCREEN on the Lisp side to detect it, but there's no #+KEYBOARD nor something equivalent.
In a CLISP version that does not provide this functionality, what would you expect:
a) no symbol named ext:with-keyboard available?
b) symbol present, but not fbound?
c) symbol only internal, not exported from EXT?
Of course, that does not explain why it "seems not to work" in the package you mention.
Regards,
Jorg Hohle.

Thread view

Don cohen wrote:
>These seem not to work in 2.38 downloaded from
>http://sourceforge.net/project/showfiles.php?group_id=1355
>e.g., clisp-2.38-x86_64-unknown-linux-gnu-2.6.9.tar.gz
Do you mean working as functional or available?
>I notice that they do seem to work in clisp.i386 2.38-1.fc4
>I do notice that working with-keyboard seems to correlate with
>#+screen. Is that coincidence? Can it be made to work even when
>#-screen?
lispbibl.d shows that they share the same conditions for availability:
#if ((defined(UNIX) && !defined(NEXTAPP) || defined(MAYBE_NEXTAPP)) && !defined\
(NO_TERMCAP_NCURSES)) || defined(WIN32_NATIVE)
Alas, there's #+SCREEN on the Lisp side to detect it, but there's no #+KEYBOARD nor something equivalent.
In a CLISP version that does not provide this functionality, what would you expect:
a) no symbol named ext:with-keyboard available?
b) symbol present, but not fbound?
c) symbol only internal, not exported from EXT?
Of course, that does not explain why it "seems not to work" in the package you mention.
Regards,
Jorg Hohle.

Hoehle, Joerg-Cyril writes:
> Don cohen wrote:
> >These seem not to work in 2.38 downloaded from
> >http://sourceforge.net/project/showfiles.php?group_id=1355
> >e.g., clisp-2.38-x86_64-unknown-linux-gnu-2.6.9.tar.gz
> Do you mean working as functional or available?
Well, the symbols are available. The stuff needed to make them
functional is not.
> >I notice that they do seem to work in clisp.i386 2.38-1.fc4
>
> >I do notice that working with-keyboard seems to correlate with
> >#+screen. Is that coincidence? Can it be made to work even when
> >#-screen?
> lispbibl.d shows that they share the same conditions for availability:
> #if ((defined(UNIX) && !defined(NEXTAPP) || defined(MAYBE_NEXTAPP)) && !defined\
> (NO_TERMCAP_NCURSES)) || defined(WIN32_NATIVE)
>
> Alas, there's #+SCREEN on the Lisp side to detect it, but there's no #+KEYBOARD nor something equivalent.
>
> In a CLISP version that does not provide this functionality, what would you expect:
> a) no symbol named ext:with-keyboard available?
> b) symbol present, but not fbound?
> c) symbol only internal, not exported from EXT?
I'd expect (a). I'd also expect the dependency to be mentioned in impnotes.
But I don't understand what keyboard has to do with screen.
Why shouldn't it always be available?
> Of course, that does not explain why it "seems not to work" in the
> package you mention.
That's now easy: #-screen