| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-05-23 | changelog and version bump0.31 | jao | |
| 2024-02-08 | geiser-edit: new customization group | jao | |
| Fixes issue #20 | |||
| 2024-01-13 | non-existent geiser-version removed from autoloads (fixes #64) | jao | |
| 2023-12-15 | version bump and changelog0.30 | jao | |
| 2023-08-06 | new version: require emacs 27.10.29.1 | jao | |
| 2023-07-19 | version bump0.29 | jao | |
| 2022-12-25 | version bump0.28.2 | jao | |
| 2022-11-30 | make autoloads more lazy (Stefan Monnier) | jao | |
| 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-<impl>-autoloads.el. | |||
| 2022-11-27 | version bump0.28.1 | jao | |
| 2022-11-26 | Remove duplicate 'geiser autoload. | Matt Armstrong | |
| 2022-11-04 | version bump0.28 | jao | |
| 2022-10-22 | debugging commands up to the specific scheme implementation | jao | |
| the half backed attempt at standardising guile's model won't work well with other schemes, and it's not really well thought-out anyway: let's guile do its thing, and we'll see what we can do in chez. | |||
| 2022-10-15 | news and version bump0.27 | jao | |
| 2022-09-06 | reinstating run-geiser alias (for now!)0.26.1 | jao | |
| 2022-08-25 | Version bump0.26 | jao | |
| 2022-08-25 | run-geiser obsoleted (just use M-x geiser) | jao | |
| 2022-08-25 | New geiser-repl-switch[-to-module] obsoleting switch-to-geiser[module] | jao | |
| 2022-08-21 | Version bump0.25.1 | jao | |
| 2022-08-21 | Version bump0.25 | jao | |
| 2022-05-07 | Version bump0.24 | jao | |
| 2022-04-10 | autodoc: make do without dependending on elpa's eldoc | jao | |
| Playing the trick of checking for eldoc-documentation-functions to know wheter we're at a new enough version, and (hopefully) falling back to the old implementation otherwise. | |||
| 2022-04-10 | autodoc: new-style eldoc interface | jao | |
| We remove by-now obsolete usage of eldoc, and depend on the elpa package to ensure backwards compatibility. | |||
| 2022-03-23 | Missing version tag, and version bumped0.23.2 | jao | |
| 2022-03-09 | Version bump0.23 | jao | |
| 2022-03-06 | Actually depend on project.el! | jao | |
| 2022-02-03 | Version bump0.22.2 | jao | |
| 2022-01-23 | Version bump0.22.1 | jao | |
| 2021-12-29 | Version bump0.22 | jao | |
| 2021-12-22 | Version bump0.21async | jao | |
| 2021-12-20 | Version bump0.20.1 | jao | |
| 2021-12-19 | Requiring Emacs 25.1, for transient's sake | jao | |
| 2021-12-19 | Docs, news and version | jao | |
| 2021-12-04 | Version bump (0.19)0.19 | jao | |
| 2021-10-03 | Version bump (0.18)0.18 | jao | |
| 2021-08-08 | Version bump (0.17)0.17 | jao | |
| 2021-04-21 | Version bump0.16 | jao | |
| 2021-04-16 | Version bump (0.15)0.15 | jao | |
| 2021-04-16 | New public api for registering file extensions | jao | |
| 2021-04-09 | Version bump (0.14) | jao | |
| 2021-04-05 | autoload geiser activate implementation0.14 | jao | |
| 2021-04-04 | duplicated commetary section gone | jao | |
| 2021-04-04 | proper ELPA header for geiser.el | jao | |
| 2021-04-04 | empty geiser-active-implementations | jao | |
| 2021-04-04 | geiser.el: autoloads removed | jao | |
| 2020-07-19 | the long road to doc updates starts with one commit | jao | |
| 2020-07-19 | scheme and autotools removals | jao | |
| The plan is to have geiser-core contain only, well, the elisp core engine. The autotools scafolding is no really worth it, so it's gone too (and in the process, i'll look younger). | |||
| 2020-03-27 | Fix indentation | Jonas Bernoulli | |
| 2020-03-27 | Mark the beginning of code part of elisp libraries with Code: heading | Jonas Bernoulli | |
| 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-08-20 | add top level functions | mathieu2em | |
| 2018-04-14 | Adding proper entries to load-path (fixes #246) | Jose Antonio Ortega Ruiz | |
| And we also take the chance to let add-to-list do its job of not adding duplicates. | |||
 |
index : geiser | |
| emacs and scheme talk to each other | jao |
| summaryrefslogtreecommitdiff |