summaryrefslogtreecommitdiff
path: root/elisp/geiser.el
AgeCommit message (Collapse)Author
2022-01-23Version bump0.22.1jao
2021-12-29Version bump0.22jao
2021-12-22Version bump0.21asyncjao
2021-12-20Version bump0.20.1jao
2021-12-19Requiring Emacs 25.1, for transient's sakejao
2021-12-19Docs, news and versionjao
2021-12-04Version bump (0.19)0.19jao
2021-10-03Version bump (0.18)0.18jao
2021-08-08Version bump (0.17)0.17jao
2021-04-21Version bump0.16jao
2021-04-16Version bump (0.15)0.15jao
2021-04-16New public api for registering file extensionsjao
2021-04-09Version bump (0.14)jao
2021-04-05autoload geiser activate implementation0.14jao
2021-04-04duplicated commetary section gonejao
2021-04-04proper ELPA header for geiser.eljao
2021-04-04empty geiser-active-implementationsjao
2021-04-04geiser.el: autoloads removedjao
2020-07-19the long road to doc updates starts with one commitjao
2020-07-19scheme and autotools removalsjao
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-27Fix indentationJonas Bernoulli
2020-03-27Mark the beginning of code part of elisp libraries with Code: headingJonas 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-20add top level functionsmathieu2em
2018-04-14Adding 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.
2016-09-06Add link to project homepageChunyang Xu
C-h P (`display-package') can make use of it.
2016-08-10Add chez, mit, and chibi to autoloadDan Leslie
2016-04-30Add chez to Makefile, add autoloads for chezPeter
2016-04-30Add chez to Makefile, add autoloads for chezPeter
2016-04-26Add preliminary support for MIT/GNU Scheme.Peter
2015-09-09WhitespaceJose Antonio Ortega Ruiz
2015-09-09Autoload geiser-connect-local as wellChristoph Egger
2015-02-09Documentation updates and nits for FreijaJose Antonio Ortega Ruiz
Preparing the release of 0.7, which will feature support for Chicken thanks to Dan and Freija!
2015-02-09Initial Chicken supportDan Leslie
2013-09-19Fix file headers and footer for ELPA compatibilitySteve Purcell
This will allow `package-buffer-info` to parse the description out of the file.
2013-09-19Missing autoload cookies for MELPAJose Antonio Ortega Ruiz
Everything in geiser.el needs one, so that the generated geiser-autoloads.el initializes variables and the like properly automatically.
2013-09-19Paving the way to MELPA (and simpler ELPA generation)Jose Antonio Ortega Ruiz
Following the discussion in GitHub, i'm adding an alternative scheme path to geiser.el as well as ##autoload cookies. As a first benefit, this simplifies a bit the elpa target, after playing a similar path trick in bin/geiser-racket.sh. Things should be almost ready for creating a MELPA recipe.
2012-09-30New make target, elpa, to create ELPA targetJose Antonio Ortega Ruiz
A bunch of shellish ops, but seems to be working fine.
2012-09-29Autoload cookies in geiser.elJose Antonio Ortega Ruiz
Useless there right now, but Emacs package engine is going to use them.
2012-09-02Image display functionality refactored to its own moduleJose Antonio Ortega Ruiz
2011-08-02elisp: add-hook doesn't need a defvared hookJose Antonio Ortega Ruiz
Thanks, Leo.
2010-12-18Missing autoload for connect-to-racketJose Antonio Ortega Ruiz
Maybe i should bite the bullet and use ##autoload cookies, but then geiser.el would need to be a generated file, breaking out-of-the-boxness (unless i update it by hand). Sticking to manual maintenance for now.
2010-12-11Make the position of long expressions in debug buffer customizableJose Antonio Ortega Ruiz
This is Emacs, after all.
2010-11-13geiser-mode-auto-p: automatic geiser-mode is now optionalJose Antonio Ortega Ruiz
It hadn't occurred to me that anyone wouldn't want non-automatic geiser-mode often enough to require its own customization variable. Rotty proved me wrong. Or maybe not, but he deserves a custom var!
2010-10-11Guile: remote REPLs (connect-to-guile)Jose Antonio Ortega Ruiz
geiser-connect (or its specialisation, connect-to-guile) working for Guile, where the external process is started with the new --listen flag.
2010-10-11Remote REPLs: elisp support (geiser-connect)Jose Antonio Ortega Ruiz
New user command geiser-connect, which will try to connect to a remote server and use it in the REPL.
2010-09-11Racket: support for gracket-textJose Antonio Ortega Ruiz
2010-09-06Allow loading byte-compiled Geiser without make installJose Antonio Ortega Ruiz
2010-05-24Racket: PLT implementation renamed to Racket.Jose Antonio Ortega Ruiz
2010-05-23Racket support (PLT 5 needed).Jose Antonio Ortega Ruiz
2009-09-22New implementation registration mechanism, for the elisp side of things.Jose Antonio Ortega Ruiz
Implementations must invoke define-geiser-implementation with an appropriate set of methods. Simple inheritance is supported. Each geiser module defines and registers the method names it uses.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 09:37:30 +0000