emacs and scheme talk to each other https://jao.io/cgit/geiser/atom?h=0.33 2026-05-02T23:08:05Z 2026-05-02T23:08:05Z jao jao@gnu.org 2026-05-02T23:08:05Z urn:sha1:55b4b7847902d626a76e110a862d0fde1d1ff297 2025-08-10T03:08:52Z jao jao@gnu.org 2025-08-10T03:08:52Z urn:sha1:9e76f336b91151315642de9bcbed0ffe83b69db7 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-09-01T19:54:11Z jao jao@gnu.org 2024-09-01T19:54:11Z urn:sha1:c034c129cfa7442881f13ae146c87785b367cff5 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:27:28Z urn:sha1:b57fdc8fde91734b34b7ad1c2f1a06b46a1f5822 This makes it possible to `eval-buffer' the buffer defining this constant. Not that doing so makes all that much sense, but I tried doing it before reading its content, because generally speaking that is a sensible thing to do, at least for someone working on the code. 2024-05-23T00:33:47Z jao jao@gnu.org 2024-05-23T00:33:47Z urn:sha1:b6b4ac070d136345345c80ff649f0084e3c512a5 2024-02-08T00:26:36Z jao jao@gnu.org 2024-02-08T00:26:36Z urn:sha1:4e64934bd2ae7c6f0e4acb9f2ed017844c187223 Fixes issue #20 2024-01-13T20:47:26Z jao jao@gnu.org 2024-01-13T20:47:26Z urn:sha1:d25b2a3e176fb1a8dade23e2e827f774e3599a8c 2023-12-15T21:48:49Z jao jao@gnu.org 2023-12-15T21:48:49Z urn:sha1:f343592a52da0f947989d07c208a51ad6c972a5e