cmucl.common-lisp.dev issueshttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues2023-11-30T15:10:19Zhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/61Document ~ in pathnames2023-11-30T15:10:19ZRaymond ToyDocument ~ in pathnamesWhen cmucl#266 is implemented to support ~ in pathnames, we need to update the docs to reflect this.When cmucl#266 is implemented to support ~ in pathnames, we need to update the docs to reflect this.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/60Add favicon to repo2023-10-18T15:39:03ZRaymond ToyAdd favicon to repoAs mentioned in #16, a favicon was missing, but it actually exists on cmucl.org. However, it doesn't exist for cmucl.common-lisp.dev. We need to check in the favicon so that it is available for both.
But while we're at it, we might wa...As mentioned in #16, a favicon was missing, but it actually exists on cmucl.org. However, it doesn't exist for cmucl.common-lisp.dev. We need to check in the favicon so that it is available for both.
But while we're at it, we might want to consider updating the icon. Currently, it's a black lambda on a white background with some border lines. That's not how typical favicons look these days. I think this favicon looks better.
![favicon-32x32](/uploads/b935a3cd91e35470848a5663ea53e16f/favicon-32x32.png)Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/57Fix warnings produced by texinfo 7.0.22023-08-05T15:49:27ZRaymond ToyFix warnings produced by texinfo 7.0.2When building cmu-user with texinfo 7.0.2, there are warnings now:
```plaintext
TEXINPUTS=..:$TEXINPUTS makeinfo --info cmu-user.texi
debugger.texi:1240: warning: @ref node name should not contain `:'
debugger.texi:1247: warning: @ref n...When building cmu-user with texinfo 7.0.2, there are warnings now:
```plaintext
TEXINPUTS=..:$TEXINPUTS makeinfo --info cmu-user.texi
debugger.texi:1240: warning: @ref node name should not contain `:'
debugger.texi:1247: warning: @ref node name should not contain `:'
debugger.texi:1247: warning: @ref node name should not contain `:'
debugger.texi:1247: warning: @ref node name should not contain `:'
compiler.texi:237: warning: @xref cross-reference name should not contain `:' (possibly involving @keyref)
compiler.texi:1266: warning: @xref cross-reference name should not contain `:' (possibly involving @keyref)
compiler.texi:1266: warning: `.' or `,' must follow @xref (possibly involving @keyref)
compiler-hint.texi:140: warning: @xref cross-reference name should not contain `:' (possibly involving @keyref)
```
We should fix these warnings. And check the other docs to see if there are warnings there too.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/49Move the developer information to the Wiki2023-07-08T23:10:43ZCarl ShapiroMove the developer information to the WikiThis would make the website smaller and focused on providing just end user information.
Here is a proposal
- [x] Move the Benchmarks, Ports, Projects pages to the Wiki.
- [x] Move the documentation part of Hemlock page to the Documen...This would make the website smaller and focused on providing just end user information.
Here is a proposal
- [x] Move the Benchmarks, Ports, Projects pages to the Wiki.
- [x] Move the documentation part of Hemlock page to the Documentation page
- [ ] Move the rest of the Hemlock page to the FAQ
- [ ] Move the installation content from the Platforms page to the Download page
- [ ] Move the rest of the Platforms page to the Wiki
- [x] Make the Wiki more discoverable from the website perhaps by giving it a menu item
Moving does not necessarily mean preserving all of the content. Information that is obviously stale does not need to be preserved.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/47More cross-references needed2023-04-20T15:31:01ZRaymond ToyMore cross-references neededI noticed this while looking up the `optimize-interface` section. The last paragraph references `:context-declarations` in `with-compilation-unit`. Since `with-compilation-unit` is defined in the doc, the reference should be a link to ...I noticed this while looking up the `optimize-interface` section. The last paragraph references `:context-declarations` in `with-compilation-unit`. Since `with-compilation-unit` is defined in the doc, the reference should be a link to that section of the doc. There are quite a few references to `with-compilation-unit` in the doc; these should all be links.
I suspect there are many other things that should be links but aren't. We should make links for these to make it easier to find things in the manual.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/46Convert rtguts.mss to texinfo2023-02-26T15:39:49ZRaymond ToyConvert rtguts.mss to texinfoSince we have "rtguts.mss" that describes internal design for the RT PC, we should convert it to texinfo. This is mostly for historical reference since we do currently link to the [scanned pdf](https://figshare.com/articles/journal_cont...Since we have "rtguts.mss" that describes internal design for the RT PC, we should convert it to texinfo. This is mostly for historical reference since we do currently link to the [scanned pdf](https://figshare.com/articles/journal_contribution/Internal_design_of_CMU_common_Lisp_on_the_IBM_RT_PC/6606587/1).
It would be nice to have an HTML version of the doc.
Shouldn't be too hard since it's in Scribe format and is only 182 KB long, about the same size as the Hemlock Command Implementor's Manual.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/41Unicode section needs to be updated2022-10-15T14:12:46ZRaymond ToyUnicode section needs to be updatedSeveral issues I just noticed:
- [x] [open](https://cmucl.common-lisp.dev/docs/cmu-user/html/Files.html) doesn't even list the `:external-format` keyword and other keywords mentioned in the description.
- [x] [Methods for
strings](htt...Several issues I just noticed:
- [x] [open](https://cmucl.common-lisp.dev/docs/cmu-user/html/Files.html) doesn't even list the `:external-format` keyword and other keywords mentioned in the description.
- [x] [Methods for
strings](https://cmucl.common-lisp.dev/docs/cmu-user/html/Methods-for-Strings.html)
needs updating because some of these functions are actually in the
`unicode` package.
- [x] Update `string-downcase` and friends
- [ ] Update `string=` and friends
- [ ] Update `string-equal` and friends
- [ ] Update `string-trim` and friends
- [x] Add some missing documentation
- [x] `WITH-STRING-CODEPOINT-ITERATOR`
- [x] `WITH-STRING-GLYPH-ITERATOR`
- [x] New loop keywords `being the codepoint` and `being the glyph`
- [x] Reader supports `#\u+nnnn` where `nnnn` is larger than 16 bits. While not really quite legal, it is immensely useful.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/38Site requires Javascript2021-12-23T17:34:50ZRaymond ToySite requires JavascriptCurrently, the site requires Javascript to display the left menu. This means that you can't navigate if you have Javascript disabled. It would be nice if we didn't require Javascript---just pure html and css.Currently, the site requires Javascript to display the left menu. This means that you can't navigate if you have Javascript disabled. It would be nice if we didn't require Javascript---just pure html and css.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/33cmucl-history should be a bit more prominent2020-09-08T23:51:46ZRaymond Toycmucl-history should be a bit more prominentcmucl-history.html is linked from index.html with a link in the Tips and Tricks section. That's pretty hard to find. We should make it a bit more prominent, or at least not in the tips and tricks.cmucl-history.html is linked from index.html with a link in the Tips and Tricks section. That's pretty hard to find. We should make it a bit more prominent, or at least not in the tips and tricks.