| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-11-20 | Fix: allow implementations to tell us if they entered their debugger | jao | |
| We were always displaying the debug buffer, regardless, which is not what we want: upon entering a debugger, we switch to the repl, and all the needed info is already there. | |||
| 2021-10-03 | Version bump (0.18)0.18 | jao | |
| 2021-08-08 | Version bump (0.17)0.17 | jao | |
| 2021-04-28 | There is no session (fixes #22) | jao | |
| 2021-04-21 | Use defvar-local | Jonas Bernoulli | |
| It is available since Emacs 24.3 and we already depend on Emacs 24.4. | |||
| 2021-04-21 | Version bump0.16 | jao | |
| 2021-04-19 | Fix for the fix (avoid popping up on empty output strings) | jao | |
| 2021-04-19 | Fix for output display in schemes not defining their own handler | jao | |
| See discussion in issue #21. | |||
| 2021-04-16 | Version bump (0.15)0.15 | jao | |
| 2021-04-16 | New public api for registering file extensions | jao | |
| 2021-04-16 | fix for doom emacs | Chris McClellen | |
| 2021-04-11 | Fix for ANSI color treatments | jao | |
| 2021-04-10 | autoload cookie for geiser-eval-load-path | jao | |
| 2021-04-10 | Simpler error reporting for symbol lookup failures | jao | |
| 2021-04-09 | cl-case with an eval-when-compile | jao | |
| 2021-04-09 | Optionally treat ANSI colors in dbg buffer | jao | |
| This is controlled by the new customizable variable geiser-debug-treat-ansi-colors, which can be set to either nil (do nothing), 'colors (fontify colors) or 'remove (just strip all ANSI codes). | |||
| 2021-04-09 | Version bump (0.14) | jao | |
| 2021-04-05 | autoload geiser activate implementation0.14 | jao | |
| 2021-04-04 | stale geiser-install references removed0.13 | jao | |
| 2021-04-04 | duplicated commetary section gone | jao | |
| 2021-04-04 | proper ELPA header for geiser.el | jao | |
| 2021-04-04 | empty geiser-active-implementations | jao | |
| 2021-04-04 | geiser.el: autoloads removed | jao | |
| 2021-03-07 | geiser-messages-mode: Don't quote lambda expressions | Jonas Bernoulli | |
| 2021-02-15 | Determine the display string of command key dynamically. | Zhu Zihao | |
| * elisp/geiser-repl.el(geiser-repl--sentinel): Use `substitute-command-keys'. | |||
| 2020-12-02 | Add doc-string to geiser-custom--defcustom | Jonas Bernoulli | |
| Also add a FIXME comment about how this macro isn't actually needed. | |||
| 2020-12-02 | Improve doc-strings of some options | Jonas Bernoulli | |
| The whole first sentence should fit on the first line. If that makes the line a bit long then that is unfortunate but better than wrapping it onto a new line. When wrapping onto a new line anyway then the second line should never be intended. When it can be avoided, then long first lines should be made shorter. | |||
| 2020-12-02 | Declare keymaps using defvar explicitly | Jonas Bernoulli | |
| This makes it possible to re-evaluate the containing buffers without user customizations being clobbered. | |||
| 2020-12-02 | Placate byte compiler (Brian Leung) | jao | |
| 2020-12-02 | Support buffer-local binary and arglist configuration | jao | |
| 2020-07-19 | the long road to doc updates starts with one commit | jao | |
| 2020-07-19 | scheme and autotools removals | jao | |
| The plan is to have geiser-core contain only, well, the elisp core engine. The autotools scafolding is no really worth it, so it's gone too (and in the process, i'll look younger). | |||
| 2020-07-12 | Always display error in minibuffer after eval | Aaron Marks | |
| When evaluating expressions in a Scheme buffer, display the error of an evaluation in the minibuffer regardless of whether `geiser-debug-show-debug-p` or `geiser-debug-jump-to-debug-p` are set or not. | |||
| 2020-07-06 | Tag project functions instead of overriding docs | Andrew Whatson | |
| 2020-07-06 | Fix byte-compiler warning | Andrew Whatson | |
| 2020-07-06 | Improve project function selection, make ignore default | Andrew Whatson | |
| 2020-07-06 | Refactor to make repl/impl proj argument optional | Andrew Whatson | |
| 2020-07-06 | Use a separate REPL instance per project | Andrew Whatson | |
| 2020-07-06 | Returning C-c k back to users, that key's theirs! | Jose Antonio Ortega Ruiz | |
| Should close issue #315, where it is pointed out that "sequences consisting of `C-c` and a letter (either upper or lower case) are reserved for users; they are the *only* sequences reserved for users, so do not block them." | |||
| 2020-05-10 | Better handcrafted reader, now with numbers! | Jose Antonio Ortega Ruiz | |
| For no good reason, we were transforming numbers in retorts to symbols and then failing to recognise things like line or column numbers there. The "fix" here only works for the intersection of numbers that are written in the same way in elisp and scheme; one day we'll find a situation where this doesn't cut it, but right now we only really use integers. | |||
| 2020-05-10 | Completion for vanilla users | Jose Antonio Ortega Ruiz | |
| Restoring what seem reasonable definitions for the completion functions when called away from the current buffer. Should fix issue | |||
| 2020-04-26 | Fix typos | Jonas Bernoulli | |
| 2020-04-06 | Chop off trailing whitespace before printing REPL result | Philip K | |
| 2020-03-27 | Use cl-lib instead of cl | Jonas Bernoulli | |
| Starting with Emacs 27 cl is fully deprecated, including at compile-time. | |||
| 2020-03-27 | Declare geiser-restart-repl in geiser-compile.el | Jonas Bernoulli | |
| 2020-03-27 | Fix indentation | Jonas Bernoulli | |
| 2020-03-27 | Mark the beginning of code part of elisp libraries with Code: heading | Jonas Bernoulli | |
| It's the convention and by following it we make a big step towards supporting outline navigation. The convention doesn't say much about what parts of the code are supposed to be part of that sections and what parts belong in a subsequent section. Here we put the `require' forms in this section and maybe some setup code, that's a popular approach. In most cases there was " " where we now insert "Code:". They both serve a similar purpose and we keep the former because some users depend on that for navigation. We even add this " " in libraries where it previously was missing. In some cases the permission statement was followed by a commentary, which obviously does not belong in the "Code:" section. In such cases add the conventional "Commentary:" section. | |||
| 2020-03-27 | Begin the summary lines of all elisp libraries with three semicolons | Jonas Bernoulli | |
| It's the convention and by following it we make a big step towards supporting outline navigation. | |||
| 2020-03-16 | define-geiser-implementation - un-unquote load-file-name | spellcard199 | |
| 2020-02-25 | Fix for misspelled geiser-completion-module-list-func (#271) | Jose Antonio Ortega Ruiz | |
 |
index : geiser | |
| emacs and scheme talk to each other | jao |
| summaryrefslogtreecommitdiff |