Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-11-27 | version bump0.28.1 | jao | |
2022-11-26 | Make geiser-activate-implementation a defun to fix autoloading. | Matt Armstrong | |
See issue #47. | |||
2022-11-26 | Remove duplicate 'geiser autoload. | Matt Armstrong | |
2022-11-15 | spurious transient require | jao | |
2022-11-04 | version bump0.28 | jao | |
2022-11-01 | requiring subr-x at compile time for older emacsen | jao | |
2022-10-29 | geiser-doc: support for elisp-cooked docstrings | jao | |
2022-10-24 | geiser-debug: ensure next-error buffer and buttonize output | jao | |
2022-10-24 | geiser-xref: lexical binding | jao | |
2022-10-22 | debugging commands up to the specific scheme implementation | jao | |
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. | |||
2022-10-21 | nit: skip eval requests of empty strings | jao | |
2022-10-21 | fix: long standing bug in regexp recognising columns in error links | jao | |
2022-10-21 | debug: accept debug msg of any type (e.g., a list with location info) | jao | |
2022-10-21 | geiser-debug--debugger-active-p -> geiser-debug--debugger-active | jao | |
2022-10-21 | more tweaks to regexp signature finding | jao | |
and its use in autodoc (for instance, skip it when in the REPL). | |||
2022-10-19 | geiser-doc: untabbify and lexical binding | jao | |
2022-10-16 | fix: don't signal an error when we find module as an alternative | jao | |
2022-10-16 | better error when we fail in edit symbol at point | jao | |
2022-10-16 | fun with regular expressions for definitions fallback | jao | |
2022-10-16 | fix for autodoc, ahem, extension | jao | |
2022-10-16 | e320b982 wasn't a good idea, and lexical-binding for geiser-syntax | jao | |
2022-10-16 | fix: restore looking for module if symbol's not there | jao | |
2022-10-16 | little tweak to regexp definitions | jao | |
it's a bit of a mess and should be using the syntax reader instead, but not sure if it's worth it. | |||
2022-10-16 | fallback autodoc inferred via cheap regexps | jao | |
same code that finds putative definitions, with all its caveats | |||
2022-10-15 | little fix: duplicated first symbol in autodoc requests | jao | |
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. | |||
2022-10-15 | local definition discovery sans imenu | jao | |
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. | |||
2022-10-15 | news and version bump0.27 | jao | |
2022-10-14 | fix: marker stack for jump to module | jao | |
2022-10-13 | expect completion-in-region functions to preserve current buffer | jao | |
see discussion in issue #56 | |||
2022-10-13 | fixes for the imenu jumping fallback | jao | |
2022-10-13 | lexical scope for completion and connection | jao | |
2022-10-13 | autodoc: correctly display docsigs for in-region completions (#56) | jao | |
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. | |||
2022-10-12 | imenu as a last resort for jumping to definition | jao | |
... 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). | |||
2022-10-10 | jump to location specified as a char pos | jao | |
Chez likes to do that, which is fine now. | |||
2022-10-10 | fix for completion-for-module | jao | |
We were calling an undefined function... not too many people using the functionality (or geiser at all :)). | |||
2022-10-09 | fix: proper use of the error reporting protocol | jao | |
... 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). | |||
2022-10-08 | More -p obsolescence in geiser-debug.el | jao | |
2022-10-08 | geiser-log clean-ups | jao | |
- 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 | |||
2022-10-07 | Fix for "and-go" command variants | jao | |
Should address issue #55 for all implementations. | |||
2022-09-17 | Fix for autodoc in geiser-capf--company-docsig and beyond | jao | |
Thanks to Panagiotis Vlantis, see issue #54 | |||
2022-09-06 | reinstating run-geiser alias (for now!)0.26.1 | jao | |
2022-09-02 | undeclared function moved around | jao | |
2022-09-01 | Improve default names for per-project REPLs. | David Thompson | |
2022-08-25 | Version bump0.26 | jao | |
2022-08-25 | archaeology | jao | |
2022-08-25 | run-geiser obsoleted (just use M-x geiser) | jao | |
2022-08-25 | New geiser-repl-switch[-to-module] obsoleting switch-to-geiser[module] | jao | |
2022-08-24 | docstring for geiser-repl-maybe-send | jao | |
2022-08-24 | Make geiser-repl--maybe-send into a public function | Brian Leung | |
Some authors of downstream packages are reluctant to do stuff with upstream packages' private functions. (for example, https://github.com/abo-abo/swiper/pull/2235#issuecomment-537399457) | |||
2022-08-23 | Interactive REPL start in C-c C-k and C-c C-l | jao | |
Should address, sort of, issue #46 |