emacs and scheme talk to each other https://jao.io/cgit/geiser/atom?h=0.33 2026-04-26T18:50:45Z 2026-04-26T18:50:45Z jao jao@gnu.org 2026-04-26T18:50:45Z urn:sha1:185191df527b51ce521084f8c32030e87dabb5e9 It all seems to boil down to ansi-color-filter not recognising the format used by guile-colorized, and leaving behind some control characters that we're cleaning manually after the fact. This is not a great solution, as it applies a guile bandage to all implementations: we should define an implementation-dependent filter for input coming from a remote repl, but the fact that it has also to be applied to connections complicates matters. 2024-07-06T15:37:23Z Jonas Bernoulli jonas@bernoul.li 2022-07-14T12:33:38Z urn:sha1:de52f0e36f1709181c1ce4e787d79208fa2cb870 - In the summary line, use three dashes to separate the file name from the summary. That is the convention, which some tools depend on, and for some libraries we already did it here too. - Capitalize the first word in the summary. That is the convention, and for some libraries we already did it here too. - For libraries that have a commentary, make sure it is placed in a "Commentary:" section. - Make sure the "Code:" heading, which separates the header from the code part of the library, exists in all files. 2024-07-06T15:37:23Z Jonas Bernoulli jonas@bernoul.li 2022-07-14T12:22:44Z urn:sha1:e3dd43e247591e588f530ed15867766aa9cc9482 Right above the changed lines we require `ring'. It is therefore not necessary to delay evaluation until `ring' has been loaded; we know it has already been loaded. 2024-05-23T00:28:48Z jao jao@gnu.org 2024-05-23T00:28:48Z urn:sha1:93daa64dbe33e563d2933cafcfe55a00f3874954 2023-12-15T21:34:19Z Jonas Bernoulli jonas@bernoul.li 2023-12-15T21:29:47Z urn:sha1:9cad7e90a4cdb22b35b01f682fcb8bba641b0a93 `dotimes' has a defect (and a fixme which is over a decade old) that causes a bogus (though technically correct) warning about VAR being unused, if RESULT is not omitted but does not use VAR. 2023-12-15T21:33:58Z Jonas Bernoulli jonas@bernoul.li 2023-12-15T21:29:45Z urn:sha1:b20dd4d77b92197d88d7cf3512fe202581d5c430 Emacs 30.0.50 has started to warn when this variable isn't set, presumably so that the default can be changed from nil to t in a few years. I see no reason not to use lexical-binding. 2022-01-31T13:43:08Z Jonas Bernoulli jonas@bernoul.li 2022-01-31T13:40:14Z urn:sha1:f7d91d04e3fcca40268439e702cb6c4f5c90ab98 2020-03-27T20:38:45Z Jonas Bernoulli jonas@bernoul.li 2020-02-25T13:32:18Z urn:sha1:3ceb31b71824e59e3f000edf7cb09ab86616d723 It's the convention and by following it we make a big step towards supporting outline navigation. The convention doesn't say much about what parts of the code are supposed to be part of that sections and what parts belong in a subsequent section. Here we put the `require' forms in this section and maybe some setup code, that's a popular approach. In most cases there was "" where we now insert "Code:". They both serve a similar purpose and we keep the former because some users depend on that for navigation. We even add this "" in libraries where it previously was missing. In some cases the permission statement was followed by a commentary, which obviously does not belong in the "Code:" section. In such cases add the conventional "Commentary:" section. 2019-05-15T00:27:41Z Jose Antonio Ortega Ruiz jao@gnu.org 2019-05-15T00:27:41Z urn:sha1:a30d7dd09c5c96d31e8df749e51cdfc2c346445a 2016-06-17T16:54:35Z Jose Antonio Ortega Ruiz jao@gnu.org 2016-06-17T16:54:35Z urn:sha1:35a1dfc04f0c4f60b2384c9b5e6c99e178384801 Avoid redefining font-lock-ensure, so that haskell-mode doesn't get mad at us. Should close github's #164.