cmucl.common-lisp.dev issueshttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues2023-12-26T23:08:59Zhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/62Document that hemlock has to be in core for the -edit and -slave options to b...2023-12-26T23:08:59ZRaymond ToyDocument that hemlock has to be in core for the -edit and -slave options to be available.As discussed in cmucl#260, hemlock has to be in the core for the command line options `-edit` and `-slave` to be available. That means dumping a core file that includes hemlock. Update the hemlock docs to mention that.As discussed in cmucl#260, hemlock has to be in the core for the command line options `-edit` and `-slave` to be available. That means dumping a core file that includes hemlock. Update the hemlock docs to mention that.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/16Add favicon2023-10-18T15:39:04ZRaymond ToyAdd faviconMaybe we should add a favicon for the site?Maybe we should add a favicon for the site?https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/59Navbar missing2023-10-13T14:06:34ZRaymond ToyNavbar missingVisit https://cmucl.common-lisp.dev/ and notice that the left navbar is missing. In Firefox, the console says:
```
Loading module from “https://unpkg.com/lit-html@3.0.0/lit-html.js?module” was blocked because of a disallowed MIME type (...Visit https://cmucl.common-lisp.dev/ and notice that the left navbar is missing. In Firefox, the console says:
```
Loading module from “https://unpkg.com/lit-html@3.0.0/lit-html.js?module” was blocked because of a disallowed MIME type (“text/plain”).
cmucl.common-lisp.dev
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://unpkg.com/lit-html@3.0.0/lit-html.js?module. (Reason: CORS request did not succeed). Status code: (null).
Module source URI is not allowed in this document: “https://unpkg.com/lit-html?module”.
```
We need to fix this. It doesn't work in Chrome either, although the console message is different.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/50Original cmucl design pdf is missing2023-08-16T00:56:40ZRaymond ToyOriginal cmucl design pdf is missingThe link to the [original cmucl design doc pdf](https://cmucl.common-lisp.dev/downloads/doc/CMUCL-design.pdf) is broken. However, cmucl.org has a copy.
Perhaps we need to add the pdf file (from cmucl.org) to this repo. Or add the orig...The link to the [original cmucl design doc pdf](https://cmucl.common-lisp.dev/downloads/doc/CMUCL-design.pdf) is broken. However, cmucl.org has a copy.
Perhaps we need to add the pdf file (from cmucl.org) to this repo. Or add the original TeX files here so the we rebuild it if necessary.
I also found out that the old versions of the user manual don't exist here either, but do on cmucl.org. Actually any of the links to the old docs are missing.
I think we should preserve these old docs here as well as on cmucl.org since cmucl.org gets the files from here.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/42Update docs for :locale external format2023-08-13T02:07:34ZRaymond ToyUpdate docs for :locale external formatIf https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/102 lands, we need to update the docs to explain what this is.If https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/102 lands, we need to update the docs to explain what this is.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/56Update c-call section to mention that char is signed2023-08-07T13:39:02ZRaymond ToyUpdate c-call section to mention that char is signedWe should mention in the manual that `c-call:char` is signed. `c-call:unsigned-char` is, obviously, unsigned. This is an important detail because in C, `char` can be either, and you have to use `signed char` or `unsigned char` to be su...We should mention in the manual that `c-call:char` is signed. `c-call:unsigned-char` is, obviously, unsigned. This is an important detail because in C, `char` can be either, and you have to use `signed char` or `unsigned char` to be sure to specify the signedness of a `char`.
But see also https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/251; when that lands, we'll need to update the manual again to make a note of that.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/58References to keywords/macros/specvars not rendered correctly in html and pdf2023-08-05T16:11:14ZRaymond ToyReferences to keywords/macros/specvars not rendered correctly in html and pdfWe have a macro `keyref` that is supposed to provide a cross-ref and have the displayed text printed out with a leading colon and with al the text in a fixed-width font for code. This works for the html doc but not the pdf doc.
The prob...We have a macro `keyref` that is supposed to provide a cross-ref and have the displayed text printed out with a leading colon and with al the text in a fixed-width font for code. This works for the html doc but not the pdf doc.
The problem is an incorrect definition of the `keyref` macro:
```plaintext
@macro keyref {arg}
@xref{\arg\, @kwd{\arg\}}
@end macro
```
The second arg is used for online docs (html). If there's a third arg, it's used for the printed doc (pdf). This needs to be updated to get the printed manual to use the keyword format. See https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Three-Arguments
This also applies to the `macref` and `specvarref` macros.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/52Move the Benchmarks, Ports, Projects pages to the Wiki.2023-06-18T02:49:00ZRaymond ToyMove the Benchmarks, Ports, Projects pages to the Wiki.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/55Check if anchors are in the right place2023-06-11T00:49:09ZRaymond ToyCheck if anchors are in the right placeBased on #54, we should check that all `@anchor`'s are in the right place.
I didn't check them all, but it appears that most (if not all) are in the wrong place. The anchors should come after the nodeBased on #54, we should check that all `@anchor`'s are in the right place.
I didn't check them all, but it appears that most (if not all) are in the wrong place. The anchors should come after the nodehttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/54Link to local-call is wrong.2023-06-11T00:04:33ZRaymond ToyLink to local-call is wrong.Visit [Structure Types](https://cmucl.common-lisp.dev/docs/cmu-user/html/Structure-Types.html). At the bottom of the page there's a link to "local-call". Clicking it takes us to [Tail Recursion Exceptions](https://cmucl.common-lisp.dev...Visit [Structure Types](https://cmucl.common-lisp.dev/docs/cmu-user/html/Structure-Types.html). At the bottom of the page there's a link to "local-call". Clicking it takes us to [Tail Recursion Exceptions](https://cmucl.common-lisp.dev/docs/cmu-user/html/Tail-Recursion-Exceptions.html#local_002dcall). I was not expecting that. I was expecting something in the section [Local Call](https://cmucl.common-lisp.dev/docs/cmu-user/html/Local-Call.html).
The [pdf version](https://cmucl.org/downloads/doc/cmu-user-letter.pdf) does link to the "Local Call" section.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/53Remove hemlock doc info from hemlock page2023-05-31T14:57:48ZRaymond ToyRemove hemlock doc info from hemlock pageThe [Hemlock page](https://cmucl.org/hemlock/index.html) lists the documentation for Hemlock. But this is already provided on the [Documentation page](https://cmucl.org/doc/index.html), so remove it.
See #49The [Hemlock page](https://cmucl.org/hemlock/index.html) lists the documentation for Hemlock. But this is already provided on the [Documentation page](https://cmucl.org/doc/index.html), so remove it.
See #49Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/51Make Wiki more discoverable by giving it a menu item2023-05-29T20:49:17ZRaymond ToyMake Wiki more discoverable by giving it a menu itemhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/45Missing database directory from cmucl2023-04-25T02:07:21ZRaymond ToyMissing database directory from cmuclIn https://gitlab.common-lisp.net/cmucl/cmucl/-/tree/master/src/docs, there's a directory `database` that isn't included here. We need to add that to this repo. There's also the files `doc-diff.lisp` and `rtguts.mss` that should be mov...In https://gitlab.common-lisp.net/cmucl/cmucl/-/tree/master/src/docs, there's a directory `database` that isn't included here. We need to add that to this repo. There's also the files `doc-diff.lisp` and `rtguts.mss` that should be moved over too.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/48Time stamps in files are broken2023-04-13T23:27:32ZRaymond ToyTime stamps in files are brokenThe timestamp in each HTML file is broken because they were written for xemacs. These need to be updated to work with emacs.The timestamp in each HTML file is broken because they were written for xemacs. These need to be updated to work with emacs.Raymond ToyRaymond Toyhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/44Indices for Hemlock implementer's manual are messed up2022-11-23T18:12:30ZRaymond ToyIndices for Hemlock implementer's manual are messed upThis is easiest to see in the [PDF
doc](https://cmucl.common-lisp.dev/docs/hem/cim/cim.pdf). Go to the
Function Index and look for `check-region-query-size`. This is
correct. When you visit that page, you'll notice that the next line
s...This is easiest to see in the [PDF
doc](https://cmucl.common-lisp.dev/docs/hem/cim/cim.pdf). Go to the
Function Index and look for `check-region-query-size`. This is
correct. When you visit that page, you'll notice that the next line
says `Region Query Size`, which is a Hemlock variable. But it's not
listed in the Variable Index. If you look at the Function Index,
you'll find `Region Query Size`.
The problem is [this](https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/blob/master/docs/hem/cim/cim.texi#L691):
```
@deffn {Function} {check-region-query-size} {@i{region}}
@deffnx {Hemlock Variable} {Region Query Size} @val{30}
...
@end deffn
```
The original [Scribe version](https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/blob/master/docs/hem/cim/cim.mss#L379) has:
```
@defun[fun {check-region-query-size}, args {@i[region]}]
@defhvar1[var {Region Query Size}, val {30}]
<description>
@enddefun
```
So in the conversion, we changed `@defun` for `@deffn {Function}`, and
`@defhvar1` to `@deffnx {Hemlock Variable}`.
But I guess `@deffn` puts everything defined with it in the Function
Index. I don't know how to fix this other than to break it into two
parts like so:
```
@defun {check-region-query-size} {@i{region}}
@end deffn
@defvr {Hemlock Variable} {Region Query Size} @val{30}
<description>
@end defvr
```
This kind of works, but there's an extra line between the two entries,
kind of making it look as if they're separate. (Well, because they
are.)
Other than rewriting the entry, I don't see how to fix this.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/32Convert hemlock docs2022-11-20T02:33:17ZRaymond ToyConvert hemlock docsThe hemlock docs are currently written using Scribe from CMU. It would be nice to have these docs converted to texinfo like the others so that we can have an up-to-date version that can be built with modern tools. I don't have access to ...The hemlock docs are currently written using Scribe from CMU. It would be nice to have these docs converted to texinfo like the others so that we can have an up-to-date version that can be built with modern tools. I don't have access to Scribe to build the hemlock docs.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/43Some pages don't have navigation links at the bottom2022-11-12T15:38:09ZRaymond ToySome pages don't have navigation links at the bottom@cshapiro wrote to me that some pages are missing navigation links at the bottom. Compare the pages:
- https://cmucl.common-lisp.dev/docs/cmu-user/html/The-SERVE_002dEVENT-Function.html
- https://cmucl.common-lisp.dev/docs/cmu-user/htm...@cshapiro wrote to me that some pages are missing navigation links at the bottom. Compare the pages:
- https://cmucl.common-lisp.dev/docs/cmu-user/html/The-SERVE_002dEVENT-Function.html
- https://cmucl.common-lisp.dev/docs/cmu-user/html/Without-Object-Sets.html
The second doesn't have any navigation links at the bottom of the page. Not sure why.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/40FAQ page is very wide on mobile2022-05-01T04:25:39ZRaymond ToyFAQ page is very wide on mobileVisit https://cmucl.common-lisp.dev/FAQ.html on a mobile device. The page is very wide. I'm guessing it's because of the code snippets. We should probably put the snippets into their own scrollable text section so that the overall pag...Visit https://cmucl.common-lisp.dev/FAQ.html on a mobile device. The page is very wide. I'm guessing it's because of the code snippets. We should probably put the snippets into their own scrollable text section so that the overall page can fit in the width of the device, as most other pages on the site already do.https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/39Notice: This project will be renamed in the coming week(s)2022-01-18T21:40:34ZErik HuelsmannNotice: This project will be renamed in the coming week(s)Hi,
This issue is to notify the owners of this project about an important upcoming change: the common-lisp.net administrators are working to move all hosted project sites to their own domains - at https://cmucl.common-lisp.dev/.
To ensu...Hi,
This issue is to notify the owners of this project about an important upcoming change: the common-lisp.net administrators are working to move all hosted project sites to their own domains - at https://cmucl.common-lisp.dev/.
To ensure the content of this repository will be correctly deployed to the new domain (instead of the current https://common-lisp.net/project/cmucl/ location), the rename of the repository is required.
No action is required from your side at this point. However, after the rename, you may need to adjust your git "remotes" for any local clones. Also, you may need to verify any triggers in your `.gitlab.yml` files elsewhere in your project, because they may refer to this repository by name.
Last, the old URL will permanently redirect to the new URL. Therefore, all extant links should continue to work. However, we recommend you eventually update all links you have control over to point directly to the new URL.
Kind regards,
Erik Huelsmann
common-lisp.net adminhttps://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/issues/37Site out-of-date2022-01-15T18:34:51ZRaymond ToySite out-of-dateVisit https://common-lisp.net/project/cmucl/doc/index.html and look at the text before Tips and Tricks. It shows a link for the IBM RT design. However !39 added a new list item for the Hemlock docs. It's not there and I don't know why...Visit https://common-lisp.net/project/cmucl/doc/index.html and look at the text before Tips and Tricks. It shows a link for the IBM RT design. However !39 added a new list item for the Hemlock docs. It's not there and I don't know why CI didn't update the site appropriately.Raymond ToyRaymond Toy