| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
* elisp/geiser-impl.el (with--geiser-implementation): macro was not
setting the implementation environment correctly.
|
|
|
|
|
|
|
|
|
|
|
|
This is useful when visiting a file that has not been loaded: the
evaluation namespace is provided by its #lang, if any.
While i was at it, i also refactored the mess in geiser:load-file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
or C-x C-e).
|
|
|
|
`read-from-string'.
|
|
|
|
geiser-reload.
|
|
|
|
|
|
|
|
|
|
|
|
active argument in autodoc.
|
|
Currently put to (let's hope, good) use for context parsing in autodoc
and locals discovery (internal defines are recognised now).
|
|
- The implementation is still buggy, though, because it uses the
elisp reader, which bails at some scheme syntaxes (e.g. chars)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
