emacs and scheme talk to each other https://jao.io/cgit/geiser/atom?h=0.33 2025-01-05T15:30:41Z 2025-01-05T15:30:41Z jao jao@gnu.org 2025-01-05T15:30:41Z urn:sha1:dcded86fca731969fece47d57ce90d90e0fe701a This reverts commit 67f727855895050aca3bcf37066e804dc8f307de. While the rationale is sound, it prevents simpler uses of geiser.el to run the package without having to install it. Fixes #70 2024-07-06T15:37:23Z Jonas Bernoulli jonas@bernoul.li 2022-07-14T14:06:12Z urn:sha1:67f727855895050aca3bcf37066e804dc8f307de - Avoid defining autoload definitions in a central location. Instead add autoload cookies to the forms/definitions that should be autoloaded, in the locations where the actual definitions are located. - Do this for `geiser-mode', `turn-on-geiser-mode', `geiser-mode--maybe-activate' (including adding that to `scheme-mode-hook'), `geiser', `geiser-connect', `geiser-connect-local' and `geiser-repl-switch'. - Also do this for `run-geiser', even though it is only an obsolete function alias for `geiser', which might make it desirable to drop the autoload altogether. Some unusual autoload definitions remain in "geiser.el", see below. - One issue with defining autoloads in a central location is that it is easy to forget to remove such autoloads when the real definition is removed. No longer autoload `geiser-version' because since [1: 847d2ad] there no longer exists a proper definition of that function. - No longer autoload `geiser-unload', `geiser-reload' and `turn-off-geiser-mode', because they are only useful if Geiser has already been loaded, at which point any autoloaded definitions are no longer relevant. However, - Keep autoloading `geiser-activate-implementation' and `geiser-implementation-extension', even though I doubt that this is actually useful. - Keep using `custom-add-load' to specify dependencies of Custom groups and keep autoloading that. I don't know if this is actually necessary, and while it seems really weird, it might served a legit purpose, that I am not aware of. 1: 2020-07-19 847d2ad4c6da462c26c50af1ef7d9cd697f3a5d2 scheme and autotools removals 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-14T14:20:48Z urn:sha1:9197acbdbde392fc53ad0f2be2cef83e452f1d28 Defining it as a macro, as it was done from the start, is just weird. 2024-01-13T20:47:26Z jao jao@gnu.org 2024-01-13T20:47:26Z urn:sha1:d25b2a3e176fb1a8dade23e2e827f774e3599a8c 2022-10-16T01:59:54Z jao jao@gnu.org 2022-10-16T01:59:54Z urn:sha1:c437b1eca906f9c06eb5acef49f84bc4a87d2b8b same code that finds putative definitions, with all its caveats 2022-10-15T16:01:04Z jao jao@gnu.org 2022-10-15T15:58:18Z urn:sha1:b64ee5b8a984e06aae29b8a92362a6db03cfed3b we already had our own lighter mechanism, just needed to use it better. it will also allow guessing local signatures, quite useful in chezzy (or more generally r6rs-librarish) schemes. 2022-10-12T02:37:56Z jao jao@gnu.org 2022-10-12T02:37:56Z urn:sha1:a9b17f08a0c40d2b2ac5d3d130a8b40f5890ccfa ... as well as a way of telling imenu to look for nested define forms, as the ones one finds for instance inside (library ...) or (module ...) sexps, or simply nested defines in function bodies. it's a crappy way of finding definitions, but it's better than nothing when it's all we have (e.g., R6RS libraries don't seem to provide an environment/namespace including their privates, which is a killjoy). 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.