| Age | Commit message (Collapse) | Author |
|---|
|
Warning: ‘backward-delete-char’ is for interactive use only;
use ‘delete-char’ instead.
|
|
"geiser-repl-autoeval-delay" should be "geiser-repl-autoeval-mode-delay".
|
|
Disabled by default. Adds new custom variables
"geiser-repl-autoeval-mode-delay" and "geiser-repl-autoeval-mode-p".
|
|
|
|
Fixes #60, as diagnosed and solved by Fabian Brosda: if an implementation is
fast enough, new evaluations can override the result of eval/wait before it is
used (this seems to be the case during completion).
|
|
Should provide a better fix for extended issue #58.
|
|
This should take care of the problem reported in issue #58.
|
|
* geiser-compile-file
* geiser-compile-current-buffer
* geiser-load-current-buffer
* geiser-add-to-load-path
|
|
|
|
Fixes #57.
|
|
|
|
Thanks to Stefan's patience and actual implementation, we now don't load all
of geiser-impl.el and its dependencies just because there's a call
geiser-activate-implementation in geiser-<impl>-autoloads.el.
|
|
|
|
See issue #47.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the half backed attempt at standardising guile's model won't work well with
other schemes, and it's not really well thought-out anyway: let's guile do its
thing, and we'll see what we can do in chez.
|
|
|
|
|
|
|
|
|
|
and its use in autodoc (for instance, skip it when in the REPL).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it's a bit of a mess and should be using the syntax reader instead, but not
sure if it's worth it.
|
|
same code that finds putative definitions, with all its caveats
|
|
i think we've been sending twice the symbol at point in ge:autodoc's list of
paths since the beginning of time; not that it'll make a noticeable
difference, but let's not.
|
|
we already had our own lighter mechanism, just needed to use it better. it
will also allow guessing local signatures, quite useful in chezzy (or more
generally r6rs-librarish) schemes.
|
|
|
|
|
|
see discussion in issue #56
|
|
|
|
|
|
we were doing it really wrong: first, by not setting the evaluation
environment when things are computed outside the original buffer (the
completion in region case for consult and the likes, where the current buffer
is the minibuffer) and, to add insult to injury, by not waiting for a response
from the scheme side!
actually waiting can make things a tad laggy when the scheme is not as fast
as, say, chez and there are lots of completions (if one uses
completion-in-region; for pop ups like company it's fine), so i've also added
a flag, geiser-autodoc-use-docsig, to turn the functionality off.
|
|
... as well as a way of telling imenu to look for nested define forms, as the
ones one finds for instance inside (library ...) or (module ...) sexps, or
simply nested defines in function bodies. it's a crappy way of finding
definitions, but it's better than nothing when it's all we have (e.g., R6RS
libraries don't seem to provide an environment/namespace including their
privates, which is a killjoy).
|
|
Chez likes to do that, which is fine now.
|
|
We were calling an undefined function... not too many people using the
functionality (or geiser at all :)).
|
|
... even if that protocol is unwritten (note to self: write it already) and
nobody till now was being a good citizen (chez is becoming one).
|
|
|
|
- geiser-log: Obsoleting some -p flags and lexical binding
- geiser-eval: Ensuring logs for asynchronous retorts
- geiser-debug: don't bail on no output with errors
|
