gendl issueshttps://gitlab.common-lisp.net/gendl/gendl/-/issues2023-05-18T18:44:59Zhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/171Need method to align host SLIME to Docker version2023-05-18T18:44:59ZMark EvensonNeed method to align host SLIME to Docker versionThe user should have a way to quickly and precisely get a version of the SLIME packaged in Docker image.
Attempting to connect to `release-1868` via a contemporary SLIME in the host Emacs results in warning like
``` ...The user should have a way to quickly and precisely get a version of the SLIME packaged in Docker image.
Attempting to connect to `release-1868` via a contemporary SLIME in the host Emacs results in warning like
```
Versions differ: 2014-06-17 (slime) vs. 2.28 (swank). Continue? (y or n) y
```
After accepting the warning, swank fails to load missing classes referenced in the Docker SLIME.
Possibilties:
1. Somehow introspect and use the actual SLIME source in the Docker image
2. Provide a tag from <https://github.com/slime/slime> that may be precisely reproduced on the hostMark EvensonMark Evenson2023-05-11https://gitlab.common-lisp.net/gendl/gendl/-/issues/170Title unexpectedly refers to FreeNode2022-01-15T12:20:21ZErik HuelsmannTitle unexpectedly refers to FreeNode@dcooper The title of the project says "#gendl on irc.freenode.net"...
I'd expect it to refer to libera?@dcooper The title of the project says "#gendl on irc.freenode.net"...
I'd expect it to refer to libera?https://gitlab.common-lisp.net/gendl/gendl/-/issues/168Include sbcl in standard build pipeline.2021-07-23T02:40:03ZDave CooperInclude sbcl in standard build pipeline.Prolly best to use one of etimmons' docker images for this.Prolly best to use one of etimmons' docker images for this.Dave CooperDave Cooperhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/167Build failure in latest SBCL2023-05-02T16:42:05ZZach BeaneBuild failure in latest SBCLPosting bug report for #<BRANCHED-GIT-SOURCE "gendl" "https://gitlab.common-lisp.net/gendl/gendl.git">
Building with SBCL 2.1.6 / ASDF 3.3.1 for quicklisp dist creation.
Trying to build commit id 88dddfffec005ab599b453cce7e6b21e9ad9360...Posting bug report for #<BRANCHED-GIT-SOURCE "gendl" "https://gitlab.common-lisp.net/gendl/gendl.git">
Building with SBCL 2.1.6 / ASDF 3.3.1 for quicklisp dist creation.
Trying to build commit id 88dddfffec005ab599b453cce7e6b21e9ad9360a
*bus* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*dom* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A28293}>: The value * is not of type LIST
```
*gendl* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*geom-base* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*geysr* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*graphs* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*gwl-graphics* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*gwl* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*ledger* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*regression* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*robot* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*surf* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*ta2* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*tasty* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*translators* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1040CD8303}>: The value * is not of type LIST
```
*tree* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*wire-world* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
*yadd* fails to build with the following error:
```
Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A18103}>: The value * is not of type LIST
```
[Full log here](http://report.quicklisp.org/2021-07-02/failure-report/gendl.html)https://gitlab.common-lisp.net/gendl/gendl/-/issues/166Some systems failed to build for Quicklisp dist2021-07-05T02:19:02ZZach BeaneSome systems failed to build for Quicklisp distBuilding with SBCL 2.0.9.125-5f9d19d4a / ASDF 3.3.1 for quicklisp dist creation.
Commi...Building with SBCL 2.0.9.125-5f9d19d4a / ASDF 3.3.1 for quicklisp dist creation.
Commit id 1ba9be0c196ac3c029ef9fc5a65d5d2b05e6dc51
*gendl-asdf* fails to build with the following error:
```
; caught ERROR:
; READ error during COMPILE-FILE: Package GENDL does not exist. Line: 24, Column: 23, File-Position: 683 Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/quicklisp/quicklisp-controller/dist/build-cache/gendl/9f226fbcc1540609e85b5f9702453b3af8477703/gendl-devo-1ba9be0c-git/gendl-asdf.lisp" {10051E36F3}>
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001720103}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "gendl-asdf" "gendl-asdf">
```
[Full log here](http://report.quicklisp.org/2020-11-11/failure-report/gendl.html)https://gitlab.common-lisp.net/gendl/gendl/-/issues/165Gendl installation2021-07-23T02:46:31ZWojciech PasiekaGendl installationI am on CMUCL - is there any fix for it, as the "paserve" is NOT in the quicklisp?
> (ql:quickload "gendl")
To load "gendl":
Load 1 ASDF system:
gendl
; Loading "gendl" ...I am on CMUCL - is there any fix for it, as the "paserve" is NOT in the quicklisp?
> (ql:quickload "gendl")
To load "gendl":
Load 1 ASDF system:
gendl
; Loading "gendl"
System "paserve" not foundhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/164surf, regression don't build today2021-07-23T02:46:53ZZach Beanesurf, regression don't build todayBuild log is here -- http://report.quicklisp.org/2018-12-06/failure-report/gendl.html#surfBuild log is here -- http://report.quicklisp.org/2018-12-06/failure-report/gendl.html#surfhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/163Default loading fails in devo2017-04-10T15:43:27ZGail ZachariasDefault loading fails in devoIn a bare ccl and devo branch, (ql:quickload :gendl) fails for me with
> Error: System "paserve" not found
The problem seems to be that asdf preloads dependent asd files before loading code, and gwl.asd has conditionalizations on #+za...In a bare ccl and devo branch, (ql:quickload :gendl) fails for me with
> Error: System "paserve" not found
The problem seems to be that asdf preloads dependent asd files before loading code, and gwl.asd has conditionalizations on #+zacl, but zacl the library (as opposed to zacl the asd file) hasn't been loaded yet when gwl.asd is loaded.Dave CooperDave Cooperhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/162Custom User Interface chapter needs expansion2017-08-21T19:04:22ZDave CooperCustom User Interface chapter needs expansionThe chapter [here](documentation/tutorial/source/custom-user-interfaces.lisp) needs to be expanded upon.
If you start looking through it in the Lisp source and the HTML tutorial you can try to spin up the simple examples.
In the next ...The chapter [here](documentation/tutorial/source/custom-user-interfaces.lisp) needs to be expanded upon.
If you start looking through it in the Lisp source and the HTML tutorial you can try to spin up the simple examples.
In the next day or so I will provide instructions for getting a testbed going with the Stripe payments app and other examples.Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/161Slime loses connection if new CL is opened which does not have glime loaded, ...2017-04-10T15:43:27ZDave CooperSlime loses connection if new CL is opened which does not have glime loaded, after glime.el is loaded into the emacsIf you do
```
(load-glime)
```
this will compile & load `glime.lisp`.
If you then
```
M-x load-file .../glime.el
```
it will enable the emacs extentions which make completions etc work better in glime.
However if you now sp...If you do
```
(load-glime)
```
this will compile & load `glime.lisp`.
If you then
```
M-x load-file .../glime.el
```
it will enable the emacs extentions which make completions etc work better in glime.
However if you now spawn a new Lisp from the same Slime/emacs session, e.g. with
```
M-- M-x slime
```
and load Gendl on top of it, but without glime loaded, now you will get errors and lose the Slime connection, if you try to edit a Gendl file.Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/160Tags missing from HTML output2017-08-21T19:04:22ZDave CooperTags missing from HTML outputThis Issue presents a simple initial exercise, and as a side-effect it's intended for getting up to speed on how the Tutorial is being generated.
If it will help to have more explanation of what is actually going on to generate the m...This Issue presents a simple initial exercise, and as a side-effect it's intended for getting up to speed on how the Tutorial is being generated.
If it will help to have more explanation of what is actually going on to generate the manual, then please say the word and I'll provide more description here in the comments.
As a first exercise, please load and generate the tutorial as follows:
```
GDL-USER> (ql:quickload :tutorial)
GDL-USER> (gendl-doc::make-html-and-css)
```
Notice all the warnings various markup tags "not recognized."
Find where these warnings are coming from and try to add the missing markup tags.Dave CooperDave Cooperhttps://gitlab.common-lisp.net/gendl/gendl/-/issues/159Object inputs are not filtering as normal messages do2017-04-10T15:43:27ZDave CooperObject inputs are not filtering as normal messages doIn the following snippet:
```
(in-package :gwl)
(define-object base-clnet-mixin (base-ajax-sheet)
:objects ((proto :type 'base-ajax-sheet
:u
```
the list of completions in minibuffer continues to display all ...In the following snippet:
```
(in-package :gwl)
(define-object base-clnet-mixin (base-ajax-sheet)
:objects ((proto :type 'base-ajax-sheet
:u
```
the list of completions in minibuffer continues to display all available input-slots, even after typing the `:u`. It should filter down to ui-specific-layout-js and use-jquery?
This appears to be an issue wether `:u` or `u` is entered (but normally of course these are given as keyword symbols).Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/158slime-documentation fails when symbol not in package2017-04-10T15:43:27ZGail Zachariasslime-documentation fails when symbol not in packagem-x slime-documentation fails when invoked on a symbol that doesn't exist (i.e. is not interned in the current package). That's the wrong thing for messages, which are package independent.m-x slime-documentation fails when invoked on a symbol that doesn't exist (i.e. is not interned in the current package). That's the wrong thing for messages, which are package independent.Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/157Gendl Function arguments not showing up in Glime2017-04-10T15:43:27ZDave CooperGendl Function arguments not showing up in Glime
Please try the following snippet:
```
(in-package :gdl-user)
(define-object try (box)
:computed-slots ((top-vector (the (face-normal-vector
```
After the `(face-normal-vector` I would think you should see the argumen...
Please try the following snippet:
```
(in-package :gdl-user)
(define-object try (box)
:computed-slots ((top-vector (the (face-normal-vector
```
After the `(face-normal-vector` I would think you should see the argument list for the `face-normal-vector` message of `base-object`, which is `(direction)`.
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/156Glime not showing messages in computed-slots2017-04-10T15:43:27ZDave CooperGlime not showing messages in computed-slots
Ok here's another one --- Please try the following snippet:
```
(in-package :gdl-user)
(define-object test-box (box)
:computed-slots
((linear-size (+ (the
```
If you put the cursor after the `the`, I would expect ...
Ok here's another one --- Please try the following snippet:
```
(in-package :gdl-user)
(define-object test-box (box)
:computed-slots
((linear-size (+ (the
```
If you put the cursor after the `the`, I would expect messages from `box` to show up (because `box` is a mixin here). But, i'm only seeing
```
(the &rest reference-chain)
```
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/155required input not showing up in Glime for points-display2017-04-10T15:43:27ZDave Cooperrequired input not showing up in Glime for points-displayYou should be able to replicate by making the following:
```
(define-object try ()
:objects
((points-disp :type 'points-display
:...
```
At the `:...`, I think the minibuffer should be showing
...You should be able to replicate by making the following:
```
(define-object try ()
:objects
((points-disp :type 'points-display
:...
```
At the `:...`, I think the minibuffer should be showing
`&required points`
seeing as `points` is a required input-slot for `'points-display`. However it is only showing the `&optional` input-slots, which appear to be coming from the base-object mixin.
I have yet to do really comprehensive testing, but other objects I've seen which have required input-slots show up with them properly listed under the `&required` section...
Gail ZachariasGail Zachariashttps://gitlab.common-lisp.net/gendl/gendl/-/issues/154cosmetic: links in readme still point to github2017-04-10T15:43:27ZDaniel KochmaĆskicosmetic: links in readme still point to githubminor issueminor issuehttps://gitlab.common-lisp.net/gendl/gendl/-/issues/153cl-lite fails on :create-asd-file? with relative pathname2017-04-10T15:43:27ZDave Coopercl-lite fails on :create-asd-file? with relative pathname*Created by: genworks*
It appears that cl-lite generates bogus .asd files when called on a relative pathname with :create-asd-file? t.
I have called it on surf/ directory with full pathname, so the .asd file there is now correct.
...*Created by: genworks*
It appears that cl-lite generates bogus .asd files when called on a relative pathname with :create-asd-file? t.
I have called it on surf/ directory with full pathname, so the .asd file there is now correct.
But, the cl-lite itself needs to be fixed to generate proper .asd files when called with relative pathnames.
**Imported comments:**
*By genworks on 2013-11-01 03:46:50 UTC*
Fixed. https://gitlab.common-lisp.net/gendl/gendl/-/issues/152gwl:start-gwl does not roll over to next available port for Allegroserve2017-04-10T15:43:27ZDave Coopergwl:start-gwl does not roll over to next available port for Allegroserve*Created by: genworks*
Currently crashes when trying to start AllegroServe on port 9000 when one is already running.
**Imported comments:**
*By genworks on 2011-11-18 23:24:40 UTC*
This is duplicated in Issue #8.
*Created by: genworks*
Currently crashes when trying to start AllegroServe on port 9000 when one is already running.
**Imported comments:**
*By genworks on 2011-11-18 23:24:40 UTC*
This is duplicated in Issue #8.
https://gitlab.common-lisp.net/gendl/gendl/-/issues/151nurbs-to-beziers sometimes unstable for rational NURBS curves2017-04-10T15:43:27ZDave Coopernurbs-to-beziers sometimes unstable for rational NURBS curves*Created by: genworks*
Just like the title says, and this is very much affected by the *display-tolerance* parameter.
We have example code which throws the error (in Genworks Support email).
Note that the code for the smlib inte...*Created by: genworks*
Just like the title says, and this is very much affected by the *display-tolerance* parameter.
We have example code which throws the error (in Genworks Support email).
Note that the code for the smlib interface module is not part of this git repo - issues relating to this module might be moved to a different Issues list.
**Imported comments:**
*By genworks on 2015-01-30 23:23:59 UTC*
Moved to internal tracking list.