| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  |  | 
|  | Since geiser-guile--startup is calling in the new buffer already, buffer-local
value of geiser-guile-warning-level had no effect.  Luckily the original buffer
is accessible using geiser-repl--last-scm-buffer, so we can let-bind the value
from it for the duration of geiser-guile-update-warning-level.
Fixes #45.
* geiser-guile.el (geiser-guile--startup): Let-bind geiser-guile-warning-level
before calling geiser-guile-update-warning-level. | 
|  | This commit adds support for processing texinfo in docstrings.  That allows
using texinfo in them while still having readable, nicely formatted plain text
representation in geiser-doc-symbol-at-point.
Fixes #43.
* geiser-guile.el (geiser-guile-doc-process-texinfo): New custom controlling the
behavior.
(geiser-guile-update-doc-process-texinfo): New procedure to apply change of the
controlling custom to a current REPL.
(geiser-guile--startup): Call it.
* geiser-guile.texi (Start up): Document the custom.
* src/geiser/doc.scm (%process-texinfo?): New variable.
(try-texinfo->plain-text): New procedure.
(docstring): Call it on doc iff doc. | 
|  |  | 
|  | Fixes issue #38 (use-modules not completed at buffers) by excluding trailing
parens from module name completion prefixes. Things could be better if geiser
detected that in, say
      (use-modules (ice-9 and|
one is still completing a module name (right now, it notices that `and' can be
completed as a procedure/macro name), but that has always been above module
name completion's paycheck. | 
|  |  | 
|  | At least Emacs 29's byte-compiler warns when you don't do it in this
order. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | using ideas and code from Christine Lemmer-Webber, see #25 for discussion. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | The -p suffix, meaning predicate, is meant for functions (which is what a
predicate is). | 
|  | Fixes #24 | 
|  | Fixes #22 | 
|  |  | 
|  |  | 
|  | program-arities is expected (in its only usage a few lines below its
definition) to return #f if program-address-range doesn't return anything
useful, and i was incorrectly using when instead of and for that. | 
|  | program-arities now returns an empty list if no arities information is found.
This fixes the bug that happens when calling, say, `(autodoc '(display))`,
which leads to following error:
```
scheme@(guile-user)> (autodoc '(display))
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
In procedure map: Wrong type argument: #<unspecified>
Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]> ,q
``` | 
|  | Fixes issue #18. | 
|  |  | 
|  |  | 
|  | Might help addressing #17 | 
|  |  | 
|  | See discussion in issue #13 | 
|  |  | 
|  |  | 
|  | It appears that the master branch of emacs does not load tramp by
default in some instances. That makes the `run-geiser` function fail,
as `tramp-tramp-file-p` is not defined. This patch makes it check
whether the tramp function was loaded before using it. | 
|  |  | 
|  |  | 
|  |  | 
|  | - correct process call (to check version of guile) to make sure that it's executed in the remote host
- implement `geiser-guile-ensure-scheme-dir` that will (somehow) make sure the scheme files that need sourcing will be available to remote process
- use `geiser-guile-ensure-scheme-dir` instead of `geiser-guile-scheme-dir` in the rest of the code
- cache the guile files being sourced in `geiser-guile-scheme-local-dir` ensure process is called in remote host | 
|  |  | 
|  |  | 
|  | And precludes cancellation of asynchronous evaluations. | 
|  |  | 
|  |  | 
|  | Fixes issue #5, and then more. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  |