geiser/elisp/geiser-impl.el, branch 0.33

whitespace

2025-01-05T15:33:20Z

Revert "Define autoloads how that is normally done"

2025-01-05T15:30:41Z

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

Define autoloads how that is normally done

2024-07-06T15:37:23Z

- 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

Cleanup library headers

2024-07-06T15:37:23Z

- 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.

make autoloads more lazy (Stefan Monnier)

2022-11-30T13:33:43Z

Thanks to Stefan's patience and actual implementation, we now don't load all of geiser-impl.el and its dependencies just because there's a call geiser-activate-implementation in geiser--autoloads.el.

Make geiser-activate-implementation a defun to fix autoloading.

2022-11-26T22:50:48Z

See issue #47.

run-geiser obsoleted (just use M-x geiser)

2022-08-25T00:46:42Z

New geiser-repl-switch[-to-module] obsoleting switch-to-geiser[module]

2022-08-25T00:20:19Z

Back to using a real lambda value rather than a list

2022-01-28T22:58:54Z

Thanks again to Stefan for a useful discussion.

geiser-impl--normalize-method: quick fix for previous change

2022-01-28T19:47:36Z

I haven't fully understood why, the two versions seem at first sight equivalent, but they're not behaving equivalently.