| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  |  | 
|  |  | 
|  | * scheme/guile/geiser/doc.scm (obj-args): producing always ... for macros. | 
|  | * 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. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Definitions of the form (define (foo bar) (lambda ---) --) were not
being matched correctly. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | 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. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  |