emacs and scheme talk to each other https://jao.io/cgit/geiser/atom?h=0.33 2024-07-06T15:37:23Z 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. 2022-12-05T14:17:55Z Jonas Bernoulli jonas@bernoul.li 2022-12-05T14:17:55Z urn:sha1:a60efa80cdb8c72dacb1e16729a801206a4e80bf 2022-10-13T01:59:07Z jao jao@gnu.org 2022-10-13T01:59:07Z urn:sha1:52ae251eb6ec868890a38564e462fdea69a70ee0 2022-04-23T18:05:57Z jao jao@gnu.org 2022-04-23T18:05:57Z urn:sha1:1b1fdd2be47fcbadab4b224266d30dee4484a4b0 2022-04-23T15:01:15Z Daniel Mendler mail@daniel-mendler.de 2022-04-02T00:19:54Z urn:sha1:18faa0ba32c9ce751c16960b2a39b3880b523272 NOTE: The patch is largely untested. Modifications: - Update readme.org - Remove geiser-company - Move Company extensions to geiser-completion Omissions: - geiser-company--inhibit-autodoc has been removed. Eldoc handling should be implemented in the frontend, not in the backend. See for example: https://github.com/minad/corfu/blob/04fbfce3d7e9c125a7fd22a34455a508247a522b/corfu.el#L1212 - The quickhelp-string action and geiser-company--docstring have been removed. company-quickhelp can use `:company-doc-buffer` instead with minimal overhead. See: https://github.com/company-mode/company-quickhelp/blob/3ca2708b4e5190205aca01d65fe1b391963a53f9/company-quickhelp.el#L138 - The automatic Company setup has been removed. Personally I am not a fan of such auto configuration. It is better if completion is configured consistently in the user configuration. You may want to restore the auto configuration for backward compatibility. It depends on your backward compatibility story. I am fine with rare breaking changes from time to time. - There is a cyclic dependency between geiser-edit/geiser-doc and geiser-completion, which should be untangled. 2021-12-22T02:02:18Z jao jao@gnu.org 2021-12-22T02:02:18Z urn:sha1:2230f8e1c68697bd09619071a45b8438eacbc4e4 2021-12-03T03:29:08Z jao jao@gnu.org 2021-12-03T03:29:08Z urn:sha1:8c2fcf6b8a072f6fe896178747119766c6609dd0 It seems we were abusing comint-dynamic-complete-filename when there's the perfectly fine comint-filename-completion. 2021-04-21T19:38:40Z Jonas Bernoulli jonas@bernoul.li 2021-04-21T18:54:12Z urn:sha1:2b45bd368b4acbcef53c3c761725241fb6846102 It is available since Emacs 24.3 and we already depend on Emacs 24.4. 2020-05-10T16:28:00Z Jose Antonio Ortega Ruiz jao@gnu.org 2020-05-10T16:28:00Z urn:sha1:c25a0562962c0f4dfbdc81b4662609f7df715b98 Restoring what seem reasonable definitions for the completion functions when called away from the current buffer. Should fix issue 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.