summaryrefslogtreecommitdiff
path: root/elisp/geiser-debug.el
AgeCommit message (Collapse)Author
2021-12-29New function geiser-eval-region/waitjao
2021-12-20Asynchronous, interruptable evaluationsjao
2021-12-20Better handling of (:debug) evaluationsjao
2021-12-19Tweaks to geiser-debug-mode keymapjao
2021-12-19New debugger commands: locals, registers, errorjao
2021-12-19Debugger: fixes and better determination of debugging statusjao
2021-12-18'debug commands so that each impl can take care of themjao
2021-12-18Allowing debuggers to use Dbg buffer for outputjao
2021-11-27Customizable next-error on evaluation errorsjao
Set to nil by default, which might surprise some users, if we had enough :)
2021-11-20Fix: allow implementations to tell us if they entered their debuggerjao
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-04-19Fix for the fix (avoid popping up on empty output strings)jao
2021-04-19Fix for output display in schemes not defining their own handlerjao
See discussion in issue #21.
2021-04-11Fix for ANSI color treatmentsjao
2021-04-09cl-case with an eval-when-compilejao
2021-04-09Optionally treat ANSI colors in dbg bufferjao
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).
2020-12-02Improve doc-strings of some optionsJonas 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-02Placate byte compiler (Brian Leung)jao
2020-07-12Always display error in minibuffer after evalAaron 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-04-06Chop off trailing whitespace before printing REPL resultPhilip K
2020-03-27Fix indentationJonas Bernoulli
2020-03-27Mark the beginning of code part of elisp libraries with Code: headingJonas 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-02-13Proper wrapping of final comment lines (fixes #292)Jose Antonio Ortega Ruiz
Thanks a lot Sean Delvin for a great bug report which, moreover, contained the solution to the problem! (even though i'm risking a small modification).
2016-06-11Cleanups to the show/jump debug buffer messJose Antonio Ortega Ruiz
Let's see if i finally got this right...
2016-05-29Fixes for geiser-debug-jump-to-debug-p and geiser-debug-show-debug-pJose Antonio Ortega Ruiz
I wonder if this has ever worked fine: geiser-debug--display-retort was a little mess. It should be a bit better now, but Guile is still displaying funny messages.
2016-04-23Define 'geiser-debug-mode' with 'define-derived-mode'Alex Kost
2015-10-12Keeping the elisp compiler happyJose Antonio Ortega Ruiz
Mainly by reordering definitions so that functions are not used before defined. There are a couple of places where the compiler and I disagree (it complains withing eval-after-load), and a valid complain about functions defined via geiser-popup--define that should be addressed).
2014-05-31Finer control of debugging window popupsJose Antonio Ortega Ruiz
It's now possible to control whether we jump to the debug window on evaluation errors (geiser-debug-jump-to-debug-p) and whether we show it all (geiser-debug-show-debug-p).
2013-04-12Simplifications to previous patchJose Antonio Ortega Ruiz
2013-04-12Evaluate last expression to buffer with a prefixDiogo F. S. Ramos
Use a prefix before pressing C-x C-e to print the result of evaluating the expression before mark to the current buffer.
2012-10-11WhitespaceJose Antonio Ortega Ruiz
2012-09-02racket: displaying images also during evaluationsJose Antonio Ortega Ruiz
2011-11-26Racket: capturing and displaying standard error during evaluationJose Antonio Ortega Ruiz
This bugs was exposed by using rackunit, where all the output of, say, check-eq? was lost for good (it was being sent to the stderr black hole). Hat tip Grant Retkke.
2010-12-28Bug fix for postfix error message display in debug bufferJose Antonio Ortega Ruiz
The message and the evaluated expression where getting mixed for Guile.
2010-12-28Finer grained maintenance of autodoc's cacheJose Antonio Ortega Ruiz
2010-12-11Make the position of long expressions in debug buffer customizableJose Antonio Ortega Ruiz
This is Emacs, after all.
2010-12-11Print long expressions after errors in debug buffer.Jose Antonio Ortega Ruiz
You won't believe it, but people write procedures spanning several pages, even in Scheme. Where's the art and the poetry of programming?
2010-10-30Elisp: more flexible parsing of :eval and :ge formsJose Antonio Ortega Ruiz
This allows the implementation decide the concrete structure of the code sent to the REPL. For instance, it doesn't need to be a single s-expression, and argument order can be re-arranged.
2010-10-16Bug fix: setting correct default-directory in debug buffersJose Antonio Ortega Ruiz
2010-09-07Make next-error (C-x `) work on debug buffersJose Antonio Ortega Ruiz
2010-09-07Support for evaluation warningsJose Antonio Ortega Ruiz
2010-09-06Autodoc: clean cache upon evaluationJose Antonio Ortega Ruiz
2010-07-25C-c z as a to and fro jump, plus documentation.Jose Antonio Ortega Ruiz
2010-06-15Menu for debug buffer.Jose Antonio Ortega Ruiz
2010-06-06Whitespace.Jose Antonio Ortega Ruiz
2010-06-05Racket: providing error contextsJose Antonio Ortega Ruiz
2010-03-27Automatically pop-up dbg buffer if there's any output during evaluation.Jose Antonio Ortega Ruiz
2010-03-08Hook to setup the debugger when it's launched.Jose Antonio Ortega Ruiz
2010-01-28Generic support for debugging prompts in the REPLJose Antonio Ortega Ruiz
2009-12-18Guile: bug in backtrace display fixed.Jose Antonio Ortega Ruiz
2009-09-22New implementation registration mechanism, for the elisp side of things.Jose Antonio Ortega Ruiz
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-01 13:30:18 +0000