I think definitions in the glossary should have HTML IDs, so that they can be hyperlinked from other entries in CLCS. That's what the HyperSpec does, and it's quite useful.

html_in/Glossary.html has anchors that use the name attribute:

<a name="index-absolute"></a>

But they're not present in html_out/Glossary.html. Also, the name attribute for the <a> tag is deprecated in HTML5.

I think the correct way to do it is like this, using the id attribute instead:

<dt id="absolute"><b>absolute</b></dt>
<dd><p><i>adj.</i>
  1. (of a <i>time</i>)
     representing a specific point in time.
  2. (of a <i>pathname</i>)
     representing a specific position in a directory hierarchy.
  See <i>relative</i>.
</p>
</dd>

Hi

This is a feature request for Documentation and Instructions For How To Build The Website From The Python Scripts. and other files. There is no Makefile so I'm not sure which one is the entry point script and what they are for. I think it should be documented for the community users and contributors.

On the page for destructuring lambda lists (https://cl-community-spec.github.io/pages/Destructuring-Lambda-Lists.html), it explicitly says "except for &environment", but then lists "envvar ::= [&environment var]", the envvar is not reference anywhere on the page including by lambda-list. It should be removed. It is covered on the macro lambda list page (https://cl-community-spec.github.io/pages/Macro-Lambda-Lists.html).

The specialized lambda list page (https://cl-community-spec.github.io/pages/Specialized-Lambda-Lists.html) has the opposite issue. There is a specializer mentioned, but it does not appear in the grammar. There is also an extra set of parenthesis around specializer. The grammar is properly defined on the defmethod page (https://cl-community-spec.github.io/pages/defmethod.html) and should appear the same here. &allow-other-keys is strangely in bold on that page though. There is also something a little funny going on with the &key, but I'm not sure how to describe it.

it looks like some un-rednered latex perhaps. \left{i_0,i_1,\dots,i_{r-1}\right}. On this page: https://cl-community-spec.github.io/pages/array.html

Thank you for the great amount of work put into the new specification site.

Would it be possible to add support for viewing the spec on mobile devices?

I read a lot of content on my mobile phone (especially during prolonged illness).

Unfortunately it's very hard to navigate and scale content on a mobile phone (Google Pixel 2 XL) - see example screenshot

Thank you

Hi,

Would it be possible to enable GitHub Discussion so we can ask questions that are not issues and discuss the project?

Do you have any thoughts on distributing this documentation in PDF?

a page like this http://clhs.lisp.se/Body/f_mod_r.htm

Interestingly the mod type specifier is not missing.

CLCS

CLHS

WDYT

Hi, I'd like to package the CLCS for Guix.

I think the easiest way might be to provide a Makefile for creating a distributable single info file that I can then install to the /gnu/store/... directory.

WDYT

Do you accept new examples?

For example,

I would like to contribute fresh examples for gethash on this page:

https://cl-community-spec.github.io/pages/gethash.html

Brunzus helpfully highlighted a worrying discrepancy.

The best dpans source I can recommend is my fork, which is directly derived from Xach's fork, which is directly derived from the original dpans download, so it is extremely likely to be correct. (The advantage of my fork over Xach's is the user-friendly pdf directory, see the README there for more information.)

That has the correct information. Here is the corresponding tex source.

I love this project.

This page is looking a little funny
https://cl-community-spec.github.io/pages/multiple_002dvalue_002dprog1.html

multiple-value-prog 1 ⇒ first-form {form}*

Thanks for the great work!

I'm curious about one question. Usually, turning texi files into other format is much easier, as that's one goal of texi. The original dpANS3 document however was written in tex with lots of obscure tex macros. How did you turn those into texi files?

Hi,

Can you please provide the .tex files you used to produce the html? I imagine you had to make modifications to the .tex files for them to be converted to html.

I would like to use them as a starting point, to then add all the changes by hand of the last dpANS3R draft. Per your comment:

There are still some issues. One of them is that I started out using not the latest version of the draft, so that X3J13 changes were not included.

Thanks!

Unless I am mistaken this sentence describing unless:
"Otherwise, if the test-form yields false, the forms are not evaluated, and the unless form returns nil"
Should read
"Otherwise, if the test-form yields true, the forms are not evaluated, and the unless form returns nil"

The Hyperspec has the same error though.

Returns the elements of the list as multiple values_2.

WDYT

Hi,

Is there an index mapping symbol to html locations, so that we can implement an emacs mode to match the hyperspec one that can be called to describe a symbol?

Hello,

Do what you want but I thought I'd let you know about my CLHS replacement project which is coming up in 2023.

I don't claim I'm unbiased, but I certainly think I'm by far the one who has the best shot at this.

So probably only work on this if you don't mind the duplication of effort. ;)

CLiki lists many errors in the ANSI standard, and some of them are quite glaring. For instance, SETQ is described as a "special form" rather than "special operator". Is it outside the scope of this project to amend these errors?

https://www.cliki.net/ANSI%20Clarifications%20and%20Errata

The readme states:

The content is left unchanged at this stage*, the only work right now goes into the presentation.

Which seems to imply a possibility of this being addressed.

Hi,

Would you accept a PR to add an example to call-next-method?

The .info files are an output from the original documentation build. I might be wrong, but the original source files which created the .info files still look to be available: http://ftp.gnu.org/pub/gnu/gcl/old/gcl-info+texi.tgz

There are a lot of errors and warnings when building but it still (just about) builds:

wget http://ftp.gnu.org/pub/gnu/gcl/old/gcl-info+texi.tgz
tar -xzf gcl-info+texi.tgz
cd gcl-info
texi2any --html --error-limit=999999999 --force gcl.texi
xdg-open gcl/index.html

As a suggestion, it might be feasible to just update and fix the original texi files to work with current version of texinfo. From there you could export directly to HTML or to an intermediary format to pass to a different tool.

Hello, while browsing the spec this one returned a 404: https://cl-community-spec.github.io/pages/Array-Dimensions.html#Array-Dimensions

CLHS: http://www.lispworks.com/documentation/HyperSpec/Body/f_ar_dim.htm

this one too: https://cl-community-spec.github.io/pages/Array-Rank.html#Array-Rank

this one has no content: https://cl-community-spec.github.io/pages/Multidimensional-Arrays.html#Multidimensional-Arrays

Best,

IDK how to help (I only see a Python script with no dev instructions)

Hi! Looks like the arrow is incorrectly placed for macroexpand-1 at macroexpand page, it should be

• macroexpand-1 form &optional env ⇒ expansion, expanded-p, instead of currently present
• macroexpand-1 ⇒ form &optional env expansion, expanded-p

P.S. Thanks for the awesome project!