summaryrefslogtreecommitdiff
path: root/elisp/geiser-reload.el
AgeCommit message (Collapse)Author
2022-04-23Suggestive patch for simplified completionDaniel Mendler
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.
2021-04-04stale geiser-install references removed0.13jao
2020-07-19the long road to doc updates starts with one commitjao
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.
2020-03-27Begin the summary lines of all elisp libraries with three semicolonsJonas Bernoulli
It's the convention and by following it we make a big step towards supporting outline navigation.
2014-10-06remove geiser-mode--maybe-activate from scheme-mode-hook on geiser-unloadHenry Till
2012-10-11WhitespaceJose Antonio Ortega Ruiz
2012-09-02Image display functionality refactored to its own moduleJose Antonio Ortega Ruiz
2010-11-11Partial work (connections working)Jose Antonio Ortega Ruiz
2010-09-06Allow loading byte-compiled Geiser without make installJose Antonio Ortega Ruiz
2010-09-06Bug fix: assign a default scheme to syntax hilighting bufferJose Antonio Ortega Ruiz
2010-09-06Autodoc: clean cache upon evaluationJose Antonio Ortega Ruiz
2010-06-14Generic support for menus.Jose Antonio Ortega Ruiz
2010-06-12New buttons (source, forward/backward) in document browser.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.
2009-09-11Reload: we now remember user customizations and restore them during ↵Jose Antonio Ortega Ruiz
geiser-reload.
2009-09-11BSD relicensing: elisp code.Jose Antonio Ortega Ruiz
2009-08-25Now this is cool: support for company mode.Jose Antonio Ortega Ruiz
2009-08-23geiser-reload works again (was broken for installed geiser).Jose Antonio Ortega Ruiz
2009-08-23Autotoolification.Jose Antonio Ortega Ruiz