| Newsgroups |
gmane.lisp.ilisp.devel |
| Message-ID |
<[email protected]> |
1. I should have mailed you about this one before, sorry. The version
6.0 of the Common Lisp Hyperspec now available at our website is in
8.3 filename format. Therefore the inlined symbol -> page mapping in
extra/hyperspec-naggum.el
will not work.
For HyperSpec v5.0+ the data from the page
http://www.xanalys.com/software_tools/reference/HyperSpec/Data/Map_Sym.txt
is needed. I suggest adding this as an alternate mapping rather than
replacing the old (HyperSpec v4.0-) data because some users will still
be using - and prefer - their previously downloaded copies of
HyperSpec v4.0- on local file system.
The other hyperspec-* files will also need modifying. I wonder if
they're all used in practice?
2. It would be helpful if this could be added to the
'o Xanalys LispWorks (formerly Harlequin LispWorks)' instructions in the file
ilisp/INSTALLATION:
----------------------------------------------------------------------
LispWorks users who wish to use the CAPI (LispWorks GUI toolkit) via
ILISP can create a suitable image with this script (call it
'console-capi.lisp')
(in-package "CL-USER")
(load-all-patches)
(compile (defun my-restart ()
#+Unix
(capi:ensure-motif-libraries)
(mp:initialize-multiprocessing)))
(save-image "lw-ilisp-capi" :restart-function 'my-restart
:environment nil
#+Win32 :console #+Win32 t)
(quit)
This is because the CAPI requires multiprocessing, and on some Unix
platforms the GUI libraries that CAPI uses are normally loaded on
startup of the IDE, which we're bypassing with :environment nil for
ILISP.
----------------------------------------------------------------------
thanks
Dave
Dave Fox Email: [email protected]
Xanalys Inc, Barrington Hall, Tel: +44 1223 873879
Barrington, Cambridge CB2 5RG, England. Fax: +44 1223 873873
These opinions are not necessarily those of Xanalys.
_______________________________________________
Ilisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ilisp-devel